Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
AFAIK, you cannot have two conflicting axis versions deployed in jboss at the same time. In theory you would need to scope your laszlo client in a seperate loader repository and set parent delegation to false. This would work if Axis did not do all sorts of funky things with static references to class loaders, etc - it just does not play nicely in server managed CL environments.
Starting from jboss-4.0.2, we moved the classes that WS4EE depends on from org.apache.axis to org.jboss.axis. So you should be able to deploy Axis to JBoss as part of your WS client.
Why do you prefer a Laszlo client over a WS4EE client?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3873739#3873739
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3873739