Re: [axis2] Problem : Provider null could not be instantiated

[Davanum Srinivas]

Bingo, i faced the same problemBasically delete
jre/lib/jaxp.properties file if you have one.

thanks,
dims

On 8/26/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Could you please log a bug? along with info on how you deployed it in
> your servlet container?
> 
> thanks,
> dims
> 
> On 8/26/05, Johan Andersson <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > I've recently started to test and evaluate Axis2.
> >
> > I wrote a wsdl and ran it through WSDL2Java, made some modifications to the 
> > skeleton code,
> > built the .aar archive as detailed by the axis2 documentation and deployed 
> > the service.
> >
> > The service is correctly deployed as far as I can tell (shows up in listing 
> > without errors).
> > HappyAxis page is, well.., happy =)
> >
> > Still the server is dumping with the (server-side) exception included below.
> >
> > I had a similar problem on the client side which I cured with a 
> > System.setProperty("javax.xml.stream.XMLInputFactory", 
> > "com.bea.xml.stream.MXParserFactory");
> >
> > Doing the same server-side (-Djavax...) on Tomcat 4.1 OR Websphere 6 does 
> > not work.
> >
> > Should not this work out of the box without fiddling around with setting 
> > system properties in the JVM?
> >
> > I am clueless how to procede, please help.
> >
> > Also I cannot find any information of the intended target platform or java 
> > version for Axis2, is it Java 1.4 or 1.5?
> >
> > Thank you in advance and best regards,
> >
> > Johan
> >
> >
> >
> > 2005-08-26 11:22:40 StandardWrapperValve[AxisServlet]: Servlet.service() 
> > for servlet AxisServlet threw exception
> > org.apache.axis2.AxisFault: Provider null could not be instantiated: 
> > java.lang.NullPointerException; nested exception is:
> > javax.xml.stream.FactoryConfigurationError: Provider null could not 
> > be instantiated: java.lang.NullPointerException
> > at 
> > org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:137)
> > at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:169)
> > at 
> > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:206)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:716)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:809)
> > at 
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:200)
> > at 
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:146)
> > at 
> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:209)
> > at 
> > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
> > at 
> > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
> > at 
> > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
> > at 
> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:144)
> > at 
> > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
> > at 
> > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
> > at 
> > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
> > at 
> > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358)
> > at 
> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)
> > at 
> > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
> > at 
> > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:118)
> > at 
> > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
> > at 
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:116)
> > at 
> > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
> > at 
> > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
> > at 
> > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
> > at 
> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:127)
> > at 
> > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
> > at 
> > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
> > at 
> > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
> > at 
> > org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:152)
> > at 
> > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
> > at 
> > org.apache.co

Re: xsd:any element not in the generated

[Garret Pick]

Hello,

I found that this had been documented under 

http://issues.apache.org/jira/browse/AXIS-1881

I was wondering if anyone had a workaround or knew
when a patch might be available?

thanks,
Garret




List:   axis-user
Subject:Re: xsd:any element not in the generated
wsdl
From:   Davanum Srinivas 
Date:   2005-03-16 18:29:53
Message-ID: 19e0530f050316102967b69c85 () mail ! gmail
! com
[Download message RAW]

this is a bug. please report it.

thx,
dims


On Wed, 16 Mar 2005 18:03:45 - (GMT), Daniel
Beland
<[EMAIL PROTECTED]> wrote:
> 
> 
> Hi,
> 
> I try to generate java code from a wsdl with the
following complexType:
> 
> 
>   
>  maxOccurs="unbounded"/>
>   
> 
> 
> wsdl2java generates the XmlData class correctly with
a single field
> private org.apache.axis.message.MessageElement []
_any;
> 
> But when I install this on tomcat and look at the
wsdl generated by Axis,
> the xmlData complexType now looks like this:
> 
> 
>   
> 
> 
> Now I cannot validate my client against the wsdl,
because it says that the
> complexType xmlData doesn't have a child element. Is
this a bug or is
> there a special serializer to use instead of
BeanSerializer, or am I doing
> something wrong?
> 
> I tried a lot of things but I'm stuck so any help
would be appreciated.
> 
> Thanks,
> Daniel
> 
> 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Axis 1.2 WSDl2Java creating packages in the REVERSE order

[Guy Rixon]

AFAIK, the packaged in the code are chosen entirely from the XML namespaces.
Your WSDL has a target namespace for the overall contract and that's the
package where the files end up.

If you want your value objects in separate packages, then you need to sort
them into separate namespaces in the types section of your WSDL or in the
schemata that the WSDL includes.

Getting the (client) stub and the skeleton into separate packages is harder.
It looks to me like they are both associated with the binding, so both will
have the package associated with the binding's namespace. Two ways out:

 1. Hack on the code after generation.

 2. Split the WSDL into three files. File #1 has the port-type, message
and types sections. Files #2 and #3 each have the binding and service
sections but have different target namespaces; these files wsdl:import
file #1. Generate the stub from one and the skeleton from another.

Solution 1 is simple but can't easily be automated. Solution 2 is baroque but
can run in an automated build. I'm waving my hands here; I haven't tried this
with Axis on real WSDL. Note that in solution 2 you've made two different
contracts and implemented one in the client and the other in the service. It
may well work out that the contracts are equivalent (I think the namespaces
used in the SOAP messages would come from the port-type, not from the
bindings, and so would match), but it's a technical mis-use of WSDL.

The WSDD files can be fished out of their default package and put in whatever
folder you want.

Is it really worth the grief to get the bits where you want them?


On Fri, 26 Aug 2005 [EMAIL PROTECTED] wrote:

> Thanks a lot Guy.   I gave the right package name in the mapping during
> WSD2Java invocation and got the package name that I needed.
>
> Here is another question that relates to the package created by WSDL2Java.
>   Currenty it creates all the java classes ..(Interface, stub,
> BindingImpl, skeleton etc)   in ONE package.. is there any way I can route
> the generated classes in to different  pakages?  ie.   I need to put my
> .wsdd in a separate folder, stub in one package, skeleton in one
> packgage..  my value objects for the messages in one package ..   any
> idea?
>
>
> Your help is highly appreciated!
>
> Raj
>
>
>
>
> Guy Rixon <[EMAIL PROTECTED]>
> 08/26/2005 12:00 PM
> Please respond to axis-user
>
>
> To: axis-user@ws.apache.org
> cc:
> Subject:Re: Axis 1.2   WSDl2Java  creating packages in the 
> REVERSE order
>
>
> Hi,
>
> I think Axis is expecting to see namespace URIs with the http scheme, as
> in
> the http://www.w3.org/2001/XMLSchema of your example. When it finds the
> authority part of the URI it reverses it, because it expects it to look
> like a
> server name a la DNS. Arguably, it should only do this if the scheme of
> the
> URI is one of those where the authority is really an address (http, https,
> ftp, etc.), so yes, I'd call this a bug.
>
> To get round this, you need to use an explicit mapping of the namespace to
> your preferred package and to set this mapping in the invocation of
> WSDL2java.
> See the "reference documentation" for details.
>
> On Fri, 26 Aug 2005 [EMAIL PROTECTED] wrote:
>
> > Hello,
> >
> > I am trying to throw an custom exception and when I run WSDL2Java  it
> > creates my excepion  but the package name is REVERSED for
> InvalidDataFormatException.java   WSDL2Java puts this java class in
> exceptions.ws.com package instead of
> > com.ws.exceptions package
> >
> > Please let me know if its a bug in AXIS 1.2 or  I am making a mistake in
> > my declaration( I hope so.. but I don't have a clue)
> >
> > Here is the schema for my exception (ExceptionSchema.xsd)
> >
> > 
> > http://www.w3.org/2001/XMLSchema";
> > xmlns:stns="java:com.ws.exceptions"
> > elementFormDefault="qualified"
> > attributeFormDefault="qualified"
> > targetNamespace="java:com.ws.exceptions">
> >
> >
> >
> > 
> >   >name="errorCode"
> >minOccurs="1"
> >nillable="true"
> >maxOccurs="1">
> >  
> >   >name="errorDescription"
> >minOccurs="1"
> >nillable="true"
> >maxOccurs="1">
> >  
> >   >name="variables"
> >minOccurs="1"
> >nillable="true"
> >maxOccurs="1">
> >  
> > 
> >
> > 
> >
> > and here is my WSDL
> >
> >
> >
> > 
> >
> >  >  targetNamespace="urn:DataInquiry2"
> >  xmlns:tns="urn:DataInquiry2"
> >  xmlns:typens="urn:DataInquiry2"
> >  xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> >  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
> >  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
> >  xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
> >  xmlns="http://schemas.xmlsoap.org/wsdl/"; 
> > xmlns:xsd1="java:com.ws.exceptions">
> >
> >   
> >> location="ExceptionSchema.xs

ClassCastException After Upgrade From Axis 1.1 to 1.2.1

[Tootell, James]

All:

I wrote a webservice client a year ago using a combination of Axis 1.1
to handle transmissions and Castor 0.9.7 to handle un/marshalling.  We
recently decided to upgrade to Axis 1.2RC3 and forgo the use of Castor.
I ran WSDL2Java and regenerated all the stub code and supporting classes
and got no compile errors.  At runtime though I consistently get the
following error:


; nested exception is: 
java.lang.ClassCastException
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode: 
faultString: java.lang.ClassCastException
faultActor: 
faultNode: 
faultDetail: 
{http://xml.apache.org/axis/}stackTrace:java.lang.ClassCastException
at
org.apache.axis.message.SOAPFaultBuilder.onEndChild(SOAPFaultBuilder.jav
a:299)
at
org.apache.axis.encoding.DeserializationContext.endElement(Deserializati
onContext.java:1090)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source) at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source) at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis
patcher.dispatch(Unknown Source) at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno
wn 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(DeserializationCon
text.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:424)
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java
:796)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.j
ava:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
...


My call is failing before I even get it to the wire.  I even upgraded
again from 1.2RC3 to 1.2.1 Final thinking maybe it was a bug in Axis but
still no joy.  I've also tried using newer versions of Xerces but to no
avail.  

The service I'm trying to access is a document-style service.  I have
another 1.2.1 client that accesses an RPC-style service just fine.  This
leads me to believe their might be something wrong in the schemas
supporting the document-style service's WSDL but everything validates
and compiles flawlessly.  Does anyone have any ideas why I'm getting
this error?

Also, I tried inspecting the raw SOAP message just prior to calling
_call.invoke() and _call.getMessageContext()'s .getCurrentMessage() and
getRequestMessage() always return null.  Is this normal?  I wouldn't
think it would be.
 

Thanks in advance, 

Jim Tootell
System Design, Development, 
 & Integration Department
Anteon  Corporation
2251 San Diego Ave.
Suite A240
San Diego, CA  92110
(619) 542-0240 x123
mailto:[EMAIL PROTECTED] 

 

There are 10 kinds of people: 
  those who understand binary and those who don't.

NodeImpl not found?

[Javier Gonzalez]

Hi!

I have a webservice that creates a soap response that must be sent to
the caller - so, at a given time I have a SOAPBody object that must be
set as the body of the response.

But when I do

resp.setBody(mySoapBody);

I get this:

javax.xml.soap.SOAPException: javax.xml.soap.SOAPException:
org.w3c.dom.DOMException: NodeImpl Not found
at org.apache.axis.message.SOAPBody.setParentElement(SOAPBody.java:91)
at org.apache.axis.message.SOAPEnvelope.setBody(SOAPEnvelope.java:308)
at 
my.package.mms.mm7receiver.MessageService.echoElements(MessageService.java:105)

root cause being:

