|
Good Morning everyone, We’ve installed the CF 7.01 upgrade
which includes axis 1.2.1 final – 2243 – cool… I’m compiling against the same jar…. Our application is trying to use axis/soap
to communicate the a web service (AmericaDirectConnector does this) At first I got a log4j class cast error –
I then deleted my existing log4.properties (configured for hibernate) And now am receiving the exception below…. Got any suggestions? Thanks in Advance…… (192.168.1.79-4) 07:49:35.698:
com.ezrez.util.exceptions.EzRezInternalException
at com.ezrez.util.JavaUtil.newInstance(JavaUtil.java:204)
at com.ezrez.ezrez.EzRezInstantiator.CrsConnector(EzRezInstantiator.java:535)
at com.ezrez.ezrez.EzRezInstantiator.RoomConnector(EzRezInstantiator.java:769)
at
com.ezrez.processors.RoomChoiceProcessor$NamedRoomSearchThread.createCrs(RoomChoiceProcessor.java:1159)
at com.ezrez.processors.RoomChoiceProcessor$RoomSearchThread.getAvailability(RoomChoiceProcessor.java:1052)
at
com.ezrez.processors.ChoiceProcessor$AvailabilityProcessor.run(ChoiceProcessor.java:487) Caused by:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.ezrez.util.JavaUtil.newInstance(JavaUtil.java:196)
... 5 more Caused by: java.lang.NoClassDefFoundError
at org.apache.axis.client.Service.getAxisClient(Service.java:143)
at org.apache.axis.client.Service.<init>(Service.java:152)
at
com.ezrez.crs.americadirect.wsdl.ws.ads.americantours.com.WebServiceSoapBindingImplServiceLocator.<init>(WebServiceSoapBindingImplServiceLocator.java:12)
at com.ezrez.crs.americadirect.AmericaDirectConnector.initialize(AmericaDirectConnector.java:275)
at
com.ezrez.crs.americadirect.AmericaDirectConnector.<init>(AmericaDirectConnector.java:233)
... 10 more (192.168.1.79-4) 07:49:35.698:
=========================roomChoiceProcessor.addException========================= (192.168.1.79-4) 07:49:35.699:
com.ezrez.util.exceptions.EzRezInternalException
at com.ezrez.util.JavaUtil.newInstance(JavaUtil.java:204)
at com.ezrez.ezrez.EzRezInstantiator.CrsConnector(EzRezInstantiator.java:535)
at com.ezrez.ezrez.EzRezInstantiator.RoomConnector(EzRezInstantiator.java:769)
at
com.ezrez.processors.RoomChoiceProcessor$NamedRoomSearchThread.createCrs(RoomChoiceProcessor.java:1159)
at com.ezrez.processors.RoomChoiceProcessor$RoomSearchThread.getAvailability(RoomChoiceProcessor.java:1052)
at
com.ezrez.processors.ChoiceProcessor$AvailabilityProcessor.run(ChoiceProcessor.java:487) Caused by:
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.ezrez.util.JavaUtil.newInstance(JavaUtil.java:196)
... 5 more Caused by: java.lang.NoClassDefFoundError
at org.apache.axis.client.Service.getAxisClient(Service.java:143)
at org.apache.axis.client.Service.<init>(Service.java:152)
at
com.ezrez.crs.americadirect.wsdl.ws.ads.americantours.com.WebServiceSoapBindingImplServiceLocator.<init>(WebServiceSoapBindingImplServiceLocator.java:12)
at
com.ezrez.crs.americadirect.AmericaDirectConnector.initialize(AmericaDirectConnector.java:275)
at
com.ezrez.crs.americadirect.AmericaDirectConnector.<init>(AmericaDirectConnector.java:233)
... 10 more From: Tom Jordahl
[mailto:[EMAIL PROTECTED] Hi Kurt, My mistake, we did ship CFMX 7 with 1.2RC2
+ fixes. The upcoming (free) update for CFMX 7 will include 1.2.1 (the
actual release binary). Expect this to be available very soon
(days). You notes about compatibility are well taken.
>From a product perspective, Axis 1.1 -> 1.2 was NOT a smooth
transition. We waited too long to release, and changed too many things to
make it ‘better’, breaking lots of stuff (arrays, soapenc vs. XSD
types, etc). Still, I think that it is the best Java SOAP stack
available, particularly if you need WSDL2Java and Java2WSDL functionality
(which CF uses extensively). Note that in ColdFusion MX 7, you can
package your application as an ear/war file - with the CFML compiled to
bytecode - which *is* a J2EE
application. It just happens to include the CF runtime. We did this
specifically so customers won’t have to “defend” ColdFusion. -- From: Kurt Olsen
[mailto:[EMAIL PROTECTED] Hello Tom, thanks for responding… We’re gonna be keeping cf for
some of our admin tasks but the main ‘app’ is going j2ee. The reason we’re moving away is
‘industry perception’ – We have a pretty intense travel
application, and apparently the powers that be are getting tired of defending
coldfusion….Which is unfortunate, because I’ve seen one of our
co-founders do things in coldfusion so quickly that it’s stunning. Really
complicated things can be done very quickly and it’s a shame. But we
can’t change what the customers think, rightly or wrongly. Regarding axis in CF: I noticed that the
axis is 1.2.1RC2, but the manifest file in the axis.jar indicates a date in
December, while the ‘official’ RC2 (as near as I can tell) is dated
a month earlier in November. I tried doing elective surgery on the system,
namely tring to copy the axis files from CF into our development environment
but because 1. cf didn’t include axis-ant.jar and 2. The cf/rc2 version
of axis didn’t seem to be compatible with the ‘official rc2’
version of ant-jar. I also tried copying 1.2.1 final into
coldfusion’s lib dir (after backing it up) but that didn’t work
either, although the problem is looking like a classloading issue among axis,
log4j and our jars. Argh……. So, As soon as I put out a couple
brushfires (cruisecontrol is down and demanding attention) I”ll capture
some exceptions so you can see what I mean. Again, thanx, and email me at [EMAIL PROTECTED] when you get a chance. Kurt From: Tom Jordahl
[mailto:[EMAIL PROTECTED] Note that the latest version of ColdFusion
MX (7) has the latest version of Axis (1.2.1). The previous version of ColdFusion MX
(6.1) has the previous release of Axis - 1.1. I would also be very interested in what
problems you have encountered, and how you expect other web service stacks to
avoid them. Speaking as a Macromedia employee, why are
you moving away from CF? -- From: Kurt Olsen
[mailto:[EMAIL PROTECTED] Hi Folks, As you continue axis development I wanted to share the
experience the developers at our co. are having with axis. We’re sorry to report that even though axis is a powertool,
and we like it – we are about ‘’ that close to abandoning it
when communicating with soap services due to compatability issues when doing
system upgrades etc. For a long time our application server was/is coldfusion,
which includes axis. We are in the process of migrating off of coldfusion into
a jboss environment but we’re moving the server side code first, and
before long we’ll be completely off of coldfusion. Meanwhile, every time we have to go thru a systems evolution
we have to fight, and fight hard with the axis stuff. All manner of incompatability problems. I know there
aren’t easy solutions to this kind of thing but there it is. Out of the 20 something jars scattered about in our system
the majority of them interoperate/upgrade with few or no difficultions. Axis unfortunately stands out as something that keeps biting
back, and ends up causing us a lot of difficulty when things change. None of us here is an axis expert per-se, we just want to
use it to make our lives easier, but these compatability issues have irritated
most everyone here, and we’ve been yanking axis out of the
system….. This isn’t meant as a criticism per-se, but hopefully
this feedback from the field can be used when going forward with your
development. Thanks for listening, Kurt |
