This content has been marked as final.
Show 2 replies
-
1. Re: org.apache.axis --> org.jboss.axis issue!
beyarecords Feb 25, 2006 7:16 PM (in response to beyarecords)"beyarecords" wrote:
Hi,
as org.apache.axis is no longer supported, i'm running Jboss 4.0.2 (OS X), could someone please tell me what has become of:
import org.apache.axis.message.MessageElement;
import org.apache.axis.message.PrefixedQName;
import org.apache.axis.message.SOAPHeaderElement;
I changed them to:
import org.jboss.axis.message.MessageElement;
import org.jboss.axis.message.PrefixedQName;
import org.jboss.axis.message.SOAPHeaderElement;
but am issued an 'cannot be resolved' message by my eclipse IDE.
many thanks
Andrew
Ok,
so far I have discovered that:
1. PrefixedQName.java (deleted)
with the advie to synchronise with JB401.
2. SOAPHeaderElement resided in either
a. SOAPHeaderElementAxisImpl.java (deleted)
b. SOAPHeaderElementImpl.java (deleted)
c. SOAPHeaderImpl.java (deleted)
with the advice to use axis-ws4ee.jar. I have done this, but still no joy
3. MessageElement I have been unable to find out anything about.
So, any ideas anyone....PLEASE!!!
Andrew
P.S. All information was gleaned from http://anoncvs.forge.jboss.com/viewrep/JBoss/jaxrpc/src/main/org/apache/axis/message -
2. Re: org.apache.axis --> org.jboss.axis issue!
thomas.diesler Mar 5, 2006 9:34 AM (in response to beyarecords)Why do you have dependencies on implementation details? What is the use case that is not covered by standard J2EE-1.4 web services?