Caused by: org.w3c.dom.DOMException: NodeImpl Not found
at org.apache.axis.message.NodeImpl.removeChild(NodeImpl.java:515)
at 
org.apache.axis.message.SOAPEnvelope.removeChild(SOAPEnvelope.java:616)
at org.apache.axis.message.NodeImpl.detachNode(NodeImpl.java:660)
at org.apache.axis.message.NodeImpl.appendChild(NodeImpl.java:493)
at org.apache.axis.message.NodeImpl.setParent(NodeImpl.java:791)
at org.apache.axis.message.NodeImpl.setParentElement(NodeImpl.java:632)
... 32 more

This happened after switching the app from Axis 1.1 to axis 1.2, due
to 1.1's misbehaviour while dealing with mustUnderstand headers
(rejecting soap but passing message along the chain for further
processing)

Thanks in advance,

-- 
Javier Gonzalez Nicolini

Re: Axis 1.2 WSDl2Java creating packages in the REVERSE order

[raj . x . arunmugan]

Thanks a lot Guy.   I gave the right package name in the mapping during WSD2Java invocation and got the package name that I needed.  

Here is another question that relates to the package created by WSDL2Java.   Currenty it creates all the java classes ..(Interface, stub, BindingImpl, skeleton etc)   in ONE package.. is there any way I can route the generated classes in to different  pakages?  ie.   I need to put my .wsdd in a separate folder, stub in one package, skeleton in one packgage..  my value objects for the messages in one package ..   any idea?


Your help is highly appreciated!

Raj






Guy Rixon <[EMAIL PROTECTED]>
08/26/2005 12:00 PM
Please respond to axis-user

        
        To:        axis-user@ws.apache.org
        cc:        
        Subject:        Re: Axis 1.2   WSDl2Java  creating packages in the REVERSE order


Hi,

I think Axis is expecting to see namespace URIs with the http scheme, as in
the http://www.w3.org/2001/XMLSchema of your example. When it finds the
authority part of the URI it reverses it, because it expects it to look like a
server name a la DNS. Arguably, it should only do this if the scheme of the
URI is one of those where the authority is really an address (http, https,
ftp, etc.), so yes, I'd call this a bug.

To get round this, you need to use an explicit mapping of the namespace to
your preferred package and to set this mapping in the invocation of WSDL2java.
See the "reference documentation" for details.

On Fri, 26 Aug 2005 [EMAIL PROTECTED] wrote:

> Hello,
>
> I am trying to throw an custom exception and when I run WSDL2Java  it
> creates my excepion  but the package name is REVERSED for InvalidDataFormatException.java   WSDL2Java puts this java class in exceptions.ws.com package instead of
> com.ws.exceptions package
>
> Please let me know if its a bug in AXIS 1.2 or  I am making a mistake in
> my declaration( I hope so.. but I don't have a clue)
>
> Here is the schema for my exception (ExceptionSchema.xsd)
>
> 
> 
>     xmlns:stns="java:com.ws.exceptions"
>     elementFormDefault="qualified"
>     attributeFormDefault="qualified"
>     targetNamespace="java:com.ws.exceptions">
>
>
>    
>     
>      
>        name="errorCode"
>        minOccurs="1"
>        nillable="true"
>        maxOccurs="1">
>      
>      
>        name="errorDescription"
>        minOccurs="1"
>        nillable="true"
>        maxOccurs="1">
>      
>      
>        name="variables"
>        minOccurs="1"
>        nillable="true"
>        maxOccurs="1">
>      
>     
>    
> 
>
> and here is my WSDL
>
>
>
> 
>
> 
>              targetNamespace="urn:DataInquiry2"
>              xmlns:tns="urn:DataInquiry2"
>              xmlns:typens="urn:DataInquiry2"
>              xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>              xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>              xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>              xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
>              xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd1="java:com.ws.exceptions">
>
>   
>   
>   
>     
>                 xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>
>
>       
>         
>             
>             
>         
>       
>
>       
>         
>             
>             
>             
>             
>             
>         
>       
>
>
>
>
>     
>   
>
>   
>   
>
>
>
>   
>
>    
>     
>   
>
>    
>     
>   
>
>   
>   
>   
>   
>
>
>   
>   
>
>     
>       
>       
>       
>
>     
>   
>
>   
>   
>     
>                   transport="http://schemas.xmlsoap.org/soap/http"/>
>
>     
>
>        
>       
>         
>       
>       
>         
>       
>       
>         
>       
>     
>   
>
>   
>   
>     
>       
>     
>   
>
> 
>
>

Guy Rixon                                                                             [EMAIL PROTECTED]
Institute of Astronomy                                    Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA                                  Fax: +44-1223-337523

Re: How to throw custom exceptions?

[Davanum Srinivas]

Let's treat this as a bug then. Please create a bug report and attach your wsdl.

thanks,
dims

On 8/26/05, Chris Nappin <[EMAIL PROTECTED]> wrote:
> Thanks Dims, but if you are referring to putting Axis into "production"
> mode then I've already tried that - it has no affect.
> 
> All I'm trying to do is get Axis generate a WS-I Basic Profile
> 1.0-compilant SOAP fault that compiles with my wsdl?
> 
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: 26 August 2005 14:13
> To: axis-user@ws.apache.org
> Subject: Re: How to throw custom exceptions?
> 
> check if axis.development.system helps
> (http://ws.apache.org/axis/java/security.html)
> 
> -- dims
> 
> On 8/26/05, Chris Nappin <[EMAIL PROTECTED]> wrote:
> > And if I add further details from the auto-generated deploy.wsdd to my
> server-config.wsdd, I get proper local names and namespaces on my custom
> tags. However I can't stop Axis adding the exceptionName and hostname.
> >
> > Any folks seen this please? I seem to be having a conversation with
> myself - very worrying!  ;-)
> >
> > -Original Message-
> > From: Chris Nappin [mailto:[EMAIL PROTECTED]
> > Sent: 26 August 2005 09:51
> > To: axis-user@ws.apache.org
> > Subject: RE: How to throw custom exceptions?
> >
> > Okay, I've been trying to get a bit further by using wsdl2java to
> generate the exceptions for me, so it can put in all the Axis-specifics.
> >
> > I have defined a custom in my wsdl as follows:
> >
> > 
> >
> > 
> >   maxOccurs="1" nillable="false"/>
> > 
> >
> >   
> >
> > When running my service Axis returns the following response:
> >
> > 
> >  > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> > 
> > 
> > soapenv:Server.generalException
> > 
> > 
> > 
> > Test!
> > 
> >  xmlns:ns1="http://xml.apache.org/axis/";>com.test.MyFirstException xceptionName>
> >  xmlns:ns2="http://xml.apache.org/axis/";>PC55-ABMUK
> > 
> > 
> > 
> > 
> >
> > This is a step forward, as I now have custom fields (text) in the
> "detail" block. However, is there any way of stopping Axis generating
> the "exceptionName" and "hostname" fields?
> >
> > Cheers,
> >
> >   Chris.
> >
> > 
> > From: Chris Nappin [mailto:[EMAIL PROTECTED]
> > Sent: 25 August 2005 16:42
> > To: axis-user@ws.apache.org
> > Subject: How to throw custom exceptions?
> >
> >
> > Hi,
> >
> >  I'm having trouble throwing custom exceptions in an interoperable way
> in Axis 1.2.1. I've read previous mailing list messages and looked at
> the "samples/faults" files but haven't got very far. I've been unable to
> get any custom data into the "detail" section of the fault.
> >
> > Can someone please clarify:
> >
> > 1. What should my exception look like - does it extend Exception,
> RemoteException or ApacheFault? Does it need to be Serializable? Does
> Axis support the JAX-RPC way of having exceptions as immutable beans
> (constructors for setting properties, getters for reading, no setters)?
> > 2. What should my service signature look like - simply "throws
> MyCustomException"?
> > 3. What extra needs to go into my server-config.wsdd - I've tried
> adding an operation section with a fault, and a typeMapping.
> > 4. I have lots of details of my custom fault in my wsdl, but if we
> don't use wsdl2java then Axis won't actually use that, right?
> >
> > Thanks,
> >
> > Chris Nappin
> > Technical Architect
> >
> > ABM United Kingdom Limited
> > Telephone: +44 (0) 115 977 6999
> > Facsimile: +44 (0) 115 977 6850
> > Web: http://www.abm-uk.com
> >
> > ABM for Intelligent Solutions
> >
> >
> > CONFIDENTIALITY & PRIVILEGE NOTICE
> > This e-mail is confidential to its intended recipient. It may also be
> privileged. Neither the confidentiality nor any privilege attaching to
> this e-mail is waived lost or destroyed by reason that it has been
> mistakenly transmitted to a person or entity other than its intended
> recipient. If you are not the intended recipient please notify us
> immediately by telephone or fax at the numbers provided above or e-mail
> by Reply To Author and return the printed e-mail to us by post at our
> expense. We believe, but do not warrant, that this e-mail and any
> attachments are virus-free, but you should check. We may monitor traffic
> data of both business and personal e-mails. We are not liable for any
> opinions expressed by the sender where this is a non-business e-mail. If
> you do not receive all the message, or if you have difficulty with the
> transmission, please telephone us immediately.
> >
> >
> > CONFIDENTIALITY & PRIVILEGE NOTICE
> >
> > This e-mail is confidential to its intended recipient. It may also be
> privileged. Neither 

Re: Axis 1.2 WSDl2Java creating packages in the REVERSE order

[Guy Rixon]

Hi,

I think Axis is expecting to see namespace URIs with the http scheme, as in
the http://www.w3.org/2001/XMLSchema of your example. When it finds the
authority part of the URI it reverses it, because it expects it to look like a
server name a la DNS. Arguably, it should only do this if the scheme of the
URI is one of those where the authority is really an address (http, https,
ftp, etc.), so yes, I'd call this a bug.

To get round this, you need to use an explicit mapping of the namespace to
your preferred package and to set this mapping in the invocation of WSDL2java.
See the "reference documentation" for details.

On Fri, 26 Aug 2005 [EMAIL PROTECTED] wrote:

> Hello,
>
> I am trying to throw an custom exception and when I run WSDL2Java  it
> creates my excepion  but the package name is REVERSED for 
> InvalidDataFormatException.java   WSDL2Java puts this java class in 
> exceptions.ws.com package instead of
> com.ws.exceptions package
>
> Please let me know if its a bug in AXIS 1.2 or  I am making a mistake in
> my declaration( I hope so.. but I don't have a clue)
>
> Here is the schema for my exception (ExceptionSchema.xsd)
>
> 
> http://www.w3.org/2001/XMLSchema";
> xmlns:stns="java:com.ws.exceptions"
> elementFormDefault="qualified"
> attributeFormDefault="qualified"
> targetNamespace="java:com.ws.exceptions">
>
>
>
> 
>  name="errorCode"
>minOccurs="1"
>nillable="true"
>maxOccurs="1">
>  
>  name="errorDescription"
>minOccurs="1"
>nillable="true"
>maxOccurs="1">
>  
>  name="variables"
>minOccurs="1"
>nillable="true"
>maxOccurs="1">
>  
> 
>
> 
>
> and here is my WSDL
>
>
>
> 
>
>   targetNamespace="urn:DataInquiry2"
>  xmlns:tns="urn:DataInquiry2"
>  xmlns:typens="urn:DataInquiry2"
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>  xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
>  xmlns="http://schemas.xmlsoap.org/wsdl/"; 
> xmlns:xsd1="java:com.ws.exceptions">
>
>   
>location="ExceptionSchema.xsd">
>   
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
>
>   
> 
> 
> 
> 
>   
>
>   
> 
> 
> 
> 
> 
> 
> 
>   
>
>
>
>
> 
>   
>
>   
>   
>
>
>
>   
>
>
> 
>   
>
>
> 
>   
>
>   
>type="xsd1:InvalidDataFormatException">
>   
>   
>
>
>   
>   
>
> 
>   
>   
>message="tns:InvalidDataFormatException"/>
>
> 
>   
>
>   
>   
>transport="http://schemas.xmlsoap.org/soap/http"/>
>
> 
>
>
>   
> 
>   
>   
> 
>   
>   
> 
>   
> 
>   
>
>   
>   
> 
>location="http://localhost:8080/InquiryWSWAR/services/DataInquiry"/>
> 
>   
>
> 
>
>

Guy Rixon   [EMAIL PROTECTED]
Institute of Astronomy  Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA  Fax: +44-1223-337523

Axis 1.2 WSDl2Java creating packages in the REVERSE order

[raj . x . arunmugan]

Hello,

I am trying to throw an custom exception and when I run WSDL2Java  it creates my excepion  but the package name is REVERSED for InvalidDataFormatException.java   WSDL2Java puts this java class in exceptions.ws.com package instead of com.ws.exceptions package 

Please let me know if its a bug in AXIS 1.2 or  I am making a mistake in my declaration( I hope so.. but I don't have a clue)

Here is the schema for my exception (ExceptionSchema.xsd)

xml version="1.0" encoding="UTF-8"?>

 
  
   
    
     
     xsd:element>
     
     xsd:element>
     
     xsd:element>
    xsd:sequence>
   xsd:complexType>
xsd:schema>

and here is my WSDL



xml version="1.0" ?>



  
  import>
  
    


      
        
            
            
        xsd:all>
      xsd:complexType>

      
        
            
            
            
            
            
        xsd:all>
      xsd:complexType>
      
      
   
    
    xsd:schema>
  types>

  
  

  
  
  
  
   
    
  message>

   
    
  message>
  
  
  
  part>
  message>
  
  
  
  
    
    
      
      

      
      
    operation>
  portType>

  
  
    
    
    
      
        
       
         
      input> 
      
 
         
      output>
      
        
      wsdl:fault>
    operation>
  binding>

  
  
    
      
    port>
  service>

definitions>

Re: [axis2] Problem : Provider null could not be instantiated

[jayachandra]

This might sound disconnected, but Johan just try renaming axis2.xml
to some axis2.xml.bckp and restart the Tomcat and repeat the try
(Axis2 will create an axis2.xml afresh anyway). The reason why I'm
saying this is, sometime back I too struggled for a while on a
clueless error in a scenario similar to what you described, the
default deployment information being read happened to be from an older
axis2.xml that I had and that caused all the trouble. Was just
wondering if that be the case on your end as well. Just give it a try,
wudn't take more than 2minutes.

regards
Jayachandra

On 8/26/05, Johan Andersson <[EMAIL PROTECTED]> wrote:
> Hello,
> 
> I've recently started to test and evaluate Axis2.
> 
> I wrote a wsdl and ran it through WSDL2Java, made some modifications to the 
> skeleton code,
> built the .aar archive as detailed by the axis2 documentation and deployed 
> the service.
> 
> The service is correctly deployed as far as I can tell (shows up in listing 
> without errors).
> HappyAxis page is, well.., happy =)
> 
> Still the server is dumping with the (server-side) exception included below.
> 
> I had a similar problem on the client side which I cured with a 
> System.setProperty("javax.xml.stream.XMLInputFactory", 
> "com.bea.xml.stream.MXParserFactory");
> 
> Doing the same server-side (-Djavax...) on Tomcat 4.1 OR Websphere 6 does not 
> work.
> 
> Should not this work out of the box without fiddling around with setting 
> system properties in the JVM?
> 
> I am clueless how to procede, please help.
> 
> Also I cannot find any information of the intended target platform or java 
> version for Axis2, is it Java 1.4 or 1.5?
> 
> Thank you in advance and best regards,
> 
> Johan
> 
> 
> 
> 2005-08-26 11:22:40 StandardWrapperValve[AxisServlet]: Servlet.service() for 
> servlet AxisServlet threw exception
> org.apache.axis2.AxisFault: Provider null could not be instantiated: 
> java.lang.NullPointerException; nested exception is:
>javax.xml.stream.FactoryConfigurationError: Provider null could not be 
> instantiated: java.lang.NullPointerException
>at 
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:137)
>at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:169)
>at 
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:206)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:716)
>at javax.servlet.http.HttpServlet.service(HttpServlet.java:809)
>at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:200)
>at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:146)
>at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:209)
>at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
>at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
>at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
>at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:144)
>at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
>at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
>at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
>at 
> org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358)
>at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)
>at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
>at 
> org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:118)
>at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
>at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:116)
>at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
>at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
>at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
>at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:127)
>at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
>at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
>at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
>at 
> org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:152)
>at 
> org.apache.coyote.http11.Htt

