One more tiny tip to build cvs sources :-)
Keep servlet.jar in classpath to get classes like AdminServlet,
AxisServlet. After deploying the webapp on webserver, check
happyaxis.jsp.

Cheers
Venkat


On Mon, 7 Feb 2005 09:26:09 -0500, Praveen Peddi
<[EMAIL PROTECTED]> wrote:
> I still could not figure out a workaround to make 1.2 work with weblogic. I
> am switching to document style so I can't use 1.1. Could anyone suggest
> something? If I can't make it work, I will have to go back to 1.1 and just
> RPC style. But this seems wierd. No one has deployed Axis1.2 on weblogic? Or
> am I missing something? This seems like a showstopper to me.
> 
> I tried to build cvs code. It build fine after putting mail.jar and
> activation.jar but with some warnings. Also, axis.jar didn't have some http
> related classes like AdminServlet, AxisServlet. So the jar file didn't
> deploy at all on weblogic.
> 
> I gotto figure out a way to make it work with weblogic since document style
> is lot more efficient than RPC. Any help would be really appreciated.
> 
> Srinivas: If you are fixing this bug and If you need any help in testing it
> in weblogic, Pls send me private email and we can work co-ordinate each
> other. I will try to be as prompt as possible.
> 
> Thanks
> Praveen
> 
> ----- Original Message -----
> From: "Venkat Reddy" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, February 06, 2005 11:02 AM
> Subject: Re: Is latest nightly build stable
> 
> > To build axis sources, first remove everything from your classpath
> > environment and keep some optional jars in axis/lib folder -
> > activation.jar and mail.jar etc, and make sure your ant and jdk stuff
> > are in path. And then just run "ant" from ws-axis/java folder. It
> > builds fine for me right now.
> >
> > -venkat
> >
> >
> > On Sun, 6 Feb 2005 10:34:53 -0500, Praveen Peddi
> > <[EMAIL PROTECTED]> wrote:
> >> Hi Srinivas,
> >> Thanks a lot for checking the fix. I tried the latest nightly build dated
> >> Feb 6th. It still throws Nullpointer. But its in a different place now. I
> >> think XML parser is now throwing nullpointer.
> >> After debugging the cvs code (assuming the cvs code code is same as
> >> Feb6th's
> >>  nightly build), I found that the nullpointer is thrown in
> >> DeserializationContext.parse method at line 227.
> >>
> >> Following is the snippet:
> >>
> >> public void parse() throws SAXException
> >>     {
> >>         if (inputSource != null) {
> >>             SAXParser parser = XMLUtils.getSAXParser();
> >>             try {
> >>
> >> parser.setProperty("http://xml.org/sax/properties/lexical-handler";,
> >> this);
> >>                 parser.parse(inputSource, this); //Nullpointer is thrown
> >> here
> >>
> >>                 try {
> >>                     // cleanup - so that the parser can be reused.
> >>
> >>                     {some code here}
> >>
> >> }
> >>
> >> My soap enevlope looks as follows:
> >>
> >>
> >> <?xml version="1.0" encoding="utf-8"?>
> >> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
> >> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> >> xmlns:tns="http://localhost:7001/axis/services/CMISOAPAuthenticationService";
> >> xmlns:types="http://localhost:7001/axis/services/CMISOAPAuthenticationService/encodedTypes";
> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
> >>  <soap:Body
> >> soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
> >>   <q1:login xmlns:q1="http://soap.session.ip.contextmedia.com";>
> >>    <userID xsi:type="xsd:string">ISAdmin</userID>
> >>    <password xsi:type="xsd:string">ISAdmin</password>
> >>   </q1:login>
> >>  </soap:Body>
> >> </soap:Envelope>
> >> One thing I noticed is that the xml parser it found is
> >> weblogic.xml.jaxp.RegistrySAXParser. Even if it is coming from
> >> weblogic.jar,
> >> I think its still the bug of Axis since axis is sending invalid content
> >> to
> >> xml parser. Would it be possible to fix this exception and test with
> >> weblogic. When you are testing with another server, it is probably
> >> working
> >> fine but not in weblogic. In fact I don't mind testing it with weblogic
> >> once
> >> I make the cvs build work.
> >>
> >> I checked out cvs code but could not build. Where can I find the process
> >> of
> >> building cvs code. It looks like xerces and other libraries in the
> >> classpath
> >> so it is giving me compile time errors.
> >>
> >> Thanks
> >> Praveen
> >>
> >>
> >> ----- Original Message -----
> >> From: "Davanum Srinivas" <[EMAIL PROTECTED]>
> >> To: <[EMAIL PROTECTED]>
> >> Sent: Saturday, February 05, 2005 12:50 PM
> >> Subject: Re: Is latest nightly build stable
> >>
> >> >I checked ina fix. please take latest CVS or tonight's nightly.
> >> >
> >> > -- dims
> >> >
> >> >
> >> > On Sat, 5 Feb 2005 12:03:27 -0500, Praveen Peddi
> >> > <[EMAIL PROTECTED]> wrote:
> >> >>
> >> >> There is no stack trace. The code is not logging the runtime
> >> >> exception. I
> >> >> didn't see any exceptions in my log file.
> >> >>
> >> >> All I know is the exception is caught at line 324 (in my 1.2 rc2
> >> >> code).
> >> >> Following is the snippet where I saw the exception. My comments are in
> >> red
> >> >> font.
> >> >>
> >> >> public void invoke(MessageContext msgContext) throws AxisFault {
> >> >>
> >> >>             {some code here}
> >> >>
> >> >>                 // Ensure that if we get SOAP1.2, then reply using
> >> SOAP1.2
> >> >>
> >> >> if(msgContext.getRequestMessage().getSOAPEnvelope().getSOAPConstants()
> >> >> !=
> >> >> null) { // nullpointer is thrown here
> >> >>                     SOAPConstants soapConstants =
> >> >> msgContext.getRequestMessage().getSOAPEnvelope().getSOAPConstants();
> >> >>                     msgContext.setSOAPConstants(soapConstants);
> >> >>                 }
> >> >>
> >> >>             {some code here}
> >> >>
> >> >>
> >> >>
> >> >>  catch (AxisFault e) {
> >> >>             throw e;
> >> >>         } catch (Exception e) {//exception is caught and AxisFault is
> >> thrown
> >> >> w/o even logging
> >> >>             // Should we even bother catching it ?
> >> >>             throw AxisFault.makeFault(e);
> >> >>
> >> >>         } finally {
> >> >>             // restore previous state
> >> >>             setCurrentMessageContext(previousContext);
> >> >>         }
> >> >> }
> >> >>
> >> >>
> >> >> BTW is there a stable build that works with weblogic 8.1.3 where I can
> >> use
> >> >> document style webservices. Axis1.1 doesn't seem to support document
> >> style
> >> >> properly. 1.2 RC2 release have bug with weblogic 8.1.3. Nightly build
> >> >> is
> >> not
> >> >> stable. I would gretaly appreciate if someone can point me to a stable
> >> build
> >> >> that works with weblogic8.1.3.
> >> >>
> >> >> Thanks
> >> >> Praveen
> >> >>
> >> >>
> >> >>
> >> >> ----- Original Message -----
> >> >> From: "Davanum Srinivas" <[EMAIL PROTECTED]>
> >> >> To: <[EMAIL PROTECTED]>
> >> >> Sent: Saturday, February 05, 2005 8:47 AM
> >> >> Subject: Re: Is latest nightly build stable
> >> >>
> >> >> > Praveen,
> >> >> >
> >> >> > please send the stack trace.
> >> >> >
> >> >> > -- dims
> >> >> >
> >> >> >
> >> >> > On Fri, 4 Feb 2005 23:17:41 -0500, Praveen Peddi
> >> >> > <[EMAIL PROTECTED]> wrote:
> >> >> >>
> >> >> >> We were using 1.1 and I tried to move to 1.2 RC2 but it doesn't
> >> >> >> seem
> >> to
> >> >> work
> >> >> >> with weblogic 8.1.3 due to bug
> >> >> >> http://issues.apache.org/jira/browse/AXIS-1683. I see that Davanam
> >> >> Srinivas
> >> >> >> fixed this bug on Dec 04 which means RC2 also doesn't have this. So
> >> >> >> I
> >> >> tried
> >> >> >> to get latest nightly build dated feb4. That seemed to have fixed
> >> >> >> the
> >> >> above
> >> >> >> bug but I can use any of services.
> >> >> >>
> >> >> >> I get the NullPointerException.
> >> >> >>
> >> >> >> I don't see any errors in the log file but after debugging Axis
> >> >> >> code I
> >> >> found
> >> >> >> the error at line 279 of org.apache.axis.server.AxisServer.java (I
> >> >> actually
> >> >> >> attached 1.2RC2 code with Feb4th nightly build so I am very sure if
> >> its
> >> >> line
> >> >> >> 279 but it is surely in AxisServer.java).
> >> >> >>
> >> >> >> Doesn't anyone know about this error.
> >> >> >>
> >> >> >> Praveen
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> **************************************************************
> >> >> >> Praveen Peddi
> >> >> >> Sr Software Engg, Context Media, Inc.
> >> >> >> email:[EMAIL PROTECTED]
> >> >> >> Tel:  401.854.3475
> >> >> >> Fax:  401.861.3596
> >> >> >> web: http://www.contextmedia.com
> >> >> >> **************************************************************
> >> >> >> Context Media- "The Leader in Enterprise Content Integration"
> >> >> >>
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Davanum Srinivas - http://webservices.apache.org/~dims/
> >> >> >
> >> >
> >> >
> >> > --
> >> > Davanum Srinivas - http://webservices.apache.org/~dims/
> 
>

Reply via email to