I'm using the default conf in Jboss 4.0.2 (OS X 10.4.5) and am trying to access
the paypals webservice. From earlier replies here it seems i'm having an axis
issue as well. What do I need to do to resolve this?
anonymous wrote :
| 09:20:51,610 WARN [EngineConfigurationFactoryFinder] Factory
If I add jboss-net-client.jar to the classpath I get the following error logs:
anonymous wrote :
| 12:46:08,772 WARN [EngineConfigurationFactoryFinder] Factory
org.apache.axis.configuration.EngineConfigurationFactoryServlet Ignored:
missing required method: public static
What libraries are you using to generate your java classes? Your 4.0.2 log
snip with org.apache.axis indicates that you've used a different version of
axis than the one packaged with jboss 4.0.2.
Have a look in jboss/server/default/deploy/jboss-ws4ee.sar for the axis
libraries to use with
I'm using default conf from jboss 4.0.2.
I'm trying to access a .net webservice with java classes generated with
WSDL2Java.
I've created a simple java test class that I can run from eclipse to try the
webservice which works.
I have a j2ee application with a service that is trying to use the
Thanks to Jason for locating the relevant change that happened in CVS.
http://marc.theaimsgroup.com/?l=jboss-cvs-commitsm=109863231314461w=2
Something is messed up in your distribution of 4.0.2 If ever there was such
issues, our testsuite would have caught it. Is it possbile to start fresh
I can appreciate that, Anil. Speaking of stack traces...
Using a default jboss configuration, I have an issue currently that a web
service which we used before (JBoss 4.0.1sp1) will now puke an exception as
follows:
|org.jboss.axis.ConfigurationException:
client/jboss-ws4ee-client.jar
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3877714#3877714
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3877714
---
This SF.Net email
Ah, see that's the point. jboss-ws4ee-client.jar has this class
org.jboss.webservice.handler.ClientLoginHandler
which is not the same as
org.jboss.webservice.client.ClientLoginHandler
The latter class is the cause of the problem. Why is this older class still
being called and how can I fix
You're missing a library for org.jboss.net client classes. Look in
JBOSS_HOME/docs/examples/jboss.net/ directory and add the jboss-net-client.jar
file to you classpath. I just copy it into my server configuration's lib
directory.
So if you're running your server in the all configuration,
Tyler Black wrote : In JBoss 4.0.2 they have repacked things to be
org.jboss.axis. I'm working on issues that this causes right now. What fun!
Hey, we had to repackage it keeping customers like you in mind. Whenever you
post a stacktrace involving axis, now we can know whether the user is
10 matches
Mail list logo