Re: [axis2] Problem with Websphere 6 and Axis2 security module
Hi,
RE: Problem #2:
>
> Caused by: java.lang.RuntimeException: Unable to create
> nullNodejava.lang.NullPointerException
> at
> org.apache.xml.security.c14n.implementations.CanonicalizerBase.(Unknown
> Source)
The Axis2 security module contains the wss4j-SNAPSHOT.jar and the
xml-security.jar since its required by WSS4J. When WSS4J initializes
the xml-security library it will load the
org.apache.xml.security.c14n.implementations.CanonicalizerBase class.
At that point the following static block will be called.
static {
try {
nullNode=DocumentBuilderFactory.newInstance().
newDocumentBuilder().newDocument().createAttributeNS(Constants.NamespaceSpecNS,XMLNS);
nullNode.setValue("");
} catch (Exception e) {
throw new RuntimeException("Unable to create nullNode"/*,*/+e);
}
}
nullNode is an org.w3c.dom.Attr attribute.
Therefore as you can see it was not possible to create the nullNode.
Please check whether you can do the above within WebSphere.
The security module shipped with Axis2 0.94 will change the default
DOM impl of the VM to be DOOM (AXIOM complient DOM impl)... but this
works without a problem in Tomcat, Jetty and Axis2-SimpleHTTPServer.
I'm not sure whether changing the VM's DOM impl to DOOM caused any
problems inside WebSphere.
Right now the DOOM impl is changed to be able to set the DOM impl in a
ThreadLocal manner where the changed DOM impl will only be visible on
the thread that changed it not the whole VM. Therefore you can try the
SVN head as well.
Thanks,
Ruchith
Problem with WSDL2Java for the DataHandler type using ?wsdl
Hi, I am using AXIS 1.2 over Tomcat 5.5.9 appserver with jdk1.5.0_03. I have deployed my web services in both Linux and Windows. I found the problem in only linux. The problem that I am facing is that the ?wsdl feature of the Axis is not generating the wsdl:types section correctly. I have defined a dataHandler element as followsAnd also I have added the xmlns:apachesoap in the deployment tag of my deploy.wsdd My web service in the deploy.wsdd looks like this. operation> The problem is that the ?wsdl that generates the wsdl for my service does not generate the correct wsdl:type. It some times have and some times does not have the type declaration in the generated wsdl because of which the stubs generation throws the following error. java.io.IOException: Type DataHandler is referenced but not defined. at org.apache.axis.wsdl.symbolTable.SymbolTable.checkForUndefined(Symbol Table.java:663) at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543 ) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav a:516) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav a:493) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:360) at java.lang.Thread.run(Thread.java:534) Can some one tell me the reason for this? Thanks and regards Subir S The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
RE: MustUnderstand header
Thanks Dies. I understood. But I am not a java programmer, though I
write this client as part of a POC. After going through a number of WS
implementations, I found Axis is able to generate proxies for WCF
services.
Seems I will have to explore more on Axis now.
Regards,
Girish Kumar
-Original Message-
From: Dies Koper [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 23, 2006 10:16 AM
To: axis-user@ws.apache.org
Subject: Re: MustUnderstand header
Hello Girish,
I am not sure what your question is but does my answer to Sajith (see
below: "employ a client-side handler that understands the header and
removes it from the SOAP message after processing it.") not help?
Axis 1.2/1.3 stubs do not understand other people's headers so headers
marked with mustUnderstand="1" will lead to the exception below. You'll
have to process (and then remove) the headers in client handlers.
Regards,
Dies
Girish_Kumar wrote:
> Hi all,
>
> I am getting the following exception from an Axis client trying to
> consume a WCF(Indigo) service. I am not an Axis programmer, but want
to
> see if it can consume a WCF service. I am using Sun java studio for
> creating this client.
> Exception :
> Did not understand "MustUnderstand"
> header(s):{http://schemas.xmlsoap.org/ws/2004/08/addressing}Action,
> {http://schemas.xmlsoap.org/ws/2004/08/addressing}To
>
>
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstan
> dChecker.java:96)
> org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
> org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> org.apache.axis.client.Call.invoke(Call.java:2767)
> org.apache.axis.client.Call.invoke(Call.java:2443)
> org.apache.axis.client.Call.invoke(Call.java:2366)
> org.apache.axis.client.Call.invoke(Call.java:1812)
>
>
org.tempuri.WSHttpBinding_IProfileStub.login(WSHttpBinding_IProfileStub.
> java:419)
> LoginServlet.processRequest(LoginServlet.java:62)
> LoginServlet.doGet(LoginServlet.java:106)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
> sun.reflect.GeneratedMethodAccessor192.invoke(Unknown Source)
>
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:25)
> java.lang.reflect.Method.invoke(Method.java:585)
>
> org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
> java.security.AccessController.doPrivileged(Native Method)
> javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
>
>
org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
>
>
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.jav
> a:165)
>
>
> note The full stack trace of the root cause is available in the
> Sun-Java-System/Application-Server logs.
>
>
> Regards,
> Girish Kumar
>
> -Original Message-
> From: Dies Koper [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 22, 2006 2:19 PM
> To: axis-user@ws.apache.org
> Subject: Re: Problem with MustUnderstand headers when migrating from
> axis 1.1 to 1.3
>
> Hello Sajith,
>
> Refer to the JAX-RPC1.1 spec to see how to use a client handler in a
> portable way. I believe it goes something like this:
>
>sf = javax.xml.rpc.ServiceFactory.newInstance();
>SEIService si = (SEIService)sf.loadService(SEIService.class);
>
>// register client handler
>javax.xml.rpc.handler.HandlerRegistry hr = si.getHandlerRegistry();
>java.util.List hl = new java.util.ArrayList();
>hl.add(new
> javax.xml.rpc.handler.HandlerInfo(YourHandler.class,null,null));
>hr.setHandlerChain(new
QName("http://localhost/xxx/","yourPort";),hl);
>
>SEI sei = si.getSEIPort();
>
> ((javax.xml.rpc.Stub)sei)._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY,
> url);
>
> YourHandler should implement javax.xml.rpc.handler.Handler.
>
> Hope that helps,
> Dies
>
>
> sajith wrote:
>> Hi Dies,
>>
>> As you suggested I debugged both axis 1.1 and 1.3 it seems Axis 1.1
> does not
>> handle "mustUnderstand", where as axis 1.3 provides a handle
> implementation
>> called "MustUnderstandChecker". This is the place where the error is
>> generated.
>>
>> So either I could make changes to this class or I could have my own
> handler
>> instead. Since I'm very new to web services I don't know how to
> plug-in this
>> handler to axis. It doesn't seem like it cannot be externally
> plugged-in to
>> AxisClient without modifying the existing 1.3 code.
>>
>> Any thoughts on this will be highly appreciated.
>>
>>
>> Thanks and regards
>> Sajith.
>>
>>
>> -Original Message-
>> Sent: Wednesday, February 22, 2006 11:56 AM
>> To: axis-user@ws.apache.org
>> Subject: Re: Problem with MustUnderstand headers when migrating from
> axis
>> 1.1 to 1.3
>>
>> Hello Sajith,
>>
>> The stub seems to generate a Fault when it receives a SOAP message
> with
>
Re: WSDD2Java + Admin util for deployment = Undescribably strange error...
Thanks for your input, although this does generate working code and my actual problem, was that in xsd. But before I complete this project, I do have the requirement of ensuring WS-I compliance, and I think this will help me move in that direction.
Thanks,Scott S. McCoyOn 2/22/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
Scott, there are a bunch of errors in your WSDL. I've corrected a few of them (including notes about the corrections in comments): targetNamespace="
http://plm.marchex.com/service/account" xmlns:tns="
http://plm.marchex.com/service/account
" xmlns:typens="http://plm.marchex.com/service/account" xmlns:authns="
http://plm.marchex.com/credentials
" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/
" xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/">
http://plm.marchex.com/services/account">
http://plm.marchex.com/credentials
" schemaLocation="credentials.xsd"/>
<-- You don't need to include the "credentials" part in each of your
messages. You can reference the "CredentialsOnly" message for your header elements. (Definitely cleaner if you want to use the same header in multiple messages.)-->
transport="
http://schemas.xmlsoap.org/soap/http"/>
Regards,AnneOn 2/22/06, Scott McCoy <
[EMAIL PROTECTED]> wrote:
Okay, I have a hand-crafted WSDL I'm using to generate Java with WSDL2Java and I'm using the deployment descriptor generated by WSDL2Java to generate a server-config.wsdd, which I package in a war and deploy to my tomcat server.
This has all been working fine and dandy, util today, when I added a new method that uses (an element and message I had already used before)...But I'm ending up with this error:Fault - Bean attribute password is of type
java.lang.String, which is not a simple typeAxisFault faultCode: {
http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: Bean attribute password is of type java.lang.String, which is not a simple type faultActor: faultNode: faultDetail: {
http://xml.apache.org/axis/}hostname:sludge.marchex.com
The only thing that really makes me scratch my head here is that I thought xsd:string *was* a simple type? I've got the WSDL and XSDs generating the code in question attached to this message. Thanks,
Scott S. McCoy
Re: [axis2] rpcMessageReceiver
I just run ur code with small modification and it worked for me and got
the folliwng result
http://org.apache.axis2/xsd";>456
the only modification I have done to ur client code is
QName qn = new QName("http://org.apache.axis2/xsd";, "addInventory");
and I did not do any modification to service code
btw wt the Axis2 version that ur using ?
atoi atoi wrote:
>I have the following service deployed on axis2:
>public class InventoryService {
> public int addInventory(String sku, int quantity) {
>//do something
>return quantity;
> }
>
>with the following services.xml
>
>
>locked="false">ch02.InventoryService
>
>mep="http://www.w3.org/2004/08/wsdl/in-out";
>class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
>
>
>
>Here is the client code:
>public class InventoryClient {
>private static EndpointReference targetEPR = new
>EndpointReference("http://localhost:8081/axis2/services/InventoryService";);
> public static void main(String[] args) throws
>Exception {
>try {
> QName qn = new QName("http://ch02","addInventory";);
> String sku = "ANT456";
> Integer quantity = new Integer("456");
> Object [] inputParams = new Object[]
>{"ant123","456"};
>
>Options options = new Options();
>options.setTo(targetEPR);
>
>options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
>
>//Blocking invocation
>RPCServiceClient sender = new
>RPCServiceClient();
>sender.setOptions(options);
> OMElement result =
>sender.invokeBlocking(qn,inputParams);
>
>StringWriter writer = new StringWriter();
>
>result.serialize(XMLOutputFactory.newInstance()
>.createXMLStreamWriter(writer));
>writer.flush();
>
>System.out.println(writer.toString());
>
>} catch (AxisFault axisFault) {
>axisFault.printStackTrace();
>}
>
> }
>}
>
>I keep getting the following error:
>
>encoding='UTF-8'?>xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>/>ClientRaw
>Xml provider supports only the methods bearing the
>signature public OMElement
><method-name>(OMElement) where the
>method name can be
>anythinghttp://myAxisServer/role/defaultorg.apache.axis2.AxisFault:
>Raw Xml provider supports only the methods bearing the
>signature public OMElement
><method-name>(OMElement) where the
>method name can be anything
>
> at
>org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:121)
>
> at
>org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
>
> at
>org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:331)
>
> at
>org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:274)
>
> at
>org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:150)
>
> at
>javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>
> at
>javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
> at
>org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
>
> at
>org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
>
> at
>org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
>
> at
>org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>
> at
>org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>
> at
>org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
>
> at
>org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
>
> at
>org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>
> at
>org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>
> at
>org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
>
> at
>org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>
> at
>org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
>
> at
>org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
>
> at
>org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>
> at
>org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>
> at
>org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
>
> at
>org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
>
> at
>org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
>
> at
>org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
>
> at
>org.
Complex bean object
Hi,
I'm building a service which returns a complex java
object that holds a vector of object.
I generated the server site and client stub using axis
1.3 tools.
Everything was OK in the server site. However, I got
an error when executing the client code.
Exception in thread "main" AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: org.xml.sax.SAXParseException: Premature
end of file.
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:org.xml.sax.SAXParseException:
Premature end of file.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
at
org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown
Source)
at
org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
.
And also an error about type mapping in tomcat
console:
java.io.IOException No serializer found for class
dw.lexicon.bean.GeneralObj in registry
[EMAIL PROTECTED]
Is it possible for axis to serialize an object that
contains a vector of object?
This is how the object looks like:
GeneralObj.java:
- String message
- Vector lexicon(hold the Lexicon bean)
Lexicon.java:
- String source
- String target
-
Mohd Faizul Sulaiman
--
__
Find your next car at http://autos.yahoo.ca
Re: MustUnderstand header
Hello Girish,
I am not sure what your question is but does my answer to Sajith (see
below: "employ a client-side handler that understands the header and
removes it from the SOAP message after processing it.") not help?
Axis 1.2/1.3 stubs do not understand other people's headers so headers
marked with mustUnderstand="1" will lead to the exception below. You'll
have to process (and then remove) the headers in client handlers.
Regards,
Dies
Girish_Kumar wrote:
Hi all,
I am getting the following exception from an Axis client trying to
consume a WCF(Indigo) service. I am not an Axis programmer, but want to
see if it can consume a WCF service. I am using Sun java studio for
creating this client.
Exception :
Did not understand "MustUnderstand"
header(s):{http://schemas.xmlsoap.org/ws/2004/08/addressing}Action,
{http://schemas.xmlsoap.org/ws/2004/08/addressing}To
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstan
dChecker.java:96)
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
org.apache.axis.client.Call.invokeEngine(Call.java:2784)
org.apache.axis.client.Call.invoke(Call.java:2767)
org.apache.axis.client.Call.invoke(Call.java:2443)
org.apache.axis.client.Call.invoke(Call.java:2366)
org.apache.axis.client.Call.invoke(Call.java:1812)
org.tempuri.WSHttpBinding_IProfileStub.login(WSHttpBinding_IProfileStub.
java:419)
LoginServlet.processRequest(LoginServlet.java:62)
LoginServlet.doGet(LoginServlet.java:106)
javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
sun.reflect.GeneratedMethodAccessor192.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.jav
a:165)
note The full stack trace of the root cause is available in the
Sun-Java-System/Application-Server logs.
Regards,
Girish Kumar
-Original Message-
From: Dies Koper [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 22, 2006 2:19 PM
To: axis-user@ws.apache.org
Subject: Re: Problem with MustUnderstand headers when migrating from
axis 1.1 to 1.3
Hello Sajith,
Refer to the JAX-RPC1.1 spec to see how to use a client handler in a
portable way. I believe it goes something like this:
sf = javax.xml.rpc.ServiceFactory.newInstance();
SEIService si = (SEIService)sf.loadService(SEIService.class);
// register client handler
javax.xml.rpc.handler.HandlerRegistry hr = si.getHandlerRegistry();
java.util.List hl = new java.util.ArrayList();
hl.add(new
javax.xml.rpc.handler.HandlerInfo(YourHandler.class,null,null));
hr.setHandlerChain(new QName("http://localhost/xxx/","yourPort";),hl);
SEI sei = si.getSEIPort();
((javax.xml.rpc.Stub)sei)._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY,
url);
YourHandler should implement javax.xml.rpc.handler.Handler.
Hope that helps,
Dies
sajith wrote:
Hi Dies,
As you suggested I debugged both axis 1.1 and 1.3 it seems Axis 1.1
does not
handle "mustUnderstand", where as axis 1.3 provides a handle
implementation
called "MustUnderstandChecker". This is the place where the error is
generated.
So either I could make changes to this class or I could have my own
handler
instead. Since I'm very new to web services I don't know how to
plug-in this
handler to axis. It doesn't seem like it cannot be externally
plugged-in to
AxisClient without modifying the existing 1.3 code.
Any thoughts on this will be highly appreciated.
Thanks and regards
Sajith.
-Original Message-
Sent: Wednesday, February 22, 2006 11:56 AM
To: axis-user@ws.apache.org
Subject: Re: Problem with MustUnderstand headers when migrating from
axis
1.1 to 1.3
Hello Sajith,
The stub seems to generate a Fault when it receives a SOAP message
with
a header with a mustUnderstand="1" attribute.
I thought this was according to the spec, as the Axis generated stub
does not understand your header.
However, I believe some months ago there was some debate on this ML
whether Axis should be doing this, or whether the client application
should be responsible for this itself.
There was no conclusion.
If you get no response from others, you could try searching the source
code for a comment regarding this change (as you said it used to work
fine with Axis 1.1, maybe you can find why it was changed, and then
judge whether that was a mistake or a new feature you'd have to work
with).
Otherwise, you co
Jar file service deployment not working
Hey everyone! I've got a quick question... Created a new service, deployed the service, put the classes in the WEB-INF/classes directory, and the service works great! When I try to deploy the service classes in a jar file in the WEB-INF/ lib directory I get a ClassNotFoundException exception. Why isn't axis finding my jar in the lib directory and loading the class from there? Again, the service works wonderfully if I put the .class files in the classes directory instead Thanks!
[axis2] rpcMessageReceiver
I have the following service deployed on axis2:
public class InventoryService {
public int addInventory(String sku, int quantity) {
//do something
return quantity;
}
with the following services.xml
ch02.InventoryService
http://www.w3.org/2004/08/wsdl/in-out";
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
Here is the client code:
public class InventoryClient {
private static EndpointReference targetEPR = new
EndpointReference("http://localhost:8081/axis2/services/InventoryService";);
public static void main(String[] args) throws
Exception {
try {
QName qn = new QName("http://ch02","addInventory";);
String sku = "ANT456";
Integer quantity = new Integer("456");
Object [] inputParams = new Object[]
{"ant123","456"};
Options options = new Options();
options.setTo(targetEPR);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
//Blocking invocation
RPCServiceClient sender = new
RPCServiceClient();
sender.setOptions(options);
OMElement result =
sender.invokeBlocking(qn,inputParams);
StringWriter writer = new StringWriter();
result.serialize(XMLOutputFactory.newInstance()
.createXMLStreamWriter(writer));
writer.flush();
System.out.println(writer.toString());
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
}
}
}
I keep getting the following error:
http://schemas.xmlsoap.org/soap/envelope/";>ClientRaw
Xml provider supports only the methods bearing the
signature public OMElement
<method-name>(OMElement) where the
method name can be
anythinghttp://myAxisServer/role/defaultorg.apache.axis2.AxisFault:
Raw Xml provider supports only the methods bearing the
signature public OMElement
<method-name>(OMElement) where the
method name can be anything
at
org.apache.axis2.receivers.RawXMLINOutMessageReceiver.invokeBusinessLogic(RawXMLINOutMessageReceiver.java:121)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37)
at
org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:331)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:274)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:150)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
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)
Why isnt rpcMessageReceiver picking this up?
__
Do You Yahoo!?
T
Re: Retrieve Web Service name in Axis2
yes you can do that , meaning if you want to get the name of the service
at your service impl class level , you have to following procedure.
add a new method to service impl class called "init"
class MyService {
String serviceName;
void init(MessageContext msgctx){
serviceName = msgctx.getAxisService().getName();
}
//rest o fthe code
public String myMethod(){
// you know the name of the sevrice this point
}
}
Yariel Ramos Moreno wrote:
> Thanks for your help Deepal...
>
> I know that. My problem is that I want to get the name of my WS in the
> moment I invoke it, from one of the clases implemented in the WS. I
> want to know if there is a class in the Axis2 API that alows me to do
> that (get my name from code if I'm the invoked WS).
>
> On 2/22/06, *Deepal Jayasinghe* <[EMAIL PROTECTED]
> > wrote:
>
> Hi Yariel;
>
> Name of the service will be the name of the archive file if the
> services.xml has only one service element meaning if the services.xml
> look like below
>
> // service data
>
>
> In the case of servicegroup name of the service will be the name that
> you specified in services.xml as an example if the services.xml is
> like
> below;
>
>
>
>
>
> so name of the service will be foo in this case.
>
> Yariel Ramos Moreno wrote:
>
> > How can I retrieve the name of a Web Service deployed in Axis2 sever
> > in runtime? I mean, when the service is invoked, I need to get the
> > name of it from inside it in my code.
> >
> > Thanks in advance,
> >
> > Yariel.
>
>
> --
> Thanks,
> Deepal
>
> ~Future is Open~
>
>
>
--
Thanks,
Deepal
~Future is Open~
Re: Problem with XML QName when sending it to a webservice
This a more detailed and accurate piece of my code and error.
Just so that everybody understands what I'm trying to do is for the
client to pass to my service some initializations parameters.
Pedro
*My Client Function*
private void setSOAPDefaultSetttings() throws Exception {
Document document = db.newDocument();
Element docRoot = document.createElement("config");
document.appendChild(docRoot);
Element itemElem = document.createElement("datadir");
itemElem.setAttribute("value",dataDir);
docRoot.appendChild(document.createTextNode("\n"));
docRoot.appendChild(itemElem);
docRoot.appendChild(document.createTextNode("\n"));
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress(new
URL("http://localhost:8080"+webServiceURL));
call.setOperationName(new QName("setServiceSettings"));
SOAPBodyElement[] input = new SOAPBodyElement[1];
input[0] = new SOAPBodyElement(document.getDocumentElement());
Vector elems = (Vector) call.invoke(input);
}
*My Service*
public Element[] setServiceSettings(Element[] sbe) {
NodeList nl = sbe[0].getElementsByTagName("datadir");
NamedNodeMap attrs = nl.item(0).getAttributes();
for (int i = 0; i < attrs.getLength(); i++) {
if ("value".equals(attrs.item(i))) {
data.AdaptData.setDataDir(attrs.item(i).getNodeValue());
}
}
Element[] elems = new Element[1];
elems[0] = null;
return elems;
}
*The Error*
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: Couldn't find an appropriate operation for XML QName config
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:kheijo.dracus.homeip.net
Couldn't find an appropriate operation for XML QName config
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
[]
*My WSDD*
http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
*My WSDL*
http://localhost:8080/SOMadapter/services/Register";
xmlns:apachesoap="http://xml.apache.org/xml-soap";
xmlns:impl="http://localhost:8080/SOMadapter/services/Register";
xmlns:intf="http://localhost:8080/SOMadapter/services/Register";
xmlns:tns1="http://adaptor";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
http://adaptor";
xmlns="http://www.w3.org/2001/XMLSchema";>
http://localhost:8080/SOMadapter/services/Register";
xmlns="http://www.w3.org/2001/XMLSchema";>
http://schemas.xmlsoap.org/soap/http"/>
http://localhost:8080/SOMadapter/services/Register"/>
> Based on the error, my guess is that the services is not expected the
> child element of the SOAP Body to contain the element. (This
> element should be namespace qualified.)
>
> Can you provide the WSDL for the service?
>
> Anne
>
> On 2/22/06, *Pedro Silva* <[EMAIL PROTECTED]
> > wrote:
>
> Hi again,
>
> Sorry I sent you some buggy code, sorry. I'm looking at this for hours
>
>
> This is the correct code:
>
> DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
> Document db = dbf.newDocumentBuilder ();
> Document document = db.newDocument();
> Element docRoot = document.createElement("itemcount");
> document.appendChild(docRoot);
> Element itemElem = document.createElement("item");
> itemElem.setAttribute ("userid",userId);
> itemElem.setAttribute("itemid",itemId);
> docRoot.appendChild(document.createTextNode("\n"));
> docRoot.appendChild(itemElem);
> docRoot.appendChild(document.createTextNode ("\n"));
>
>
> Service service = new Service();
> Call call = (Call) service.createCall();
> call.setTargetEndpointAddress(new URL(localUrl+webServiceURL));
> call.setOperationName(new QName("
> http://adaptor","incrementUserItemCount";));
>
> SOAPBodyElement[] soapInput = new SOAPBodyElement[1];
> soapInput[0] = new SOAPBodyElement(document.getDocumentElement());
>
> call.invoke(soapInput);
>
>
> and here is the error:
>
>
> AxisFault
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
> faultSubcode:
> faultString: Couldn't find an appropriate operation for XML QName
> itemcount
> faultActor:
> faultNode:
> faultDetail:
> { http://xml.apache.org/axis/}hostname:kheijo.dracus.homeip.net
>
> Couldn't find an appro
Re: WebServices very slow after some requests
Try Eclipse TPTP to profile your Tomcat and services for free. On 2/22/06, Erik Daughtrey <[EMAIL PROTECTED] > wrote:Hello,For this sort of problem, I've found analysis of jvm thread dumps very effective.If you're using unix, then "kill -QUIT pid" is usually sufficient to get acurrent thread dump. In this case, pid would be the process id of therunning Tomcat process.If you're using Windows, then the easiest way to get a thread dump is by running the target process in the foreground and using CTRL+BREAK. Theoutput will usually go to stderr or stdout so, using output redirection onthe process at startup is recommended.Where the output goes depends on the jdk in use. It may wind up in the stderr/stdout, or files like javadump may appear in the current directoryof the process being dumped.Analyzing a threaddump can be tricky, but I suspect that in this case it mayjump from the output. Personally, I'd look for some number of threads having the same or very similar top of stack. This will indicate the first level ofdebug. I suspect that the threads are waiting on some external resource --at least that's been my experience in cases like these. Good luck. On Wednesday 22 February 2006 12:54, Franz Coriand wrote:> Hi all,>> we have the problem, that our webservices become very slow after some> requests.> For the first request we need about 10s. > For the 100th request we need about 2mins - its the same request like> the first one, with the same result.>> We use Tomcat 5.5.12 and Axis 1.3.>> We have no clue what's the problem. > Do you have any ideas?>> Thanks, Franz--Regards,Erik
Re: WSDD2Java + Admin util for deployment = Undescribably strange error...
Scott, there are a bunch of errors in your WSDL. I've corrected a few of them (including notes about the corrections in comments): targetNamespace="
http://plm.marchex.com/service/account" xmlns:tns="http://plm.marchex.com/service/account
" xmlns:typens="http://plm.marchex.com/service/account" xmlns:authns="http://plm.marchex.com/credentials
" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="
http://schemas.xmlsoap.org/wsdl/">
http://plm.marchex.com/services/account"> http://plm.marchex.com/credentials
" schemaLocation="credentials.xsd"/>
<-- You don't need to include the "credentials" part in each of your
messages. You can reference the "CredentialsOnly" message for your header elements. (Definitely cleaner if you want to use the same header in multiple messages.)-->
transport="
http://schemas.xmlsoap.org/soap/http"/>
Regards,AnneOn 2/22/06, Scott McCoy <[EMAIL PROTECTED]> wrote:
Okay, I have a hand-crafted WSDL I'm using to generate Java with WSDL2Java and I'm using the deployment descriptor generated by WSDL2Java to generate a server-config.wsdd, which I package in a war and deploy to my tomcat server.
This has all been working fine and dandy, util today, when I added a new method that uses (an element and message I had already used before)...But I'm ending up with this error:Fault - Bean attribute password is of type
java.lang.String, which is not a simple typeAxisFault faultCode: {
http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: Bean attribute password is of type java.lang.String, which is not a simple type faultActor: faultNode: faultDetail: {
http://xml.apache.org/axis/}hostname:sludge.marchex.com
The only thing that really makes me scratch my head here is that I thought xsd:string *was* a simple type? I've got the WSDL and XSDs generating the code in question attached to this message. Thanks,
Scott S. McCoy
java.lang.NullPointerException when invoking axis2 web service !!!
Hello,
When I test the web service by using the code that generated by the
wsdl2java tools provided in axis2, it just raised
NullPointerException:
java.lang.NullPointerException
at
org.apache.axis2.databinding.utils.ConverterUtil.convertToString(ConverterUtil.java:195)
at
test.client.TestservicePortStub$EchoRequest.getPullParser(TestservicePortStub.java:264)
at
test.client.TestservicePortStub.toEnvelope(TestservicePortStub.java:353)
at test.client.TestservicePortStub.echo(TestservicePortStub.java:90)
at test.client.Client1.main(Client1.java:41)
But if I followed the client coding in the userguide sample, it works fine.
Is there any problem in the code generator ?
The wsdl.
http://org.apache.axis2/xsd";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
xmlns:tns="http://org.apache.axis2/";
targetNamespace="http://org.apache.axis2/";>http://www.w3.org/2001/XMLSchema";
xmlns:ns1="http://org.apache.axis2/xsd";
targetNamespace="http://org.apache.axis2/xsd";
elementFormDefault="qualified" attributeFormDefault="unqualified">
http://schemas.xmlsoap.org/soap/http"; style="document"
/>http://www.org.apache.axis2";
/>http://www.org.apache.axis2";
/>http://localhost/axis2/services/testservice";
/>
The client code:
/**
* Client1.java
*
* Copyright (C) 2006 Eric Chow. All right Reserved.
*
* This software is the confidential and proprietary information of Eric Chow.
*/
package test.client;
import org.apache.axis2.databinding.ADBBean;
/**
* Client1.java
*
* @author Chao Hoi Ka, Eric
*
*/
public class Client1 {
/**
*
*/
public Client1() {
super();
// TODO Auto-generated constructor stub
}
/**
* @param args
*/
public static void main(String[] args) {
try {
TestservicePortStub stub = new TestservicePortStub();
TestservicePortStub.EchoRequest req =
(TestservicePortStub.EchoRequest)
getTestObject(TestservicePortStub.EchoRequest.class);
System.out.println(stub.echo(req));
} catch (Exception e) {
e.printStackTrace();
}
}
public static ADBBean getTestObject(Class type) throws Exception {
return (ADBBean) type.newInstance();
}
}
The code that generate from wsdl2java
/**
* TestservicePortStub.java
*
* This file was auto-generated from WSDL
* by the Apache Axis2 version: 0.94 Jan 11, 2006 (08:01:58 LKT)
*/
package test.client;
/*
* TestservicePortStub java implementation
*/
public class TestservicePortStub extends org.apache.axis2.client.Stub {
// default axis home being null forces the system to pick up the mars
from
// the axis2 library
public static final String AXIS2_HOME = null;
protected static org.apache.axis2.description.AxisOperation[]
_operations;
static {
// creating the Service
_service = new org.apache.axis2.description.AxisService(
"TestservicePort");
// creating the operations
org.apache.axis2.description.AxisOperation __operation;
_operations = new
org.apache.axis2.description.OutInAxisOperation[1];
__operation = new
org.apache.axis2.description.OutInAxisOperation();
__operation.setName(new javax.xml.namespace.QName(
"http://org.apache.axis2/";, "echo"));
_operations[0] = __operation;
_service.addOperation(__operation);
}
public TestservicePortStub(
org.apache.axis2.context.ConfigurationContext
configurationContext,
String targetEndpoint) throws java.lang.Exception {
_serviceClient = new org.apache.axis2.client.ServiceClient(
configurationContext, _service);
_serviceClient.getOptions().setTo(
new
org.apache.axis2.addressing.EndpointReference(
targetEndpoint));
}
/**
* Default Constructor
*/
public TestservicePortStub() throws java.lang.Exception {
this("http://localhost/axis2/services/testservice";);
}
/**
* Constructor taking the traget endpoint
*/
public TestservicePortStub(String targetEndpoint)
throws java.lang.Exception {
this(new org.apache.axis2.context.ConfigurationContextFactory()
.createConfigurationContextFromFileSystem(AXIS2_HOME),
Re: Problem with XML QName when sending it to a webservice
Based on the error, my guess is that the services is not expected the child element of the SOAP Body to contain the element. (This element should be namespace qualified.)Can you provide the WSDL for the service?
AnneOn 2/22/06, Pedro Silva <[EMAIL PROTECTED]> wrote:
Hi again,Sorry I sent you some buggy code, sorry. I'm looking at this for hoursThis is the correct code:DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();Document db = dbf.newDocumentBuilder
();Document document = db.newDocument();Element docRoot = document.createElement("itemcount");document.appendChild(docRoot);Element itemElem = document.createElement("item");itemElem.setAttribute
("userid",userId);itemElem.setAttribute("itemid",itemId);docRoot.appendChild(document.createTextNode("\n"));docRoot.appendChild(itemElem);docRoot.appendChild(document.createTextNode
("\n"));Service service = new Service();Call call = (Call) service.createCall();call.setTargetEndpointAddress(new URL(localUrl+webServiceURL));call.setOperationName(new QName("
http://adaptor","incrementUserItemCount"));SOAPBodyElement[] soapInput = new SOAPBodyElement[1];soapInput[0] = new SOAPBodyElement(document.getDocumentElement());call.invoke(soapInput);
and here is the error:AxisFault faultCode:{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: Couldn't find an appropriate operation for XML QName itemcount faultActor: faultNode: faultDetail:{
http://xml.apache.org/axis/}hostname:kheijo.dracus.homeip.netCouldn't find an appropriate operation for XML QName itemcountatorg.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at Thanks once more,Pedro Silva> Hi everybody!>>> I'm trying to build some XML document and send it on the fly to a> webservice. I've managed to do this with a file using the parse method
> from javax.xml.parsers, But now I'm tryning to do it building my own XML> doc.>> If I print the document I built everything looks ok, but when I invoke> the service I get:>> xisFault
> faultCode:> {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException> faultSubcode:> faultString: Couldn't find an appropriate operation for XML QName
> {http://adaptor}itemcount> faultActor:> faultNode:> faultDetail:> {
http://xml.apache.org/axis/}hostname:kheijo.dracus.homeip.net>> Couldn't find an appropriate operation for XML QName> {http://adaptor}itemcount> at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)> at> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)> ...>
>> This is the code I'm using to build the XML ands send it. I just can't> figure waht is wrong...>> DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();> Document db =
dbf.newDocumentBuilder();> Document document = db.newDocument();> Element docRoot=document.createElement("itemcount");> document.appendChild(docRoot);> Element itemElem = document.createElement
("item");> itemElem.setAttribute("userid",userId);> itemElem.setAttribute("itemid",itemId);> docRoot.appendChild(document.createTextNode("\n"));> docRoot.appendChild
(itemElem);> docRoot.appendChild(document.createTextNode("\n"));>> Service service = new Service();> Call call = (Call) service.createCall();> call.setTargetEndpointAddress(new URL(localUrl+webServiceURL));
> call.setOperationName(new QName("incrementUserItemCount"));> SOAPBodyElement[] soapInput = new SOAPBodyElement[1];> soapInput[0] = new SOAPBodyElement(document.getDocumentElement());>
System.out.println(document.getDocumentElement());> System.out.println(soapInput[0]);> call.invoke(soapInput);>>> The simple XML doc I'm sending looks like this:>
> > >> Thanks in advance!> Pedro Silva>>>
Re: Problem with XML QName when sending it to a webservice
Hi again,
Sorry I sent you some buggy code, sorry. I'm looking at this for hours
This is the correct code:
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
Document db = dbf.newDocumentBuilder();
Document document = db.newDocument();
Element docRoot = document.createElement("itemcount");
document.appendChild(docRoot);
Element itemElem = document.createElement("item");
itemElem.setAttribute("userid",userId);
itemElem.setAttribute("itemid",itemId);
docRoot.appendChild(document.createTextNode("\n"));
docRoot.appendChild(itemElem);
docRoot.appendChild(document.createTextNode("\n"));
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress(new URL(localUrl+webServiceURL));
call.setOperationName(new QName("http://adaptor","incrementUserItemCount";));
SOAPBodyElement[] soapInput = new SOAPBodyElement[1];
soapInput[0] = new SOAPBodyElement(document.getDocumentElement());
call.invoke(soapInput);
and here is the error:
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: Couldn't find an appropriate operation for XML QName itemcount
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:kheijo.dracus.homeip.net
Couldn't find an appropriate operation for XML QName itemcount
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
Thanks once more,
Pedro Silva
> Hi everybody!
>
>
> I'm trying to build some XML document and send it on the fly to a
> webservice. I've managed to do this with a file using the parse method
> from javax.xml.parsers, But now I'm tryning to do it building my own XML
> doc.
>
> If I print the document I built everything looks ok, but when I invoke
> the service I get:
>
> xisFault
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
> faultSubcode:
> faultString: Couldn't find an appropriate operation for XML QName
> {http://adaptor}itemcount
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}hostname:kheijo.dracus.homeip.net
>
> Couldn't find an appropriate operation for XML QName
> {http://adaptor}itemcount
> at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
> at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
> ...
>
>
> This is the code I'm using to build the XML ands send it. I just can't
> figure waht is wrong...
>
> DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
> Document db = dbf.newDocumentBuilder();
> Document document = db.newDocument();
> Element docRoot=document.createElement("itemcount");
> document.appendChild(docRoot);
> Element itemElem = document.createElement("item");
> itemElem.setAttribute("userid",userId);
> itemElem.setAttribute("itemid",itemId);
> docRoot.appendChild(document.createTextNode("\n"));
> docRoot.appendChild(itemElem);
> docRoot.appendChild(document.createTextNode("\n"));
>
> Service service = new Service();
> Call call = (Call) service.createCall();
> call.setTargetEndpointAddress(new URL(localUrl+webServiceURL));
> call.setOperationName(new QName("incrementUserItemCount"));
> SOAPBodyElement[] soapInput = new SOAPBodyElement[1];
> soapInput[0] = new SOAPBodyElement(document.getDocumentElement());
> System.out.println(document.getDocumentElement());
> System.out.println(soapInput[0]);
> call.invoke(soapInput);
>
>
> The simple XML doc I'm sending looks like this:
>
>
>
>
> Thanks in advance!
> Pedro Silva
>
>
>
Problem with XML QName when sending it to a webservice
Hi everybody!
I'm trying to build some XML document and send it on the fly to a
webservice. I've managed to do this with a file using the parse method
from javax.xml.parsers, But now I'm tryning to do it building my own XML
doc.
If I print the document I built everything looks ok, but when I invoke
the service I get:
xisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: Couldn't find an appropriate operation for XML QName
{http://adaptor}itemcount
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:kheijo.dracus.homeip.net
Couldn't find an appropriate operation for XML QName
{http://adaptor}itemcount
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
...
This is the code I'm using to build the XML ands send it. I just can't
figure waht is wrong...
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
Document db = dbf.newDocumentBuilder();
Document document = db.newDocument();
Element docRoot=document.createElement("itemcount");
document.appendChild(docRoot);
Element itemElem = document.createElement("item");
itemElem.setAttribute("userid",userId);
itemElem.setAttribute("itemid",itemId);
docRoot.appendChild(document.createTextNode("\n"));
docRoot.appendChild(itemElem);
docRoot.appendChild(document.createTextNode("\n"));
Service service = new Service();
Call call = (Call) service.createCall();
call.setTargetEndpointAddress(new URL(localUrl+webServiceURL));
call.setOperationName(new QName("incrementUserItemCount"));
SOAPBodyElement[] soapInput = new SOAPBodyElement[1];
soapInput[0] = new SOAPBodyElement(document.getDocumentElement());
System.out.println(document.getDocumentElement());
System.out.println(soapInput[0]);
call.invoke(soapInput);
The simple XML doc I'm sending looks like this:
Thanks in advance!
Pedro Silva
Re: wsdl to java
Hi James, That is also not working. If i want to change WSDL generated java file to make it as arry element, will it throw any exception during serialization. where and all i have to change in generated java file. Thanks & Regards Arul Thayalan --- James Chamberlain <[EMAIL PROTECTED]> wrote: > This happened to me when I switched to 1.3 from > 1.2.1. There is a new > setting that you need to use in the wsdl2java > wrapArrays="true" > > - James > > On Dec 7, 2005, at 1:17 AM, arul thayalan wrote: > > > Hi, > >when i'm converting wsdl to java i'm not > getting > > array type for the element > "VehicleOccupantDetails" in > > VehicleOccupants class. What could be the reason? > > My WSDL style is document-literal.I'm using Axis > 1.3.0 > > > > wsdl extraction: > > > > > > > maxOccurs="unbounded"> minOccurs="0" > > name="VehicleOccupantDetails"> > > > > > > name="Person" type="ns1:PersonType"/> > > > type="ns1:string2"/> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Do you Yahoo!? > > Yahoo! Photos: Now with unlimited storage > > http://au.photos.yahoo.com > > > > Do you Yahoo!? Listen to over 20 online radio stations and watch the latest music videos on Yahoo! Music. http://au.launch.yahoo.com
WSDD2Java + Admin util for deployment = Undescribably strange error...
Okay, I have a hand-crafted WSDL I'm using to generate Java with WSDL2Java and I'm using the deployment descriptor generated by WSDL2Java to generate a server-config.wsdd, which I package in a war and deploy to my tomcat server.
This has all been working fine and dandy, util today, when I added a new method that uses (an element and message I had already used before)...But I'm ending up with this error:Fault - Bean attribute password is of type
java.lang.String, which is not a simple typeAxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode: faultString: Bean attribute password is of type java.lang.String, which is not a simple type faultActor: faultNode: faultDetail: {
http://xml.apache.org/axis/}hostname:sludge.marchex.com
The only thing that really makes me scratch my head here is that I thought xsd:string *was* a simple type? I've got the WSDL and XSDs generating the code in question attached to this message. Thanks,
Scott S. McCoy
http://plm.marchex.com/service/account";
xmlns:tns="http://plm.marchex.com/service/account";
xmlns:typens="http://plm.marchex.com/service/account";
xmlns:authns="http://plm.marchex.com/credentials";
xmlns:xsd="http://www.w3.org/1999/XMLSchema";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";>
http://plm.marchex.com/service/account";
location="account.xsd"/>
http://plm.marchex.com/credentials";
location="credentials.xsd"/>
http://schemas.xmlsoap.org/soap/http"/>
http://localhost:8080/axis/services/Account"/>
account.xsd
Description: Binary data
credentials.xsd
Description: Binary data
RE: No data back on doc / lit based wsdl generated code - Response Time Still Too High
Thanks Anne! That seems to have fixed whatever the issue was. I still have a very slow client though (which is the core problem)… I’m looking for sub-second or a second and some change response time for the entire run (including JVM load time, or .Net load time), and it’s taking anywhere from 6-12 seconds to perform the web service call. The actual code that I’m calling takes a few tenths of a second (I’ve got time print-outs confirming this). Any ideas on how to drop my response time down dramatically? It maybe unreasonable to ask for sub-second response time, but if so I’d at least like to know before I do much more development with web services. Thank you, Paul Lessard From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 22, 2006 4:21 PM To: axis-user@ws.apache.org Subject: Re: No data back on doc / lit based wsdl generated code Try generating the service as style="WRAPPED". Anne On 2/22/06, Lessard, Paul <[EMAIL PROTECTED] > wrote: All, I got my web service working fine in Axis 1.3 by using the jws instant deployment. Data was going to and coming from the service just fine. The default on the instant deploy appears to be RPC based, so I wanted to deploy it out as doc / lit using the wsdd deployment file. I have data going to the service, I can see the service process the data, and the returned String variable is populated with data. The issue is, however, when I return the populated String from the web service, the data comes back as null or "" in both a .Net and a Java client (both auto generated from wsdl). Here is the wsdl: http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl=" http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns:intf="http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns:tns1="http://DefaultNamespace" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap=" http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> http://DefaultNamespace" xmlns=" http://www.w3.org/2001/XMLSchema"> http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns="http://www.w3.org/2001/XMLSchema"> http://schemas.xmlsoap.org/soap/http"/> http://fh2k039.fhmis.net:8080/axis/services/Dictaphone"/> Is there any other information I can supply? Again, it does return data using the instant deploy, and in both the instant deploy AND the doc / lit wsdd version data get to the web service. Thank you, Paul Lessard
RE: Strange WSDL -> SOAP type mapping; can anyone explain
Hi Guys, I found that I had to add the Apache Axis Meta Data to the Java Beans that I created. This alllowed Axis 1.3 using Wrapped Document/Literal style to serialize the bean correctly. -Original Message-From: Alick Buckley [mailto:[EMAIL PROTECTED]Sent: Tuesday, 14 February 2006 8:25 AMTo: axis-user@ws.apache.orgSubject: RE: Strange WSDL -> SOAP type mapping; can anyone explain Hi John, I am getting the same when I return a BeanArray using Wrapped document/literal - Axis 1.3 Also when returning just a Bean which contains a bean array, this bean array has the same problem. Also, I found when the service runs a second time, the return bean array problem does not occur, it was only on the first request. Looking at some Apache Axis logging, I noticed that a setReturnType ( qname ) call on the OperationDesc object was using a null, so I put some code in to set the qname of the OperationDesc.setReturnType method and it starting working on the first go. The Bean containing a bean array still has the problem. = http://schemas.xmlsoap.org/soap/envelope/"> http://server.soap.acme.com"> http://server.soap.acme.com" xsi:type="ns1:Employee"> A1001 BEN 2345.82 JONES http://server.soap.acme.com" xsi:type="ns2:Employee"> A1012 PATRICK 26456.04 PAUL = -Original Message-From: John Prout [mailto:[EMAIL PROTECTED]Sent: Monday, 13 February 2006 4:31 PMTo: axis-user@ws.apache.orgSubject: Strange WSDL -> SOAP type mapping; can anyone explain I have written a service that returns an array of Name/Value pairs and then de-serializes to a Java HashMap. This works so far, but monitoring the SOAP data stream that's returned, I'm puzzled by the schema returned. I'll include the WSDL and SOAP at the end of this posting, but to summerize: I would expect the to contain something like this: http://api.ws.digitalimpact.com"> firstName JohnregistrationDate2006-01-26 15:12:00.0 But instead I get: http://api.ws.digitalimpact.com"> firstNameJohnregistrationDate 2006-01-26 15:12:00.0 See that has been replaced by a repeat of I will need to call this service from .NET and I think this will be a problem. This service is using Axis 1.2.1 in tomcat 5.5.9. I built the service from WSDL, using wsdl2java. Does anyone know why this is happening? Thanks in advance: John The WSDL is as follows: name="API.wsdl" targetNamespace="http://api.ws.myco.com" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://api.ws.myco.com" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> Digital Impact API targetNamespace="http://api.ws.myco.com" xmlns:SOAP-ENC=" http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"> http://schemas.xmlsoap.org/soap/http"/> http://localhost"/> An expample of the SOAP response (from TCPMonitor) is:
Return XML text of the response instead of a value object.
I have java client which invokes web services (SOAP in TIBCO). I sent some SUBJECT and DATA from java client and SOAP is running on TIBCO side which returns DATA and STATUS. The java client is working fine and I am getting the value inside DATA and STATUS. But now I would like to Return XML text of the response instead of a value object. I used AXIS to create java client etc. My code looks like this: public class Main { public static void main(String [] args) throws Exception { // Make a service
SOAPServer service = new SOAPServerLocator(); // Now use the service to get a stub which implements the SDI. PortType port = service.getSOAPServerHttpPort(); REQUEST req = new REQUEST("order","TV"); REPLY reply = port.operation(req); System.out.println("DATA: "+reply.getDATA()+" STATUS: "+reply.getSTATUS()); } }// Could someone help me on this. Thanks
Yahoo! Mail
Use Photomail to share photos without annoying attachments.
Re: No data back on doc / lit based wsdl generated code
Try generating the service as style="WRAPPED".AnneOn 2/22/06, Lessard, Paul <[EMAIL PROTECTED] > wrote: All, I got my web service working fine in Axis 1.3 by using the jws instant deployment. Data was going to and coming from the service just fine. The default on the instant deploy appears to be RPC based, so I wanted to deploy it out as doc / lit using the wsdd deployment file. I have data going to the service, I can see the service process the data, and the returned String variable is populated with data. The issue is, however, when I return the populated String from the web service, the data comes back as null or "" in both a .Net and a Java client (both auto generated from wsdl). Here is the wsdl: http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl=" http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns:intf="http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns:tns1="http://DefaultNamespace" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap=" http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> http://DefaultNamespace" xmlns=" http://www.w3.org/2001/XMLSchema"> http://fh2k039.fhmis.net:8080/axis/services/Dictaphone" xmlns="http://www.w3.org/2001/XMLSchema"> http://schemas.xmlsoap.org/soap/http"/> http://fh2k039.fhmis.net:8080/axis/services/Dictaphone"/> Is there any other information I can supply? Again, it does return data using the instant deploy, and in both the instant deploy AND the doc / lit wsdd version data get to the web service. Thank you, Paul Lessard
Re: generate WSDL using java code
What would you like to generate it from, then?There are plenty of XML/Schema/WSDL editors available.If you simply want an API for writing a WSDL file, try WSDL4J.Anne On 2/22/06, Asaf Lahav <[EMAIL PROTECTED]> wrote: Hi all, Does anyone know of utility or framework classes for generating a WSDL? I'm not talking about generating WSDL from existing java files. What I need is a way to generate a WSDL file. I know its possible to generate it by simply using XMLDOM of my choice. But what I'm looking for is a utility that will make the job easier. Thanks, Asaf Lahav VP R&D, Prima Grid LTD. Cellular: 972-54-4717955 Phone: 972-3-6540255 Fax: 972-3-6540254
Re: Is there a .NET equivalent of Axis handlers?
See also http://msdn.microsoft.com/msdnmag/issues/04/02/ASPColumn/default.aspx. On 2/22/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: HTTP Pipelines. See http://msdn.microsoft.com/msdnmag/issues/02/09/HTTPPipelines/ .AnneOn 2/22/06, GEORGE MCKINNEY <[EMAIL PROTECTED]> wrote: We are exploring using webservices and clients with messages that have attachments. My understanding is that SwA ( as described in http://www.w3.org/TR/SOAP-attachments ) doesn't require anything specific in the wsdl - but an article in DeveloperWorks ( http://www-128.ibm.com/developerworks/webservices/library/ws-tip-soapjax.html ) has stuff in the wsdl. On the gripping hand, we've built a toy service and client that use handlers to add and retrieve attachments while having the wsdl completely ignore them. Because we will need to be compatible with .NET clients and webservices that our partners will use, I want to know if there is a .NET way to do what our handlers do.Thanks,George McKinney
Re: Is there a .NET equivalent of Axis handlers?
HTTP Pipelines. See http://msdn.microsoft.com/msdnmag/issues/02/09/HTTPPipelines/.AnneOn 2/22/06, GEORGE MCKINNEY <[EMAIL PROTECTED]> wrote:We are exploring using webservices and clients with messages that have attachments. My understanding is that SwA ( as described in http://www.w3.org/TR/SOAP-attachments ) doesn't require anything specific in the wsdl - but an article in DeveloperWorks ( http://www-128.ibm.com/developerworks/webservices/library/ws-tip-soapjax.html ) has stuff in the wsdl. On the gripping hand, we've built a toy service and client that use handlers to add and retrieve attachments while having the wsdl completely ignore them. Because we will need to be compatible with .NET clients and webservices that our partners will use, I want to know if there is a .NET way to do what our handlers do.Thanks,George McKinney
Is there a .NET equivalent of Axis handlers?
We are exploring using webservices and clients with messages that have attachments. My understanding is that SwA ( as described in http://www.w3.org/TR/SOAP-attachments ) doesn't require anything specific in the wsdl - but an article in DeveloperWorks ( http://www-128.ibm.com/developerworks/webservices/library/ws-tip-soapjax.html ) has stuff in the wsdl. On the gripping hand, we've built a toy service and client that use handlers to add and retrieve attachments while having the wsdl completely ignore them. Because we will need to be compatible with .NET clients and webservices that our partners will use, I want to know if there is a .NET way to do what our handlers do. Thanks, George McKinney
generate WSDL using java code
Hi all, Does anyone know of utility or framework classes for generating a WSDL? I'm not talking about generating WSDL from existing java files. What I need is a way to generate a WSDL file. I know its possible to generate it by simply using XMLDOM of my choice. But what I'm looking for is a utility that will make the job easier. Thanks, Asaf Lahav VP R&D, Prima Grid LTD. Cellular: 972-54-4717955 Phone: 972-3-6540255 Fax: 972-3-6540254
Re: WebServices very slow after some requests
Hello, For this sort of problem, I've found analysis of jvm thread dumps very effective. If you're using unix, then "kill -QUIT pid" is usually sufficient to get a current thread dump. In this case, pid would be the process id of the running Tomcat process. If you're using Windows, then the easiest way to get a thread dump is by running the target process in the foreground and using CTRL+BREAK. The output will usually go to stderr or stdout so, using output redirection on the process at startup is recommended. Where the output goes depends on the jdk in use. It may wind up in the stderr/stdout, or files like javadump may appear in the current directory of the process being dumped. Analyzing a threaddump can be tricky, but I suspect that in this case it may jump from the output. Personally, I'd look for some number of threads having the same or very similar top of stack. This will indicate the first level of debug. I suspect that the threads are waiting on some external resource -- at least that's been my experience in cases like these. Good luck. On Wednesday 22 February 2006 12:54, Franz Coriand wrote: > Hi all, > > we have the problem, that our webservices become very slow after some > requests. > For the first request we need about 10s. > For the 100th request we need about 2mins - its the same request like > the first one, with the same result. > > We use Tomcat 5.5.12 and Axis 1.3. > > We have no clue what's the problem. > Do you have any ideas? > > Thanks, Franz -- Regards, Erik
Re: WebServices very slow after some requests
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Franz Coriand wrote: > Hi all, > > we have the problem, that our webservices become very slow after some > requests. > For the first request we need about 10s. > For the 100th request we need about 2mins - its the same request like > the first one, with the same result. > > We use Tomcat 5.5.12 and Axis 1.3. > > We have no clue what's the problem. > Do you have any ideas? You may not to profile the tomcat server and see where the slowdown occurs. It may not be in the webservice, but in something you are doing. For example, if there is a memory leak, and so lots of garbage collections, then that would slow things down. I use jprofiler for this, but we had to buy it. - -- "Love is mutual self-giving that ends in self-recovery." Fulton Sheen James Black[EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD/KzdikQgpVn8xrARA+uqAJ4wtYo7vwcfxjKx6/YH2Ej4y5WLZgCgkBNF ol/Fcy9UyI5EAsidIgY2rpM= =3/J8 -END PGP SIGNATURE-
RE: need to compile Java code
Hi!
You have to add all the jars in axis/lib to your
classpath!
Best regards,
--DI Günter
GrossbergerSolution Architect Tel: +43 1 329 50
161Software AG Österreich Fax: +43 1 329 50 171Guglgasse
7-9 GSM: +43 676 833 29
2611030
Wien
http://www.softwareag.com/austria
From: Alasadi, Saad
[mailto:[EMAIL PROTECTED] Sent: Wednesday, February
22, 2006 6:44 PMTo: 'axis-user@ws.apache.org'Subject:
need to compile Java code
I have
java files that use axis. Every time I try to compile I get
loads of errors. My java code is in c:\javacode and the axis is c:\axis. I set
the axis_home as the documentation stated.
C:\javaCode>echo %classpath%
C:\j2sdk1.4.2_06\lib;
C:\javaCode>javac -classpath
%AXIS_HOME%\lib\axis.jar SingleSignOnLocator.java
SingleSignOnLocator.java:11: cannot access
javax.xml.rpc.Service
file javax\xml\rpc\Service.class not found
public class SingleSignOnLocator extends org.apache.axis.client.Service implemen
ts org.tempuri.SingleSignOn {
^
SingleSignOnLocator.java:31: cannot resolve
symbol
symbol : class SingleSignOnSoap
location: package tempuri
public org.tempuri.SingleSignOnSoap getSingleSignOnSoap() throws
javax.xml.r
pc.ServiceException {
^
SingleSignOnLocator.java:31: package
javax.xml.rpc does not exist
public org.tempuri.SingleSignOnSoap getSingleSignOnSoap() throws
javax.xml.r
pc.ServiceException {
^
SingleSignOnLocator.java:42: cannot resolve
symbol
symbol : class SingleSignOnSoap
location: package tempuri
public org.tempuri.SingleSignOnSoap getSingleSignOnSoap(java.net.URL portAdd
ress) throws
javax.xml.rpc.ServiceException {
WebServices very slow after some requests
Hi all, we have the problem, that our webservices become very slow after some requests. For the first request we need about 10s. For the 100th request we need about 2mins - its the same request like the first one, with the same result. We use Tomcat 5.5.12 and Axis 1.3. We have no clue what's the problem. Do you have any ideas? Thanks, Franz begin:vcard fn:Franz Coriand n:Coriand;Franz adr:;;Buchaer Str. 8c;Jena;Thueringen;07745;Germany email;internet:[EMAIL PROTECTED] tel;home:+49-(0)3641-215542 tel;cell:+49-(0)171-3665238Buc url:http://www.coriand.com/ version:2.1 end:vcard
need to compile Java code
I have java files that use axis. Every time I try to compile I get loads
of errors. My java code is in c:\javacode and the axis is c:\axis. I set the axis_home as the documentation stated.
C:\javaCode>echo %classpath%
C:\j2sdk1.4.2_06\lib;
C:\javaCode>javac -classpath
%AXIS_HOME%\lib\axis.jar SingleSignOnLocator.java
SingleSignOnLocator.java:11: cannot access javax.xml.rpc.Service
file javax\xml\rpc\Service.class not found
public class SingleSignOnLocator
extends org.apache.axis.client.Service implemen
ts org.tempuri.SingleSignOn
{
^
SingleSignOnLocator.java:31: cannot resolve symbol
symbol : class SingleSignOnSoap
location: package tempuri
public
org.tempuri.SingleSignOnSoap getSingleSignOnSoap()
throws javax.xml.r
pc.ServiceException {
^
SingleSignOnLocator.java:31: package javax.xml.rpc does not exist
public
org.tempuri.SingleSignOnSoap getSingleSignOnSoap()
throws javax.xml.r
pc.ServiceException {
^
SingleSignOnLocator.java:42: cannot resolve symbol
symbol : class SingleSignOnSoap
location: package tempuri
public
org.tempuri.SingleSignOnSoap getSingleSignOnSoap(java.net.URL portAdd
ress) throws javax.xml.rpc.ServiceException {
RE: Generate Java from XSD only
To Stefan: Robert's points are valid. Just be forewarned that the XSB files he mentions contain globally unique identifiers for schemas and packages that must be referenced from your calling code. So, if your application 1 necessitates changing code in your XMLBeans class library, you'll have to re-generate the stub code for application 1 AND application 2 because re-compiling the schema can result in a new GUID for that schema and its corresponding package. Axis2 may have done a better job of insulating this annoyance but I haven't started using Axis2 yet so I don' t know for sure. JT From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 22, 2006 9:25 AMTo: axis-user@ws.apache.orgSubject: Re: Generate Java from XSD only Someone else may want to comment that has some better knowledge on this. Axis2 is XML Binding independant or at least strives to be. Axis 1 less so. Axis2 has at least adb, xmlbeans and I believe jaxb - all to varying degrees of stability. IMHO is that xmlbeans is currently the most stable in regards to axis2. Now what xmlbeans does is convert xml to java source files. It also generates xsb files, and also interesting enough for your case, is a class file. See the axis2 code generation guide - particularly the ant task - for more info. So in short, I'd bet you could indeed acomplish the first part of the wsdl data binding, ie, the part, save those .class and .xsb files, and then later reference those to complete the databinding. I don't think that currently exists - you'd have to hack the source a bit. Keep in mind that axis2 wsdl2java generates skeletons, callbacks, message receivers etc. What you're asking to do I think is to resume that part at a later time. Possible? Probably but not out of the box. HTH,Robert http://www.braziloutsource.com/ On 2/22/06, Stefan Freyr Stefansson <[EMAIL PROTECTED] > wrote: Hello.I was hoping someone could shed some light on the following issue.I have to program against two webservices that use datatypes specified by athird party. These datatypes are specified by XSD's that are publically available.So what I'd like to do is to generate the Java classes for the third partydatatypes first, and then generate the Java classes for the two webservices,referencing the already generated datatypes somehow. I want to do this to avoid having the same Java classes in two places in my code tree.I'm working on getting the WSDL for the two webservices changed (thesewebservices are not developed on site so it takes a little longer to get such changes) but the main questions are:1) How do I generate Java classes from XSD's only with no WSDL referencingthem.2) How do I generate Java code for the web services and "reference" thealready created Java classes for the datatypes used. You may be asking why I want to do this and the reason is that I don't wantthe code for the two webservices to be put into the same code tree. So, Ibasically want three code trees, one for the common datatypes and two more for the web services code.Can this be done somehow? Anybody have any pointers as to how it would bebetter to do this?Kind regards, Stefan Freyr.
Re: Generate Java from XSD only
Someone else may want to comment that has some better knowledge on this. Axis2 is XML Binding independant or at least strives to be. Axis 1 less so. Axis2 has at least adb, xmlbeans and I believe jaxb - all to varying degrees of stability. IMHO is that xmlbeans is currently the most stable in regards to axis2. Now what xmlbeans does is convert xml to java source files. It also generates xsb files, and also interesting enough for your case, is a class file. See the axis2 code generation guide - particularly the ant task - for more info. So in short, I'd bet you could indeed acomplish the first part of the wsdl data binding, ie, the part, save those .class and .xsb files, and then later reference those to complete the databinding. I don't think that currently exists - you'd have to hack the source a bit. Keep in mind that axis2 wsdl2java generates skeletons, callbacks, message receivers etc. What you're asking to do I think is to resume that part at a later time. Possible? Probably but not out of the box. HTH, Robert http://www.braziloutsource.com/ On 2/22/06, Stefan Freyr Stefansson <[EMAIL PROTECTED] > wrote: Hello.I was hoping someone could shed some light on the following issue.I have to program against two webservices that use datatypes specified by athird party. These datatypes are specified by XSD's that are publically available.So what I'd like to do is to generate the Java classes for the third partydatatypes first, and then generate the Java classes for the two webservices,referencing the already generated datatypes somehow. I want to do this to avoid having the same Java classes in two places in my code tree.I'm working on getting the WSDL for the two webservices changed (thesewebservices are not developed on site so it takes a little longer to get such changes) but the main questions are:1) How do I generate Java classes from XSD's only with no WSDL referencingthem.2) How do I generate Java code for the web services and "reference" thealready created Java classes for the datatypes used. You may be asking why I want to do this and the reason is that I don't wantthe code for the two webservices to be put into the same code tree. So, Ibasically want three code trees, one for the common datatypes and two more for the web services code.Can this be done somehow? Anybody have any pointers as to how it would bebetter to do this?Kind regards, Stefan Freyr.
RE: Generate Java from XSD only
There are other schema compilers out there that do the same thing for XSDs that WSDL2JAVA does for WSDLs. Whether you use XMLBeans, Castor, or some other XML binding, the principles will be similar to this Castor-based example: http://www-128.ibm.com/developerworks/webservices/library/ws-castor/ Jim Tootell Anteon Corp. -Original Message- From: Stefan Freyr Stefansson [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 22, 2006 8:38 AM To: axis-user@ws.apache.org Subject: Generate Java from XSD only Hello. I was hoping someone could shed some light on the following issue. I have to program against two webservices that use datatypes specified by a third party. These datatypes are specified by XSD's that are publically available. So what I'd like to do is to generate the Java classes for the third party datatypes first, and then generate the Java classes for the two webservices, referencing the already generated datatypes somehow. I want to do this to avoid having the same Java classes in two places in my code tree. I'm working on getting the WSDL for the two webservices changed (these webservices are not developed on site so it takes a little longer to get such changes) but the main questions are: 1) How do I generate Java classes from XSD's only with no WSDL referencing them. 2) How do I generate Java code for the web services and "reference" the already created Java classes for the datatypes used. You may be asking why I want to do this and the reason is that I don't want the code for the two webservices to be put into the same code tree. So, I basically want three code trees, one for the common datatypes and two more for the web services code. Can this be done somehow? Anybody have any pointers as to how it would be better to do this? Kind regards, Stefan Freyr.
No data back on doc / lit based wsdl generated code
All, I got my web service working fine in Axis 1.3 by using the jws instant deployment. Data was going to and coming from the service just fine. The default on the instant deploy appears to be RPC based, so I wanted to deploy it out as doc / lit using the wsdd deployment file. I have data going to the service, I can see the service process the data, and the returned String variable is populated with data. The issue is, however, when I return the populated String from the web service, the data comes back as null or “” in both a .Net and a Java client (both auto generated from wsdl). Here is the wsdl: Is there any other information I can supply? Again, it does return data using the instant deploy, and in both the instant deploy AND the doc / lit wsdd version data get to the web service. Thank you, Paul Lessard
Generate Java from XSD only
Hello. I was hoping someone could shed some light on the following issue. I have to program against two webservices that use datatypes specified by a third party. These datatypes are specified by XSD's that are publically available. So what I'd like to do is to generate the Java classes for the third party datatypes first, and then generate the Java classes for the two webservices, referencing the already generated datatypes somehow. I want to do this to avoid having the same Java classes in two places in my code tree. I'm working on getting the WSDL for the two webservices changed (these webservices are not developed on site so it takes a little longer to get such changes) but the main questions are: 1) How do I generate Java classes from XSD's only with no WSDL referencing them. 2) How do I generate Java code for the web services and "reference" the already created Java classes for the datatypes used. You may be asking why I want to do this and the reason is that I don't want the code for the two webservices to be put into the same code tree. So, I basically want three code trees, one for the common datatypes and two more for the web services code. Can this be done somehow? Anybody have any pointers as to how it would be better to do this? Kind regards, Stefan Freyr. pgpYv8Eawc2Y0.pgp Description: PGP signature
Re: Retrieve Web Service name in Axis2
Thanks for your help Deepal... I know that. My problem is that I want to get the name of my WS in the moment I invoke it, from one of the clases implemented in the WS. I want to know if there is a class in the Axis2 API that alows me to do that (get my name from code if I'm the invoked WS).On 2/22/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote: Hi Yariel;Name of the service will be the name of the archive file if the services.xml has only one service element meaning if the services.xmllook like below // service dataIn the case of servicegroup name of the service will be the name that you specified in services.xml as an example if the services.xml is likebelow; so name of the service will be foo in this case. Yariel Ramos Moreno wrote:> How can I retrieve the name of a Web Service deployed in Axis2 sever> in runtime? I mean, when the service is invoked, I need to get the> name of it from inside it in my code. >> Thanks in advance,>> Yariel.--Thanks,Deepal~Future is Open~
sessions frameworks interoperable
Hi, >From my research on the web, the topic about sessions in web services seems to generate quite alot of questions but not alot of answers. I know that Axis 1.3 handles session IDs well in the Soap Header with the SimpleSessionHandler but I need to know if there is an interoperable way of doing this. It is extremely difficult to get clear information about how different framework handle sessions. I can't rely on any namespaces but those in the WS-I Basic Profile and my own. My hope was that I would be able to specify the sessionID in the WSDL as a Soap Header and that the frameworks would be able to use this to handle sessions. The only reliable way I can think of is to send a session ID in the message body and let my application code handle sessions. I'm in a hurry to solve this issue since my boss is on me about it and my stress level is way up there... It feels kinda hopeless. kind regards, Clarence
How to dynamically modify a server-side handler parameter?
Hello I would like to know how I can programmatically modify a parameter for a handler invoked on the server side? THanks a lot Jean-Noel Colin
Re: [Axis2] read documentation but still lost
@Ajith Ranabahu it's just the wsdl from the Code Generator Wizard - Command Line Tool tutorial, however I have attached it. @Chinthaka - axis2 snaphot compile failed I have started a new thread 'junit tests on today svn build failed' thanks for your help! andreas > Hi, > Can you attach the WSDL ? > > Ajith > > On 2/22/06, Andreas Bohnert <[EMAIL PROTECTED]> wrote: >>> You could try >>> minOccurs = 0 on any new fields, and my guess is that since the service >>> doesn't require them to be part of then envelope, they won't be missed if >>> they are not there. IOW, they can't be mandatory fields. >> I tried it with XMLBean databinding and it even works if I do not set >> them to minOccurs=0. >> thats perfect for me! >> >> I would like to check out if adb works as well, but since wsdl2java does >> not support adb right now (gives me a nullpointer exception), I have to >> wait for the next release. >> tried to compile current axis2 snapshot, but it failed :( >> >> >> thanks very much for your help, robert! >> andreas >> >> > > > -- > Ajith Ranabahu > http://login"; xmlns:tns="http://login"; xmlns="http://schemas.xmlsoap.org/wsdl/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:ns2="http://login/types";> http://login/types"; xmlns:tns="http://login/types"; xmlns:soap11-enc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns="http://www.w3.org/2001/XMLSchema";> http://schemas.xmlsoap.org/soap/encoding/"/> http://schemas.xmlsoap.org/soap/http"; style="document"/> http://localhost:8080/axis2/services/LoginEndpoint"/>
Re: [Axis2] read documentation but still lost
Hi, Can you attach the WSDL ? Ajith On 2/22/06, Andreas Bohnert <[EMAIL PROTECTED]> wrote: > > You could try > > minOccurs = 0 on any new fields, and my guess is that since the service > > doesn't require them to be part of then envelope, they won't be missed if > > they are not there. IOW, they can't be mandatory fields. > > I tried it with XMLBean databinding and it even works if I do not set > them to minOccurs=0. > thats perfect for me! > > I would like to check out if adb works as well, but since wsdl2java does > not support adb right now (gives me a nullpointer exception), I have to > wait for the next release. > tried to compile current axis2 snapshot, but it failed :( > > > thanks very much for your help, robert! > andreas > > -- Ajith Ranabahu
Re: [Axis2] read documentation but still lost
Andreas Bohnert wrote: >tried to compile current axis2 snapshot, but it failed :( > > If you give us some information, may be we can help. Chinthaka > >thanks very much for your help, robert! >andreas > > > > signature.asc Description: OpenPGP digital signature
Invalid security context
Hi, call.invoke(java.lang.Object[] params) is generating axisFaultException saying Invalid security context. Any body have experience of this. please help me. ~Alok
Re: [Axis2] read documentation but still lost
> You could try > minOccurs = 0 on any new fields, and my guess is that since the service > doesn't require them to be part of then envelope, they won't be missed if > they are not there. IOW, they can't be mandatory fields. I tried it with XMLBean databinding and it even works if I do not set them to minOccurs=0. thats perfect for me! I would like to check out if adb works as well, but since wsdl2java does not support adb right now (gives me a nullpointer exception), I have to wait for the next release. tried to compile current axis2 snapshot, but it failed :( thanks very much for your help, robert! andreas
junit tests on today svn build failed
some junit test on the today svn sources failed: test:test: [junit] Running samples.wsdl.perf.PerfPortTypeTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 13,588 sec [junit] Running org.apache.axis2.integration.EchoTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,486 sec [junit] Running org.apache.axis2.rpc.RPCCallTest [junit] Tests run: 16, Failures: 0, Errors: 0, Time elapsed: 45,255 sec [junit] Running org.apache.axis2.rpc.MultirefTest [junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 26,033 sec [junit] Running org.apache.axis2.engine.ThreadingTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 5,512 sec [junit] Running org.apache.axis2.engine.EchoRawXMLOnTwoChannelsSyncTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,01 sec [junit] Running org.apache.axis2.engine.EchoRawXMLTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 11,606 sec [junit] Running org.apache.axis2.engine.CharactersetEncodingTest [junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 31,739 sec [junit] Running org.apache.axis2.engine.ServiceGroupContextTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,158 sec [junit] Running org.apache.axis2.engine.ServiceCreateTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,636 sec [junit] Running org.apache.axis2.engine.EchoRawXMLMultipleTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 12,948 sec [junit] Running org.apache.axis2.engine.MessageContextInjectionTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1,449 sec [junit] Running org.apache.axis2.engine.OneWayRawXMLTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,077 sec [junit] Running org.apache.axis2.engine.CommonsHTTPEchoRawXMLTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6,335 sec [junit] Running org.apache.axis2.engine.MessageWithServerTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 64,298 sec [junit] Running org.apache.axis2.engine.WSDLClientTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,664 sec [junit] Running org.apache.axis2.engine.SOAPversionTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 8,193 sec [junit] Running org.apache.axis2.engine.EchoRawXMLLoadTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,934 sec [junit] Running org.apache.axis2.engine.EchoRawXMLChunkedTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4,041 sec [junit] Running org.apache.axis2.engine.EchoRawXMLOnTwoChannelsTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,683 sec [junit] Running org.apache.axis2.engine.CallUnregisteredServiceTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,712 sec [junit] Running org.apache.axis2.engine.ServiceDispatchingTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 3,978 sec [junit] Running org.apache.axis2.engine.FaultHandlingTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 6,031 sec [junit] Running org.apache.axis2.engine.HandlerFailureTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,663 sec [junit] Running org.apache.axis2.engine.AxisServiceBuilderTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0,772 sec [junit] Running org.apache.axis2.engine.EchoRawRuntimeProxyTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,829 sec [junit] Running org.apache.axis2.groovy.GroovyServiceTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 13,046 sec [junit] Running org.apache.axis2.tcp.TCPEchoRawXMLTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 11,065 sec [junit] Running org.apache.axis2.tcp.TCPTwoChannelEchoRawXMLTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3,32 sec [junit] Running org.apache.axis2.security.Scenario1Test [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 8,629 sec [junit] Running org.apache.axis2.security.Scenario2Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 13,439 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario2Test FAILED [junit] Running org.apache.axis2.security.Scenario2aTest [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 14,039 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario2aTest FAILED [junit] Running org.apache.axis2.security.Scenario3Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 13,102 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario3Test FAILED [junit] Running org.apache.axis2.security.Scenario4Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 13,097 sec [junit] [ERROR] TEST org.apac
RE: Problem with MustUnderstand headers when migrating from axis 1.1 to 1.3
Hi Dies,
Thanks for all the information. I will look at the JAX-RPC spec and try it
out.
Thanks and regards
Sajith
-Original Message-
From: Dies Koper [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 22, 2006 2:49 PM
To: axis-user@ws.apache.org
Subject: Re: Problem with MustUnderstand headers when migrating from axis
1.1 to 1.3
Hello Sajith,
Refer to the JAX-RPC1.1 spec to see how to use a client handler in a
portable way. I believe it goes something like this:
sf = javax.xml.rpc.ServiceFactory.newInstance();
SEIService si = (SEIService)sf.loadService(SEIService.class);
// register client handler
javax.xml.rpc.handler.HandlerRegistry hr = si.getHandlerRegistry();
java.util.List hl = new java.util.ArrayList();
hl.add(new
javax.xml.rpc.handler.HandlerInfo(YourHandler.class,null,null));
hr.setHandlerChain(new QName("http://localhost/xxx/","yourPort";),hl);
SEI sei = si.getSEIPort();
((javax.xml.rpc.Stub)sei)._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY, url);
YourHandler should implement javax.xml.rpc.handler.Handler.
Hope that helps,
Dies
sajith wrote:
> Hi Dies,
>
> As you suggested I debugged both axis 1.1 and 1.3 it seems Axis 1.1 does
not
> handle "mustUnderstand", where as axis 1.3 provides a handle
implementation
> called "MustUnderstandChecker". This is the place where the error is
> generated.
>
> So either I could make changes to this class or I could have my own
handler
> instead. Since I'm very new to web services I don't know how to plug-in
this
> handler to axis. It doesn't seem like it cannot be externally plugged-in
to
> AxisClient without modifying the existing 1.3 code.
>
> Any thoughts on this will be highly appreciated.
>
>
> Thanks and regards
> Sajith.
>
>
> -Original Message-
> Sent: Wednesday, February 22, 2006 11:56 AM
> To: axis-user@ws.apache.org
> Subject: Re: Problem with MustUnderstand headers when migrating from axis
> 1.1 to 1.3
>
> Hello Sajith,
>
> The stub seems to generate a Fault when it receives a SOAP message with
> a header with a mustUnderstand="1" attribute.
> I thought this was according to the spec, as the Axis generated stub
> does not understand your header.
> However, I believe some months ago there was some debate on this ML
> whether Axis should be doing this, or whether the client application
> should be responsible for this itself.
> There was no conclusion.
>
> If you get no response from others, you could try searching the source
> code for a comment regarding this change (as you said it used to work
> fine with Axis 1.1, maybe you can find why it was changed, and then
> judge whether that was a mistake or a new feature you'd have to work
with).
> Otherwise, you could employ a client-side handler that understands the
> header and removes it from the SOAP message after processing it.
>
> Good luck,
> Dies
>
>
> sajith wrote:
>> Hi,
>>
>>
>>
>> I'm migrating from axis 1.1 to 1.3. My webservice client fails when
> invoking
>> the method with following axis error.
>>
>> I tested the same code with axis 1.1 and it works fine.
>>
>>
>>
>>
>>
>> Axis fault
>>
>>
>>
>> Exception in thread "main" AxisFault
>>
>> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}MustUnderstand
>>
>> faultSubcode:
>>
>> faultString: Did not understand "MustUnderstand" header(s):
>>
>> faultActor:
>>
>> faultNode:
>>
>> faultDetail:
>>
>> {http://xml.apache.org/axis/}stackTrace:
>>
>> at
>>
>
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChe
>> cker.java:96)
>>
>> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
>> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>>
>> at org.apache.axis.client.Call.invoke(Call.java:2767)
>>
>> at org.apache.axis.client.Call.invoke(Call.java:2443)
>>
>> at org.apache.axis.client.Call.invoke(Call.java:2366)
>>
>> at org.apache.axis.client.Call.invoke(Call.java:1812)
>>
>> at
>>
>
net.scandinavian.nibp2.SAPI_v2.AvailabilitySoap_BindingStub.getAvailabilityN
>> ewReservation(AvailabilitySoap_BindingStub.java:587)
>>
>> at Test.main(Test.java:21)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
>>
>> at
>>
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
>> )
>>
>> at
>>
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
>> .java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:585)
>>
>> at
>> com.intellij.rt.execution.application.AppMain.main(AppMain.java:86)
>>
>>
>>
>> {http://xml.apache.org/axis/}hostname:sajith
>>
>>
>>
>> Did not understand "MustUnderstand" header(s):
>>
>> at
>>
>
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChe
>> cker.java:96)
>>
>> at
>
Re: axis on Sun Application Server 8.2
Even when I add activation.jar and mail.jar to my classpath to eliminate the warning I get while deploying web service I still get the same fault.On 2/21/06,
Gedas A <[EMAIL PROTECTED]> wrote:Hello,
I deployed axis 1.3 on Sun App Server 8.2. I granted the following permissions in order to get it running:==grant { permission java.lang.RuntimePermission "getClassLoader";
permission java.lang.RuntimePermission "createClassLoader"; permission java.net.SocketPermission "*", "connect,accept,resolve"; permission java.io.FilePermission "<>", "read,write,delete";
permission java.util.PropertyPermission "user.language", "write"; permission javax.management.MBeanPermission "org.apache.commons.modeler.BaseModelMBean#-[axis:type=server]", "registerMBean";
permission javax.management.MBeanPermission "org.apache.commons.modeler.BaseModelMBean#-[axis:type=deploy]", "registerMBean"; permission javax.management.MBeanPermission "org.apache.commons.modeler.BaseModelMBean#-
[axis:type=query]", "registerMBean";};==Validation page is happy.But when I try to deploy a web service I get:==$ java org.apache.axis.client.AdminClient
deploy.wsdd2006.2.21 15.45.17 org.apache.axis.utils.JavaUtils isAttachmentSupportedWARNING: Unable to find required classes (javax.activation.DataHandler and javax.mail.internet.MimeMultipart). Attachment support is disabled.
Processing file deploy.wsddException: AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.reflect.InvocationTargetException faultActor: faultNode: faultDetail: {
http://xml.apache.org/axis/}hostname:gedas
==Application server log says:[#|2006-02-21T15:45:18.359+0200|INFO|sun-appserver-pe8.2|javax.enterprise.system.stream.out|_ThreadID=11;|- Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-
config.wsdd|#]I checked the server-config.wsdd file. The entry for my web service is there but there is no entry in list of the web services in the axis webapp.Everything works on Tomcat 5.5.15, using the same wsdl, wsdd and web services code.
Am I missing something?--Gedas
[axis2] Problem with Websphere 6 and Axis2 security module
Hello, I have some issues when trying to run Axis2 version 0.94 in Websphere 6 with the security module engaged. Please note that the services do not actually perform any encryption/signing etc, the module is only engaged in the axis2.xml. Problem no 1: - In Websphere 6 on WinXP. 1) Deploy one of the sample services included in the 0.94 release, I used MyService.aar. 2) Execute the service through a call from the client. It works as expected returning a response. Now trying to stop the Websphere windows service it fails with: "Could not stop the IBM WebSphere Application Server V6 - XXX service on Local Computer. The service did not return an error. ..." To restart websphere I have to kill the process. This has been verified on two different Websphere 6 installations. If I do not execute any webservice calls the server can be restarted in a controlled fashion. Problem no 2: - The reason I am restarting the entire Websphere server in the first place is that trying to restart the actual Axis2 webapp is failing for some reason, after executing a webservice call. The webapp restarts but is then broken and give me errors each time I send a web service request to the server. [2006-02-22 11:23:16:710 CET] 004a ServletWrappe E SRVE0100E: Did not realize init() exception thrown by servlet AxisServlet: java.lang.ExceptionInInitializerError at java.lang.Class.forName1(Native Method) at java.lang.Class.forName(Class.java:180) at org.apache.xml.security.Init.init(Unknown Source) at org.apache.ws.security.WSSConfig.(WSSConfig.java:72) <> Caused by: java.lang.RuntimeException: Unable to create nullNodejava.lang.NullPointerException at org.apache.xml.security.c14n.implementations.CanonicalizerBase.(Unknown Source) ... 39 more If I disengaged the security module (remove the entry from axis2.xml) the webapp in Websphere can be restarted and will function properly. Problem no 3: - The reason I have to restart the webapp is that hotupdate is not working properly (I believe there is a Jira for this already). In effect this means I have to force-kill my Websphere process each time I deploy/update a webservice which is not very nice. Best Regards, Johan Andersson
MustUnderstand header
Hi all,
I am getting the following exception from an Axis client trying to
consume a WCF(Indigo) service. I am not an Axis programmer, but want to
see if it can consume a WCF service. I am using Sun java studio for
creating this client.
Exception :
Did not understand "MustUnderstand"
header(s):{http://schemas.xmlsoap.org/ws/2004/08/addressing}Action,
{http://schemas.xmlsoap.org/ws/2004/08/addressing}To
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstan
dChecker.java:96)
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
org.apache.axis.client.Call.invokeEngine(Call.java:2784)
org.apache.axis.client.Call.invoke(Call.java:2767)
org.apache.axis.client.Call.invoke(Call.java:2443)
org.apache.axis.client.Call.invoke(Call.java:2366)
org.apache.axis.client.Call.invoke(Call.java:1812)
org.tempuri.WSHttpBinding_IProfileStub.login(WSHttpBinding_IProfileStub.
java:419)
LoginServlet.processRequest(LoginServlet.java:62)
LoginServlet.doGet(LoginServlet.java:106)
javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
sun.reflect.GeneratedMethodAccessor192.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
java.lang.reflect.Method.invoke(Method.java:585)
org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.jav
a:165)
note The full stack trace of the root cause is available in the
Sun-Java-System/Application-Server logs.
Regards,
Girish Kumar
-Original Message-
From: Dies Koper [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 22, 2006 2:19 PM
To: axis-user@ws.apache.org
Subject: Re: Problem with MustUnderstand headers when migrating from
axis 1.1 to 1.3
Hello Sajith,
Refer to the JAX-RPC1.1 spec to see how to use a client handler in a
portable way. I believe it goes something like this:
sf = javax.xml.rpc.ServiceFactory.newInstance();
SEIService si = (SEIService)sf.loadService(SEIService.class);
// register client handler
javax.xml.rpc.handler.HandlerRegistry hr = si.getHandlerRegistry();
java.util.List hl = new java.util.ArrayList();
hl.add(new
javax.xml.rpc.handler.HandlerInfo(YourHandler.class,null,null));
hr.setHandlerChain(new QName("http://localhost/xxx/","yourPort";),hl);
SEI sei = si.getSEIPort();
((javax.xml.rpc.Stub)sei)._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY,
url);
YourHandler should implement javax.xml.rpc.handler.Handler.
Hope that helps,
Dies
sajith wrote:
> Hi Dies,
>
> As you suggested I debugged both axis 1.1 and 1.3 it seems Axis 1.1
does not
> handle "mustUnderstand", where as axis 1.3 provides a handle
implementation
> called "MustUnderstandChecker". This is the place where the error is
> generated.
>
> So either I could make changes to this class or I could have my own
handler
> instead. Since I'm very new to web services I don't know how to
plug-in this
> handler to axis. It doesn't seem like it cannot be externally
plugged-in to
> AxisClient without modifying the existing 1.3 code.
>
> Any thoughts on this will be highly appreciated.
>
>
> Thanks and regards
> Sajith.
>
>
> -Original Message-
> Sent: Wednesday, February 22, 2006 11:56 AM
> To: axis-user@ws.apache.org
> Subject: Re: Problem with MustUnderstand headers when migrating from
axis
> 1.1 to 1.3
>
> Hello Sajith,
>
> The stub seems to generate a Fault when it receives a SOAP message
with
> a header with a mustUnderstand="1" attribute.
> I thought this was according to the spec, as the Axis generated stub
> does not understand your header.
> However, I believe some months ago there was some debate on this ML
> whether Axis should be doing this, or whether the client application
> should be responsible for this itself.
> There was no conclusion.
>
> If you get no response from others, you could try searching the source
> code for a comment regarding this change (as you said it used to work
> fine with Axis 1.1, maybe you can find why it was changed, and then
> judge whether that was a mistake or a new feature you'd have to work
with).
> Otherwise, you could employ a client-side handler that understands the
> header and removes it from the SOAP message after processing it.
>
> Good luck,
> Dies
>
>
> sajith wrote:
>> Hi,
>>
>>
>>
>> I'm migrating from axis 1.1 to 1.3. My webservice client fails when
> invoking
>> the method with following axis error.
>>
>> I tested the same code with axis 1.1 and it works fine.
>>
>>
>>
>>
>>
>> Axis fault
>>
>>
>
Re: Problem with MustUnderstand headers when migrating from axis 1.1 to 1.3
Hello Sajith,
Refer to the JAX-RPC1.1 spec to see how to use a client handler in a
portable way. I believe it goes something like this:
sf = javax.xml.rpc.ServiceFactory.newInstance();
SEIService si = (SEIService)sf.loadService(SEIService.class);
// register client handler
javax.xml.rpc.handler.HandlerRegistry hr = si.getHandlerRegistry();
java.util.List hl = new java.util.ArrayList();
hl.add(new
javax.xml.rpc.handler.HandlerInfo(YourHandler.class,null,null));
hr.setHandlerChain(new QName("http://localhost/xxx/","yourPort";),hl);
SEI sei = si.getSEIPort();
((javax.xml.rpc.Stub)sei)._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY, url);
YourHandler should implement javax.xml.rpc.handler.Handler.
Hope that helps,
Dies
sajith wrote:
Hi Dies,
As you suggested I debugged both axis 1.1 and 1.3 it seems Axis 1.1 does not
handle "mustUnderstand", where as axis 1.3 provides a handle implementation
called "MustUnderstandChecker". This is the place where the error is
generated.
So either I could make changes to this class or I could have my own handler
instead. Since I'm very new to web services I don't know how to plug-in this
handler to axis. It doesn't seem like it cannot be externally plugged-in to
AxisClient without modifying the existing 1.3 code.
Any thoughts on this will be highly appreciated.
Thanks and regards
Sajith.
-Original Message-
Sent: Wednesday, February 22, 2006 11:56 AM
To: axis-user@ws.apache.org
Subject: Re: Problem with MustUnderstand headers when migrating from axis
1.1 to 1.3
Hello Sajith,
The stub seems to generate a Fault when it receives a SOAP message with
a header with a mustUnderstand="1" attribute.
I thought this was according to the spec, as the Axis generated stub
does not understand your header.
However, I believe some months ago there was some debate on this ML
whether Axis should be doing this, or whether the client application
should be responsible for this itself.
There was no conclusion.
If you get no response from others, you could try searching the source
code for a comment regarding this change (as you said it used to work
fine with Axis 1.1, maybe you can find why it was changed, and then
judge whether that was a mistake or a new feature you'd have to work with).
Otherwise, you could employ a client-side handler that understands the
header and removes it from the SOAP message after processing it.
Good luck,
Dies
sajith wrote:
Hi,
I'm migrating from axis 1.1 to 1.3. My webservice client fails when
invoking
the method with following axis error.
I tested the same code with axis 1.1 and it works fine.
Axis fault
Exception in thread "main" AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}MustUnderstand
faultSubcode:
faultString: Did not understand "MustUnderstand" header(s):
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChe
cker.java:96)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
net.scandinavian.nibp2.SAPI_v2.AvailabilitySoap_BindingStub.getAvailabilityN
ewReservation(AvailabilitySoap_BindingStub.java:587)
at Test.main(Test.java:21)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.intellij.rt.execution.application.AppMain.main(AppMain.java:86)
{http://xml.apache.org/axis/}hostname:sajith
Did not understand "MustUnderstand" header(s):
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChe
cker.java:96)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
net.scandinavian.nibp2.SAPI_v2.AvailabilitySoap_BindingStub.getAvailabilityN
ewReservation(AvailabilitySoap_BindingStub.java:587)
at Test.main(Test.java:21)
at sun.reflect.NativeMethodAccessorImpl.in
Module validation failed module.xml not found for the module
Hello, I am trying to use Axis2. I followed up the User Guide and samples to write a simple services (it is same as the Echo service). After I deployed the services successfully, I tried to use the wsdl2java to generate the Stub and Test case. But when I run the test. It just shows the following error, anything I missed to do, please help me. Testsuite: test.services.TestservicePortTest Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.437 sec - Standard Output --- - Module validation failed module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing - --- Testcase: testecho took 0.437 sec Caused an ERROR module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing at org.apache.axis2.deployment.DeploymentEngine.load(DeploymentEngine.java:542) at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:56) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:39) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:53) at test.services.TestservicePortStub.(TestservicePortStub.java:64) at test.services.TestservicePortStub.(TestservicePortStub.java:56) at test.services.TestservicePortTest.testecho(TestservicePortTest.java:23) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) Caused by: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing at org.apache.axis2.deployment.repository.util.ArchiveReader.creatModuleArchivefromResource(ArchiveReader.java:193) at org.apache.axis2.engine.AxisConfiguration.loadModulefromResources(AxisConfiguration.java:385) at org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:328) at org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:502) at org.apache.axis2.deployment.DeploymentEngine.load(DeploymentEngine.java:537) ... 21 more Caused by: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing at org.apache.axis2.deployment.repository.util.ArchiveReader.creatModuleArchivefromResource(ArchiveReader.java:158) ... 25 more