Re: basic authentication

[Plorks mail]

Thanks Guy

I think i'll stick to creating my own headers within the soap envelope - I'm 
still new to webservices/axis i don't really understand the wss4j


Thanks for your help



From: Guy Rixon <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: basic authentication
Date: Fri, 26 Aug 2005 15:49:52 +0100 (BST)

Hi,

all my code is for the digital-signature mode of WSS4J. But the project's 
own

site has some deployment examples for UsernameToken.  See

  http://ws.apache.org/wss4j/

and

  http://ws.apache.org/wss4j/axis.html

Cheers,
Guy

On Fri, 26 Aug 2005, Plorks mail wrote:

>
>
> Hi Guy
>
> Thanks fr getting back to me.  Do you haveor can you lead me to an WSS4J
> example ?
>
> Thanks for your help
>
>
>
>
>
>
> >From: Guy Rixon <[EMAIL PROTECTED]>
> >Reply-To: axis-user@ws.apache.org
> >To: axis-user@ws.apache.org
> >Subject: Re: basic authentication
> >Date: Fri, 26 Aug 2005 14:47:05 +0100 (BST)
> >
> >If you are able to change the WSDL contract, then you can indeed 
include

> >the
> >username and password in the SOAP body. Just put them in a message 
part,

> >like
> >any other parameter.
> >
> >If you want to put username and password in the SOAP header, then you 
can

> >use
> >the UsernameToken mode of WSS4J to be compatible with the WS-Security
> >standard; or you can invent your own header if you don't have to be
> >standard
> >or interoperable. Using WSS4J is probably better.
> >
> >On Fri, 26 Aug 2005, Plorks mail wrote:
> >
> > > hi all
> > >
> > > i'm currntly getting username and password using basic 
authentication in

> >my
> > > web service.
> > >
> > > we are using a product that doesn't support basic authentaication in 
the

> > > http header, so now i have to re-write my web service.  Can anyone
> >suggest
> > > an alternative way to do this?
> > >
> > > Can i set the username and password in the SOAP Envelope/body?
> > >
> > > Thsi is the code i'm curently using
> > > String headerAuth =
> > > (String)msgContext.getProperty(HTTPConstants.HEADER_AUTHORIZATION);
> > >
> > > if (headerAuth != null)
> > > {
> > >headerAuth = headerAuth.trim();
> > > }
> > >
> > > if (headerAuth != null && headerAuth.startsWith("Basic "))
> > > {
> > > int i;
> > >
> > > headerAuth = new String(Base64.decode(headerAuth.substring(6)));
> > >
> > > String [] userNamePassword = headerAuth.split(":");
> > >
> > > userName = userNamePassword[0];
> > > password = userNamePassword[1];
> > > }
> > >
> > > thanks for  any help
> > >
> > > _
> > > Express yourself instantly with MSN Messenger! Download today - it's
> >FREE!
> > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> > >
> >
> >Guy Rixon  [EMAIL PROTECTED]
> >Institute of Astronomy Tel: +44-1223-337542
> >Madingley Road, Cambridge, UK, CB3 0HA Fax: +44-1223-337523
>
> _
> Winks & nudges are here - download MSN Messenger 7.0 today!
> http://messenger.msn.co.uk
>

Guy Rixon   [EMAIL PROTECTED]
Institute of Astronomy  Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA  Fax: +44-1223-337523


_
Want to block unwanted pop-ups? Download the free MSN Toolbar now!  
http://toolbar.msn.co.uk/

RE: How to throw custom exceptions?

[Chris Nappin]

Thanks Dims, but if you are referring to putting Axis into "production"
mode then I've already tried that - it has no affect.

All I'm trying to do is get Axis generate a WS-I Basic Profile
1.0-compilant SOAP fault that compiles with my wsdl?

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
Sent: 26 August 2005 14:13
To: axis-user@ws.apache.org
Subject: Re: How to throw custom exceptions?

check if axis.development.system helps
(http://ws.apache.org/axis/java/security.html)

-- dims

On 8/26/05, Chris Nappin <[EMAIL PROTECTED]> wrote:
> And if I add further details from the auto-generated deploy.wsdd to my
server-config.wsdd, I get proper local names and namespaces on my custom
tags. However I can't stop Axis adding the exceptionName and hostname.
> 
> Any folks seen this please? I seem to be having a conversation with
myself - very worrying!  ;-)
> 
> -Original Message-
> From: Chris Nappin [mailto:[EMAIL PROTECTED]
> Sent: 26 August 2005 09:51
> To: axis-user@ws.apache.org
> Subject: RE: How to throw custom exceptions?
> 
> Okay, I've been trying to get a bit further by using wsdl2java to
generate the exceptions for me, so it can put in all the Axis-specifics.
> 
> I have defined a custom in my wsdl as follows:
> 
> 
>
> 
>  
> 
>
>   
> 
> When running my service Axis returns the following response:
> 
> 
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> 
> 
> soapenv:Server.generalException
> 
> 
> 
> Test!
> 
> http://xml.apache.org/axis/";>com.test.MyFirstException
> http://xml.apache.org/axis/";>PC55-ABMUK
> 
> 
> 
> 
> 
> This is a step forward, as I now have custom fields (text) in the
"detail" block. However, is there any way of stopping Axis generating
the "exceptionName" and "hostname" fields?
> 
> Cheers,
> 
>   Chris.
> 
> 
> From: Chris Nappin [mailto:[EMAIL PROTECTED]
> Sent: 25 August 2005 16:42
> To: axis-user@ws.apache.org
> Subject: How to throw custom exceptions?
> 
> 
> Hi,
> 
>  I'm having trouble throwing custom exceptions in an interoperable way
in Axis 1.2.1. I've read previous mailing list messages and looked at
the "samples/faults" files but haven't got very far. I've been unable to
get any custom data into the "detail" section of the fault.
> 
> Can someone please clarify:
> 
> 1. What should my exception look like - does it extend Exception,
RemoteException or ApacheFault? Does it need to be Serializable? Does
Axis support the JAX-RPC way of having exceptions as immutable beans
(constructors for setting properties, getters for reading, no setters)?
> 2. What should my service signature look like - simply "throws
MyCustomException"?
> 3. What extra needs to go into my server-config.wsdd - I've tried
adding an operation section with a fault, and a typeMapping.
> 4. I have lots of details of my custom fault in my wsdl, but if we
don't use wsdl2java then Axis won't actually use that, right?
> 
> Thanks,
> 
> Chris Nappin
> Technical Architect
> 
> ABM United Kingdom Limited
> Telephone: +44 (0) 115 977 6999
> Facsimile: +44 (0) 115 977 6850
> Web: http://www.abm-uk.com
> 
> ABM for Intelligent Solutions
> 
> 
> CONFIDENTIALITY & PRIVILEGE NOTICE
> This e-mail is confidential to its intended recipient. It may also be
privileged. Neither the confidentiality nor any privilege attaching to
this e-mail is waived lost or destroyed by reason that it has been
mistakenly transmitted to a person or entity other than its intended
recipient. If you are not the intended recipient please notify us
immediately by telephone or fax at the numbers provided above or e-mail
by Reply To Author and return the printed e-mail to us by post at our
expense. We believe, but do not warrant, that this e-mail and any
attachments are virus-free, but you should check. We may monitor traffic
data of both business and personal e-mails. We are not liable for any
opinions expressed by the sender where this is a non-business e-mail. If
you do not receive all the message, or if you have difficulty with the
transmission, please telephone us immediately.
> 
> 
> CONFIDENTIALITY & PRIVILEGE NOTICE
> 
> This e-mail is confidential to its intended recipient. It may also be
privileged. Neither the confidentiality nor any privilege attaching to
this e-mail is waived lost or destroyed by reason that it has been
mistakenly transmitted to a person or entity other than its intended
recipient. If you are not the intended recipient please notify us
immediately by telephone or fax at the numbers provided above or e-mail
by Reply To Author and return the printed e-mail to us by post at our
expense. We believe, but do not warrant, that this e-mail and any

Re: [axis2] Problem : Provider null could not be instantiated

[Davanum Srinivas]

Could you please log a bug? along with info on how you deployed it in
your servlet container?

thanks,
dims

On 8/26/05, Johan Andersson <[EMAIL PROTECTED]> wrote:
> Hello,
> 
> I've recently started to test and evaluate Axis2.
> 
> I wrote a wsdl and ran it through WSDL2Java, made some modifications to the 
> skeleton code,
> built the .aar archive as detailed by the axis2 documentation and deployed 
> the service.
> 
> The service is correctly deployed as far as I can tell (shows up in listing 
> without errors).
> HappyAxis page is, well.., happy =)
> 
> Still the server is dumping with the (server-side) exception included below.
> 
> I had a similar problem on the client side which I cured with a 
> System.setProperty("javax.xml.stream.XMLInputFactory", 
> "com.bea.xml.stream.MXParserFactory");
> 
> Doing the same server-side (-Djavax...) on Tomcat 4.1 OR Websphere 6 does not 
> work.
> 
> Should not this work out of the box without fiddling around with setting 
> system properties in the JVM?
> 
> I am clueless how to procede, please help.
> 
> Also I cannot find any information of the intended target platform or java 
> version for Axis2, is it Java 1.4 or 1.5?
> 
> Thank you in advance and best regards,
> 
> Johan
> 
> 
> 
> 2005-08-26 11:22:40 StandardWrapperValve[AxisServlet]: Servlet.service() for 
> servlet AxisServlet threw exception
> org.apache.axis2.AxisFault: Provider null could not be instantiated: 
> java.lang.NullPointerException; nested exception is:
> javax.xml.stream.FactoryConfigurationError: Provider null could not 
> be instantiated: java.lang.NullPointerException
> at 
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:137)
> at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:169)
> at 
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:206)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:716)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:809)
> at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:200)
> at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:146)
> at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:209)
> at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
> at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
> at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
> at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:144)
> at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
> at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
> at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
> at 
> org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358)
> at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)
> at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
> at 
> org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:118)
> at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
> at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:116)
> at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
> at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
> at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
> at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:127)
> at 
> org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
> at 
> org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
> at 
> org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
> at 
> org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:152)
> at 
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
> at 
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
> at 
> org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
> at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
> at java.lang.Thread.run(Thread.java:534)
> Caused by: javax.xml.stream.Factor

