Re: JavaXML.framework replacement
Re: JavaXML.framework replacement
- Subject: Re: JavaXML.framework replacement
- From: Ramsey Gurley <email@hidden>
- Date: Mon, 4 Oct 2010 10:10:53 -0400
On Oct 4, 2010, at 9:57 AM, Kieran Kelleher wrote:
Resurrecting an old thread since I am trying to understand my
options for moving to WO 5.4.3 quickly in active WO 5.3.3 projects
without disturbing old reliably working code that consumes
webservices with Axis 1.1 and uses SAX parsers for parsing these and
other XML data formats.........
1) David A. (or anyone that knows so I don't end up doing the same
research, trial and error that someone else has done), what are the
exact list of jars you used to replace JavaXML.framework?
2) Is there a different list of jars for replacing JavaXML in WO
5.4.3 and JavaXML in WO 5.3.3?
3) IIRC, JavaXML is included in new projects by default, and is on
the build path of many commonly used frameworks, even ERExtensions,
so isn't replacing it with something different risky since a
framework that has it in its build path _might_ be calling some API
that is not in your "replacement" collection of jars?
4) When Pierre made the statement below about Axis compatability,
(a) is he talking about compatability between Axis and the bundled
JavaXML framework *only*, OR is he talking about compatability
between Axis and code WebObjects appserver frameworks, and
(b) if the latter, is he talking specifically about compatability
with DirectToWebServices functionality?
DirectToWebServices in my experience is broken under 5.4.x. The
webservice assistant will not launch. I recall they required that the
D2WModel descended from D2WFastModel which made it incompatible with
ERD2W. Even attempting to launch it using vanilla WebObjects failed
for me.
That was over a year ago though. Perhaps I was doing something wrong
at the time, but I would be very wary of migrating a D2WS project from
5.3 to 5.4... if that is what you are trying to do.
Ramsey
Regards, Kieran
On Jul 2, 2009, at 1:30 PM, Mr. Pierre Frisch wrote:
JavaXML is a convenience so that you can deploy easily. there is no
specific WO code in there and it can easily be replaced by its
components. Be careful about Axis, WO 5.2.x works with Axis 1.0, WO
5.3.x with Axis 1.1 and WO 5.4.x with Axis 1.4. Any other
combination is known NOT to work without serious hacking.
Cheers
Pierre
--
Pierre Frisch
email@hidden
On Jul 1, 2009, at 5:52, Dov Rosenberg wrote:
We ended up doing exactly that. If you deploy your apps as a
servlet the
JavaXML framework is not even loaded by the servlet container
because it
contains servlet classes like HTTPRequest. The J2EE spec that any
jar that
contains those classes will be ignored by the classloader. Which
means all
of the other things that you thought you were using were also not
being
loaded from that jar.
Dov
On 7/1/09 8:48 AM, "David Avendasora" <email@hidden>
wrote:
Hi all,
I am trying to figure out the best way to replace any jars
required by
projects that in the past were provided by the JavaXML.framework.
Should I simply download the latest versions of the needed jars
from
their original sources and put them in my Libraries directory?
While I'm sure Maven would be a possible solution for this, right
now
I'm looking for the non-maven (Fluffy Bunny Layout) solution.
Thanks!
Dave
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden