java.lang.NoSuchMethodError witch WSDL2ws
Hi,
I have created a web service with the java axis tool.
It works fine from a java client.
Now , I need to make a C/C++ program.
I got this exception raised when running the WSDL2ws in order to make my C stubs:
Exception in thread main java.lang.NoSuchMethodError: org.apache.axis.wsdl.symbolTable.BindingEntry.getBindingStyle()Lorg/apache/axis/enum/Style;
at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.setMethodInfo(Unknown Source)
at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.getServiceInfo(Unknown Source)
at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.generateWrappers(Unknown Source)
at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main(Unknown Source)
Here are my arguments :
-sclient -v ${project_loc}/src/WebServiceAncre.wsdl
I run this command from Eclipse. It has the other required axis libraries (axis.jar, commons-*, jaxrpc etc..) in its classpath (I have tried
both axis 1.6 beta and 1.6 without success)
What is wrong please?
Help will be greatly appreciated. Many thanks in advance.
Re: Reporting bugs
Derek schrieb: This means that the next person who does blah hits the same problem, and MAYBE eventually resolves it by searching the mailing list archive, or maybe just wanders off and finds another SOAP server with a less user-hostile interface. Actually, I did. I wandered off to Axis 1 and found the error output of the old WSDL2Java more helpful, which eventually led me to those online validators. -Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Yet another security/rampart question
Hi. I'm still a novice concerning ws-security but I have been studying the security sample from the axis2 distribution and I think I have a fair understanding of how it works. But now I am considering a use case where a number of clients each has its ows certificate. This excludes me from using encryptionUser in the server side services.xml. So is it possible to set this dynamically from the service class to get the response encrypted with the public key of the current client and how would I go about doing it? Kind regards, -- Jan Bauer Nielsen Center of Knowledge Technology, Technical Knowledge Center of Denmark Anker Engelunds Vej 1, Postboks 777, 2800 Kongens Lyngby, Denmark Direct: (+45) 4525 7221, [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2]Module not found
Hi All, When I run the sample of EchoBlockingDualClient, I receive that: org.apache.axis2.AxisFault: Module not found What should I do? Thanks, Jiang
[Axis2] Service interface question
Hi all, the method declared into the Service interface does not throw any exception, while the usual implementation: this.inMsgCtx = opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE) does. Is it possible to remove the throws clause from the OperationContext.getMessageContext() method (which is a simply look-up from a HashMap and thus it will never throw any exception since the HashMap allows both null keys and values)? Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2 v1.0] send file with security
Dear All,
I have been trying to combine the test about sending file and
securing message.
My environment is Axis2 v1.0, nightly build released 4 June 06 on the
Jetty Servlet.
From other individual test such as sending text file, and security
sample had no problem on this, however with the combination one i got the
following error.
Client code:
/*
* Created on 19.07.2006
*
* TODO To change the template for this generated file go to
* Window - Preferences - Java - Code Style - Code Templates
*/
package security;
/**
* @author alice3
*
* TODO To change the template for this generated type comment go to
* Window - Preferences - Java - Code Style - Code Templates
*/
import org.apache.axiom.om.OMAbstractFactory;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMFactory;
import org.apache.axiom.om.OMNamespace;
import org.apache.axiom.om.OMText;
import org.apache.axis2.AxisFault;
import org.apache.axis2.Constants;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.context.ConfigurationContext;
import org.apache.axis2.context.ConfigurationContextFactory;
//import org.apache.axis2.soapmonitor.*;
import javax.activation.DataHandler;
import javax.activation.FileDataSource;
import javax.xml.namespace.QName;
import javax.xml.stream.XMLOutputFactory;
import javax.xml.stream.XMLStreamException;
import java.io.File;
import java.io.StringWriter;
public class SecureClient {
private File inputFile = null;
private QName operationName = new QName(fileSecurity);
public static void main(String[] args) {
try {
// Get the repository location from the args
String repo = args[0];
String port = args[1];
OMElement payload =
getEchoElement(/users/alice3/myDoc/Jettty6-Axis2.txt);
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(repo,
null);
ServiceClient serviceClient = new ServiceClient(configContext,
null);
Options options = new Options();
options.setTo(new EndpointReference(http://127.0.0.1:; + port +
/axis2/services/FileSecurity));
//options.setTo(new
EndpointReference(http://localhost:8080/axis2_new/services/SecureService;));
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);
options.setAction(urn:fileSecurity);
serviceClient.setOptions(options);
//Blocking invocation
OMElement result = serviceClient.sendReceive(payload);
StringWriter writer = new StringWriter();
result.serialize(XMLOutputFactory.newInstance()
.createXMLStreamWriter(writer));
writer.flush();
//System.out.println(Response: + writer.toString());
System.out.println(SecureService Invocation successful :-));
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
} catch (XMLStreamException e) {
e.printStackTrace();
}
}
private static OMElement getEchoElement(String fileName) {
DataHandler dh;
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs =
fac.createOMNamespace(http://ws.apache.org/axis2/xsd;, example1);
OMElement data = fac.createOMElement(fileSecurity, omNs);
OMElement input = fac.createOMElement(file, omNs);
OMElement pack = fac.createOMElement(pack, omNs);
FileDataSource f1 = new FileDataSource(fileName);
dh = new DataHandler(f1);
OMElement filename = fac.createOMElement(fileName, omNs);
// OMText textName = fac.createOMText(filename, myFile.txt);
OMText textData = fac.createOMText(dh, true);
input.addChild(textData);
pack.addChild(filename);
pack.addChild(input);
data.addChild(pack);
//System.out.println(data);
return data;
}
}
server code:
public class fileS {
public OMElement fileSecurity(OMElement element) throws Exception
{
//System.out.println(element);
element.build();
element.detach();
Iterator children = element.getChildElements();
OMElement name = (OMElement)children.next(); //get name of the file,
first element of element
OMElement content = (OMElement)children.next(); //get text that
contains the file, second element
System.out.println(before creating OMText);
OMText fnode = (OMText)content.getFirstOMChild();
System.out.println(after creating OMText);
// fnode.setOptimize(true);
//String fname = name.getText();
//create data handler to extract
Re: [Axis2]Module not found
zhu jiang wrote: Hi All, When I run the sample of EchoBlockingDualClient, I receive that: *org.apache.axis2.AxisFault: Module not found* **What should I do? Did u read Engaging Addressing in Client Side in http://ws.apache.org/axis2/1_0/userguide3.html. -- Chinthaka signature.asc Description: OpenPGP digital signature
Re: [Axis2 v1.0] send file with security
Dear Ruchith,
you means
remove :
optimizeParts//xenc:EncryptedData/xenc:CipherData/xenc:CipherValue/optimizeParts
from my services.xml right? or other place?
Wan
Hi Wan,
Please remove :
optimizeParts//xenc:EncryptedData/xenc:CipherData/xenc:CipherValue/optimizeParts
entry from your rampart configuration parameters and try again.
Thanks,
Ruchith
On 7/20/06, Wan Kaveevivitchai [EMAIL PROTECTED] wrote:
Dear All,
I have been trying to combine the test about sending file and
securing message.
My environment is Axis2 v1.0, nightly build released 4 June 06 on
the
Jetty Servlet.
From other individual test such as sending text file, and security
sample had no problem on this, however with the combination one i got the
following error.
Client code:
/*
* Created on 19.07.2006
*
* TODO To change the template for this generated file go to
* Window - Preferences - Java - Code Style - Code Templates
*/
package security;
/**
* @author alice3
*
* TODO To change the template for this generated type comment go to
* Window - Preferences - Java - Code Style - Code Templates
*/
import org.apache.axiom.om.OMAbstractFactory;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMFactory;
import org.apache.axiom.om.OMNamespace;
import org.apache.axiom.om.OMText;
import org.apache.axis2.AxisFault;
import org.apache.axis2.Constants;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.context.ConfigurationContext;
import org.apache.axis2.context.ConfigurationContextFactory;
//import org.apache.axis2.soapmonitor.*;
import javax.activation.DataHandler;
import javax.activation.FileDataSource;
import javax.xml.namespace.QName;
import javax.xml.stream.XMLOutputFactory;
import javax.xml.stream.XMLStreamException;
import java.io.File;
import java.io.StringWriter;
public class SecureClient {
private File inputFile = null;
private QName operationName = new QName(fileSecurity);
public static void main(String[] args) {
try {
// Get the repository location from the args
String repo = args[0];
String port = args[1];
OMElement payload =
getEchoElement(/users/alice3/myDoc/Jettty6-Axis2.txt);
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(repo,
null);
ServiceClient serviceClient = new
ServiceClient(configContext,
null);
Options options = new Options();
options.setTo(new EndpointReference(http://127.0.0.1:; +
port +
/axis2/services/FileSecurity));
//options.setTo(new
EndpointReference(http://localhost:8080/axis2_new/services/SecureService;));
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);
options.setAction(urn:fileSecurity);
serviceClient.setOptions(options);
//Blocking invocation
OMElement result = serviceClient.sendReceive(payload);
StringWriter writer = new StringWriter();
result.serialize(XMLOutputFactory.newInstance()
.createXMLStreamWriter(writer));
writer.flush();
//System.out.println(Response: + writer.toString());
System.out.println(SecureService Invocation successful
:-));
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
} catch (XMLStreamException e) {
e.printStackTrace();
}
}
private static OMElement getEchoElement(String fileName) {
DataHandler dh;
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs =
fac.createOMNamespace(http://ws.apache.org/axis2/xsd;, example1);
OMElement data = fac.createOMElement(fileSecurity, omNs);
OMElement input = fac.createOMElement(file, omNs);
OMElement pack = fac.createOMElement(pack, omNs);
FileDataSource f1 = new FileDataSource(fileName);
dh = new DataHandler(f1);
OMElement filename = fac.createOMElement(fileName, omNs);
// OMText textName = fac.createOMText(filename, myFile.txt);
OMText textData = fac.createOMText(dh, true);
input.addChild(textData);
pack.addChild(filename);
pack.addChild(input);
data.addChild(pack);
//System.out.println(data);
return data;
}
}
server code:
public class fileS {
public OMElement fileSecurity(OMElement element) throws Exception
{
//System.out.println(element);
element.build();
element.detach();
Iterator children = element.getChildElements();
OMElement name = (OMElement)children.next();
Can't generate SOAP Envelope, org.xml.sax.SAXParseException: Premature end of file
Hi All , I run a simple test class to access my webservice deployed on axis 1.2.1 (Built on Jun 14, 2005 (09:15:57 EDT). and got an exception.
The truth is soap msg can't be generated and an SAX xml exception is thrown. Could anyone tell me what happened ? and how to fix that ?
many thanks.
the src code SoapPart.javalooks as:
dser.getEnvelope().setOwnerDocument(this); // This may throw a SAXException try { dser.parse(); // exception } catch (SAXException e) { Exception real =
e.getException(); if (real == null) real = e; throw AxisFault.makeFault(real); }
Exception msg:
AxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userExceptionfaultSubcode: 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) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion
(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse
(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse
(SAXParser.java:375) at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) at org.apache.axis.Message.getSOAPEnvelope
(Message.java:424) at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) at org.apache.axis.client.Call.invokeEngine
(Call.java:2765) at org.apache.axis.client.Call.invoke(Call.java:2748) at org.apache.axis.client.Call.invoke(Call.java:2424) at org.apache.axis.client.Call.invoke(Call.java:2347) at
org.apache.axis.client.Call.invoke(Call.java:1804) at com.sswitch.oam.soap.intf.Bts10200SoapBindingStub.request(Bts10200SoapBindingStub.java:297) at com.sswitch.oam.soap.test.SimpleTest.main(SimpleTest.java
:22)
{http://xml.apache.org/axis/}hostname:sha-view1.cisco.com
org.xml.sax.SAXParseException: Premature end of file. at org.apache.axis.AxisFault.makeFault(AxisFault.java:101) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701) at org.apache.axis.Message.getSOAPEnvelope
(Message.java:424) at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) at org.apache.axis.client.Call.invokeEngine
(Call.java:2765) at org.apache.axis.client.Call.invoke(Call.java:2748) at org.apache.axis.client.Call.invoke(Call.java:2424) at org.apache.axis.client.Call.invoke(Call.java:2347) at
org.apache.axis.client.Call.invoke(Call.java:1804) at com.sswitch.oam.soap.intf.Bts10200SoapBindingStub.request(Bts10200SoapBindingStub.java:297) at com.sswitch.oam.soap.test.SimpleTest.main(SimpleTest.java
:22)Caused by: 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) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion
(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse
(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse
(SAXParser.java:375) at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
Re: [Axis2] Yet another security/rampart question
Hi, Yes !! This is possible.. In this case the encryptionUser value has to be useReqSigCert And the client must send a signed request to the service to pick the cert to encrypt with. thanks, Ruchith On 7/20/06, Jan Bauer Nielsen [EMAIL PROTECTED] wrote: Hi. I'm still a novice concerning ws-security but I have been studying the security sample from the axis2 distribution and I think I have a fair understanding of how it works. But now I am considering a use case where a number of clients each has its ows certificate. This excludes me from using encryptionUser in the server side services.xml. So is it possible to set this dynamically from the service class to get the response encrypted with the public key of the current client and how would I go about doing it? Kind regards, -- Jan Bauer Nielsen Center of Knowledge Technology, Technical Knowledge Center of Denmark Anker Engelunds Vej 1, Postboks 777, 2800 Kongens Lyngby, Denmark Direct: (+45) 4525 7221, [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- www.ruchith.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2 v1.0] send file with security
Yes from your services.xml and the client's axis2.xml
Thanks,
Ruchith
On 7/20/06, Wan Kaveevivitchai [EMAIL PROTECTED] wrote:
Dear Ruchith,
you means
remove :
optimizeParts//xenc:EncryptedData/xenc:CipherData/xenc:CipherValue/optimizeParts
from my services.xml right? or other place?
Wan
Hi Wan,
Please remove :
optimizeParts//xenc:EncryptedData/xenc:CipherData/xenc:CipherValue/optimizeParts
entry from your rampart configuration parameters and try again.
Thanks,
Ruchith
On 7/20/06, Wan Kaveevivitchai [EMAIL PROTECTED] wrote:
Dear All,
I have been trying to combine the test about sending file and
securing message.
My environment is Axis2 v1.0, nightly build released 4 June 06 on
the
Jetty Servlet.
From other individual test such as sending text file, and security
sample had no problem on this, however with the combination one i got the
following error.
Client code:
/*
* Created on 19.07.2006
*
* TODO To change the template for this generated file go to
* Window - Preferences - Java - Code Style - Code Templates
*/
package security;
/**
* @author alice3
*
* TODO To change the template for this generated type comment go to
* Window - Preferences - Java - Code Style - Code Templates
*/
import org.apache.axiom.om.OMAbstractFactory;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMFactory;
import org.apache.axiom.om.OMNamespace;
import org.apache.axiom.om.OMText;
import org.apache.axis2.AxisFault;
import org.apache.axis2.Constants;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.context.ConfigurationContext;
import org.apache.axis2.context.ConfigurationContextFactory;
//import org.apache.axis2.soapmonitor.*;
import javax.activation.DataHandler;
import javax.activation.FileDataSource;
import javax.xml.namespace.QName;
import javax.xml.stream.XMLOutputFactory;
import javax.xml.stream.XMLStreamException;
import java.io.File;
import java.io.StringWriter;
public class SecureClient {
private File inputFile = null;
private QName operationName = new QName(fileSecurity);
public static void main(String[] args) {
try {
// Get the repository location from the args
String repo = args[0];
String port = args[1];
OMElement payload =
getEchoElement(/users/alice3/myDoc/Jettty6-Axis2.txt);
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(repo,
null);
ServiceClient serviceClient = new
ServiceClient(configContext,
null);
Options options = new Options();
options.setTo(new EndpointReference(http://127.0.0.1:; +
port +
/axis2/services/FileSecurity));
//options.setTo(new
EndpointReference(http://localhost:8080/axis2_new/services/SecureService;));
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);
options.setAction(urn:fileSecurity);
serviceClient.setOptions(options);
//Blocking invocation
OMElement result = serviceClient.sendReceive(payload);
StringWriter writer = new StringWriter();
result.serialize(XMLOutputFactory.newInstance()
.createXMLStreamWriter(writer));
writer.flush();
//System.out.println(Response: + writer.toString());
System.out.println(SecureService Invocation successful
:-));
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
} catch (XMLStreamException e) {
e.printStackTrace();
}
}
private static OMElement getEchoElement(String fileName) {
DataHandler dh;
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs =
fac.createOMNamespace(http://ws.apache.org/axis2/xsd;, example1);
OMElement data = fac.createOMElement(fileSecurity, omNs);
OMElement input = fac.createOMElement(file, omNs);
OMElement pack = fac.createOMElement(pack, omNs);
FileDataSource f1 = new FileDataSource(fileName);
dh = new DataHandler(f1);
OMElement filename = fac.createOMElement(fileName, omNs);
// OMText textName = fac.createOMText(filename, myFile.txt);
OMText textData = fac.createOMText(dh, true);
input.addChild(textData);
pack.addChild(filename);
pack.addChild(input);
data.addChild(pack);
//System.out.println(data);
return data;
}
}
server code:
public class fileS {
public OMElement fileSecurity(OMElement element) throws Exception
{
//System.out.println(element);
Re: [Axis2] Importance of SwA (Need Your Feedback)
Sanjiva, We handle recieving SwA attachments. We don't have support for sending them. -- dims On 7/20/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: On Thu, 2006-07-20 at 05:14 +0600, Thilina Gunarathne wrote: Agreed. We need to do something to serialize the NON-MTOM attachments in the MsgContxt attachments object. I thought we did this .. Dims, didn't u put some stuff to store an unreferenced attachment in the MC?? Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2 v1.0] send file with security
Thank you Ruchith,
I have made change as your advice. However, i still got the same
error...
Any other possibility?
Best regards,
Wan
From: Ruchith Fernando [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: [Axis2 v1.0] send file with security
Date: Thu, 20 Jul 2006 16:09:23 +0530
Yes from your services.xml and the client's axis2.xml
Thanks,
Ruchith
On 7/20/06, Wan Kaveevivitchai [EMAIL PROTECTED] wrote:
Dear Ruchith,
you means
remove :
optimizeParts//xenc:EncryptedData/xenc:CipherData/xenc:CipherValue/optimizeParts
from my services.xml right? or other place?
Wan
Hi Wan,
Please remove :
optimizeParts//xenc:EncryptedData/xenc:CipherData/xenc:CipherValue/optimizeParts
entry from your rampart configuration parameters and try again.
Thanks,
Ruchith
On 7/20/06, Wan Kaveevivitchai [EMAIL PROTECTED] wrote:
Dear All,
I have been trying to combine the test about sending file and
securing message.
My environment is Axis2 v1.0, nightly build released 4 June 06
on
the
Jetty Servlet.
From other individual test such as sending text file, and
security
sample had no problem on this, however with the combination one i got
the
following error.
Client code:
/*
* Created on 19.07.2006
*
* TODO To change the template for this generated file go to
* Window - Preferences - Java - Code Style - Code Templates
*/
package security;
/**
* @author alice3
*
* TODO To change the template for this generated type comment go to
* Window - Preferences - Java - Code Style - Code Templates
*/
import org.apache.axiom.om.OMAbstractFactory;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMFactory;
import org.apache.axiom.om.OMNamespace;
import org.apache.axiom.om.OMText;
import org.apache.axis2.AxisFault;
import org.apache.axis2.Constants;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.context.ConfigurationContext;
import org.apache.axis2.context.ConfigurationContextFactory;
//import org.apache.axis2.soapmonitor.*;
import javax.activation.DataHandler;
import javax.activation.FileDataSource;
import javax.xml.namespace.QName;
import javax.xml.stream.XMLOutputFactory;
import javax.xml.stream.XMLStreamException;
import java.io.File;
import java.io.StringWriter;
public class SecureClient {
private File inputFile = null;
private QName operationName = new QName(fileSecurity);
public static void main(String[] args) {
try {
// Get the repository location from the args
String repo = args[0];
String port = args[1];
OMElement payload =
getEchoElement(/users/alice3/myDoc/Jettty6-Axis2.txt);
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(repo,
null);
ServiceClient serviceClient = new
ServiceClient(configContext,
null);
Options options = new Options();
options.setTo(new EndpointReference(http://127.0.0.1:; +
port +
/axis2/services/FileSecurity));
//options.setTo(new
EndpointReference(http://localhost:8080/axis2_new/services/SecureService;));
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);
options.setAction(urn:fileSecurity);
serviceClient.setOptions(options);
//Blocking invocation
OMElement result = serviceClient.sendReceive(payload);
StringWriter writer = new StringWriter();
result.serialize(XMLOutputFactory.newInstance()
.createXMLStreamWriter(writer));
writer.flush();
//System.out.println(Response: + writer.toString());
System.out.println(SecureService Invocation successful
:-));
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
} catch (XMLStreamException e) {
e.printStackTrace();
}
}
private static OMElement getEchoElement(String fileName) {
DataHandler dh;
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs =
fac.createOMNamespace(http://ws.apache.org/axis2/xsd;, example1);
OMElement data = fac.createOMElement(fileSecurity, omNs);
OMElement input = fac.createOMElement(file, omNs);
OMElement pack = fac.createOMElement(pack, omNs);
FileDataSource f1 = new FileDataSource(fileName);
dh = new DataHandler(f1);
OMElement filename = fac.createOMElement(fileName, omNs);
// OMText textName = fac.createOMText(filename, myFile.txt);
OMText textData = fac.createOMText(dh, true);
input.addChild(textData);
Re: [Axis2] Importance of SwA (Need Your Feedback)
Couldn't we add a flag to MTOM attachments OMText which simply says don't include the XOP. In other words, you create a standard MTOM attachment but there is no reference in the XML. Paul On 7/20/06, Davanum Srinivas [EMAIL PROTECTED] wrote: Sanjiva, We handle recieving SwA attachments. We don't have support for sending them. -- dims On 7/20/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: On Thu, 2006-07-20 at 05:14 +0600, Thilina Gunarathne wrote: Agreed. We need to do something to serialize the NON-MTOM attachments in the MsgContxt attachments object. I thought we did this .. Dims, didn't u put some stuff to store an unreferenced attachment in the MC?? Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WSDD reference or examples
Hi, Can anyone point me to a reference for creating a *.wsdd? I am trying to create a WSDD for a Message style web service. The intention is that the Axis generated WSDL will specify a user-defined XML schema (wsdlInputSchema) and assert that the input and output for the web service should be an XML document as defined by the schema. If anyone knows where I could see an example that would be great I am finding snippets of info on the web, but am having difficulty finding a detailed listing of the options etc. All the best, Andrew. The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you.
thread-safe problems with Rampart
Hi Ruchith, I have an Axis2 client webapp which determines which Axis2 Services it should call (according to own capabilities mechanisms) and then spawns threads, each one calling an Axis2 Service synchronously using ServiceClient.sendReceive(). Problem is, that sometimes 2 or more services are located on the same Axis2 server (actually, within the same ServiceGroup), then - usually the first time I have to invoke the services since the start of Tomcat (but sometimes also other times), one service fails, sometimes more than one. The failure is always on the Server side. My security configuration is either TimeStamp Signature (1) or Timestamp Signatrure Encrypt (2), according to the user's request (encryption yes/ no); of course, the client side and the server side are using the same security configuration. When I invoke I invoke either only services of type (1), or of type (2). I am sure it is a thread-safe issue, as if I invoke my services syncronously (by calling Thread.run() myself i.s.o Thread.start()) I have no problem whatsoever. I saw a mail on this issue, or a similar one; but i'm not sure if it was about the client side or the server side. Is there a new version of Rampart which I can download and try out? Hereunder you have 2 stack-traces: NullPointerExceptions at different methods of WSDoAllReceiver. The second one (II) happens only with Timestamp Signatrure Encrypt (2), the first one happens with both configurations. I 2006-07-20 13:37:12,796 [http-8080-3] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/axis2].[AxisServlet] - Servlet.service() for servlet AxisServlet threw exception java.lang.NullPointerException at org.apache.axis2.security.WSDoAllReceiver.processMessage(WSDoAllReceiver.java:195) at org.apache.axis2.security.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:82) at org.apache.axis2.engine.Phase.invoke(Phase.java:381) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:473) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:445) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:136) 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:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:833) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:639) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1285) at java.lang.Thread.run(Thread.java:595) 2006-07-20 13:37:12,968 [http-8080-3] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/axis2].[jsp] - Servlet.service() for servlet jsp threw exception java.lang.NullPointerException at org.apache.axiom.om.impl.dom.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:70) at org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:92) at org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConfig.java:76) at org.apache.jasper.compiler.JspConfig.init(JspConfig.java:197) at org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:249) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:112) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:295) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:276) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:264) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at
Re: [Axis2 v1.0] send file with security
Hi Wan,
Can you also change
parameter name=enableMTOM locked=falsetrue/parameter
to
parameter name=enableMTOM locked=falsefalse/parameter
in both axis2.xml s (client and server) and try again.
And if this fails please send what you see in tcpmon and the exception.
Thanks,
Ruchith
On 7/20/06, Wan Kaveevivitchai [EMAIL PROTECTED] wrote:
Thank you Ruchith,
I have made change as your advice. However, i still got the same
error...
Any other possibility?
Best regards,
Wan
From: Ruchith Fernando [EMAIL PROTECTED]
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: [Axis2 v1.0] send file with security
Date: Thu, 20 Jul 2006 16:09:23 +0530
Yes from your services.xml and the client's axis2.xml
Thanks,
Ruchith
On 7/20/06, Wan Kaveevivitchai [EMAIL PROTECTED] wrote:
Dear Ruchith,
you means
remove :
optimizeParts//xenc:EncryptedData/xenc:CipherData/xenc:CipherValue/optimizeParts
from my services.xml right? or other place?
Wan
Hi Wan,
Please remove :
optimizeParts//xenc:EncryptedData/xenc:CipherData/xenc:CipherValue/optimizeParts
entry from your rampart configuration parameters and try again.
Thanks,
Ruchith
On 7/20/06, Wan Kaveevivitchai [EMAIL PROTECTED] wrote:
Dear All,
I have been trying to combine the test about sending file and
securing message.
My environment is Axis2 v1.0, nightly build released 4 June 06
on
the
Jetty Servlet.
From other individual test such as sending text file, and
security
sample had no problem on this, however with the combination one i got
the
following error.
Client code:
/*
* Created on 19.07.2006
*
* TODO To change the template for this generated file go to
* Window - Preferences - Java - Code Style - Code Templates
*/
package security;
/**
* @author alice3
*
* TODO To change the template for this generated type comment go to
* Window - Preferences - Java - Code Style - Code Templates
*/
import org.apache.axiom.om.OMAbstractFactory;
import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMFactory;
import org.apache.axiom.om.OMNamespace;
import org.apache.axiom.om.OMText;
import org.apache.axis2.AxisFault;
import org.apache.axis2.Constants;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.client.Options;
import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.context.ConfigurationContext;
import org.apache.axis2.context.ConfigurationContextFactory;
//import org.apache.axis2.soapmonitor.*;
import javax.activation.DataHandler;
import javax.activation.FileDataSource;
import javax.xml.namespace.QName;
import javax.xml.stream.XMLOutputFactory;
import javax.xml.stream.XMLStreamException;
import java.io.File;
import java.io.StringWriter;
public class SecureClient {
private File inputFile = null;
private QName operationName = new QName(fileSecurity);
public static void main(String[] args) {
try {
// Get the repository location from the args
String repo = args[0];
String port = args[1];
OMElement payload =
getEchoElement(/users/alice3/myDoc/Jettty6-Axis2.txt);
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(repo,
null);
ServiceClient serviceClient = new
ServiceClient(configContext,
null);
Options options = new Options();
options.setTo(new EndpointReference(http://127.0.0.1:; +
port +
/axis2/services/FileSecurity));
//options.setTo(new
EndpointReference(http://localhost:8080/axis2_new/services/SecureService;));
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_TRUE);
options.setAction(urn:fileSecurity);
serviceClient.setOptions(options);
//Blocking invocation
OMElement result = serviceClient.sendReceive(payload);
StringWriter writer = new StringWriter();
result.serialize(XMLOutputFactory.newInstance()
.createXMLStreamWriter(writer));
writer.flush();
//System.out.println(Response: + writer.toString());
System.out.println(SecureService Invocation successful
:-));
} catch (AxisFault axisFault) {
axisFault.printStackTrace();
} catch (XMLStreamException e) {
e.printStackTrace();
}
}
private static OMElement getEchoElement(String fileName) {
DataHandler dh;
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs =
fac.createOMNamespace(http://ws.apache.org/axis2/xsd;, example1);
OMElement data =
Re: [Axis2] Importance of SwA (Need Your Feedback)
Hi Thilina, On 7/19/06, Ben Malek, Hamid [EMAIL PROTECTED] wrote: I certainly will be happy to help you guys with this if you need to. Thanks a lot. You are always welcome to join. [Hamid]: Thilina, I know very well what the MTOM specification is saying, and I agree with you that MTOM is a particular case of SwA, but the converse is not true. And that is where the problem is (for example, a mutipart/related MimeMessage is a very good example of an SwA message that is not an MTOM message). MTOM does not only differ from SwA by the use of XOP or not (the way the Mime Headers are written down on the wire is not the same when the message is SwA versus MTOM message. For example, the value of the Content-Type Mime Header is not the same for a MimeMessage versus an MTOM message). ebXML processors as well as many other SwA processors expect a MimeMessage format on the wire, not an MTOM format. If you read the spec of ebms-2 for example, you will see the mime format well specified in the spec, and the MSH processor will throw a fault if the mime headers are not consistent with the spec. This is not about parsing (SAAJ and other parsers may be able to parse both format). Axis2 supports receiving of SwA messages which are not MTOM. I agree that there are limitations like not supporting content location based addressing of MIME parts(supports content-id based addressing only). [Thilina]: We can always come up with a separate API, as I have mentioned in my reply to your earlier mail. May be you can start working on it as Dims suggested:). [Hamid]: I don't know if that is a good idea to have two different APIs. I know that you believe that Axiom should stay an XML infoset, but I don't believe like you that it will break the goal of Axiom to add functionality to the Axiom API to allow MimeMessage format on the wire when serialized. Since everything that circulates inside Axis2 is from the Axiom Object Model, I think it would better to just add the functionality to the Axiom API itself. For example, when you call the method ServiceClient.sendReceive(OMElement elem), you want this API to work correctly regardless of whether you specify MTOM format or MimeMessage format. OMElement as in ServiceClient.sendReceive(OMElement elem) represents the XML payload which goes inside the SOAP body. IMHO SwA attachments belong to the SOAP message level. They do not belong to the SOAP envelope or the XML payload, since they do not have defined relationship to the XML payload. According to what I understand MessageContext is the Axis2 entity which contains the SOAP message level information. I believe SwA attachments should be put in to MsgContext. I do not see any justifiable placeholder for SwA type attachments in XML representation of the payload. This is just how I feel:). [Thilina]: BTW try to convince the the ebms guys to use MTOM. SwA is just a submission to W3C. AFAIK it never came out of W3C as a spec. IMHO SwA is fast out dating. [Hamid]: I indeed suggested to ebMS-3 TC to support MTOM in the core spec (as an addition to SwA), and I presented all the positive arguments, but the TC decided to do this in the second part of the spec and not in the first part. It is not that simple to just ignore SwA and replace it with MTOM. SwA is well alive and has a big deployment. Whether it is out-dated or not does not change anything in the matter. For example, we all say that Cobol is dead but the reality is that 70% of the transactions are done in Cobol. We have designed the ebMS-3 spec very differently from the ebms-2 spec (for very good reasons), and one of the feedback we got when our spec was in public review was the backward compatibility issue. Big companies such as TMobile (which has thousands of deployed software) were not very happy to know that ebMS-3 SOAP headers were not the same thing as those of ebMS-2. Below is an extract of TMobile feedback: Extract of TMobile feedback === From Gait Boxman (TIE) : This is a major change and will certainly mean that we can no longer reuse a lot of the coding done for ebMS2. It will also mean a serious migration problem. I hope you didn't rule out SwA use, because the last thing I want to do is to push data through an XML parser that doesn't need to do anything with it. The separation of control data from the payload as a *very good thing*, and should be kept. IMO, the ebMS handler should not touch payloads ever. If I pass it a zipped executable or PDF on one side, it should come out on the other side bitwise identical. While I'm sure it's possible to do this by embedding the info inside XML after some wrapping and encoding, I don't want to push that data through the XML parser in the SOAP handler, if only to ensure it doesn't stall. End of feedback === Just to add my two cents, In Axis2 we don't parse any
RE: Article on Intalio|BPMS Community site
Hi Robert, The axis team has already reported the issue at: http://issues.apache.org/jira/browse/WSCOMMONS-11?page=all I am not sure why the bug is reported as minor though. Thanks, Arnaud -Original Message- From: robert lazarski [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 19, 2006 9:56 PM To: axis-user@ws.apache.org Subject: Re: Article on Intalio|BPMS Community site Is there a JIRA for this issue? If not, could you please file one? From the links src download, src/com/intalio/bpms/tools/webservices/email/Body_type1.java // This is horrible, but the OM implementation of getElementText() does not obey the proper contract. Specifically, it does // does not advance the reader to the END_ELEMENT. This bug is triggered by calls to getElementText() unpredictably, e.g. it // happens with outer (document) elements, but not with inner elements. The root bug is in OMStAXWrapper.java, which is now part // of commons and so cannot just be fixed in axis2. This method should be removed and the calls to it below replaced with // simple calls to getElementText() as soon as this serious bug can be fixed. Thanks, Robert http://www.braziloutsource.com/ On 7/19/06, Arnaud Blandin [EMAIL PROTECTED] wrote: Dear Axis users and developers, We have just released an article detailling how you can write a web service with Axis 2 to later embed it in a business process defined in Intalio|BPMS. The article details the process of writing a webservice to send an email and how you can leverage the Axis2 Code Generator and Service Archiver. There is also a section presenting the Axis2 project. You can find the article at: http://bpms.intalio.com/content/view/114/84/ Can you please add it in your list of articles on the Axis2 page? Do not hesitate to contact me if you need more information about the article or Intalio|BPMS. Cheers, Arnaud EMEA Manager Intalio, The OpenSource BPMS Company www.intalio.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2 v1.0] Deployment Engine BUG?
Hi I have questions on the implementation of DeploymentEngine.buidModule() The method takes a AxisConfiguration as a parameter, but in its implementation uses the private member AxisConfiguration of the DeploymentEngine. Since the only way to initialize the privet member is trough DeploymentEngine.populateAxisConfiguration() the .buildModule() method uses a reference that points null. I can't understand the point of taking a AxisConfiguration and then using the privet member to build the module. For those of the users,who for one or other reason try not to use axis2.xml a AxisConfiguration setter would be nice to have. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] log4j configuration issue
Hi all, where should I put the log4j.properties file into my axis2 web service? And how do I locate it? Thanks in advance, Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WSDD reference or examples
Good Morning Andrew- AdminClient can create it with -lEndpoint option OR if you want to automateyou can execute create-wsdd ant targetImplementation details are available at http://bioinfo.mpiz-koeln.mpg.de/araws/documentation/help/jmoby-step-by-step/deploy-on-tomcat Be sure to make a backup of server-config.wsdd beforehand! Viel Gluck,Martin -- *This email message and any files transmitted with it contain confidentialinformation intended only for the person(s) to whom this email message isaddressed. If you have received this email message in error, please notifythe sender immediately by telephone or email and destroy the originalmessage without making a copy. Thank you. - Original Message - From: Andrew Morrison To: axis-user@ws.apache.org Sent: Thursday, July 20, 2006 8:11 AM Subject: WSDD reference or examples Hi, Can anyone point me to a reference for creating a *.wsdd? I am trying to create a WSDD for a Message style web service. The intention is that the Axis generated WSDL will specify a user-defined XML schema (wsdlInputSchema) and assert that the input and output for the web service should be an XML document as defined by the schema. If anyone knows where I could see an example that would be great I am finding snippets of info on the web, but am having difficulty finding a detailed listing of the options etc. All the best, Andrew. The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you.
[AXIS2] userguide Writing Web Service Clients using Code Generation with Data Binding Support
Hi all,
I have one question concerning the userguide and
more precisely the part:
Writing Web Service Clients using Code Generation with Data Binding
Support
In fact, I did everything and more precisely, I deployed the service but
now I have a problem with the client.
In fact, I copy paste the following client to invoke the service (like it
is written in the userguide):
try {
//Create the stub by passing the AXIS_HOME and target EPR.
//We pass null to the AXIS_HOME and hence the stub will use the current directory as the AXIS_HOME
Axis2SampleDocLitPortTypeStub stub= new Axis2SampleDocLitPortTypeStub(null,
"http://localhost:8080/axis2/services/Axis2SampleDocLitPortType");
//Create the request document to be sent.
EchoStringParamDocument reqDoc= EchoStringParamDocument.Factory.newInstance();
reqDoc.setEchoStringParam("Axis2 Echo");
//invokes the Web service.
EchoStringReturnDocument resDoc=stub.echoString(reqDoc);
System.out.println(resDoc.getEchoStringReturn());
} catch (Exception e) {
e.printStackTrace();
}The problem is that this code above is wrong or maybe I have missed something. I mean the echoString cannot take a EchoStringParamDocument parameter. It is a EchoStringParam which is convenient. How can I translate a EchoStringParamDocument parameter to EchoStringParam?Thx for your responsesFabien
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
Re: [Axis2]Module not found
Jiang- Isaxis.jar is on your CLASSPATH??M- *This email message and any files transmitted with it contain confidentialinformation intended only for the person(s) to whom this email message isaddressed. If you have received this email message in error, please notifythe sender immediately by telephone or email and destroy the originalmessage without making a copy. Thank you. - Original Message - From: zhu jiang To: axis-user@ws.apache.org Sent: Wednesday, July 19, 2006 11:49 PM Subject: [Axis2]Module not found Hi All, When I run the sample of EchoBlockingDualClient, I receive that: org.apache.axis2.AxisFault: Module not found What should I do? Thanks, Jiang
RE: WSDD reference or examples
Here is an example of wsdd for what you describe: deployment name="test" xmlns="http://xml.apache.org/axis/wsdd/" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" !-- note that either style="message" OR provider="java:MSG" both work -- service name="serviceName" provider="java:MSG" parameter name="className" value="com.test.service.MyWebService" / parameter name="allowedMethods" value="MyMethodName" / /service/deployment From: Andrew Morrison [mailto:[EMAIL PROTECTED] Sent: Thursday, July 20, 2006 7:11 AMTo: axis-user@ws.apache.orgSubject: WSDD reference or examples Hi, Can anyone point me to a reference for creating a *.wsdd? I am trying to create a WSDD for a Message style web service. The intention is that the Axis generated WSDL will specify a user-defined XML schema (wsdlInputSchema) and assert that the input and output for the web service should be an XML document as defined by the schema. If anyone knows where I could see an example that would be great I am finding snippets of info on the web, but am having difficulty finding a detailed listing of the options etc. All the best, Andrew. The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you.
Re: Cannot load SchemaTypeSystem
When you run WSDL2Java with xmlbeans, there will indeed be a
TypeSystemHolder class generated and you have to somehow get that
class into you classpath. From the codegen guide:
http://ws.apache.org/axis2/tools/1_0/CodegenToolReference.html
An important detail is that an XMLBean class file is also generated
by WSDL2Java, TypeSystemHolder.class. That file is placed into
build/classes by the above ant task and will be needed to compile the
generated sources. A frequent problem is users get an error such as:
ClassNotFoundException : Cannot load SchemaTypeSystem. Unable to load
class with name
schemaorg_apache_xmlbeans.system.s68C41DB812F52C975439BA10FE4FEE54.TypeSystemHolder.
Make sure the generated binary files are on the classpath.
The TypeSystemHolder.class generated by WSDL2Java must be placed in
your classpath in order to avoid this error.
For example, when I run WSDL2Java, I do it thru an ant task:
target name=wsdl2java depends=clean,prepare
delete dir=output /
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpath refid=axis.classpath/
arg value=-d/
!-- none ??? --
arg value=xmlbeans/
arg value=-uri/
arg file=wsdl/Maragato.wsdl/
arg value=-ss/
arg value=-ssi/
arg value=-g/
arg value=-sd/
arg value=-o/
arg file=output/
arg value=-p/
arg value=br.com.atlantico.maragato.webservices.endpoint/
/java
!-- Move the schema folder to classpath--
move todir=${build.classes}
fileset dir=output/resources
include name=*schema*/**/*.class/
include name=*schema*/**/*.xsb/
/fileset
/move
/target
In this case, I get:
build/classes/schemaorg_apache_xmlbeans/system/sC4DADC577FF83F46C2C248EE4254F70D/TypeSystemHolder.class
I just confirmed that still works with todays svn.
HTH,
Robert
http://www.braziloutsource.com/
On 7/19/06, Derek [EMAIL PROTECTED] wrote:
Hi, folks.
I just ran WSDL2Java (from yesterday's nightly build), and generated a bunch
of output files. Now, I am trying to test a client which is written with
those output files. Whenever I try, however, I get the following exception:
Exception in thread main java.lang.ExceptionInInitializerError
at
crc.ieee1512import.xmlbeans.im.IMWrapper$Factory.newInstance(IMWrapper.java:
79)
at
crc.importtestclient.IEEE1512Client.createIMWrapper(IEEE1512Client.java:67)
at
crc.importtestclient.IEEE1512Client.runTest(IEEE1512Client.java:50)
at crc.importtestclient.ClientMain.main(ClientMain.java:39)
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:90)
Caused by: java.lang.RuntimeException: Cannot load SchemaTypeSystem. Unable
to load class with name
schemaorg_apache_xmlbeans.system.s3F178E0A50CC587BC745803A994CE78D.TypeSyste
mHolder. Make sure the generated binary files are on the classpath.
at
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:781)
at
crc.ieee1512import.xmlbeans.im.IMWrapper.clinit(IMWrapper.java:18)
... 9 more
Caused by: java.lang.ClassNotFoundException:
schemaorg_apache_xmlbeans.system.s3F178E0A50CC587BC745803A994CE78D.TypeSyste
mHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans.java:767)
... 10 more
I have verified that the generated 'resources' directory is in my classpath.
I have also verified that there exists a subdirectory of it named
schemaorg_apache_xmlbeans/system/s3F178E0A50CC587BC745803A994CE78D. However,
there is no TypeSystemHolder class in that directory (although there are a
bunch of .xsb files in it).
I am rather flummoxed as to what to do. Has anybody seen this before?
Derek
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't generate SOAP Envelope, org.xml.sax.SAXParseException: Premature end of file
Xu-
Things to look for are is the input XML contain
perhapsmissing End Tag (e.g. element without a
/element)Sub elements content clipped or chopped
offSOAP:header
...no end tag
or missing SOAP:body
Use any XML Editor such as XMLSpy or even IE in a
pinchandtheXMLParserwill tell you where the
error/missing contentoccurs
Martin
*This
email message and any files transmitted with it contain
confidentialinformation intended only for the person(s) to whom this email
message isaddressed. If you have received this email message in error,
please notifythe sender immediately by telephone or email and destroy the
originalmessage without making a copy. Thank you.
- Original Message -
From:
xu cai
To: axis-user@ws.apache.org ; axis-dev@ws.apache.org
Sent: Thursday, July 20, 2006 5:41
AM
Subject: Can't generate SOAP Envelope,
"org.xml.sax.SAXParseException: Premature end of file"
Hi All , I run a simple test class to access my webservice deployed on
axis 1.2.1 (Built on Jun 14, 2005 (09:15:57 EDT).
and got an exception. The truth is soap msg can't be generated and an SAX xml
exception is thrown. Could anyone tell me what
happened ? and how to fix that ?
many thanks.
the src code SoapPart.javalooks
as:
dser.getEnvelope().setOwnerDocument(this);
// This may throw a SAXException
try {
dser.parse(); // exception
} catch (SAXException e)
{
Exception real =
e.getException();
if (real ==
null)
real =
e; throw
AxisFault.makeFault(real);
}
Exception msg:
AxisFaultfaultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userExceptionfaultSubcode:
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) at
org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source) at
org.apache.xerces.impl.XMLVersionDetector.determineDocVersion (Unknown
Source) at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source) at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source) at
org.apache.xerces.parsers.XMLParser.parse (Unknown
Source) at
org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source) at
org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source) at
javax.xml.parsers.SAXParser.parse
(SAXParser.java:375) at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope
(Message.java:424) at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine
(Call.java:2765) at
org.apache.axis.client.Call.invoke(Call.java:2748)
at
org.apache.axis.client.Call.invoke(Call.java:2424)
at
org.apache.axis.client.Call.invoke(Call.java:2347)
at
org.apache.axis.client.Call.invoke(Call.java:1804)
at
com.sswitch.oam.soap.intf.Bts10200SoapBindingStub.request(Bts10200SoapBindingStub.java:297)
at com.sswitch.oam.soap.test.SimpleTest.main(SimpleTest.java :22)
{http://xml.apache.org/axis/}hostname:sha-view1.cisco.com
org.xml.sax.SAXParseException: Premature end of
file. at
org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at
org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701)
at org.apache.axis.Message.getSOAPEnvelope
(Message.java:424) at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine
(Call.java:2765) at
org.apache.axis.client.Call.invoke(Call.java:2748)
at
org.apache.axis.client.Call.invoke(Call.java:2424)
at
org.apache.axis.client.Call.invoke(Call.java:2347)
at
org.apache.axis.client.Call.invoke(Call.java:1804)
at
com.sswitch.oam.soap.intf.Bts10200SoapBindingStub.request(Bts10200SoapBindingStub.java:297)
at com.sswitch.oam.soap.test.SimpleTest.main(SimpleTest.java :22)Caused
by: 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) at
RE: Cannot load SchemaTypeSystem
Thanks for your response, Robert.
I did some more looking, and found that my IDE (IntelliJ Idea) was hiding
the class file that was generated from me, so I didn't know it existed. I
also found that the specific run target that I was using wasn't including
the resources directory in the class path like I thought it was. I had set
up Idea to include the directory in the source path for compilation, not the
class path, assuming that what was going to be generated was Java source
code rather than a class file. I am still a bit surprised that an actual
class file is being generated here, particularly after looking at the code
in WSDL2Java which does it by copying and modifying an existing class file
(!). With the directory now properly included in my runtime class path, the
code now seems to run correctly.
Derek
-Original Message-
From: robert lazarski [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 20, 2006 9:20 AM
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Subject: Re: Cannot load SchemaTypeSystem
When you run WSDL2Java with xmlbeans, there will indeed be a
TypeSystemHolder class generated and you have to somehow get
that class into you classpath. From the codegen guide:
http://ws.apache.org/axis2/tools/1_0/CodegenToolReference.html
An important detail is that an XMLBean class file is also
generated by WSDL2Java, TypeSystemHolder.class. That file is
placed into build/classes by the above ant task and will be
needed to compile the generated sources. A frequent problem
is users get an error such as:
ClassNotFoundException : Cannot load SchemaTypeSystem. Unable
to load class with name
schemaorg_apache_xmlbeans.system.s68C41DB812F52C975439BA10FE4F
EE54.TypeSystemHolder.
Make sure the generated binary files are on the classpath.
The TypeSystemHolder.class generated by WSDL2Java must be
placed in your classpath in order to avoid this error.
For example, when I run WSDL2Java, I do it thru an ant task:
target name=wsdl2java depends=clean,prepare
delete dir=output /
java classname=org.apache.axis2.wsdl.WSDL2Java fork=true
classpath refid=axis.classpath/
arg value=-d/
!-- none ??? --
arg value=xmlbeans/
arg value=-uri/
arg file=wsdl/Maragato.wsdl/
arg value=-ss/
arg value=-ssi/
arg value=-g/
arg value=-sd/
arg value=-o/
arg file=output/
arg value=-p/
arg
value=br.com.atlantico.maragato.webservices.endpoint/
/java
!-- Move the schema folder to classpath--
move todir=${build.classes}
fileset dir=output/resources
include name=*schema*/**/*.class/
include name=*schema*/**/*.xsb/
/fileset
/move
/target
In this case, I get:
build/classes/schemaorg_apache_xmlbeans/system/sC4DADC577FF83F
46C2C248EE4254F70D/TypeSystemHolder.class
I just confirmed that still works with todays svn.
HTH,
Robert
http://www.braziloutsource.com/
On 7/19/06, Derek [EMAIL PROTECTED] wrote:
Hi, folks.
I just ran WSDL2Java (from yesterday's nightly build), and
generated a
bunch of output files. Now, I am trying to test a client which is
written with those output files. Whenever I try, however, I get the
following exception:
Exception in thread main java.lang.ExceptionInInitializerError
at
crc.ieee1512import.xmlbeans.im.IMWrapper$Factory.newInstance(IMWrapper
.java:
79)
at
crc.importtestclient.IEEE1512Client.createIMWrapper(IEEE1512Cl
ient.java:67)
at
crc.importtestclient.IEEE1512Client.runTest(IEEE1512Client.java:50)
at crc.importtestclient.ClientMain.main(ClientMain.java:39)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess
orImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth
odAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)
Caused by: java.lang.RuntimeException: Cannot load
SchemaTypeSystem. Unable
to load class with name
schemaorg_apache_xmlbeans.system.s3F178E0A50CC587BC745803A994C
E78D.TypeSyste
mHolder. Make sure the generated binary files are on the classpath.
at
org.apache.xmlbeans.XmlBeans.typeSystemForClassLoader(XmlBeans
.java:781)
at
crc.ieee1512import.xmlbeans.im.IMWrapper.clinit(IMWrapper.java:18)
... 9 more
Caused by: java.lang.ClassNotFoundException:
schemaorg_apache_xmlbeans.system.s3F178E0A50CC587BC745803A994C
E78D.TypeSyste
mHolder
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at
java.security.AccessController.doPrivileged(Native Method)
at
Re: [Axis2] log4j configuration issue
WEB-INF/classes . Make sure you have log4j.jar under WEB-INF/lib or another appropriate place. HTH, Robert http://www.braziloutsource.com/ On 7/20/06, Michele Mazzucco [EMAIL PROTECTED] wrote: Hi all, where should I put the log4j.properties file into my axis2 web service? And how do I locate it? Thanks in advance, Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2 1.0] newbie: operation params and return types
Hi All, I am new to Axis2 and wondering about the supported datatypes for method parameters and return types. All the samples use OMElement. If an implementation class were to be written with all OMElements, would the generated WSDL show the corresponding schemas? If not, how would a client know the format of the params and returned results by looking at a WSDL? If this is a limitation of OM, then what other options does one have? I need to be able to return a List/Array of custom Beans. How can I do that? Excuse me for this basic question, but I couldn't find a good pointer. Thanks, -Nirmit - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Michael Rheinheimer/Austin/IBM is out of the office.
I will be out of the office starting 07/20/2006 and will not return until 07/31/2006. If you need to reach me immediately, please try my personal cell phone at 512-797-6788. You may also contact Henry Deangelis or Ann Robinson, who both know my backups for all related projects. Thanks. Mike
General error handling question
When an uncaught exception occurs, I would like to send a generic message saying only that an error occurred, instead of the default behavior which returns the exception message to the client in a soap fault. While I do have appropriate exception handling in my services, does axis2 have any functionality to do this in a more centralized manner?
Re: WSDD reference or examples
See http://www.oio.de/axis-wsdd/ On 7/20/06, Andrew Morrison [EMAIL PROTECTED] wrote: Thanks, but I am looking for something a bit more detailed. I am able to create working Message style web services from a WSDD, but I would like to specify a schema in the generated WSDL to state the type of the XML in the soap body. Has anyone done this? I want to: 1. Include a schema in the generated WSDL – this can be achieved using: parameter name=wsdlInputSchema value=http://localhost:8080/axis/schemas/eligibility_noxs.xsd/ 2. Specify that the request message should contain an XML message that can also be validated against the same schema – does anyone know if this is possible, or have an example of how to specify this in the WSDD? 3. Specify the response will be of a type defined by that schema – I think this can be achieved with: operation name=processSOAPBody qname=myns:processSOAPBody returnQName=myns:processSOAPBodyReturn returnType=myns:eligibility /operation My complete WSDD so far is below – if anyone can suggest any references or examples they would be appreciated. BTW: this site is useful but not complete: http://www.oio.de/axis-wsdd/deployment.htm Thanks Andrew. deployment name=MyWebService xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java xmlns:xsi=http://www.w3.org/2000/10/XMLSchema-instance; service name=MyMessageService1 provider=java:MSG style=message use=literal xmlns:curamns=http://localhost:8080/axis/services/MyMessageService1Namespace; namespacehttp://localhost:8080/axis/services/MyMessageService1Namespace/namespace parameter name=className value=my.messagestyle.service.MyMessageService / parameter name=allowedMethods value=processSOAPBody / parameter name=wsdlInputSchema value=http://localhost:8080/axis/schemas/eligibility_noxs.xsd/ parameter name=wsdlTargetNamespace value=http://localhost:8080/axis/services/MyMessageService1Namespace/ operation name=processSOAPBody qname=myns:processSOAPBody returnQName=myns:processSOAPBodyReturn returnType=myns:eligibility /operation /service /deployment From: Ted Jones [mailto:[EMAIL PROTECTED] Sent: 20 July 2006 16:49 To: axis-user@ws.apache.org; Andrew Morrison Subject: RE: WSDD reference or examples Here is an example of wsdd for what you describe: deployment name=test xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; xmlns:xsi=http://www.w3.org/2000/10/XMLSchema-instance; !-- note that either style=message OR provider=java:MSG both work -- service name=serviceName provider=java:MSG parameter name=className value=com.test.service.MyWebService / parameter name=allowedMethods value=MyMethodName / /service /deployment From: Andrew Morrison [mailto:[EMAIL PROTECTED] Sent: Thursday, July 20, 2006 7:11 AM To: axis-user@ws.apache.org Subject: WSDD reference or examples Hi, Can anyone point me to a reference for creating a *.wsdd? I am trying to create a WSDD for a Message style web service. The intention is that the Axis generated WSDL will specify a user-defined XML schema (wsdlInputSchema) and assert that the input and output for the web service should be an XML document as defined by the schema. If anyone knows where I could see an example that would be great – I am finding snippets of info on the web, but am having difficulty finding a detailed listing of the options etc. All the best, Andrew. The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you. The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,
Re: Problems with WSDL2Java
And just for clarity -- the sample WSDL in the WSDL spec is not valid... Anne On 7/19/06, Christian Pöcher [EMAIL PROTECTED] wrote: Just for the archive: I resolved the problem. It was of course my fault, although I wished the WSDL2Java tool would do a validity check, before generating code. In types I defined elements like element name=sum type=integer/ while in message I used a type attribute. message name=getSum part name=rightHandSide type=sum/ /message I also seem to have referenced an old version of the Schema namespace. Changing schema xmlns=http://www.w3.org/2000/10/XMLSchema; to schema xmlns=http://www.w3.org/2001/XMLSchema; finally helped. -Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Generating soap:header info in the WSDL
If you specify the header in the WSDL, then you intend the application to supply the header (hence the inclusion of the AuthenticationHeader parameter in the interface). If you don't intend the application to supply the header, then you should not include the header in the WSDL. Your security policies should be specified using WS-Policy. Anne On 7/19/06, Brian Fitzpatrick [EMAIL PROTECTED] wrote: So, I figured out how to configure Axis to generate soap:header information in the WSDL file, but it breaks the wrapped document-literal spec. Configuring Axis to send a parameter in the header, by setting parameter inHeader=true in the WSDD file creates WSDL that does not comply with the wrapped document-literal spec. It generates a wsdl:message that contains 2 parts instead of the 1 required by the spec. wsdl:message name=TestParametersRequest wsdl:part element=impl:AuthenticationHeader name=AuthenticationHeader/ wsdl:part element=impl:TestParameters name=parameters/ /wsdl:message As a result, when trying to create an Axis client using WSDL2Java, it fails to unwrap the TestParameters type (the code will only unwrap if it contains only one part and meets other criteria). Thus a service operation defined as: public void testParameters(String stringParam, int integerParam, Boolean booleanParam ) becomes public void testParameters(AuthenticationHeader header, TestParameters parameters ) in the generated Axis client proxies. It seems like the WSDL generation for headers is incorrect. It should be generated like .NET generates them, using 2 wsdl:message's: one for the parameters and one for the header. Then the header is referenced in the wsdl:binding. If Axis is going to generate the soap:header information in this way in the WSDL, then at least the Axis client proxies should be able to recognize this pattern and unwrap the parameters. Currently, the .NET 2.0 proxies (against the Axis generated WSDL) do correctly recognize the header and create method signatures that match the parameters, not a wrapped object containing the parameters. From: Brian Fitzpatrick Sent: Wednesday, July 12, 2006 8:19 AM To: axis-user@ws.apache.org Subject: Generating soap:header info in the WSDL Does Axis 1.4 support generating the WSDL for a soap header? I can't find a configuration or samples where it is done. We have a web service deployed under .NET and Axis. In .NET you can add a directive to the source code and it will create the wsdl that includes the soap header info. It creates the binding shown below and also the message and parts required. If this is not supported, any suggestions on how to accomplish this (handlers?, sample code?). Thanks. wsdl:operation name=TestParameters soap:operation soapAction=urn:Test/TestParameters style=document/ wsdl:input soap:body use=literal/ soap:header message=tns:TestParametersAuthenticationHeader part=AuthenticationHeader use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Repost: WSSecurityException - Check Signature confirmation (Axis 1.4 + wss4j)
Trying my luck if anybody can suggest any pointers, Hello: Would appreciate if someone could give me some pointers. Thanks, Ravi Ravi Krishnamurthy wrote: Hello: I'm trying to use wss4j with Axis1.4 and trying out the samples that comes with wss4j/interop. On executing the org.apache.ws.axis.oasis.Scenario3 I get the following exception: WSHandler: Check Signature confirmation: stored SV vector not empty; nested exception is: org.apache.ws.security.WSSecurityException: WSHandler: Check Signature confirmation: stored SV vector not empty at org.apache.ws.axis.security.WSDoAllReceiver.invoke(WSDoAllReceiver.java:351) I monitor the soap messages through the tcpmon and they are below: request soap message: -- ?xml version="1.0" encoding="UTF-8"? soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" soapenv:Header wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soapenv:mustUnderstand="1" wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Timestamp-6559246" wsu:Created2006-07-10T20:19:53.011Z/wsu:Created wsu:Expires2006-07-10T20:24:53.011Z/wsu:Expires /wsu:Timestamp xenc:EncryptedKey Id="EncKeyId-13076987" xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/xenc:EncryptionMethod ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#" wsse:SecurityTokenReference wsse:KeyIdentifier EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier"Xeg55vRyK3ZhAEhEf+YT0z986L0=/wsse:KeyIdentifier /wsse:SecurityTokenReference /ds:KeyInfo xenc:CipherData xenc:CipherValueHEhP2Wm923TOcrC6vcfyf3I7BQPFW6pzZb4oRsV6GHL1THJvLbmjeIGTX9p3/6bLL4lQEy/7M3Sk2znE7QBjTtQuip+WAiJuiKONzQRC175FZTkhNgF6iD62/ikuGMihR3yn/1KZtjMiH8k/gh1Q+sRW0pD8JmEKnBWw2hhX/n8=/xenc:CipherValue /xenc:CipherData xenc:ReferenceList xenc:DataReference URI="#EncDataId-30568553"/xenc:DataReference /xenc:ReferenceList /xenc:EncryptedKey wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="CertId-1776694"MIIDDDCCAfSgAwIBAgIQM6YEf7FVYx/tZyEXgVComTANBgkqhkiG9w0BAQUFADAwMQ4wDAYDVQQKDAVPQVNJUzEeMBwGA1UEAwwVT0FTSVMgSW50ZXJvcCBUZXN0IENBMB4XDTA1MDMxOTAwMDAwMFoXDTE4MDMxOTIzNTk1OVowQjEOMAwGA1UECgwFT0FTSVMxIDAeBgNVBAsMF09BU0lTIEludGVyb3AgVGVzdCBDZXJ0MQ4wDAYDVQQDDAVBbGljZTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAoqi99By1VYo0aHrkKCNT4DkIgPL/SgahbeKdGhrbu3K2XG7arfD9tqIBIKMfrX4Gp90NJa85AV1yiNsEyvq+mUnMpNcKnLXLOjkTmMCqDYbbkehJlXPnaWLzve+mW0pJdPxtf3rbD4PS/cBQIvtpjmrDAU8VsZKT8DN5Kyz+EZsCAwEAAaOBkzCBkDAJBgNVHRMEAjAAMDMGA1UdHwQsMCowKKImhiRodHRwOi8vaW50ZXJvcC5iYnRlc3QubmV0L2NybC9jYS5jcmwwDgYDVR0PAQH/BAQDAgSwMB0GA1UdDgQWBBQK4l0TUHZ1QV3V2QtlLNDm+PoxiDAfBgNVHSMEGDAWgBTAnSj8wes1oR3WqqqgHBpNwkkPDzANBgkqhkiG9w0BAQUFAAOCAQEABTqpOpvW+6yrLXyUlP2xJbEkohXHI5OWwKWleOb9hlkhWntUalfcFOJAgUyH30TTpHldzx1+vK2LPzhoUFKYHE1IyQvokBN2JjFO64BQukCKnZhldLRPxGhfkTdxQgdf5rCK/wh3xVsZCNTfuMNmlAM6lOAg8QduDah3WFZpEA0s2nwQaCNQTNMjJC8tav1CBr6+E5FAmwPXP7pJxn9Fw9OXRyqbRA4v2y7YpbGkG2GI9UvOHw6SGvf4FRSthMMO35 YbpikGsLix3vAsXWWi4rwfVOYzQK0OFPNi9RMCUdSH06m9uLWckiCxjos0FQODZE9l4ATGy9s9hNVwryOJTw==/wsse:BinarySecurityToken ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="Signature-2950265" ds:SignedInfo ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/ds:CanonicalizationMethod ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/ds:SignatureMethod ds:Reference URI="#id-30568553" ds:Transforms ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/ds:Transform /ds:Transforms ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/ds:DigestMethod ds:DigestValuezzx3ig1a7LmzkrkBpLOTIJbLd3s=/ds:DigestValue /ds:Reference /ds:SignedInfo ds:SignatureValueIuRirKy+x18gU00p0uhMEDzEAFvpoHMGKcq45ROmpzQ6ZpD/VEghpYjru6Kff0y3tyWzSvW6nA1mH1pudDP1yLxP5geYvXNPQlFV5X+7T60QPlM6ho3sBj2D3IDAZZXZQdJV+fqC7JycqdzLfXU15fHw+ReZm2r7hIPoys9eHgg=/ds:SignatureValue ds:KeyInfo Id="KeyId-13452612" wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="STRId-29769356" wsse:Reference URI="#CertId-1776694" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/wsse:Reference /wsse:SecurityTokenReference
Axis 1.3 document-style client-side handling of Japanese characters
Title: Axis 1.3 document-style client-side handling of Japanese characters I have an Axis 1.3 HTTP web service that is returning Japanese characters. TcpMon shows these characters to be in the response. However, call.invoke() returns a SOAPEnvelope where the Japanese characters have been converted into question marks (?). The HTTP response has the following XML declaration (from TcpMon): ?xml version=1.0 encoding=UTF-8? A snippet of the actual response (from TcpMon) looks like the following: Id#x65E5;#x672C;#x8A9E;/Id Description#x82B1;#x5B50;/Description But after calling call.invoke(), the snippet looks like: Id???/Id Description??/Description Any ideas how I can preserve the Japanese characters that are being returned using client-side Axis 1.3? Regards, Dave P.S. The HTTP response content-type header (from TcpMon) is: Content-Type: text/xml;charset=utf-8
Re: No 'message' attribute in input for operation ...
Start by validating the WSDL. The error message indicates that you're missing the message attribute in the input definition for the SellServiceFee operation. Proper format for a portType definition looks something like this: wsdl:portType name=myPortType wsdl:operation name=myOperation wsdl:input name=myOperationRequest message=tns:myOperationRequest/ wsdl:output name=myOperationResponse message=tns:myOperationResponse/ /wsdl:operation /wsdl:portType The message attribute must reference a wsdl:message definition. Anne On 7/18/06, akkachotu [EMAIL PROTECTED] wrote: I have a complex WSDL with lot of schema files and when I generated WSDL2Java using AXIS 1.3 then I am getting below error: java.io.IOException: No 'message' attribute in input for operation 'SellServiceFee' at org.apache.axis.wsdl.symbolTable.SymbolTable.ensureOperationValid(SymbolTable.java:1536) at org.apache.axis.wsdl.symbolTable.SymbolTable.ensureOperationsOfPortTypeValid(SymbolTable.java:1608) at org.apache.axis.wsdl.symbolTable.SymbolTable.populatePortTypes(SymbolTable.java:1629) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:743) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:734) at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:518) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361) at java.lang.Thread.run(Thread.java:534) I cannot paste the wsdl and the schemas (.xsd) files here as they are very huge and can anyone please let me know what can be problem with my wsdl ? Thanks in advance. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
CalendarDeserializer and empty dates
The XML message we're attempting to deserialize has the following elements in it: assignedDate xsi:type=xsd:dateTime / createdDate xsi:type=xsd:dateTime2006-07-19T18:23:46.327Z/createdDate The createDate element has no problems, but assignedDate, which has no data, fails with the following: java.lang.NumberFormatException: Invalid date/time Is this a known limitation of the Calendar deserializer? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: CalendarDeserializer and empty dates
The empty string is not a valid xsd:dateTime. To make this a valid response from your service, you would have to specify in the schema that assignedDate was nillable and in the respponse, assignedDate xsi:nil=true ... . I don't know whether the Calendar serializer would have to be able to handle it then -- probably not. Another possibility is to make the assignedDate element optional in the schema (minOccurs=0) and omit in the response when it has no value. Jeff Mike Wallace wrote: The XML message we're attempting to deserialize has the following elements in it: assignedDate xsi:type=xsd:dateTime / createdDate xsi:type=xsd:dateTime2006-07-19T18:23:46.327Z/createdDate The createDate element has no problems, but assignedDate, which has no data, fails with the following: java.lang.NumberFormatException: Invalid date/time Is this a known limitation of the Calendar deserializer? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't generate SOAP Envelope, org.xml.sax.SAXParseException: Premature end of file
Martin,
thanks for your reply. I appreciate it.
I know that it's may because the input xml is not well-formed.
but, as you know, I am invoking an web-service through the generatd stub class by wsdl2java. the soap request is also generated by Axis, so I even can't see the content of the generated soap request.
can anybody tell me how can I have a look at the generated soap request ?
if the soap message is not well-formed,what's the possible root cause ? what should I do ? should I report a bug to axis ? or it's caused by my own code or wsdl ?
thanks
-xucai.
On 7/21/06, Martin Gainty [EMAIL PROTECTED] wrote:
Xu-
Things to look for are is the input XML contain perhapsmissing End Tag (e.g. element without a /element)Sub elements content clipped or chopped offSOAP:header
...no end tag
or missing SOAP:body
Use any XML Editor such as XMLSpy or even IE in a pinchandtheXMLParserwill tell you where the error/missing contentoccurs
Martin
*This email message and any files transmitted with it contain confidentialinformation intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notifythe sender immediately by telephone or email and destroy the originalmessage without making a copy. Thank you.
- Original Message -
From:
xu cai
To: axis-user@ws.apache.org
; axis-dev@ws.apache.org
Sent: Thursday, July 20, 2006 5:41 AM
Subject: Can't generate SOAP Envelope, org.xml.sax.SAXParseException: Premature end of file
Hi All , I run a simple test class to access my webservice deployed on axis 1.2.1 (Built on Jun 14, 2005 (09:15:57 EDT). and got an exception.
The truth is soap msg can't be generated and an SAX xml exception is thrown. Could anyone tell me what happened ? and how to fix that ?
many thanks.
the src code SoapPart.javalooks as:
dser.getEnvelope().setOwnerDocument(this); // This may throw a SAXException try { dser.parse(); // exception } catch (SAXException e) { Exception real =
e.getException(); if (real == null) real = e; throw AxisFault.makeFault(real); }
Exception msg:
AxisFaultfaultCode: {
http://schemas.xmlsoap.org/soap/envelope/}Server.userExceptionfaultSubcode: 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) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion
(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse
(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse
(SAXParser.java:375) at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) at org.apache.axis.Message.getSOAPEnvelope
(Message.java:424) at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) at org.apache.axis.client.Call.invokeEngine
(Call.java:2765) at org.apache.axis.client.Call.invoke(Call.java:2748) at org.apache.axis.client.Call.invoke(Call.java:2424) at org.apache.axis.client.Call.invoke(Call.java:2347) at
org.apache.axis.client.Call.invoke(Call.java:1804) at com.sswitch.oam.soap.intf.Bts10200SoapBindingStub.request(Bts10200SoapBindingStub.java:297) at com.sswitch.oam.soap.test.SimpleTest.main(SimpleTest.java
:22)
{http://xml.apache.org/axis/}hostname:sha-view1.cisco.com
org.xml.sax.SAXParseException: Premature end of file. at org.apache.axis.AxisFault.makeFault(AxisFault.java:101) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:701) at org.apache.axis.Message.getSOAPEnvelope
(Message.java:424) at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206) at org.apache.axis.client.Call.invokeEngine
(Call.java:2765) at org.apache.axis.client.Call.invoke(Call.java:2748) at org.apache.axis.client.Call.invoke(Call.java:2424) at org.apache.axis.client.Call.invoke(Call.java:2347) at
org.apache.axis.client.Call.invoke(Call.java:1804) at com.sswitch.oam.soap.intf.Bts10200SoapBindingStub.request(Bts10200SoapBindingStub.java:297) at com.sswitch.oam.soap.test.SimpleTest.main(SimpleTest.java
:22)Caused by:
How can I use my Axis2 service with Cpp client ?
hi all, I have deployed my service on axis2 ,could I use it with a cpp client and how?
Re: How can I use my Axis2 service with Cpp client ?
Hi, Add Web reference to your project from menu, if you use Visual Studio .NET. --- ºÂ¿¡½Ü [EMAIL PROTECTED] wrote: hi all, I have deployed my service on axis2 ,could I use it with a cpp client and how ? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Generating soap:header info in the WSDL
It's really an interoperability problem with .NET clients. .NET requires that the soap header definition appear in the WSDL, otherwise you are forced to modify the generated proxies to allow them to pass the soap header. Forcing clients of the API to have to modify the proxies is not viable. One of the advantages of the header is that you can pass information to the service that does not clutter up the method signature; otherwise you might as well just pass it as a regular parameter. Ideally, wsdl2java would interpret the WSDL by allowing the header information to be set once on the service, and then unwrap the parameters so that you would have the intended method signature. I do believe the way it is generating the header information in the WSDL is a bug, since it is set to be wrapped document-literal, yet it generates messages with 2 parts. How it decides to represent the header in the proxies, either as a parameter or a way to set the header on the service is certainly a design choice, but not unwrapping the rest of the parameters certainly results in a proxy that does not honor the intent of the service author. Does Axis 1.4 support WS-Policy? I did not see any reference to it in the docs or samples. -Original Message- From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] Sent: Thursday, July 20, 2006 5:07 PM To: axis-user@ws.apache.org Subject: Re: Generating soap:header info in the WSDL If you specify the header in the WSDL, then you intend the application to supply the header (hence the inclusion of the AuthenticationHeader parameter in the interface). If you don't intend the application to supply the header, then you should not include the header in the WSDL. Your security policies should be specified using WS-Policy. Anne On 7/19/06, Brian Fitzpatrick [EMAIL PROTECTED] wrote: So, I figured out how to configure Axis to generate soap:header information in the WSDL file, but it breaks the wrapped document-literal spec. Configuring Axis to send a parameter in the header, by setting parameter inHeader=true in the WSDD file creates WSDL that does not comply with the wrapped document-literal spec. It generates a wsdl:message that contains 2 parts instead of the 1 required by the spec. wsdl:message name=TestParametersRequest wsdl:part element=impl:AuthenticationHeader name=AuthenticationHeader/ wsdl:part element=impl:TestParameters name=parameters/ /wsdl:message As a result, when trying to create an Axis client using WSDL2Java, it fails to unwrap the TestParameters type (the code will only unwrap if it contains only one part and meets other criteria). Thus a service operation defined as: public void testParameters(String stringParam, int integerParam, Boolean booleanParam ) becomes public void testParameters(AuthenticationHeader header, TestParameters parameters ) in the generated Axis client proxies. It seems like the WSDL generation for headers is incorrect. It should be generated like .NET generates them, using 2 wsdl:message's: one for the parameters and one for the header. Then the header is referenced in the wsdl:binding. If Axis is going to generate the soap:header information in this way in the WSDL, then at least the Axis client proxies should be able to recognize this pattern and unwrap the parameters. Currently, the .NET 2.0 proxies (against the Axis generated WSDL) do correctly recognize the header and create method signatures that match the parameters, not a wrapped object containing the parameters. From: Brian Fitzpatrick Sent: Wednesday, July 12, 2006 8:19 AM To: axis-user@ws.apache.org Subject: Generating soap:header info in the WSDL Does Axis 1.4 support generating the WSDL for a soap header? I can't find a configuration or samples where it is done. We have a web service deployed under .NET and Axis. In .NET you can add a directive to the source code and it will create the wsdl that includes the soap header info. It creates the binding shown below and also the message and parts required. If this is not supported, any suggestions on how to accomplish this (handlers?, sample code?). Thanks. wsdl:operation name=TestParameters soap:operation soapAction=urn:Test/TestParameters style=document/ wsdl:input soap:body use=literal/ soap:header message=tns:TestParametersAuthenticationHeader part=AuthenticationHeader use=literal/ /wsdl:input wsdl:output soap:body use=literal/ /wsdl:output /wsdl:operation - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2]Module not found
Hi Martin, Do I only need Axis2.jar,or all the jars in lib directory of axis2-std-1.0-bin? Thanks, Jiang 2006/7/20, Martin Gainty [EMAIL PROTECTED]: Jiang- Isaxis.jar is on your CLASSPATH??M- *This email message and any files transmitted with it contain confidentialinformation intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notifythe sender immediately by telephone or email and destroy the originalmessage without making a copy. Thank you. - Original Message - From: zhu jiang To: axis-user@ws.apache.org Sent: Wednesday, July 19, 2006 11:49 PM Subject: [Axis2]Module not found Hi All, When I run the sample of EchoBlockingDualClient, I receive that: org.apache.axis2.AxisFault: Module not found What should I do? Thanks, Jiang
Re: [Axis2]Module not found
Hi Chinthaka, I have read the userguide, and followed all the instructions, but still it shows module not found. Whatshould I do? Thanks, Jiang 2006/7/20, Eran Chinthaka [EMAIL PROTECTED]: zhu jiang wrote: Hi All, When I run the sample of EchoBlockingDualClient, I receive that: *org.apache.axis2.AxisFault: Module not found* **What should I do?Did u read Engaging Addressing in Client Side in http://ws.apache.org/axis2/1_0/userguide3.html.-- Chinthaka
Why I could not get MessageContext in error routine method processAxisFault()?
hi all, Using Axis1.4 I extended the AxisServlet class and overwrote the processAxisFault(AxisFault fault) method to do some error handlering things, like logging the service name and method name, but when I use MessageContext.getCurrentContext() in that method to get the message context, it is null. Is there any way to get the service name and method name in that method? or is there another method to do the error routine? Any help or web resources would be greatly appreciated ! Regards, - sukie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Upgrade from Axis Beta 2 to Axis 1.4
Hello all, I am upgrading from Axis Beta 2 to Axis 1.4. Is there a link telling me which members in a class in one version of Axis are deprecated? I want to compare them and try to know the impact on my application, also I want to share the particular changes that needs to be done. Please help me out in this. Thanks in advance, Nandita
