Strange Axis Fault at client side

["Hewitt, Christopher" <Ch...@tdsecurities.com>]

Hello,

I have an Axis 1.2rc3 client running under weblogic 8.1.
Everything seems to be fine, except for the fact that I occasionally get nullpointer exceptions at the client side when processing a response.

Has anyone else ever seen anything like the following:

AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.lang.NullPointerException
 faultActor:
 faultNode:
 faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.lang.NullPointerException
        at java.io.FilterInputStream.read(FilterInputStream.java:66)
        at org.apache.xerces.impl.XMLEntityManager$RewindableInputStream.read(Unknown Source)
        at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
        at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
        at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
        at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
        at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
        at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2754)
        at org.apache.axis.client.Call.invoke(Call.java:2737)
        at org.apache.axis.client.Call.invoke(Call.java:2413)
        at org.apache.axis.client.Call.invoke(Call.java:2336)
        at org.apache.axis.client.Call.invoke(Call.java:1793)
        at org.apache.axis.client.AxisClientProxy.invoke(AxisClientProxy.java:163)
        at $Proxy9.execute(Unknown Source)
        ...

This exception does not occur every time either.  It almost seems random.  Also, there appears to be no issue on the server side.
Any help would be appreciated.


Thanks,

Chris
christopher.hewitt@tdsecurities.com

Re: wsdl2java or java2wsdl best practise

[Anne Thomas Manes <at...@gmail.com>]

It is always better to create a service from wsdl/schema. 
If you try to generate a service from a java class, you are very
likely to expose language-specific features and structures that impede
interoperability.

Anne

On 4/22/05, Patrick Cogan <pa...@gmail.com> wrote:
> Hi,
> 
> I have looked for guidence and articles on this, but can't find any,
> so my question is:
> 
> which is generally the better practise:
> 
> - creating a web service from a wsdl using wsdl2java or;
> - creating a web service from a java class using java2wsdl
> 
> I remember reading that wsdl2java using a wsdl is best but can anyone
> confirm this and give reasons why?
> 
> Regards,
> 
> Patrick.
>

wsdl2java or java2wsdl best practise

[Patrick Cogan <pa...@gmail.com>]

Hi,

I have looked for guidence and articles on this, but can't find any,
so my question is:

which is generally the better practise:

- creating a web service from a wsdl using wsdl2java or;
- creating a web service from a java class using java2wsdl

I remember reading that wsdl2java using a wsdl is best but can anyone
confirm this and give reasons why?

Regards,

Patrick.