axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Jordahl <t...@macromedia.com>
Subject RE: Initial Axis 1.1b Install Failure & Build Error
Date Tue, 07 Jan 2003 16:35:27 GMT

Maybe it would be good to fish or cut bait on the CommonsHTTPSender class.
Should we switch this to be the default implementation or remove the Commons based code all
together.  I believe the only (undocumented) way to use this class is to set a property.

It *is* very confusing.  Does the Commons version give us something we don't have with the
home grown one?  If so, is it important enough to make it the default?

Dims, I believe you checked in the commons based code originally...

Opinions?

--
Tom Jordahl
Macromedia Server Development



-----Original Message-----
From: Chris Haddad [mailto:chris.haddad@cobia.net]
Sent: Tuesday, January 07, 2003 11:19 AM
To: axis-user@xml.apache.org; axis-dev@xml.apache.org
Cc: tomj@macromedia.com; httpclient-dev@jakarta.apache.org
Subject: Re: Initial Axis 1.1b Install Failure & Build Error


All -

I ran into this same issue a few weeks ago.

The Release 2.0-Alpha-1 version of commons-httpclient is no longer
compatible with the Axis build.  A recent nightly build of
commons-httpclient works.   The public commons-httpclient API was changed.

I'm not sure how to re-phrase it in the Axis documentation, because there is
no official major/minor release except release 2.0 to suggest.  If someone
can come up with some appropriate verbaige, i'll change the docs, but i
don't think it is a good idea to hardcode a nightly build date (but maybe
the only one available).

 Maybe the commons-httpclient committers can cut another release.

/Chris

----- Original Message -----
From: "Tom Jordahl" <tomj@macromedia.com>
To: <axis-user@xml.apache.org>
Sent: Tuesday, January 07, 2003 9:58 AM
Subject: RE: Initial Axis 1.1b Install Failure & Build Error


>
> Tim,
>
> I don't run Tomcat, so I can't help you there.
>
> I am sorry about the commons-httpclient problems, if its any help I have a
version with sources dated 7/30/2002 and it builds fine.
>
> The nightly Gump builds are performed against the lastest versions of all
the Apache sources, and I believe it does this for commons-httpclient too.
So this is why you should not have problems with a recent source drop from
them.
>
> --
> Tom Jordahl
> Macromedia Server Development
>
>
>
> -----Original Message-----
> From: Tim Colson [mailto:tcolson@cisco.com]
> Sent: Monday, January 06, 2003 6:13 PM
> To: axis-user@xml.apache.org
> Subject: RE: Initial Axis 1.1b Install Failure & Build Error
>
>
> Tom -
>   Thanks for a reply. :-)
>
> > Problem #1:
> > You fixed by upgrading Tomcat - from the original error, you have
> > CLASSPATH issues since org/apache/axis/MessageContext is a pretty
> basic class.
>
> It's not actually fixed, since in production, we are still running 3.2.x
> - so if I can't get this figured out, I can't deploy. Doh!
>
> My colleage and myself both installed according to the directions. Has
> anyone else gotten 1.1 running on Tomcat 3.2.x?
>
>
> > Problem #2:
> > You have the wrong version of the commons-http.jar file.
> > Try compiling with the latest nightly build, not the latest release.
> > (don't ask ME why this is.. :-)
> Hmm... okay, I won't ask, but I did follow the Axis setup directions
> explicitly... anyway, I'll try that, thanks. ;-)
>
> > Hope this helps.
> Thanks - any reply is better than none. :-)
>
> Still, it would be nice to find out if anyone has run 1.1 on Tomcat
> 3.2.1.
>
> Cheers,
> Tim
>
>
>
>
>
>
> -----Original Message-----
> From: Tim Colson [mailto:tcolson@cisco.com]
> Sent: Monday, December 23, 2002 8:53 AM
> To: axis-user@xml.apache.org
> Subject: RE: Initial Axis 1.1b Install Failure & Build Error
>
>
> Replying to myself here...at least to keep the thread alive - still
> hoping for additional help. ;-)
>
> I loaded up Axis 1.1b inside Tomcat 4.1.18 and it runs swimmingly. No
> errors. The 3.2.1 issue appears to be a classpath problem of some sort.
>
> Can anybody get 1.1b to run in Tomcat 3.2.1?
>
> Thanks!
> Tim
>
> -----Original Message-----
> From: Tim Colson [mailto:tcolson@cisco.com]
> Sent: Friday, December 20, 2002 9:45 AM
> To: axis-user@xml.apache.org
> Subject: Initial Axis 1.1b Install Failure & Build Error
>
>
> Hey folks -
>   I've run Axis before, but I'm starting fresh with 1.1beta and running
> into two problems - the first is EchoHeaders throwing an
> InvocationTargetException when using the binary DIST of Axis, the second
> is a compile problem while trying to build Axis from src with -ALL- of
> the optional libraries (but narrowed down to the HTTPClient lib I
> think).
>
> Problem #1:
>   Following the 1.1 install instructions, myself and a colleage have
> both reproduced the following Fault (below). We are using the binary
> dist of 1.1 with Tomcat 3.2.1 and JSDK 1.3.1_02. happyaxis.jsp reports
> back success finding everything. The View works, and so does the 'show
> me the wsdl' url...but
> http://localhost:8080/axis/EchoHeaders.jws?method=list throws this
> fault:
>
> AXIS error
> Sorry, something seems to have gone wrong... here are the details:
>
> Fault - java.lang.reflect.InvocationTargetException
> AxisFault
>  faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>  faultSubcode:
>  faultString: java.lang.reflect.InvocationTargetException
>  faultActor: null
>  faultNode: null
>  faultDetail:
> stackTrace: java.lang.reflect.InvocationTargetException:
> java.lang.NoClassDefFoundError: org/apache/axis/MessageContext
> at EchoHeaders.getRequest(EchoHeaders.java:112)
> at EchoHeaders.list(EchoHeaders.java:73)
> at java.lang.reflect.Method.invoke(Native Method)
> (snipped)
> ----
>
> Problem #2:
>   Figuring that maybe something in the build was fubar... I decided to
> start from src and build my own. :-)  Followed the excellent build
> instructions and after a little bit of time, compiled and built the
> 'bare bones' jars. Tried these jars in tomcat - but it wouldn't work
> because the servlet stuff wasn't compiled in (I assume that's why.)
>
>   So I spent the next hour or so pulling down and expanding ALL of the
> other optional jars. (I should be up to date now for any Jakarta project
> I care to build...heh heh). I try to compile...but get compile errors.
> If I yank out the commons-httpclient.jar, it compiles fine.
>
> Here are the errors:
>      [echo] classpath:
> D:\java\xml-axis\java\${xerces.jar};D:\java\xml-axis\java
> \test\lib\jakarta-oro-2.0.5.jar;D:\java\xml-axis\java\lib\jsse.jar;D:\ja
> va\xml-a
> xis\java\lib\JimiProClasses.zip;D:\java\xml-axis\java\lib\activation.jar
> ;D:\java
> \xml-axis\java\lib\mailapi.jar;D:\java\jdk1.3.1_02\lib\tools.jar;D:\java
> \xml-axi
> s\java\${j2ee.jar};D:\java\xml-axis\java\lib\junit.jar;D:\java\xml-axis\
> java\lib
> \castor-0.9.4.1.jar;D:\java\xml-axis\java\lib\commons-discovery.jar;D:\j
> ava\xml-
> axis\java\lib\commons-httpclient.jar;D:\java\xml-axis\java\lib\commons-l
> ogging.j
> ar;D:\java\xml-axis\java\lib\jcert.jar;D:\java\xml-axis\java\lib\jms.jar
> ;D:\java
> \xml-axis\java\lib\jnet.jar;D:\java\xml-axis\java\lib\log4j-1.2.4.jar;D:
> \java\xm
> l-axis\java\lib\servlet.jar;D:\java\xml-axis\java\lib\wsdl4j.jar;D:\java
> \xml-axi
> s\java\lib\xalan.jar;D:\java\xml-axis\java\lib\xercesImpl.jar;D:\java\xm
> l-axis\j
> ava\lib\xml-apis.jar;D:\java\xml-axis\java\lib\xmlsec.jar;D:\java\jakart
> a-ant-1.
> 5.1\lib\xml-apis.jar;D:\java\jakarta-ant-1.5.1\lib\xercesImpl.jar;D:\jav
> a\jakart
> a-ant-1.5.1\lib\optional.jar;D:\java\jakarta-ant-1.5.1\lib\junit.jar;D:\
> java\jak
> arta-ant-1.5.1\lib\ant.jar;D:\java\xml-axis\java\build\classes;D:\java\x
> ml-axis\ java\build\tools;D:\java\xml-axis\java\build\lib\axis-ant.jar
>
>
> compile:
>     [javac] Compiling 1 source file to
> D:\java\xml-axis\java\build\classes
>     [javac]
> D:\java\xml-axis\java\src\org\apache\axis\transport\http\CommonsHTTP
> Sender.java:128: cannot resolve symbol
>     [javac] symbol  : method setRequestBody  (java.lang.String)
>     [javac] location: class
> org.apache.commons.httpclient.methods.PostMethod
>     [javac]             method.setRequestBody(new
> String(baos.toByteArray()));
>     [javac]                   ^
>     [javac]
> D:\java\xml-axis\java\src\org\apache\axis\transport\http\CommonsHTTP
> Sender.java:264: cannot resolve symbol
>     [javac] symbol  : method setProxyCredentials
> (<null>,org.apache.commons.htt
> pclient.Credentials)
>     [javac] location: class org.apache.commons.httpclient.HttpState
>     [javac]                 state.setProxyCredentials(null, proxyCred);
>     [javac]                      ^
>     [javac]
> D:\java\xml-axis\java\src\org\apache\axis\transport\http\CommonsHTTP
> Sender.java:302: cannot resolve symbol
>     [javac] symbol  : method setProxyCredentials
> (<null>,org.apache.commons.htt
> pclient.Credentials)
>     [javac] location: class org.apache.commons.httpclient.HttpState
>     [javac]                 state.setProxyCredentials(null, proxyCred);
>     [javac]                      ^
>     [javac]
> D:\java\xml-axis\java\src\org\apache\axis\transport\http\CommonsHTTP
> Sender.java:327: cannot resolve symbol
>     [javac] symbol  : method setSoTimeout  (int)
>     [javac] location: class org.apache.commons.httpclient.HttpConnection
>     [javac]             conn.setSoTimeout(msgContext.getTimeout());
>     [javac]                 ^
>     [javac] 4 errors
>
> BUILD FAILED
> file:D:/java/xml-axis/java/build.xml:92: Compile failed; see the
> compiler error output for details.
>
> P.S. I do have the Xerces libs in ${axis.home}/java/lib (xercesImpl.jar
> and xmlApis.jar)... But the classpath shows
> D:\java\xml-axis\java\${xerces.jar}; -> so what's up with that?
>
> Thanks!
> Tim
>
>
>
>
>
>

Mime
View raw message