Re: AW: Wsdl2Java and no Internet-Connection (with 1.1 ok, with 1.2.1 exception): An error occurred trying to resolve schema referenced at...

[Scott Lamb]

I've also encountered this problem. We've use wsdl2java and have a  
sometimes-flakey Internet connection. Some machines have no  
connection at all.


On 26 Aug 2005, at 01:20, Peter Koch wrote:
(quoting John Kaputin)
A possible approach might be to add something to the WSDL4J API to  
allow an
application such as Axis to configure WSDL4J to ignore specified  
URLs when

resolving schemas (e.g. to ignore the standard schema URLs like
http://schemas.xmlsoap.org/soap/encoding).


I don't know that this helps. There still are other schemas that will  
need to be resolved. It's just trying to download the .xsds for all  
these URLs, right? Isn't this the problem XML Catalog exists to solve?




Regards,
Scott

--
Scott Lamb 

Re: basic authentication

[Guy Rixon]

Hi,

all my code is for the digital-signature mode of WSS4J. But the project's own
site has some deployment examples for UsernameToken.  See

  http://ws.apache.org/wss4j/

and

  http://ws.apache.org/wss4j/axis.html

Cheers,
Guy

On Fri, 26 Aug 2005, Plorks mail wrote:

>
>
> Hi Guy
>
> Thanks fr getting back to me.  Do you haveor can you lead me to an WSS4J
> example ?
>
> Thanks for your help
>
>
>
>
>
>
> >From: Guy Rixon <[EMAIL PROTECTED]>
> >Reply-To: axis-user@ws.apache.org
> >To: axis-user@ws.apache.org
> >Subject: Re: basic authentication
> >Date: Fri, 26 Aug 2005 14:47:05 +0100 (BST)
> >
> >If you are able to change the WSDL contract, then you can indeed include
> >the
> >username and password in the SOAP body. Just put them in a message part,
> >like
> >any other parameter.
> >
> >If you want to put username and password in the SOAP header, then you can
> >use
> >the UsernameToken mode of WSS4J to be compatible with the WS-Security
> >standard; or you can invent your own header if you don't have to be
> >standard
> >or interoperable. Using WSS4J is probably better.
> >
> >On Fri, 26 Aug 2005, Plorks mail wrote:
> >
> > > hi all
> > >
> > > i'm currntly getting username and password using basic authentication in
> >my
> > > web service.
> > >
> > > we are using a product that doesn't support basic authentaication in the
> > > http header, so now i have to re-write my web service.  Can anyone
> >suggest
> > > an alternative way to do this?
> > >
> > > Can i set the username and password in the SOAP Envelope/body?
> > >
> > > Thsi is the code i'm curently using
> > > String headerAuth =
> > > (String)msgContext.getProperty(HTTPConstants.HEADER_AUTHORIZATION);
> > >
> > > if (headerAuth != null)
> > > {
> > >headerAuth = headerAuth.trim();
> > > }
> > >
> > > if (headerAuth != null && headerAuth.startsWith("Basic "))
> > > {
> > > int i;
> > >
> > > headerAuth = new String(Base64.decode(headerAuth.substring(6)));
> > >
> > > String [] userNamePassword = headerAuth.split(":");
> > >
> > > userName = userNamePassword[0];
> > > password = userNamePassword[1];
> > > }
> > >
> > > thanks for  any help
> > >
> > > _
> > > Express yourself instantly with MSN Messenger! Download today - it's
> >FREE!
> > > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> > >
> >
> >Guy Rixon[EMAIL PROTECTED]
> >Institute of Astronomy   Tel: +44-1223-337542
> >Madingley Road, Cambridge, UK, CB3 0HA   Fax: +44-1223-337523
>
> _
> Winks & nudges are here - download MSN Messenger 7.0 today!
> http://messenger.msn.co.uk
>

Guy Rixon   [EMAIL PROTECTED]
Institute of Astronomy  Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA  Fax: +44-1223-337523

Re: Axis 1.2.1 not calling my class!

[Javier Gonzalez]

Jeff,

thank you very much! Turns out that my handler was ok, but I wasn't
doing the configuration part right. Once I properly inserted the
handler in the request flow it worked.

Thanks again,

Javier.

On 8/25/05, Jeff Greif <[EMAIL PROTECTED]> wrote:
> Read the user guide.  It explains how to put the handler in the "request
> flow" using the deployment descriptor (in a .wsdd file).
> 
> Jeff
> 
> Javier Gonzalez wrote:
> 
> >Jeff,
> >
> >thanks for your reply. I was thinking that I needed a Handler, too,
> >but when it comes to handlers the documentation is pretty scant.
> >
> >Do you know how to put the handler before the axis engine drops my
> >message as "not understood"?
> >
> >thanks again
> >
> >On 8/25/05, Jeff Greif <[EMAIL PROTECTED]> wrote:
> >
> >
> >>I believe, but am not certain, that some Handler must remove any headers
> >>marked "mustUnderstand=1".  This may have to be done before the pivot
> >>(that is before the implementation method is called in the server).  I
> >>am not aware of any way to mark a header element as processed (but such
> >>a way might exist nonetheless).
> >>
> >>Jeff
> >>
> >>Javier Gonzalez wrote:
> >>
> >>
> >>
> >>>Hi,
> >>>
> >>>I have a message service over axis 1.2.1, java 1.5, tomcat 5.5.
> >>>
> >>>But it seems like it isn't calling my published class at all - thus my
> >>>code that marks mustUnderstand=1 HeaderElements as processed never
> >>>gets executed, and the message is rejected with "didn't understand
> >>>MustUnderstand headers".
> >>>
> >>>The service is published like this:
> >>>
> >>> >>>use="literal">
> >>> 
> >>>  >>>value="my.package.mms.mm7receiver.MessageService"/>
> >>> 
> >>> <... class' own parameters ...>
> >>>
> >>>
> >>>How do I tell Axis that I understand the mustUnderstand header so it
> >>>will let the message through?
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
> >
> 
> 


-- 
Javier Gonzalez Nicolini

Re: basic authentication

[Plorks mail]

Hi Guy

Thanks fr getting back to me.  Do you haveor can you lead me to an WSS4J 
example ?


Thanks for your help







From: Guy Rixon <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: basic authentication
Date: Fri, 26 Aug 2005 14:47:05 +0100 (BST)

If you are able to change the WSDL contract, then you can indeed include 
the
username and password in the SOAP body. Just put them in a message part, 
like

any other parameter.

If you want to put username and password in the SOAP header, then you can 
use

the UsernameToken mode of WSS4J to be compatible with the WS-Security
standard; or you can invent your own header if you don't have to be 
standard

or interoperable. Using WSS4J is probably better.

On Fri, 26 Aug 2005, Plorks mail wrote:

> hi all
>
> i'm currntly getting username and password using basic authentication in 
my

> web service.
>
> we are using a product that doesn't support basic authentaication in the
> http header, so now i have to re-write my web service.  Can anyone 
suggest

> an alternative way to do this?
>
> Can i set the username and password in the SOAP Envelope/body?
>
> Thsi is the code i'm curently using
> String headerAuth =
> (String)msgContext.getProperty(HTTPConstants.HEADER_AUTHORIZATION);
>
> if (headerAuth != null)
> {
>headerAuth = headerAuth.trim();
> }
>
> if (headerAuth != null && headerAuth.startsWith("Basic "))
> {
> int i;
>
> headerAuth = new String(Base64.decode(headerAuth.substring(6)));
>
> String [] userNamePassword = headerAuth.split(":");
>
> userName = userNamePassword[0];
> password = userNamePassword[1];
> }
>
> thanks for  any help
>
> _
> Express yourself instantly with MSN Messenger! Download today - it's 
FREE!

> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>

Guy Rixon   [EMAIL PROTECTED]
Institute of Astronomy  Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA  Fax: +44-1223-337523


_
Winks & nudges are here - download MSN Messenger 7.0 today! 
http://messenger.msn.co.uk

RE: Little Help for a Newbie?

[John, Anil]

Tim,

The issue that you are running into is very expected in that there
really is no direct mapping between certain language specific artifacts
and XML Schema.

A way around this is to first define what a Polygon is in XML Schema,
generate the appropriate WSDL and go in the other direction with
WSDL2Java. Then you can pump in the data that is used to generate your
polygon into the service stub that is generated.

You may want to look for tutorials on Top Down / WSDL First design of
web services. There are some on the Eclipse site and some excellent ones
were given at JavaOne, if you have access to some of the slide decks.

Regards,

- Anil

-Original Message-
From: Bish, Tim [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 25, 2005 4:28 PM
To: axis-user@ws.apache.org
Subject: Little Help for a Newbie?

Howdy

I'm pretty new to all this so I hope this isn't to dumb of a question.
I'm trying to create a web service for our existing system, and one of
our interfaces uses a class that has a java.awt.polygon in it.  When I
run Java2Wsdl on the files I get this error

05 4:13:47 PM org.apache.axis.wsdl.fromJava.Types isBeanCompatible he
class java.awt.Polygon is defined in a java or javax package and cannot
be converted into an xml e.  An xml schema anyType will be used to
define this class in the wsdl file.

What is this telling me, why are java or javax packages not convertible
to XML?


-
Timothy A. Bish
Sensis Corporation
5717 Enterprise Parkway
East Syracuse, NY 13057
Phone: (315) 634-3027
[EMAIL PROTECTED]
-

Re: basic authentication

[Guy Rixon]

If you are able to change the WSDL contract, then you can indeed include the
username and password in the SOAP body. Just put them in a message part, like
any other parameter.

If you want to put username and password in the SOAP header, then you can use
the UsernameToken mode of WSS4J to be compatible with the WS-Security
standard; or you can invent your own header if you don't have to be standard
or interoperable. Using WSS4J is probably better.

On Fri, 26 Aug 2005, Plorks mail wrote:

> hi all
>
> i'm currntly getting username and password using basic authentication in my
> web service.
>
> we are using a product that doesn't support basic authentaication in the
> http header, so now i have to re-write my web service.  Can anyone suggest
> an alternative way to do this?
>
> Can i set the username and password in the SOAP Envelope/body?
>
> Thsi is the code i'm curently using
> String headerAuth =
> (String)msgContext.getProperty(HTTPConstants.HEADER_AUTHORIZATION);
>
> if (headerAuth != null)
> {
>headerAuth = headerAuth.trim();
> }
>
> if (headerAuth != null && headerAuth.startsWith("Basic "))
> {
> int i;
>
> headerAuth = new String(Base64.decode(headerAuth.substring(6)));
>
> String [] userNamePassword = headerAuth.split(":");
>
> userName = userNamePassword[0];
> password = userNamePassword[1];
> }
>
> thanks for  any help
>
> _
> Express yourself instantly with MSN Messenger! Download today - it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>

Guy Rixon   [EMAIL PROTECTED]
Institute of Astronomy  Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA  Fax: +44-1223-337523

RE: [Axis1] Axis Memory Leak

[Hoying, Ken]

Name: org/apache/xerces/impl/Version.class
Comment: Xerces-J 2.6.2 
Implementation-Title: org.apache.xerces.impl.Version
Implementation-Version: 2.6.2
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xerces2-j/

Name: org/xml/sax/
Comment: based on xml-commons external 1.2.01
Specification-Title: Simple API for XML
Specification-Vendor: David Megginson
Specification-Version: 2.0.1
Implementation-Title: org.xml.sax
Implementation-Version: 2.0.1
Implementation-Vendor: David Megginson
Implementation-URL: http://www.saxproject.org/

Name: org/w3c/dom/
Comment: based on xml-commons external 1.2.01
Specification-Title: Document Object Model, Level 2 Core
Specification-Vendor: World Wide Web Consortium
Specification-Version: 1.0
Implementation-Title: org.w3c.dom
Implementation-Version: 1.0
Implementation-Vendor: World Wide Web Consortium
Implementation-URL: http://www.w3c.org/DOM/

Name: javax/xml/parsers/
Comment: based on xml-commons external 1.2.01
Specification-Title: Java API for XML Processing
Specification-Version: 1.2
Specification-Vendor: Sun Microsystems Inc.
Implementation-Title: javax.xml.parsers
Implementation-Version: 1.2.01
Implementation-Vendor: Sun Microsystems Inc.
Implementation-URL: http://java.sun.com/xml/jaxp.html

Name: javax/xml/transform/
Comment: based on xml-commons external 1.2.01
Specification-Title: Java API for XML Processing
Specification-Version: 1.2
Specification-Vendor: Sun Microsystems Inc.
Implementation-Title: javax.xml.transform
Implementation-Version: 1.2.01
Implementation-Vendor: Sun Microsystems Inc.
Implementation-URL: http://java.sun.com/xml/jaxp.html

Name: org/apache/xerces/xni/
Comment: Xerces Native Interface
Specification-Title: Xerces Native Interface
Specification-Version: 1.1
Specification-Vendor: Apache Software Foundation
Implementation-Title: org.apache.xerces.xni
Implementation-Version: 1.1
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xerces2-j/

Manifest-Version: 1.0
Created-By: 1.3.1 (IBM Corporation)
Main-Class: org.apache.xalan.xslt.Process
Class-Path: xercesImpl.jar xml-apis.jar

Name: org/apache/xalan
Comment: Main Xalan engine implementing TrAX/JAXP
Specification-Title: Java API for XML Processing
Specification-Vendor: Sun Microsystems Inc.
Specification-Version: 1.2
Implementation-Title: org.apache.xalan
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xalan-j/dist/

Name: org/apache/xpath
Comment: XPath engine
Implementation-Title: org.apache.xpath
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xalan-j/dist/

Name: org/apache/xml
Comment: DTM implementation and utilities
Implementation-Title: org.apache.xml
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xalan-j/dist/

Name: org/apache/xalan/xsltc
Comment: Main XSLTC engine implementing TrAX/JAXP
Specification-Title: Java API for XML Processing
Specification-Vendor: Sun Microsystems Inc.
Specification-Version: 1.2
Implementation-Title: org.apache.xalan.xsltc
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://xml.apache.org/xalan-j/dist/

Name: runtime
Comment: Runtime component of JCup 
Specification-Title: Runtime component of JCup
Specification-Vendor: Princeton University 
Specification-Version: 0.10k 
Implementation-Title: runtime 
Implementation-Version: 2.6.0
Implementation-Vendor: Princeton University  
Implementation-URL: http://www.cs.princeton.edu/~appel/modern/java/CUP/ 

Name: org/apache/bcel
Comment: Byte Code Engineering Library 
Specification-Title: Byte Code Engineering Library 
Specification-Vendor: Markus Dahm 
Specification-Version: 5.0 rc1 
Implementation-Title: org.apache.bcel
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://jakarta.apache.org/bcel

Name: org/apache/regexp
Comment: Java Regular Expression package 
Specification-Title: Java Regular Expression package 
Specification-Vendor: Apache Software Foundation 
Specification-Version: 1.2
Implementation-Title: org.apache.regexp
Implementation-Version: 2.6.0
Implementation-Vendor: Apache Software Foundation
Implementation-URL: http://jakarta.apache.org/regexp

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, August 26, 2005 9:35 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis1] Axis Memory Leak


Which version of xerces are u using?

-- dims

On 8/26/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
> We are currently running out of memory in production after about three days. 
> However, this is not our only memory leak.  We are also working on revolving 
> a leak we seem to be having in XALAN with a transform.  The XALAN leak is 
> definitely the larger of the two. Curre

Re: [Axis1] Axis Memory Leak

[Davanum Srinivas]

Which version of xerces are u using?

-- dims

On 8/26/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
> We are currently running out of memory in production after about three days. 
> However, this is not our only memory leak.  We are also working on revolving 
> a leak we seem to be having in XALAN with a transform.  The XALAN leak is 
> definitely the larger of the two. Currently, we are avoiding the problem by 
> restarting the server daily.  However, this is not an acceptable solution for 
> the long term.
> 
> -Original Message-
> From: Benjamin Marcel Flohr [mailto:[EMAIL PROTECTED]
> Sent: Friday, August 26, 2005 9:22 AM
> To: axis-user@ws.apache.org; [EMAIL PROTECTED]
> Subject: AW: [Axis1] Axis Memory Leak
> 
> 
> Hello,
> what is the effect of this memory leak. We are using Axis 1.0 in production 
> without having any problems.
> Can you tell me more ?
> thanx, benjamin
> 
> -Ursprüngliche Nachricht-
> Von: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Gesendet: Freitag, 26. August 2005 15:18
> An: axis-user@ws.apache.org
> Betreff: Re: [Axis1] Axis Memory Leak
> 
> 
> Please switch to Axis 1.2.1. No you can't replace the jar. you need to
> regen the server and client. "Axis 1.0 jar used on a client work with
> the Axis 1.2.1 server" may work but it depends if there was a bug in
> the exact scenario you are using.
> 
> -- dims
> 
> On 8/26/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > We are having issues with a slow memory leak that is resulting in
> > OutOfMemory errors in our production environment after about 3 days time. > 
> > We are currently using Axis 1.0.  After profiling the application with
> > OptimizeIt, it appears that there is a memory leak that seems to be tied to
> > the following:
> >
> >
> > org.apache.axis.Message.getSOAPEnvelope()
> >
> > Can anyone confirm that this was a known memory leak and it is have been
> > fixed in a subsequent release of Axis?
> >
> > I am also curious to know what implications would arise from switching to
> > Axis 1.2.1.  Can I just replace the jar or do I need to regen class and
> > clients? Does the Axis 1.0 jar used on a client work with the Axis 1.2.1 on
> > the server?
> >
> > Thank you,
> > Ken Hoying
> >
> > **
> >  This message, including any attachments, contains confidential information
> > intended for a specific individual and purpose, and is protected by law. If
> > you are not the intended recipient, please contact sender immediately by
> > reply e-mail and destroy all copies. You are hereby notified that any
> > disclosure, copying, or distribution of this message, or the taking of any
> > action based on it, is strictly prohibited.
> >  TIAA-CREF
> > **
> >
> 
> 
> --
> Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform
> 
> 
> **
> This message, including any attachments, contains confidential information 
> intended for a specific individual and purpose, and is protected by law.  If 
> you are not the intended recipient, please contact sender immediately by 
> reply e-mail and destroy all copies.  You are hereby notified that any 
> disclosure, copying, or distribution of this message, or the taking of any 
> action based on it, is strictly prohibited.
> TIAA-CREF
> **
> 
> 


-- 
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform

RE: [Axis1] Axis Memory Leak

[Hoying, Ken]

We are currently running out of memory in production after about three days. 
However, this is not our only memory leak.  We are also working on revolving a 
leak we seem to be having in XALAN with a transform.  The XALAN leak is 
definitely the larger of the two. Currently, we are avoiding the problem by 
restarting the server daily.  However, this is not an acceptable solution for 
the long term.

-Original Message-
From: Benjamin Marcel Flohr [mailto:[EMAIL PROTECTED]
Sent: Friday, August 26, 2005 9:22 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: AW: [Axis1] Axis Memory Leak


Hello,
what is the effect of this memory leak. We are using Axis 1.0 in production 
without having any problems.
Can you tell me more ?
thanx, benjamin

-Ursprüngliche Nachricht-
Von: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 26. August 2005 15:18
An: axis-user@ws.apache.org
Betreff: Re: [Axis1] Axis Memory Leak


Please switch to Axis 1.2.1. No you can't replace the jar. you need to
regen the server and client. "Axis 1.0 jar used on a client work with
the Axis 1.2.1 server" may work but it depends if there was a bug in
the exact scenario you are using.

-- dims

On 8/26/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
>  
>  
> 
> We are having issues with a slow memory leak that is resulting in
> OutOfMemory errors in our production environment after about 3 days time. > 
> We are currently using Axis 1.0.  After profiling the application with
> OptimizeIt, it appears that there is a memory leak that seems to be tied to
> the following: 
>  
> 
> org.apache.axis.Message.getSOAPEnvelope() 
> 
> Can anyone confirm that this was a known memory leak and it is have been
> fixed in a subsequent release of Axis? 
> 
> I am also curious to know what implications would arise from switching to
> Axis 1.2.1.  Can I just replace the jar or do I need to regen class and
> clients? Does the Axis 1.0 jar used on a client work with the Axis 1.2.1 on
> the server? 
> 
> Thank you, 
> Ken Hoying 
>  
> **
>  This message, including any attachments, contains confidential information
> intended for a specific individual and purpose, and is protected by law. If
> you are not the intended recipient, please contact sender immediately by
> reply e-mail and destroy all copies. You are hereby notified that any
> disclosure, copying, or distribution of this message, or the taking of any
> action based on it, is strictly prohibited.
>  TIAA-CREF
> **
>  


-- 
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform


**
This message, including any attachments, contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, please contact sender immediately by reply 
e-mail and destroy all copies.  You are hereby notified that any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.
TIAA-CREF
**

basic authentication

[Plorks mail]

hi all

i'm currntly getting username and password using basic authentication in my 
web service.


we are using a product that doesn't support basic authentaication in the 
http header, so now i have to re-write my web service.  Can anyone suggest 
an alternative way to do this?


Can i set the username and password in the SOAP Envelope/body?

Thsi is the code i'm curently using
String headerAuth = 
(String)msgContext.getProperty(HTTPConstants.HEADER_AUTHORIZATION);


if (headerAuth != null)
{
  headerAuth = headerAuth.trim();
}

if (headerAuth != null && headerAuth.startsWith("Basic "))
{
int i;

headerAuth = new String(Base64.decode(headerAuth.substring(6)));

String [] userNamePassword = headerAuth.split(":");

userName = userNamePassword[0];
password = userNamePassword[1];
}

thanks for  any help

_
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

RE: [Axis1] Axis Memory Leak

[Hoying, Ken]

Regenerating the clients is going to be very difficult.  We have several spread 
throughout the organization and already in production. I am disappointed to 
hear that the client version is so tightly integrated to the server version.  
Seems like this sort of defeats the goals and benefits of a web service based 
SOA.

I will start taking a look at making the switch, but can someone confirm that 
there was such a bug or leak that was addresses in the 1.2.1 version.  I would 
hate to make this change, especially due to the potentially large impact to the 
organization, if it does not fix the problem.

Thanks,
Ken

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Friday, August 26, 2005 9:18 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis1] Axis Memory Leak


Please switch to Axis 1.2.1. No you can't replace the jar. you need to
regen the server and client. "Axis 1.0 jar used on a client work with
the Axis 1.2.1 server" may work but it depends if there was a bug in
the exact scenario you are using.

-- dims

On 8/26/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
>  
>  
> 
> We are having issues with a slow memory leak that is resulting in
> OutOfMemory errors in our production environment after about 3 days time. > 
> We are currently using Axis 1.0.  After profiling the application with
> OptimizeIt, it appears that there is a memory leak that seems to be tied to
> the following: 
>  
> 
> org.apache.axis.Message.getSOAPEnvelope() 
> 
> Can anyone confirm that this was a known memory leak and it is have been
> fixed in a subsequent release of Axis? 
> 
> I am also curious to know what implications would arise from switching to
> Axis 1.2.1.  Can I just replace the jar or do I need to regen class and
> clients? Does the Axis 1.0 jar used on a client work with the Axis 1.2.1 on
> the server? 
> 
> Thank you, 
> Ken Hoying 
>  
> **
>  This message, including any attachments, contains confidential information
> intended for a specific individual and purpose, and is protected by law. If
> you are not the intended recipient, please contact sender immediately by
> reply e-mail and destroy all copies. You are hereby notified that any
> disclosure, copying, or distribution of this message, or the taking of any
> action based on it, is strictly prohibited.
>  TIAA-CREF
> **
>  


-- 
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform


**
This message, including any attachments, contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, please contact sender immediately by reply 
e-mail and destroy all copies.  You are hereby notified that any disclosure, 
copying, or distribution of this message, or the taking of any action based on 
it, is strictly prohibited.
TIAA-CREF
**

AW: [Axis1] Axis Memory Leak

[Benjamin Marcel Flohr]

Hello,
what is the effect of this memory leak. We are using Axis 1.0 in production 
without having any problems.
Can you tell me more ?
thanx, benjamin

-Ursprüngliche Nachricht-
Von: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 26. August 2005 15:18
An: axis-user@ws.apache.org
Betreff: Re: [Axis1] Axis Memory Leak


Please switch to Axis 1.2.1. No you can't replace the jar. you need to
regen the server and client. "Axis 1.0 jar used on a client work with
the Axis 1.2.1 server" may work but it depends if there was a bug in
the exact scenario you are using.

-- dims

On 8/26/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
>  
>  
> 
> We are having issues with a slow memory leak that is resulting in
> OutOfMemory errors in our production environment after about 3 days time. 
> We are currently using Axis 1.0.  After profiling the application with
> OptimizeIt, it appears that there is a memory leak that seems to be tied to
> the following: 
>  
> 
> org.apache.axis.Message.getSOAPEnvelope() 
> 
> Can anyone confirm that this was a known memory leak and it is have been
> fixed in a subsequent release of Axis? 
> 
> I am also curious to know what implications would arise from switching to
> Axis 1.2.1.  Can I just replace the jar or do I need to regen class and
> clients? Does the Axis 1.0 jar used on a client work with the Axis 1.2.1 on
> the server? 
> 
> Thank you, 
> Ken Hoying 
>  
> **
>  This message, including any attachments, contains confidential information
> intended for a specific individual and purpose, and is protected by law. If
> you are not the intended recipient, please contact sender immediately by
> reply e-mail and destroy all copies. You are hereby notified that any
> disclosure, copying, or distribution of this message, or the taking of any
> action based on it, is strictly prohibited.
>  TIAA-CREF
> **
>  


-- 
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform

[Axis1] Axis Memory Leak

[Hoying, Ken]

Title: [Axis1] Axis Memory Leak







We are having issues with a slow memory leak that is resulting in OutOfMemory errors in our production environment after about 3 days time.  We are currently using Axis 1.0.  After profiling the application with OptimizeIt, it appears that there is a memory leak that seems to be tied to the following:

org.apache.axis.Message.getSOAPEnvelope()


Can anyone confirm that this was a known memory leak and it is have been fixed in a subsequent release of Axis?


I am also curious to know what implications would arise from switching to Axis 1.2.1.  Can I just replace the jar or do I need to regen class and clients? Does the Axis 1.0 jar used on a client work with the Axis 1.2.1 on the server?

Thank you,

Ken Hoying




**
This message, including any attachments, contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, please contact sender immediately by reply e-mail and destroy all copies.  You are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
TIAA-CREF
**

Re: [Axis1] Axis Memory Leak

[Davanum Srinivas]

Please switch to Axis 1.2.1. No you can't replace the jar. you need to
regen the server and client. "Axis 1.0 jar used on a client work with
the Axis 1.2.1 server" may work but it depends if there was a bug in
the exact scenario you are using.

-- dims

On 8/26/05, Hoying, Ken <[EMAIL PROTECTED]> wrote:
>  
>  
> 
> We are having issues with a slow memory leak that is resulting in
> OutOfMemory errors in our production environment after about 3 days time. 
> We are currently using Axis 1.0.  After profiling the application with
> OptimizeIt, it appears that there is a memory leak that seems to be tied to
> the following: 
>  
> 
> org.apache.axis.Message.getSOAPEnvelope() 
> 
> Can anyone confirm that this was a known memory leak and it is have been
> fixed in a subsequent release of Axis? 
> 
> I am also curious to know what implications would arise from switching to
> Axis 1.2.1.  Can I just replace the jar or do I need to regen class and
> clients? Does the Axis 1.0 jar used on a client work with the Axis 1.2.1 on
> the server? 
> 
> Thank you, 
> Ken Hoying 
>  
> **
>  This message, including any attachments, contains confidential information
> intended for a specific individual and purpose, and is protected by law. If
> you are not the intended recipient, please contact sender immediately by
> reply e-mail and destroy all copies. You are hereby notified that any
> disclosure, copying, or distribution of this message, or the taking of any
> action based on it, is strictly prohibited.
>  TIAA-CREF
> **
>  


-- 
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform

Re: How to throw custom exceptions?

[Davanum Srinivas]

check if axis.development.system helps
(http://ws.apache.org/axis/java/security.html)

-- dims

On 8/26/05, Chris Nappin <[EMAIL PROTECTED]> wrote:
> And if I add further details from the auto-generated deploy.wsdd to my 
> server-config.wsdd, I get proper local names and namespaces on my custom 
> tags. However I can't stop Axis adding the exceptionName and hostname.
> 
> Any folks seen this please? I seem to be having a conversation with myself - 
> very worrying!  ;-)
> 
> -Original Message-
> From: Chris Nappin [mailto:[EMAIL PROTECTED]
> Sent: 26 August 2005 09:51
> To: axis-user@ws.apache.org
> Subject: RE: How to throw custom exceptions?
> 
> Okay, I've been trying to get a bit further by using wsdl2java to generate 
> the exceptions for me, so it can put in all the Axis-specifics.
> 
> I have defined a custom in my wsdl as follows:
> 
> 
>
> 
>   nillable="false"/>
> 
>
>   
> 
> When running my service Axis returns the following response:
> 
> 
>  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> 
> 
> soapenv:Server.generalException
> 
> 
> 
> Test!
> 
>  xmlns:ns1="http://xml.apache.org/axis/";>com.test.MyFirstException
>  xmlns:ns2="http://xml.apache.org/axis/";>PC55-ABMUK
> 
> 
> 
> 
> 
> This is a step forward, as I now have custom fields (text) in the "detail" 
> block. However, is there any way of stopping Axis generating the 
> "exceptionName" and "hostname" fields?
> 
> Cheers,
> 
>   Chris.
> 
> 
> From: Chris Nappin [mailto:[EMAIL PROTECTED]
> Sent: 25 August 2005 16:42
> To: axis-user@ws.apache.org
> Subject: How to throw custom exceptions?
> 
> 
> Hi,
> 
>  I'm having trouble throwing custom exceptions in an interoperable way in 
> Axis 1.2.1. I've read previous mailing list messages and looked at the 
> "samples/faults" files but haven't got very far. I've been unable to get any 
> custom data into the "detail" section of the fault.
> 
> Can someone please clarify:
> 
> 1. What should my exception look like - does it extend Exception, 
> RemoteException or ApacheFault? Does it need to be Serializable? Does Axis 
> support the JAX-RPC way of having exceptions as immutable beans (constructors 
> for setting properties, getters for reading, no setters)?
> 2. What should my service signature look like - simply "throws 
> MyCustomException"?
> 3. What extra needs to go into my server-config.wsdd - I've tried adding an 
> operation section with a fault, and a typeMapping.
> 4. I have lots of details of my custom fault in my wsdl, but if we don't use 
> wsdl2java then Axis won't actually use that, right?
> 
> Thanks,
> 
> Chris Nappin
> Technical Architect
> 
> ABM United Kingdom Limited
> Telephone: +44 (0) 115 977 6999
> Facsimile: +44 (0) 115 977 6850
> Web: http://www.abm-uk.com
> 
> ABM for Intelligent Solutions
> 
> 
> CONFIDENTIALITY & PRIVILEGE NOTICE
> This e-mail is confidential to its intended recipient. It may also be 
> privileged. Neither the confidentiality nor any privilege attaching to this 
> e-mail is waived lost or destroyed by reason that it has been mistakenly 
> transmitted to a person or entity other than its intended recipient. If you 
> are not the intended recipient please notify us immediately by telephone or 
> fax at the numbers provided above or e-mail by Reply To Author and return the 
> printed e-mail to us by post at our expense. We believe, but do not warrant, 
> that this e-mail and any attachments are virus-free, but you should check. We 
> may monitor traffic data of both business and personal e-mails. We are not 
> liable for any opinions expressed by the sender where this is a non-business 
> e-mail. If you do not receive all the message, or if you have difficulty with 
> the transmission, please telephone us immediately.
> 
> 
> CONFIDENTIALITY & PRIVILEGE NOTICE
> 
> This e-mail is confidential to its intended recipient. It may also be 
> privileged. Neither the confidentiality nor any privilege attaching to this 
> e-mail is waived lost or destroyed by reason that it has been mistakenly 
> transmitted to a person or entity other than its intended recipient. If you 
> are not the intended recipient please notify us immediately by telephone or 
> fax at the numbers provided above or e-mail by Reply To Author and return the 
> printed e-mail to us by post at our expense. We believe, but do not warrant, 
> that this e-mail and any attachments are virus-free, but you should check. We 
> may monitor traffic data of both business and personal e-mails. We are not 
> liable for any opinions expressed by the sender where this is a non-business 
> e-mail. If you do not receive all the message, or if you have diff

RE: How to throw custom exceptions?

[Chris Nappin]

And if I add further details from the auto-generated deploy.wsdd to my 
server-config.wsdd, I get proper local names and namespaces on my custom tags. 
However I can't stop Axis adding the exceptionName and hostname.

Any folks seen this please? I seem to be having a conversation with myself - 
very worrying!  ;-)

-Original Message-
From: Chris Nappin [mailto:[EMAIL PROTECTED] 
Sent: 26 August 2005 09:51
To: axis-user@ws.apache.org
Subject: RE: How to throw custom exceptions?

Okay, I've been trying to get a bit further by using wsdl2java to generate the 
exceptions for me, so it can put in all the Axis-specifics.

I have defined a custom in my wsdl as follows:


   

 

   
  

When running my service Axis returns the following response:


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>


soapenv:Server.generalException



Test!

http://xml.apache.org/axis/";>com.test.MyFirstException
http://xml.apache.org/axis/";>PC55-ABMUK





This is a step forward, as I now have custom fields (text) in the "detail" 
block. However, is there any way of stopping Axis generating the 
"exceptionName" and "hostname" fields?

Cheers,

  Chris.


From: Chris Nappin [mailto:[EMAIL PROTECTED] 
Sent: 25 August 2005 16:42
To: axis-user@ws.apache.org
Subject: How to throw custom exceptions?


Hi,

  I'm having trouble throwing custom exceptions in an interoperable way in Axis 
1.2.1. I've read previous mailing list messages and looked at the 
"samples/faults" files but haven't got very far. I've been unable to get any 
custom data into the "detail" section of the fault.

Can someone please clarify:

1. What should my exception look like - does it extend Exception, 
RemoteException or ApacheFault? Does it need to be Serializable? Does Axis 
support the JAX-RPC way of having exceptions as immutable beans (constructors 
for setting properties, getters for reading, no setters)?
2. What should my service signature look like - simply "throws 
MyCustomException"?
3. What extra needs to go into my server-config.wsdd - I've tried adding an 
operation section with a fault, and a typeMapping.
4. I have lots of details of my custom fault in my wsdl, but if we don't use 
wsdl2java then Axis won't actually use that, right?

Thanks, 

Chris Nappin
Technical Architect
 
ABM United Kingdom Limited
Telephone: +44 (0) 115 977 6999
Facsimile: +44 (0) 115 977 6850
Web: http://www.abm-uk.com
 
ABM for Intelligent Solutions

  
CONFIDENTIALITY & PRIVILEGE NOTICE
This e-mail is confidential to its intended recipient. It may also be 
privileged. Neither the confidentiality nor any privilege attaching to this 
e-mail is waived lost or destroyed by reason that it has been mistakenly 
transmitted to a person or entity other than its intended recipient. If you are 
not the intended recipient please notify us immediately by telephone or fax at 
the numbers provided above or e-mail by Reply To Author and return the printed 
e-mail to us by post at our expense. We believe, but do not warrant, that this 
e-mail and any attachments are virus-free, but you should check. We may monitor 
traffic data of both business and personal e-mails. We are not liable for any 
opinions expressed by the sender where this is a non-business e-mail. If you do 
not receive all the message, or if you have difficulty with the transmission, 
please telephone us immediately.

 
CONFIDENTIALITY & PRIVILEGE NOTICE

This e-mail is confidential to its intended recipient. It may also be 
privileged. Neither the confidentiality nor any privilege attaching to this 
e-mail is waived lost or destroyed by reason that it has been mistakenly 
transmitted to a person or entity other than its intended recipient. If you are 
not the intended recipient please notify us immediately by telephone or fax at 
the numbers provided above or e-mail by Reply To Author and return the printed 
e-mail to us by post at our expense. We believe, but do not warrant, that this 
e-mail and any attachments are virus-free, but you should check. We may monitor 
traffic data of both business and personal e-mails. We are not liable for any 
opinions expressed by the sender where this is a non-business e-mail. If you do 
not receive all the message, or if you have difficulty with the transmission, 
please telephone us immediately.


 
CONFIDENTIALITY & PRIVILEGE NOTICE

This e-mail is confidential to its intended recipient. It may also be 
privileged. Neither the confidentiality nor any privilege attaching to this 
e-mail is waived lost or destroyed by reason that it has been mistakenly 
transmitted to a person or entity other than its intended recipient. If you are 
not the intended recipient please notif

Re: Disabling multirefs on client side

[Davanum Srinivas]

add a client-config.wsdd and add it in global parameters.

-- dims

On 8/26/05, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote:
> Hi All,
> Is there any way that I could disable multiref on client side.
> 
> I found setDoMultiRefs in SerializationContext. However I am not sure how 
> to use this on cliet
> side. I looked in samples as well as in tests but could not find any code 
> that deals with clients.
> 
> Thanks in advance for your help,
> 
> Samisa...
> 
> 
> 
> 
> Start your day with Yahoo! - make it your home page
> http://www.yahoo.com/r/hs
> 
> 


-- 
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform

Re: soap:headers and explicit service context

[Hans Planting (CWEU-USERS/CWNL)]

Check JAX-RPC 1.1 #11.2 and WSDL 1.1 Example 3.

Change your wsdl to something like:


   
   *
   *



   





   
   Reset a user's password
   
   
   
   
   


   
   
   
   *
   *
   
   
   
   
   
   

   

   

   






I'm not sure I follow, given these fragments, why don't any of the
headers specified in the binding appear in the method signature ? Is
this another JAX-RPC snafu ?

Cheers
Simon

   
   
   
   
   
   
   
   
   
   
   
   
   
   

   


   
   Reset a user's password
   
   
   
   
   


   
   
   
   
   
   
   
   
   
   
   

   

   

   



-Original Message-
From: Hans Planting (CWEU-USERS/CWNL)
[mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 24, 2005 2:25 AM

To: axis-user@ws.apache.org
Subject: Re: soap:headers and explicit service context

Hi,

 


But it doesn't expose these headers are part of the method signature.
   




This is what I thought as well, hence my question, but it turns out my
wsdl was incorrect.

If you want your soap:headers be part of the method signature (explicit
service context) then as far as I understand it you need to set the part
attribute of the soap:header to a wsdl:part in the wsdl:message that is
refered to by the wsdl:input/wsdl:output of the wsdl:operation.

If the part attribute refers to a part in a message not refered to by
the input or output of the message then the header parts will not be
part of the method signature and you need to write custom handlers in
order to deal with headers (implicit service context).

However there are still a couple of strange things I encountered when
using soap:headers in document/literal style documents:
- the parameters generated from the wsdl:input parts are wrapped in a
java object, while when not using headers they are not;
- when combining explicit and implicit soap:headers in one wsdl document
the wrapped java object mentioned above is not generated but is actually
refered to by the generated stub.

Regards,
Hans


 


But it doesn't expose these headers are part of the method signature.
You're left to call setHeader yourself (and therefore have to manualy 
copy over the element names & namespaces from the WSDL, which is error 
prone). I think I logged a bug for this a while back.


Cheers
Simon

-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 23, 2005 7:35 AM
To: axis-user@ws.apache.org
Subject: Re: soap:headers and explicit service context

If you set up the wsdl correctly, then the generated code has the 
addition java objects for the stuff in soap headers.


-- dims

On 8/23/05, Hans Planting (CWEU-USERS/CWNL) 
<[EMAIL PROTECTED]> wrote:



   


Hi there,

Is there support planned for explicit soap headers as described in 
JAX-RPC 1.1 chapter 11.2.2?
With explicit soap headers I'd expect Axis to append additional 
parameters for soap:headers following the service endpoint defined 
paramers in the remote method signature. Also no custom 
parsing/deserialization would need to be implemented.
Currently in order to process soap:headers you need to implement a 
handler or use the setHeader and getHeader methods in 
org.apache.axis.client.Stub and in both cases implement code to 
parse/deserialize the soap elements; Axis does not deserialize the 
contents of soap:headers to Java objects (correct me if I'm wrong - is
  

 




   


there a way to do this?).

Thanx!

Hans

  

 


--
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service 
Platform




   



 

Disabling multirefs on client side

[Samisa Abeysinghe]

Hi All,
Is there any way that I could disable multiref on client side.

I found setDoMultiRefs in SerializationContext. However I am not sure how 
to use this on cliet
side. I looked in samples as well as in tests but could not find any code that 
deals with clients.

Thanks in advance for your help,

Samisa...




Start your day with Yahoo! - make it your home page 
http://www.yahoo.com/r/hs 
 

Re: Support of other protocols

[Thilina Gunarathne]

You can also have a look at Axis2 project. Axis2 is based on StAX parsing and Axis2 supports MTOM.
 
~Thilina 
On 8/26/05, Guy Rixon <[EMAIL PROTECTED]> wrote:
On Thu, 25 Aug 2005, Scott Goldstein wrote:> Does Axis support other SOA protocols besides SOAP over HTTP?
> I have an application in which I'm sending large amounts of data and> the SAX parsing is leading to a performance problem.  I've heard in the> past that one way to solve this is to use an alternative protocol,
> though I don't recall the details of the solution.Changing the transport protocol won't make the parser go faster, of course.Presumably you're trying to avoid parsing the bulk data along with the SOAP
envelope. Have you tried using {MIME|DIME|MTOM} attachments? You could passXML in there and parse it separately from the envelope. That way, your SOAPengine doesn't take the parsing hit. Better, you could reformat the bulk data
to leave out the XML.Guy Rixon   [EMAIL PROTECTED]Institute of Astronomy  Tel: +44-1223-337542Madingley Road, Cambridge, UK, CB3 0HA  Fax: +44-1223-337523
-- "May the SourcE be with u" http://www.bloglines.com/blog/thilina  
http://webservices.apache.org/~thilina/ 

[axis2] Problem : Provider null could not be instantiated

[Johan Andersson]

Hello,

I've recently started to test and evaluate Axis2.

I wrote a wsdl and ran it through WSDL2Java, made some modifications to the 
skeleton code, 
built the .aar archive as detailed by the axis2 documentation and deployed the 
service.

The service is correctly deployed as far as I can tell (shows up in listing 
without errors). 
HappyAxis page is, well.., happy =)

Still the server is dumping with the (server-side) exception included below.

I had a similar problem on the client side which I cured with a 
System.setProperty("javax.xml.stream.XMLInputFactory", 
"com.bea.xml.stream.MXParserFactory");

Doing the same server-side (-Djavax...) on Tomcat 4.1 OR Websphere 6 does not 
work.

Should not this work out of the box without fiddling around with setting system 
properties in the JVM?

I am clueless how to procede, please help.

Also I cannot find any information of the intended target platform or java 
version for Axis2, is it Java 1.4 or 1.5?

Thank you in advance and best regards,

Johan



2005-08-26 11:22:40 StandardWrapperValve[AxisServlet]: Servlet.service() for 
servlet AxisServlet threw exception
org.apache.axis2.AxisFault: Provider null could not be instantiated: 
java.lang.NullPointerException; nested exception is: 
javax.xml.stream.FactoryConfigurationError: Provider null could not be 
instantiated: java.lang.NullPointerException
at 
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:137)
at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:169)
at 
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:716)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:809)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:200)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:146)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:209)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:144)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
at 
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2358)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:133)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at 
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:118)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:116)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:127)
at 
org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at 
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948)
at 
org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:152)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at 
org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.xml.stream.FactoryConfigurationError: Provider null could not 
be instantiated: java.lang.NullPointerException
at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:75)
at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:136)
at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
at 
javax.xml.stream.XMLOutputFactory.newInstance(XMLOutput

laszlo

[Plorks mail]

hi all

has anyone here experience of laszlo and xould help me out?

thanks

_
Be the first to hear what's new at MSN - sign up to our free newsletters! 
http://www.msn.co.uk/newsletters

Re: Support of other protocols

[Guy Rixon]

On Thu, 25 Aug 2005, Scott Goldstein wrote:

> Does Axis support other SOA protocols besides SOAP over HTTP?
> I have an application in which I'm sending large amounts of data and
> the SAX parsing is leading to a performance problem.  I've heard in the
> past that one way to solve this is to use an alternative protocol,
> though I don't recall the details of the solution.

Changing the transport protocol won't make the parser go faster, of course.
Presumably you're trying to avoid parsing the bulk data along with the SOAP
envelope. Have you tried using {MIME|DIME|MTOM} attachments? You could pass
XML in there and parse it separately from the envelope. That way, your SOAP
engine doesn't take the parsing hit. Better, you could reformat the bulk data
to leave out the XML.

Guy Rixon   [EMAIL PROTECTED]
Institute of Astronomy  Tel: +44-1223-337542
Madingley Road, Cambridge, UK, CB3 0HA  Fax: +44-1223-337523

RE: How to throw custom exceptions?

[Chris Nappin]

Okay, I've been trying to get a bit further by using wsdl2java to generate the 
exceptions for me, so it can put in all the Axis-specifics.

I have defined a custom in my wsdl as follows:


   

 

   
  

When running my service Axis returns the following response:


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>


soapenv:Server.generalException



Test!

http://xml.apache.org/axis/";>com.test.MyFirstException
http://xml.apache.org/axis/";>PC55-ABMUK





This is a step forward, as I now have custom fields (text) in the "detail" 
block. However, is there any way of stopping Axis generating the 
"exceptionName" and "hostname" fields?

Cheers,

  Chris.


From: Chris Nappin [mailto:[EMAIL PROTECTED] 
Sent: 25 August 2005 16:42
To: axis-user@ws.apache.org
Subject: How to throw custom exceptions?


Hi,

  I'm having trouble throwing custom exceptions in an interoperable way in Axis 
1.2.1. I've read previous mailing list messages and looked at the 
"samples/faults" files but haven't got very far. I've been unable to get any 
custom data into the "detail" section of the fault.

Can someone please clarify:

1. What should my exception look like - does it extend Exception, 
RemoteException or ApacheFault? Does it need to be Serializable? Does Axis 
support the JAX-RPC way of having exceptions as immutable beans (constructors 
for setting properties, getters for reading, no setters)?
2. What should my service signature look like - simply "throws 
MyCustomException"?
3. What extra needs to go into my server-config.wsdd - I've tried adding an 
operation section with a fault, and a typeMapping.
4. I have lots of details of my custom fault in my wsdl, but if we don't use 
wsdl2java then Axis won't actually use that, right?

Thanks, 

Chris Nappin
Technical Architect
 
ABM United Kingdom Limited
Telephone: +44 (0) 115 977 6999
Facsimile: +44 (0) 115 977 6850
Web: http://www.abm-uk.com
 
ABM for Intelligent Solutions

  
CONFIDENTIALITY & PRIVILEGE NOTICE
This e-mail is confidential to its intended recipient. It may also be 
privileged. Neither the confidentiality nor any privilege attaching to this 
e-mail is waived lost or destroyed by reason that it has been mistakenly 
transmitted to a person or entity other than its intended recipient. If you are 
not the intended recipient please notify us immediately by telephone or fax at 
the numbers provided above or e-mail by Reply To Author and return the printed 
e-mail to us by post at our expense. We believe, but do not warrant, that this 
e-mail and any attachments are virus-free, but you should check. We may monitor 
traffic data of both business and personal e-mails. We are not liable for any 
opinions expressed by the sender where this is a non-business e-mail. If you do 
not receive all the message, or if you have difficulty with the transmission, 
please telephone us immediately.

 
CONFIDENTIALITY & PRIVILEGE NOTICE

This e-mail is confidential to its intended recipient. It may also be 
privileged. Neither the confidentiality nor any privilege attaching to this 
e-mail is waived lost or destroyed by reason that it has been mistakenly 
transmitted to a person or entity other than its intended recipient. If you are 
not the intended recipient please notify us immediately by telephone or fax at 
the numbers provided above or e-mail by Reply To Author and return the printed 
e-mail to us by post at our expense. We believe, but do not warrant, that this 
e-mail and any attachments are virus-free, but you should check. We may monitor 
traffic data of both business and personal e-mails. We are not liable for any 
opinions expressed by the sender where this is a non-business e-mail. If you do 
not receive all the message, or if you have difficulty with the transmission, 
please telephone us immediately.

AW: Wsdl2Java and no Internet-Connection (with 1.1 ok, with 1.2.1 exception): An error occurred trying to resolve schema referenced at...

[Peter Koch]

answer from John Kaputin, seems to be something axis should handle...


Peter,
I assume your wsdl  element contains a something like a schema
import with schemaLocation="http://schemas.xmlsoap.org/soap/encoding/";.
WSDL4J version 1.5 introduced support for navigating the tree of nested
schemas, which involves resolving any schema URLs. If a schema url cannot
be resolved an exception is raised.  I believe Axis 1.1 used the earlier
version, WSDL4J 1.4, which did not have this support.

You should post this problem on the Axis mailing list to see if/how this
situation is handled by Axis 1.2.1 (see http://ws.apache.org/axis/mail.html
).

A possible approach might be to add something to the WSDL4J API to allow an
application such as Axis to configure WSDL4J to ignore specified URLs when
resolving schemas (e.g. to ignore the standard schema URLs like
http://schemas.xmlsoap.org/soap/encoding). A maintenance release of the
WSDL4J API (defined by JSR110) is under consideration, so now would be the
right time to consider new function that changes the WSDL4J API.

regards,
John Kaputin
IBM.

-Ursprüngliche Nachricht-
Von: Peter Koch 
Gesendet: Dienstag, 23. August 2005 15:55
An: 'axis-user@ws.apache.org'; '[EMAIL PROTECTED]'
Betreff: AW: Wsdl2Java and no Internet-Connection (with 1.1 ok, with
1.2.1 exception): An error occurred trying to resolve schema referenced
at...


thanks dims, I'll ask the WSDL4J-guys.

br,
peter

-Ursprüngliche Nachricht-
Von: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 23. August 2005 15:48
An: axis-user@ws.apache.org
Betreff: Re: Wsdl2Java and no Internet-Connection (with 1.1 ok, with
1.2.1 exception): An error occurred trying to resolve schema referenced
at...


Could you please ask here (http://groups.yahoo.com/group/jsr110-eg-disc/)?

thanks,
dims

On 8/23/05, Peter Koch <[EMAIL PROTECTED]> wrote:
>  
> 
> hi folks,
>  
>  I migrated from axis 1.1 to axis 1.2.1.
>  
>  we're using WSDL2Java with a wsdl file on the local filesystem.
>  now, with 1.2.1 we get the following error, if the local
>  machine does not have access to the internet:
>  
>  WSDLException (at
> /wsdl:definitions/wsdl:types/xsd:schema):
> faultCode=OTHER_ERROR: An error occurred trying to resolve schema referenced
> at 'http://schemas.xmlsoap.org/soap/encoding/', relative to
> 'file:C:\temp\BUG-Problem mit any und
> WS\Z_IVY_ISUMETER_DOCUMENT_CHECK.wsdl'.: No route to host:
> connect: java.net.NoRouteToHostException: No route to host: connect
>   at java.net.PlainSocketImpl.socketConnect(Native Method)
>   at
> java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
>   at
> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
>   at
> java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
>   at java.net.Socket.connect(Socket.java:452)
>   at java.net.Socket.connect(Socket.java:402)
>   at sun.net.NetworkClient.doConnect(NetworkClient.java:139)
>   at
> sun.net.www.http.HttpClient.openServer(HttpClient.java:402)
>   at
> sun.net.www.http.HttpClient.openServer(HttpClient.java:618)
>   at sun.net.www.http.HttpClient.(HttpClient.java:306)
>   at sun.net.www.http.HttpClient.(HttpClient.java:267)
>   at sun.net.www.http.HttpClient.New(HttpClient.java:339)
>   at sun.net.www.http.HttpClient.New(HttpClient.java:320)
>   at sun.net.www.http.HttpClient.New(HttpClient.java:315)
>   at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:521)
>   at
> sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:498)
>   at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:626)
>   at
> java.net.URLConnection.getContent(URLConnection.java:585)
>   at java.net.URL.getContent(URL.java:927)
>   at
> com.ibm.wsdl.util.StringUtils.getContentAsInputStream(Unknown
> Source)
>   at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown
> Source)
>   at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown
> Source)
>   at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown
> Source)
>   at
> com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown
> Source)
>   at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown
> Source)
>   at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown
> Source)
>   at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown
> Source)
>   at
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
>   at
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
>   at
> org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
>   at java.lang.Thread.run(Thread.java:534)
>  
>   at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown
> Source)
>   at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown
> Source)
>   at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(Unknown
> Source)
>   at
> com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown
> Source)
>   at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown
> Source)
>   at com.ibm.wsdl.xml.WSDL

Antwort: Support of other protocols

[Oliver Wulff]

Scott,

take a look to Celtix ESB (open source) or Artix (commercial) from IONA
Technologies. It does support different bindings and transports (SOAP,
IIOP, Websphere MQ, JMS, Tuxedo,...).

Celtix:
http://celtix.objectweb.org/

Artix:
http://www.iona.com/products/artix/welcome.htm

Oliver



   
  Scott Goldstein  
  <[EMAIL PROTECTED]An:   
axis-user@ws.apache.org
  e.org>   Kopie:  
   Thema:Support of other 
protocols
  26.08.2005 01:13 
  Bitte antworten  
  an axis-user 
   
   





Does Axis support other SOA protocols besides SOAP over HTTP?  I have an
application in which I'm sending large amounts of data and the SAX parsing
is leading to a performance problem.  I've heard in the past that one way
to solve this is to use an alternative protocol, though I don't recall the
details of the solution.

In a related question, I was wondering what the purpose is of the
JavaTransport?  Is this transport only used within a single process or does
it invokes services over a network?

Thanks.

Scott








*** BITTE BEACHTEN ***
Diese Nachricht (wie auch allfällige Anhänge dazu) beinhaltet
möglicherweise vertrauliche oder gesetzlich geschützte Daten oder
Informationen. Zum Empfang derselben ist (sind) ausschliesslich die
genannte(n) Person(en) bestimmt. Falls Sie diese Nachricht
irrtümlicherweise erreicht hat, sind Sie höflich gebeten, diese unter
Ausschluss jeder Reproduktion zu zerstören und die absendende Person
umgehend zu benachrichtigen. Vielen Dank für Ihre Hilfe.