Axis C++ Stubs
Hi all, I just joined the group now. This is the first mail. I was in the Axis (java) user list. Actually our project was using the Axis for the implementation of web services. I wanted to know how better the implementation of Axis Java is compared to Axis C ++. What are the difficulties in the stubs generation and all that stuff. Can somebody throw some light into this? Or send me some links to know about this. Subir S Wipro Technologies, Survey No: 64, Madhapur, Hyderabad-500081, AP tel: 040-30795137 Want a signature like this? The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
AIX 32 bit built
Hi Folks, Quite a few people have been having trouble with the aix binaries we've got on the site at the moment (and we thought we were doing everyone a favour ;-) Looks like the issue with the aix 32 bit build is this: The xerces build on the apache website was built using xmlC 5.*. The machine that we build the aix release code on uses 6.* and so we compiled xerces to use that compiler level also. Therefore, what we are seeing is the incompatibility of name mangling (or compiler options) between compiler levels. Given that I don't know how to get around this issue i.e. tell the xlc at 6.* level to mangle the same somehow (or use the same options?) We have two ways forward either a) Compile your own version of xerces 2_2_0 for AIX using xlc 6.* b) We'll also look into upgrading the version of xerces to be the latest and the binaries for this already use xlc 6.* I'll get back to you on how well the tests go for option b) but you can always continue with option a) yourselves :-) cheers for now, John.
RE: WS-I Basic Security Profile
If that is the case, does anyone have any sample code that manipulates the SOAP header manually and adds security token elements? That is what I am going to have to do. -Original Message- Andy Weiss wrote: I need to know if Axis C++ supports the WS-I Basic Security profile at all, namely the Username token. I am afraid not, there has been no developments in this front. Samisa...
Re: WS-I Basic Security Profile
I havent got any sample code on this (may be others would), but just a tought, may be you can write a handler to do this and contribute that to the community. Samisa... Andy Weiss wrote: If that is the case, does anyone have any sample code that manipulates the SOAP header manually and adds security token elements? That is what I am going to have to do. -Original Message- Andy Weiss wrote: I need to know if Axis C++ supports the WS-I Basic Security profile at all, namely the Username token. I am afraid not, there has been no developments in this front. Samisa...
RE: Errors running wsdl2ws
I installed Sun JDK and now I can generate the C++ skeleton and stub code. But after I built the Calculator sample and deployed it, I got the following error when running the client app: terminate called after throwing an instance of 'axiscpp::SoapFaultException' what(): Cannot deserialize the requested element Aborted Does anybody else have the similar problem with Axis c++ 1.6b on the linux (Fedora Core 4)? Any help would be appreciated! Thanks, Lei -Original Message- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: Friday, March 17, 2006 9:35 PM To: Apache AXIS C User List Subject: Re: Errors running wsdl2ws Seems like you are using gcj. I suggest you use JDK from Sun, or try to compile the whole WSDL2WS Java tool, including the required jars from Axis Java using gcj. I have never been able to use gcj with Axis successfully :-( Samisa... Lei Tang wrote: I installed latest Axis C++ 1.6b on linux (Fedora 4). When I used wsdl2ws to generat the C++ code for the sample calculator.wsdl file with following command */java org.apache.axis.wsdl.wsdl2ws.WSDL2Ws /usr/local/axiscpp_deploy/wsdls/calcul ator.wsdl -lc++ -sserver -o/tests/ltang/calculator//* I got the following errors: */java.lang.NullPointerException at gnu.xml.dom.ls.ReaderInputStream.close() (/usr/lib/libgcj.so.6.0.0) at gnu.xml.aelfred2.XmlParser.doParse(java.lang.String, java.lang.String, jav a.io.Reader, java.io.InputStream, java.lang.String) (/usr/lib/libgcj.so.6.0.0) at gnu.xml.aelfred2.SAXDriver.parse(org.xml.sax.InputSource) (/usr/lib/libgcj .so.6.0.0) at gnu.xml.aelfred2.XmlReader.parse(org.xml.sax.InputSource) (/usr/lib/libgcj .so.6.0.0) at gnu.xml.dom.ls.DomLSParser.doParse(org.w3c.dom.ls.LSInput) (/usr/lib/libgc j.so.6.0.0) at gnu.xml.dom.ls.DomLSParser.parse(org.w3c.dom.ls.LSInput) (/usr/lib/libgcj. so.6.0.0) at gnu.xml.dom.DomDocumentBuilder.parse(org.xml.sax.InputSource) (/usr/lib/li bgcj.so.6.0.0) at org.apache.axis.utils.XMLUtils.newDocument(org.xml.sax.InputSource) (Unkno wn Source) at org.apache.axis.utils.XMLUtils.newDocument(java.lang.String, java.lang.Str ing, java.lang.String) (Unknown Source) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(java.lang.String , ja va.lang.String, java.lang.String) (Unknown Source) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run() (Unknown Source) at java.lang.Thread.run() (/usr/lib/libgcj.so.6.0.0) org.apache.axis.wsdl.wsdl2ws.WrapperFault: java.lang.NullPointerException at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.WSDL2Ws(org.apache.axis.wsdl.wsdl2w s. CLArgParser) (Unknown Source) at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main(java.lang.String[]) (Unknown Sou rce) at gnu.java.lang.MainThread.call_main() (/usr/lib/libgcj.so.6.0.0) at gnu.java.lang.MainThread.run() (/usr/lib/libgcj.so.6.0.0) Caused by: java.lang.NullPointerException at gnu.xml.dom.ls.ReaderInputStream.close() (/usr/lib/libgcj.so.6.0.0) at gnu.xml.aelfred2.XmlParser.doParse(java.lang.String, java.lang.String, jav a.io.Reader, java.io.InputStream, java.lang.String) (/usr/lib/libgcj.so.6.0.0) at gnu.xml.aelfred2.SAXDriver.parse(org.xml.sax.InputSource) (/usr/lib/libgcj .so.6.0.0) at gnu.xml.aelfred2.XmlReader.parse(org.xml.sax.InputSource) (/usr/lib/libgcj .so.6.0.0) at gnu.xml.dom.ls.DomLSParser.doParse(org.w3c.dom.ls.LSInput) (/usr/lib/libgc j.so.6.0.0) at gnu.xml.dom.ls.DomLSParser.parse(org.w3c.dom.ls.LSInput) (/usr/lib/libgcj. so.6.0.0) at gnu.xml.dom.DomDocumentBuilder.parse(org.xml.sax.InputSource) (/usr/lib/li bgcj.so.6.0.0) at org.apache.axis.utils.XMLUtils.newDocument(org.xml.sax.InputSource) (Unkno wn Source) at org.apache.axis.utils.XMLUtils.newDocument(java.lang.String, java.lang.Str ing, java.lang.String) (Unknown Source) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(java.lang.String , ja va.lang.String, java.lang.String) (Unknown Source) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run() (Unknown Source) at java.lang.Thread.run() (/usr/lib/libgcj.so.6.0.0)/* *//* */Code generation failed. Please see errors above./* I set my my classpath as following: */declare -x CLASSPATH=/usr/local/axiscpp_home/lib/axisjava/wsdl4j.jar:/usr/local /axiscpp_home/lib/axisjava/saaj.jar:/usr/local/axiscpp_home/lib/axisjava /jaxrpc. jar:/usr/local/axiscpp_home/lib/axisjava/commons-logging.jar:/usr/loca l/axiscpp_ home/lib/axisjava/commons-discovery.jar:/usr/local/axiscpp_home/lib/ax isjava/axi s.jar:/usr/local/axiscpp_deploy/lib/wsdl2ws.jar:/* Could anybody please help me figure out what was wrong? Thanks, Lei
Re: Errors running wsdl2ws
Yes we had the same problem, may be this is also your case. It is not related to linux, its a problem on all platforms. The calculator sample tried to set endpoint to http://localhost/axis/calculator, but the service name is Calculator. The server responded with soap fault (requested service not registered at the server), which was correctly parsed by a client, but then the client throws incorrect exception, so the user gets misleading error 'Cannot deserialize the requested element.'. So first try to run calculator sample with correct endpoint, try for ex: ./calculator div 100 5 http://localhost/axis/Calculator If it will work, you should by hand modify the client stub source code to throw the correct exception, so the user gets correct error description if there is a soap fault. Petr Lei Tang wrote: I installed Sun JDK and now I can generate the C++ skeleton and stub code. But after I built the Calculator sample and deployed it, I got the following error when running the client app: terminate called after throwing an instance of 'axiscpp::SoapFaultException' what(): Cannot deserialize the requested element Aborted Does anybody else have the similar problem with Axis c++ 1.6b on the linux (Fedora Core 4)? Any help would be appreciated! Thanks, Lei -Original Message- From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED] Sent: Friday, March 17, 2006 9:35 PM To: Apache AXIS C User List Subject: Re: Errors running wsdl2ws Seems like you are using gcj. I suggest you use JDK from Sun, or try to compile the whole WSDL2WS Java tool, including the required jars from Axis Java using gcj. I have never been able to use gcj with Axis successfully :-( Samisa... Lei Tang wrote: I installed latest Axis C++ 1.6b on linux (Fedora 4). When I used wsdl2ws to generat the C++ code for the sample calculator.wsdl file with following command */java org.apache.axis.wsdl.wsdl2ws.WSDL2Ws /usr/local/axiscpp_deploy/wsdls/calcul ator.wsdl -lc++ -sserver -o/tests/ltang/calculator//* I got the following errors: */java.lang.NullPointerException at gnu.xml.dom.ls.ReaderInputStream.close() (/usr/lib/libgcj.so.6.0.0) at gnu.xml.aelfred2.XmlParser.doParse(java.lang.String, java.lang.String, jav a.io.Reader, java.io.InputStream, java.lang.String) (/usr/lib/libgcj.so.6.0.0) at gnu.xml.aelfred2.SAXDriver.parse(org.xml.sax.InputSource) (/usr/lib/libgcj .so.6.0.0) at gnu.xml.aelfred2.XmlReader.parse(org.xml.sax.InputSource) (/usr/lib/libgcj .so.6.0.0) at gnu.xml.dom.ls.DomLSParser.doParse(org.w3c.dom.ls.LSInput) (/usr/lib/libgc j.so.6.0.0) at gnu.xml.dom.ls.DomLSParser.parse(org.w3c.dom.ls.LSInput) (/usr/lib/libgcj. so.6.0.0) at gnu.xml.dom.DomDocumentBuilder.parse(org.xml.sax.InputSource) (/usr/lib/li bgcj.so.6.0.0) at org.apache.axis.utils.XMLUtils.newDocument(org.xml.sax.InputSource) (Unkno wn Source) at org.apache.axis.utils.XMLUtils.newDocument(java.lang.String, java.lang.Str ing, java.lang.String) (Unknown Source) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(java.lang.String , ja va.lang.String, java.lang.String) (Unknown Source) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run() (Unknown Source) at java.lang.Thread.run() (/usr/lib/libgcj.so.6.0.0) org.apache.axis.wsdl.wsdl2ws.WrapperFault: java.lang.NullPointerException at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.WSDL2Ws(org.apache.axis.wsdl.wsdl2w s. CLArgParser) (Unknown Source) at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main(java.lang.String[]) (Unknown Sou rce) at gnu.java.lang.MainThread.call_main() (/usr/lib/libgcj.so.6.0.0) at gnu.java.lang.MainThread.run() (/usr/lib/libgcj.so.6.0.0) Caused by: java.lang.NullPointerException at gnu.xml.dom.ls.ReaderInputStream.close() (/usr/lib/libgcj.so.6.0.0) at gnu.xml.aelfred2.XmlParser.doParse(java.lang.String, java.lang.String, jav a.io.Reader, java.io.InputStream, java.lang.String) (/usr/lib/libgcj.so.6.0.0) at gnu.xml.aelfred2.SAXDriver.parse(org.xml.sax.InputSource) (/usr/lib/libgcj .so.6.0.0) at gnu.xml.aelfred2.XmlReader.parse(org.xml.sax.InputSource) (/usr/lib/libgcj .so.6.0.0) at gnu.xml.dom.ls.DomLSParser.doParse(org.w3c.dom.ls.LSInput) (/usr/lib/libgc j.so.6.0.0) at gnu.xml.dom.ls.DomLSParser.parse(org.w3c.dom.ls.LSInput) (/usr/lib/libgcj. so.6.0.0) at gnu.xml.dom.DomDocumentBuilder.parse(org.xml.sax.InputSource) (/usr/lib/li bgcj.so.6.0.0) at org.apache.axis.utils.XMLUtils.newDocument(org.xml.sax.InputSource) (Unkno wn Source) at org.apache.axis.utils.XMLUtils.newDocument(java.lang.String, java.lang.Str ing, java.lang.String) (Unknown Source) at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(java.lang.String , ja va.lang.String, java.lang.String) (Unknown Source) at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run() (Unknown Source) at java.lang.Thread.run() (/usr/lib/libgcj.so.6.0.0)/* *//* */Code generation failed. Please see errors above./* I
WS returns bean
Hello,
I am new in axis and WS. I want to create simple WS which sets some
bean attributes on the client side and then send this to the server
where fills other bean attributes and sends bean back.
Code:
Bean.java
---
package bean;
public class Bean {
private String Type;
private String Filter;
private String Names[];
private String Description[];
// Bean accessors
public String getType()
{ return Type; }
public void setType(String type)
{ Type = type; }
public String getFilter()
{ return Filter; }
public void setFilter(String filter)
{ Filter = filter; }
BeanInfo.java
-
package bean;
public class BeanInfo
{
public Bean processBean(Bean bean) {
String [] aa = new String [] { A, BB, };
String [] bb = new String [] { , , };
bean.setDescription(aa);
bean.setNames(bb);
return bean;
}
}
Procedure:
javac -cp $AXISCLASSPATH:/home/tomcat/workspace/axistest/WEB-INF/src/
bean/*.java
java -cp $AXISCLASSPATH:/home/tomcat/workspace/axistest/WEB-INF/src/
org.apache.axis.wsdl.Java2WSDL -o bean.wsdl
-lhttp://localhost:8080/axis/services/bean; -n urn:bean -pbean
urn:bean bean.BeanInfo
java -cp $AXISCLASSPATH org.apache.axis.wsdl.WSDL2Java -o . -d Session
-s -p bean.ws bean.wsdl
Now I have to change
bean/ws/BeanSoapBindingImpl.java
to add my impl.
generated file:
package bean.ws;
public class BeanSoapBindingImpl implements bean.ws.BeanInfo{
public bean.ws.Bean processBean(bean.ws.Bean in0) throws
java.rmi.RemoteException {
return null;
}
}
I would need to do something like this:
package bean.ws;
import bean.BeanInfo;
public class BeanSoapBindingImpl implements bean.ws.BeanInfo{
BeanInfo bI = new BeanInfo();
public bean.ws.Bean processBean(bean.ws.Bean in0) throws
java.rmi.RemoteException {
return bI.processBean(in0);
}
}
But this doesn't compile. This works for java built in types but not
for user defined.
Probably it is a simple solution, but I don't know how to solve this problem.
Regards,
Grega.
Re: Document style parameters
Anne, Thanks, though while in this case the web service I'm running against is my own so the wsdl errors are important, from now on I have to do the same type of integration against services I don't own so having a working client is the top priority here. If anyone can help with getting xml parameters into a document style call I'd be very grateful. Chris MannionIT Junction020 8452 4274 - Original Message - From: Anne Thomas Manes To: axis-user@ws.apache.org Sent: Friday, March 17, 2006 7:24 PM Subject: Re: Document style parameters Chris,Perhaps someone else can help you the proper coding of your client, but I want to point out that you have some errors in the WSDL:In the wsdl:operation defintion in the portType, you should remove the parameterOrder attribute. At the very least you must remove " resp" from the value of the attribute: wsdl:operation name="getTransactionDetails" parameterOrder="req"Also, in the wsdlsoap:body definition in the binding, you must remove the namespace attribute. The attribute is used only with RPC style bindings. Anne On 3/17/06, Chris Mannion [EMAIL PROTECTED] wrote: Hi all I'm having a problem properly putting a parameter into a call to a document style webservice. I have a generic client build in axis, the basics of while are demonstrated with the following code extracts: ServiceFactory serviceFactory = ServiceFactory.newInstance();Service webService = serviceFactory.createService(wsdlUrl, serviceQName); Call opCall = webService.createCall(portQName, operationName); Object response = opCall.invoke(params); The webservice I'm trying to call is a document style, here are the parts of the wsdl relevant to the input messages ?xml version="1.0" encoding="UTF-8"?wsdl:definitions targetNamespace="urn:TransactionTypesWs"xmlns="urn:TransactionTypesWs"xmlns:apachesoap=" http://xml.apache.org/xml-soap"xmlns:impl="urn:TransactionTypesWs"xmlns:intf="urn:TransactionTypesWs"xmlns:soapenc=" http://schemas.xmlsoap.org/soap/encoding/"xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/ "xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"xmlns:xsd=" http://www.w3.org/2001/XMLSchema" wsdl:types xsd:schema targetNamespace="urn:TransactionTypesWs" !-- Input types -- xsd:element name="Request" xsd:complexType xsd:sequence xsd:element minOccurs="1" maxOccurs="1" name="Type" type="xsd:string"/ xsd:element minOccurs="1" maxOccurs="1" name="From" type="xsd:string"/ xsd:element minOccurs="1" maxOccurs="1" name="Until" type="xsd:string"/ xsd:element minOccurs="1" maxOccurs="1" name="Status" type="xsd:string"/ xsd:element minOccurs="1" maxOccurs="1" name="ExtId" type="xsd:string"/ xsd:element minOccurs="1" maxOccurs="1" name="ExtPwd" type="xsd:string"/ /xsd:sequence /xsd:complexType /xsd:element !-- Output types --... /xsd:schema /wsdl:types wsdl:message name="getTransactionDetailsRequest" wsdl:part name="req" element="impl:Request"/ /wsdl:message ... wsdl:portType name="Transactions" wsdl:operation name="getTransactionDetails" parameterOrder="req resp" wsdl:input message="impl:getTransactionDetailsRequest" name="getTransactionDetailsRequest"/... /wsdl:operation /wsdl:portType wsdl:binding name="TransactionsSoapBinding" type="impl:Transactions" wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/ wsdl:operation name="getTransactionDetails" wsdlsoap:operation soapAction=""/ wsdl:input name="getTransactionDetailsRequest" wsdlsoap:body namespace="urn:TransactionTypesWs" use="literal"/ /wsdl:input ... /wsdl:operation /wsdl:binding wsdl:service name="TransactionsService" wsdl:port binding="impl:TransactionsSoapBinding" name="Transactions" wsdlsoap:address location="..."/ /wsdl:port /wsdl:service/wsdl:definitions So the service is expection an input message with a soap body that looks like this soap:Body Request Type.../Type From.../From Until.../Until Status.../Status ExtId.../ExtId ExtPwd.../ExtPwd /Request /soap:Body I've worked out that to have axis format my input as a proper document style soap message rather than escape the xml and make it a string parameter, I should invoke the call with an org.w3c.dom.Document object as the parameter. However, if I build a document object from xml with the Request tag as it's root element, when incorparates it into the soap message, there is an extra set of Request tags, presumably auto-generated by axis based on what's in
FW: Problems in accessing the service using Axis2
Hi Eran, Thanks for your help.I collected the apache error log for your error i.e using tcpmon.The output for this error log is given below: [Mon Mar 20 04:43:43 2006] [error] [client 222.165.174.102] chunked Transfer-Encoding forbidden: /web-services/sbml.py [Mon Mar 20 04:43:43 2006] [error] PythonHandler ws: Traceback (most recent call last): [Mon Mar 20 04:43:43 2006] [error] PythonHandler ws: File /usr/lib/python2.3/site-packages/mod_python/apache.py, line 193, in Dispatch\nresult = object(req) [Mon Mar 20 04:43:43 2006] [error] PythonHandler ws: File /home/basis/www/web-services/ws.py, line 10, in handler\n dispatch.AsHandler(modules=(sbml,kashif, ),request=req) [Mon Mar 20 04:43:43 2006] [error] PythonHandler ws: File /home/basis/pythonModules//lib/python/ZSI/dispatch.py, line 180, in AsHandler\nps = ParsedSoap(request) [Mon Mar 20 04:43:43 2006] [error] PythonHandler ws: File /home/basis/pythonModules//lib/python/ZSI/parse.py, line 60, in __init__\n str(e.__class__) + ): + str(e), 0) [Mon Mar 20 04:43:43 2006] [error] PythonHandler ws: ParseException: Can't parse document (_apache.SERVER_RETURN): 411 [Mon Mar 20 04:47:29 2006] [error] [client 222.165.174.102] chunked Transfer-Encoding forbidden: /web-services/sbml.py [Mon Mar 20 04:47:29 2006] [error] PythonHandler ws: Traceback (most recent call last): [Mon Mar 20 04:47:29 2006] [error] PythonHandler ws: File /usr/lib/python2.3/site-packages/mod_python/apache.py, line 193, in Dispatch\nresult = object(req) [Mon Mar 20 04:47:29 2006] [error] PythonHandler ws: File /home/basis/www/web-services/ws.py, line 10, in handler\n dispatch.AsHandler(modules=(sbml,kashif, ),request=req) [Mon Mar 20 04:47:29 2006] [error] PythonHandler ws: File /home/basis/pythonModules//lib/python/ZSI/dispatch.py, line 180, in AsHandler\nps = ParsedSoap(request) [Mon Mar 20 04:47:29 2006] [error] PythonHandler ws: File /home/basis/pythonModules//lib/python/ZSI/parse.py, line 60, in __init__\n str(e.__class__) + ): + str(e), 0) [Mon Mar 20 04:47:29 2006] [error] PythonHandler ws: ParseException: Can't parse document (_apache.SERVER_RETURN): 411 [Mon Mar 20 04:48:18 2006] [error] [client 222.165.174.102] chunked Transfer-Encoding forbidden: /web-services/sbml.py [Mon Mar 20 04:48:18 2006] [error] PythonHandler ws: Traceback (most recent call last): [Mon Mar 20 04:48:18 2006] [error] PythonHandler ws: File /usr/lib/python2.3/site-packages/mod_python/apache.py, line 193, in Dispatch\nresult = object(req) [Mon Mar 20 04:48:18 2006] [error] PythonHandler ws: File /home/basis/www/web-services/ws.py, line 10, in handler\n dispatch.AsHandler(modules=(sbml,kashif, ),request=req) [Mon Mar 20 04:48:18 2006] [error] PythonHandler ws: File /home/basis/pythonModules//lib/python/ZSI/dispatch.py, line 180, in AsHandler\nps = ParsedSoap(request) [Mon Mar 20 04:48:18 2006] [error] PythonHandler ws: File /home/basis/pythonModules//lib/python/ZSI/parse.py, line 60, in __init__\n str(e.__class__) + ): + str(e), 0) [Mon Mar 20 04:48:18 2006] [error] PythonHandler ws: ParseException: Can't parse document (_apache.SERVER_RETURN): 411 [Mon Mar 20 04:49:17 2006] [error] [client 222.165.174.102] chunked Transfer-Encoding forbidden: /web-services/sbml.py [Mon Mar 20 04:49:17 2006] [error] PythonHandler ws: Traceback (most recent call last): [Mon Mar 20 04:49:17 2006] [error] PythonHandler ws: File /usr/lib/python2.3/site-packages/mod_python/apache.py, line 193, in Dispatch\nresult = object(req) [Mon Mar 20 04:49:17 2006] [error] PythonHandler ws: File /home/basis/www/web-services/ws.py, line 10, in handler\n dispatch.AsHandler(modules=(sbml,kashif, ),request=req) [Mon Mar 20 04:49:17 2006] [error] PythonHandler ws: File /home/basis/pythonModules//lib/python/ZSI/dispatch.py, line 180, in AsHandler\nps = ParsedSoap(request) [Mon Mar 20 04:49:17 2006] [error] PythonHandler ws: File /home/basis/pythonModules//lib/python/ZSI/parse.py, line 60, in __init__\n str(e.__class__) + ): + str(e), 0) [Mon Mar 20 04:49:17 2006] [error] PythonHandler ws: ParseException: Can't parse document (_apache.SERVER_RETURN): 411 [Mon Mar 20 04:50:43 2006] [error] [client 222.165.174.102] chunked Transfer-Encoding forbidden: /web-services/sbml.py [Mon Mar 20 04:50:43 2006] [error] PythonHandler ws: Traceback (most recent call last): [Mon Mar 20 04:50:43 2006] [error] PythonHandler ws: File /usr/lib/python2.3/site-packages/mod_python/apache.py, line 193, in Dispatch\nresult = object(req) [Mon Mar 20 04:50:43 2006] [error] PythonHandler ws: File /home/basis/www/web-services/ws.py, line 10, in handler\n dispatch.AsHandler(modules=(sbml,kashif, ),request=req) [Mon Mar 20 04:50:43 2006] [error] PythonHandler ws: File /home/basis/pythonModules//lib/python/ZSI/dispatch.py, line 180, in AsHandler\nps = ParsedSoap(request) [Mon Mar 20 04:50:43 2006] [error] PythonHandler
[Axis2] Release plan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all; As you all know Axis2 has been around for about two years and we are still patiently waiting for the magical 1.0. As far as I can see Axis2 is feature complete and it seems to me that the time has come to seriously consider the 1.0 release. I had to postpone 0.95 release due to few blockers and I hope that we will be able to fix those soon and will be able to release 0.95 before the end of this week. And there are few dependencies and tasks that need to be fulfilled before we declare 1.0 1.The list dims suggested (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0) 2.AXIOM release , I think its better if we can do Axis2 1.0 with AXIOM release rather than SNAPSHOT 3.JIRA fixing 4.code clean up 5.I18n There is a number of JIRAs on code generation and ADB and I think it is better if we can fix them after 0.95. We will need to do another quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that boils down to the following release plan, 1.Axis2 0.95 in this week (20-25) 2.Axis2 0.96 first week of the April 3.If we dont find any major issues then we mark 0.96 as Axis2 1.0 Comments and suggestions are warmly welcome - -- Thanks, Deepal ~Future is Open~ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEHpakjOGcXNDx0CARAp0JAJ4gbEUfx8P8VeXuG/i4dlz6ws3z0gCgmpC+ g9YUcE97iKPFKXcjVC7xT8E= =MIjV -END PGP SIGNATURE-
[Axis2] wss4j
Hi there was a thread a few weeks ago (wss4j and axis2) about client problems with security.mar in [0.94]. The conclusions seemed to be: 1. make sure both the client and the service have a correctly configured repository with security.mar in the modules directory, the required jars in the lib directory and an axis2.xml with a module ref for the security module and the required security parameters. 2. explicitly specify the repository location in the client code Doing all this helped a great deal, but I'm a bit confused too see that my client now throws java.lang.ClassNotFoundException: org.apache.ws.security.transform.STRTransform I can see that this class is in wss4j-SNAPSHOT.jar, which in turn is in my security.mar in the modules directory. Extracting the jar into the lib directory seems to solve the problem, but presumably that isn't the right thing to do? The client code to set the configurationContext seemed to be for a version other than 0.94. My attempt looks like this: ConfigurationContextFactory ccf = new ConfigurationContextFactory(); ConfigurationContext ctx = ccf.createConfigurationContextFromFileSystem(C:/axis2); _serviceClient = new org.apache.axis2.client.ServiceClient(ctx, _service); (Just to get things working, I dropped this straight into the PurchasingStub constructor generated by wsdl2java. C:/axis2 is where I unzipped axis. It contains axis2.xml and subdirectories lib, modules etc.) The client classpath includes all the jars in the lib directory, but I haven't set anything else specifically in the environment when the client runs. Any help gratefully received! Cheers Rob
Re:[Axis2] FW: Problems in accessing the service using Axis2
Hi Kashif, Kashif Saleem wrote: Hi Eran, Thanks for your help.I collected the apache error log for your error i.e using tcpmon.The output for this error log is given below: [Mon Mar 20 04:43:43 2006] [error] [client 222.165.174.102] chunked Transfer-Encoding forbidden: /web-services/sbml.py Now I can see the problem. In Axis2, by default chunking is on. Your python server seems not supporting HTTP 1.1 which means not supporting chunking. So set the following to off chunking and you are done. options.setProperty(MessageContextConstants.CHUNKED, Constants.VALUE_FALSE); I tested this, but I got the following error, which says method echo not found. I hope you can fix that on your own :-) . -- Chinthaka SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:ZSI=http://www.zolera.com/schemas/ZSI/; SOAP-ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; SOAP-ENV:Body SOAP-ENV:Fault faultcodeSOAP-ENV:Server/faultcode faultstringProcessing Failure/faultstring detail ZSI:FaultDetail ZSI:stringUnknown method echo/ZSI:string ZSI:trace/home/basis/pythonModules//lib/python/ZSI/dispatch.py:37:_Dispatch/ZSI:trace /ZSI:FaultDetail /detail /SOAP-ENV:Fault /SOAP-ENV:Body /SOAP-ENV:Envelope
Re: Axis2 Deployment Options?
Hi Brian, Well, we actually do support the embedded scenario :) The synapse people (http://incubator.apache.org/synapse/) are already using it. However I'm not quite sure about your requirement of putting axis2 inside a web app. Perhaps it'll be helpful if you can give some more detail about it Ajith On 3/20/06, Brian Abbott [EMAIL PROTECTED] wrote: I was recently looking at Axis2 for possibly migrating existing code from Axis 1.2/1.3 to Axis2 however, from what I am able to tell, Axis2 does not support an embedded deployment scenario where the Axis libraries are included with an existing Web Application and an entry is made in the applications web.xml file. From what I am able to see, Axis2 runs only as a standalone web application, is that accurate? Thanks, Brian Abbott __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Ajith Ranabahu
Re: [Axis2] wss4j
Hi Rob, java.lang.ClassNotFoundException: org.apache.ws.security.transform.STRTransform I can see that this class is in wss4j-SNAPSHOT.jar, which in turn is in my security.mar in the modules directory. Extracting the jar into the lib directory seems to solve the problem, but presumably that isn't the right thing to do? No, you should not have to do that. In your scenario only the security module should contain the wss4j-SNAPSHOT.jar in its 'lib' directory and you should not be required to add it to your classpath separately. This sounds like a module classloading problem Deepal what do you think? Also can you send the complete stack trace of java.lang.ClassNotFoundException: org.apache.ws.security.transform.STRTransform The client code to set the configurationContext seemed to be for a version other than 0.94. My attempt looks like this: ConfigurationContextFactory ccf = new ConfigurationContextFactory(); ConfigurationContext ctx = ccf.createConfigurationContextFromFileSystem(C:/axis2); _serviceClient = new org.apache.axis2.client.ServiceClient(ctx, _service); (Just to get things working, I dropped this straight into the PurchasingStub constructor generated by wsdl2java. C:/axis2 is where I unzipped axis. It contains axis2.xml and subdirectories lib, modules etc.) The client classpath includes all the jars in the lib directory, but I haven't set anything else specifically in the environment when the client runs. To create a configuration context you have to give the path to an axis2 _repository_ to the createConfigurationContextFromFileSystem() method. NOT the place where you extracted Axis2. There has been a considerable amount of changes from 0.94 and I'd strongly recommend you to try the latest SVN head or checkout ht e0.95 release which will be out in a few days. Thanks, Ruchith
class loader in webservice
when webservice is executed by several clients concurrently. ¿What is happens with classloader? ¿An only classloader is created for webservice or one by each request? I have a webservice which reads data loaded in memory, and it is more important that all requests reads the same data. Thank you, very much. -- View this message in context: http://www.nabble.com/class-loader-in-webservice-t1310893.html#a3492729 Sent from the Axis - User forum at Nabble.com.
Re: array serialization in 1.3
Here it is. It is quite complex because there are dozens of operation and .xsd inclusion, so I just extracted the relevant data structures (I can provide the whole WSDL if needed). WSDL: [...] import namespace=http://search.search.services.v1.wsapi.lexisnexis.com; schemaLocation=Search.xsd/ [...] message name=Search-SearchReqMsg part element=search-search:Search name=SearchRequest/ /message message name=Search-SearchRespMsg part element=search-search:SearchResponse name=SearchResponse/ /message [...] portType name=SearchSoapPort operation name=Search input message=tns:Search-SearchReqMsg/ output message=tns:Search-SearchRespMsg/ /operation /portType [...] binding name=SearchSoapBinding type=tns:SearchSoapPort soap11:binding style=document transport=http://schemas.xmlsoap.org/soap/http/ operation name=Search soap11:operation soapAction=/ input soap11:body use=literal/ /input output soap11:body use=literal/ /output /operation operation name=NarrowSearch soap11:operation soapAction=/ input soap11:body use=literal/ /input output soap11:body use=literal/ /output /operation /binding [...] Search.xsd: ?xml version=1.0 encoding=UTF-8? schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://search.search.services.v1.wsapi.lexisnexis.com; xmlns:tns=http://search.search.services.v1.wsapi.lexisnexis.com; xmlns:common=http://common.services.v1.wsapi.lexisnexis.com; xmlns:result=http://result.common.services.v1.wsapi.lexisnexis.com; xmlns:searchcommon=http://common.search.services.v1.wsapi.lexisnexis.com; xmlns:security=http://security.common.services.v1.wsapi.lexisnexis.com; elementFormDefault=qualified attributeFormDefault=unqualified version=1.0 import namespace=http://common.services.v1.wsapi.lexisnexis.com; schemaLocation=Common.xsd/ import namespace=http://result.common.services.v1.wsapi.lexisnexis.com; schemaLocation=Result.xsd/ import namespace=http://common.search.services.v1.wsapi.lexisnexis.com; schemaLocation=SearchCommon.xsd/ import namespace=http://security.common.services.v1.wsapi.lexisnexis.com; schemaLocation=Security.xsd/ !-- Message elements -- element name=Search type=tns:Search annotation documentation Represents a LexisNexis search and retrieval. Many options are exposed to allow a user to customize the search request. /documentation /annotation /element element name=SearchResponse type=result:SearchResponse annotation documentation The response from a search request is a set of search results, containing document identifiers along with documents in the specified or default output format. /documentation /annotation /element !-- Types -- complexType name=Search complexContent extension base=common:BaseRequest sequence element name=binarySecurityToken type=security:BinarySecurityToken annotation documentation examplef4348ad8876542bc93748c89fb98a7e/example Security token that must be provided on all non-authentication requests. /documentation /annotation /element element name=sourceInformation type=searchcommon:SourceInformationChoice annotation documentation Either a list of source identifiers or a single secured source identifier. /documentation /annotation /element element name=query type=string annotation documentation examplecats and dogs and hamsters/example Query string for the search request, formatted in the appropriate syntax for the selected search method. /documentation /annotation /element element name=projectId type=common:ProjectId minOccurs=0 annotation documentation exampleResearch Project 001/example Used for client or project identification purposes. This identifier will be associated with each search transaction and will be reported on your organizationapos;s invoice. /documentation /annotation /element element
Re: Module validation failed module.xml
Are you using the war that comes with the .94 release? Or are you trying to use your own war? Are the .mar files under WEB-INF/modules really from the .94 version? One more thing: does http:/localhost:8080/axis2/listServices show any faulty services ? HTH, Robert http://www.braziloutsource.com/On 3/19/06, Yariel Ramos Moreno [EMAIL PROTECTED] wrote:Hi Robert:I've done what you say: copy .axis directory and all it's content to WEB-INF and still throwing the same exception. Is there another solution???Thanks very much... On 3/19/06, robert lazarski [EMAIL PROTECTED] wrote: The /home/myuser/.axis2 is relevant. AFAIK, only outside a servlet container. So you still apparently, somehow, have repository problems. Your WEB-INF/ showld match your /home/myuser/.axis2 . See this article on the repository and other issues that axis2 users sometimes have: http://www.developer.com/open/article.php/10930_3589126_1 HTH, Robert http://www.braziloutsource.com/ On 3/19/06, Yariel Ramos Moreno [EMAIL PROTECTED] wrote:Hi:This is the second time I wrote about this problem, but the situation is diferent now. I have an Axis2 (0.94 release) web service. It is working fine. Also, I have a web application in wich the service is invoked. When I do this, I get the followin exception: Module validation failed module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing org.apache.axis2.deployment.DeploymentException : module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException : module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing at org.apache.axis2.deployment.DeploymentEngine.load (DeploymentEngine.java:542) at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:56) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext (ConfigurationContextFactory.java:39) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:53) at org.apache.axis2.client.ServiceClient .init(ServiceClient.java:86) at org.apache.axis2.client.ServiceClient.init(ServiceClient.java:148) at facade.struts.model.NewsServiceClient.invokeService(NewsServiceClient.java:23) at facade.struts.model.NewsService.getNewsFrom(NewsService.java:93) at facade.struts.action.MenuAction.execute(MenuAction.java:68) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java :484) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482) at org.apache.struts.action.ActionServlet.doGet (ActionServlet.java:507) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) 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.Http11Processor.process (Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java :527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run (Thread.java:595)Caused by: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing at org.apache.axis2.deployment.repository.util.ArchiveReader.creatModuleArchivefromResource(ArchiveReader.java:193) at org.apache.axis2.engine.AxisConfiguration.loadModulefromResources (AxisConfiguration.java:385) at org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:328) at
Re: Module validation failed module.xml
I'm using the war that comes with axis 0.94 release, I didn't make any modification to it. The addressing.mar file is under WEB-INF/modules and home/.axis2/modules directories and in my web application/WEB-INF directory I made a copy of .axis directory. http:/localhost:8080/axis2/listServices doesn't show any faulty service. Even more, the web service work very well when I use it from a standalone application outside de container. On 3/20/06, robert lazarski [EMAIL PROTECTED] wrote: Are you using the war that comes with the .94 release? Or are you trying to use your own war? Are the .mar files under WEB-INF/modules really from the .94 version? One more thing: does http:/localhost:8080/axis2/listServices show any faulty services ? HTH, Robert http://www.braziloutsource.com/On 3/19/06, Yariel Ramos Moreno [EMAIL PROTECTED] wrote:Hi Robert:I've done what you say: copy .axis directory and all it's content to WEB-INF and still throwing the same exception. Is there another solution???Thanks very much... On 3/19/06, robert lazarski [EMAIL PROTECTED] wrote: The /home/myuser/.axis2 is relevant. AFAIK, only outside a servlet container. So you still apparently, somehow, have repository problems. Your WEB-INF/ showld match your /home/myuser/.axis2 . See this article on the repository and other issues that axis2 users sometimes have: http://www.developer.com/open/article.php/10930_3589126_1 HTH, Robert http://www.braziloutsource.com/ On 3/19/06, Yariel Ramos Moreno [EMAIL PROTECTED] wrote:Hi:This is the second time I wrote about this problem, but the situation is diferent now. I have an Axis2 (0.94 release) web service. It is working fine. Also, I have a web application in wich the service is invoked. When I do this, I get the followin exception: Module validation failed module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing org.apache.axis2.deployment.DeploymentException : module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException : module.xml not found for the module : addressing; nested exception is: org.apache.axis2.deployment.DeploymentException: module.xml not found for the module : addressing at org.apache.axis2.deployment.DeploymentEngine.load (DeploymentEngine.java:542) at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:56) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext (ConfigurationContextFactory.java:39) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:53) at org.apache.axis2.client.ServiceClient .init(ServiceClient.java:86) at org.apache.axis2.client.ServiceClient.init(ServiceClient.java:148) at facade.struts.model.NewsServiceClient.invokeService(NewsServiceClient.java:23) at facade.struts.model.NewsService.getNewsFrom(NewsService.java:93) at facade.struts.action.MenuAction.execute(MenuAction.java:68) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java :484) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482) at org.apache.struts.action.ActionServlet.doGet (ActionServlet.java:507) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) 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.Http11Processor.process (Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java :527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run (Thread.java:595)Caused by:
Creating a new Log Handler
Hello there! I need to create a new Log Handler. The example on the user guides is pretty self explanatory, but I have a few questions:1st- Do I have to explicit add on each of my service to be deployed to use that handler? Isn't there a global configuration where I could add that handler to be called for ALL services (no exceptions) on my axis engine? 2nd- How can I track info about the requester (aka HTTP_REMOTE_ADDR)?Regards
Re: [Axis2] wss4j
Hi Ruchith, thanks! I'll try a later version. Just to clarify, I was thinking a repository was just a directory which conformed to a specific structure, for instance with sub-directories called modules, lib etc. It sounds like I haven't understood this properly. Can you tell me where it is described? Many thanks Rob - Original Message - From: Ruchith Fernando [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Monday, March 20, 2006 12:53 PM Subject: Re: [Axis2] wss4j Hi Rob, java.lang.ClassNotFoundException: org.apache.ws.security.transform.STRTransform I can see that this class is in wss4j-SNAPSHOT.jar, which in turn is in my security.mar in the modules directory. Extracting the jar into the lib directory seems to solve the problem, but presumably that isn't the right thing to do? No, you should not have to do that. In your scenario only the security module should contain the wss4j-SNAPSHOT.jar in its 'lib' directory and you should not be required to add it to your classpath separately. This sounds like a module classloading problem Deepal what do you think? Also can you send the complete stack trace of java.lang.ClassNotFoundException: org.apache.ws.security.transform.STRTransform The client code to set the configurationContext seemed to be for a version other than 0.94. My attempt looks like this: ConfigurationContextFactory ccf = new ConfigurationContextFactory(); ConfigurationContext ctx = ccf.createConfigurationContextFromFileSystem(C:/axis2); _serviceClient = new org.apache.axis2.client.ServiceClient(ctx, _service); (Just to get things working, I dropped this straight into the PurchasingStub constructor generated by wsdl2java. C:/axis2 is where I unzipped axis. It contains axis2.xml and subdirectories lib, modules etc.) The client classpath includes all the jars in the lib directory, but I haven't set anything else specifically in the environment when the client runs. To create a configuration context you have to give the path to an axis2 _repository_ to the createConfigurationContextFromFileSystem() method. NOT the place where you extracted Axis2. There has been a considerable amount of changes from 0.94 and I'd strongly recommend you to try the latest SVN head or checkout ht e0.95 release which will be out in a few days. Thanks, Ruchith
differences between axis and axis2 (styles and lit vs enc)
Hi, I'm looking for the differences between axis and axis2. At the moment I'm trying to find out which styles and encodings are supported. (with document-centric I mean the possibility to get the message as xml tree. in axis2 this is covered via RawXMLMessageReceiver and OMElement) axis: rpc/enc rpc/lit doc/enc doc/lit wrapped all supported no way to create a message-centric web service axis2: rpc/enc (- I read it should be supported) rpc/lit what about the others? easy message-centric services (RawXMLMessageReceiver) And how to I configure the style and the use (- encoded vs literal) thx Dominik __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
Re: Axis2/C# Compatibility
Ok, but we expect Axis produces a WSDL file. I think if we give service.xml and related class with public methods to axis, that axis will produce the correct WSDL file. Thanks for any information luc Anne Thomas Manes schrieb: Your WSDL isn't valid. You didn't declare any namespaces. Anne On 3/16/06, *Lukas Fischer / HTA* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello there I work on a application with a Webservice-Component (Java/Axis2) and a client C# (Visual Studio 2005). The software is in a very early phase, so we still evaluate what we should use. If we add a Webservice in Visual Studio, I get the following output The document at the url http://localhost:8080/axis2/services/baas?wsdl was not recognized as a known document type. The error message from each known type may help you fix the problem: - Report from 'system.web.services.discovery.discoverydocumentreference' is 'Discovery document at the URL http://localhost:8080/axis2/services/baas?wsdl could not be found.'. - The document format is not recognized. - Report from 'system.web.services.discovery.contractreference' is 'There is an error in the XML document.'. - The required attribute 'name' is missing. - Report from 'system.web.services.discovery.schemareference' is 'Expected Schema root. Make sure the root element is schema and the namespace is 'http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema' for an XSD schema or 'urn:schemas-microsoft-com:xml-data' for an XDR schema.'. services.xml is service name=Baas description test /description parameter name=ServiceClass locked=xsd:falsebaas.webservice.Test/parameter operation name=getName /operation /service When I access through the Browser, the response seems to be ok. Like this: wsdl:definitions targetNamespace=http://org.apache.axis2/; - wsdl:types - xs:schema ns1:elementFormDefault=qualified ns0:attributeFormDefault=unqualified ns2:targetNamespace=http://org.apache.axis2/xsd; - xs:element ns0:name=getNameRequest xs:complexType/ /xs:element - xs:element ns0:name=getNameResponse - xs:complexType - xs:sequence xs:element ns0:name=return ns1:type=xs:string/ /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types - wsdl:message name=getNameResponseMessage wsdl:part name=part1 element=ns1:getNameResponse/ /wsdl:message - wsdl:message name=getNameRequestMessage wsdl:part name=part1 element=ns1:getNameRequest/ /wsdl:message - wsdl:portType name=baasPort - wsdl:operation name=getName wsdl:input message=tns:getNameRequestMessage/ wsdl:output message=tns:getNameResponseMessage/ /wsdl:operation /wsdl:portType - wsdl:binding name=baasBinding type=tns:baasPort soap:binding transport=http://schemas.xmlsoap.org/soap/http http://schemas.xmlsoap.org/soap/http style=document/ - wsdl:operation name=getName soap:operation name=operation soapAction=getName style=document/ - wsdl:input soap:body use=literal namespace=http://www.org.apache.axis2/ /wsdl:input - wsdl:output soap:body use=literal namespace= http://www.org.apache.axis2/ /wsdl:output /wsdl:operation /wsdl:binding - wsdl:service name=baas - wsdl:port name=baasPortType binding=tns:baasBinding soap:address location=http://localhost:8080/axis2/services/baas/ /wsdl:port /wsdl:service /wsdl:definitions mmmh, hope you can help me. I'm very new to axis and webservices at all. If there you know some links to related articles, ... would be wonderful. Thanks in advance, luc
java.lang.NoSuchMethodError: org.apache.axis2.context.MessageContext.getMessageInformationHeaders()
Hi All,
The problem is this, when calling ServiceClient. sendReceive (OMElement),
I
got a following message:
Exception in thread main java.lang.NoSuchMethodError:
org.apache.axis2.context.MessageContext.getMessageInformationHeaders()Lorg/apache/axis2/addressing/MessageInformationHeaders;
at
org.apache.axis2.handlers.addressing.AddressingOutHandler.invoke(AddressingOutHandler.java:56)
at org.apache.axis2.engine.Phase.invoke(Phase.java:376)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:351)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:441)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:317)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:267)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:393)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:326)
at userguide.clients.TestClient.main(TestClient.java:54)
I am just wondering about the cause of it.Attached with this mail is my
client.I would
appreciate your help.
Kind Regards
Kashif Saleem
/*
* Copyright 2004,2005 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the License);
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an AS IS BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package userguide.clients;
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.om.OMAbstractFactory;
import org.apache.axis2.om.OMElement;
import org.apache.axis2.om.OMFactory;
import org.apache.axis2.om.OMNamespace;
import javax.xml.namespace.QName;
import javax.xml.stream.FactoryConfigurationError;
import javax.xml.stream.XMLOutputFactory;
import javax.xml.stream.XMLStreamException;
import javax.xml.stream.XMLStreamWriter;
/**
* This is a Client progam that accesses 'MyService' web service in Axis2 samples
*/
public class TCPClient {
private static String toEpr = tcp://localhost:8080/axis2/services/MyService;
public static void main(String[] args) throws AxisFault {
Options options = new Options();
options.setTo(new EndpointReference(toEpr));
options.setTransportInProtocol(Constants.TRANSPORT_TCP);
ServiceClient sender = new ServiceClient();
sender.engageModule(new QName(Constants.MODULE_ADDRESSING));
sender.setOptions(options);
OMElement result = sender.sendReceive(getPayload());
try {
XMLStreamWriter writer = XMLOutputFactory.newInstance()
.createXMLStreamWriter(System.out);
result.serialize(writer);
writer.flush();
} catch (XMLStreamException e) {
e.printStackTrace();
} catch (FactoryConfigurationError e) {
e.printStackTrace();
}
}
private static OMElement getPayload() {
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs = fac.createOMNamespace(
tcp://localhost:8080/axis2/services/MyService, example1);
OMElement method = fac.createOMElement(echo, omNs);
OMElement value = fac.createOMElement(Text, omNs);
value.addChild(fac.createText(value, Axis2 Echo String ));
method.addChild(value);
return method;
}
}
Speeding up RPC
Hi, I have written an RPC webservice with Axis 1.3 and Tomcat 5.0.28 and would like to speed it up if possible. At the moment returning an array of beans takes about 13 seconds when both client and server run on a Sempron 3000+ machine. The beans are simple containing just one 11 character String and 3 int fields. I have tried with two clients (a java client and SOAPsh) and both take roughly the same amount of time. Is there a way to speed this up? I include my .wsdd file below and can provide more code if necessary. Thanks in advance Morten ?xml version=1.0? deployment xmlns=http://xml.apache.org/axis/wsdd/; xmlns:java=http://xml.apache.org/axis/wsdd/providers/java; service name=Orion provider=java:RPC parameter name=className value=dk.ange.orion.soap.Orion/ parameter name=scope value=Application/ beanMapping qname=myNS:Result xmlns:myNS=urn:Orion languageSpecificType=java:dk.ange.orion.soap.Result/ beanMapping qname=myNS:BayPlanLine xmlns:myNS=urn:Orion languageSpecificType=java:dk.ange.orion.soap.BayPlanLine/ /service /deployment
Re: [Axis2] java.lang.NoSuchMethodError: org.apache.axis2.context.MessageContext.getMessageInformationHeaders()
Hi Kashif,
Seems like you are trying to use an older version addressing mar with
Axis2. Better have the appropriate version of addressing in the modules
folder.
MessageContext.getMessageInformationHeaders is a method removed some
time back.
-- Chinthaka
P.S. Please prefix the subjects of all your emails related to Axis2 with
[Axis2].
Kashif Saleem wrote:
Hi All,
The problem is this, when calling ServiceClient. sendReceive (OMElement), I
got a following message:
Exception in thread main java.lang.NoSuchMethodError:
org.apache.axis2.context.MessageContext.getMessageInformationHeaders()Lorg/apache/axis2/addressing/MessageInformationHeaders;
at
org.apache.axis2.handlers.addressing.AddressingOutHandler.invoke(AddressingOutHandler.java:56)
at org.apache.axis2.engine.Phase.invoke(Phase.java:376)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:351)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:441)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:317)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:267)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:393)
at
org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:326)
at userguide.clients.TestClient.main(TestClient.java:54)
I am just wondering about the cause of it.Attached with this mail is my client.I would
appreciate your help.
Kind Regards
Kashif Saleem
/*
* Copyright 2004,2005 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the License);
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an AS IS BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package userguide.clients;
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.om.OMAbstractFactory;
import org.apache.axis2.om.OMElement;
import org.apache.axis2.om.OMFactory;
import org.apache.axis2.om.OMNamespace;
import javax.xml.namespace.QName;
import javax.xml.stream.FactoryConfigurationError;
import javax.xml.stream.XMLOutputFactory;
import javax.xml.stream.XMLStreamException;
import javax.xml.stream.XMLStreamWriter;
/**
* This is a Client progam that accesses 'MyService' web service in Axis2
samples
*/
public class TCPClient {
private static String toEpr =
tcp://localhost:8080/axis2/services/MyService;
public static void main(String[] args) throws AxisFault {
Options options = new Options();
options.setTo(new EndpointReference(toEpr));
options.setTransportInProtocol(Constants.TRANSPORT_TCP);
ServiceClient sender = new ServiceClient();
sender.engageModule(new QName(Constants.MODULE_ADDRESSING));
sender.setOptions(options);
OMElement result = sender.sendReceive(getPayload());
try {
XMLStreamWriter writer = XMLOutputFactory.newInstance()
.createXMLStreamWriter(System.out);
result.serialize(writer);
writer.flush();
} catch (XMLStreamException e) {
e.printStackTrace();
} catch (FactoryConfigurationError e) {
e.printStackTrace();
}
}
private static OMElement getPayload() {
OMFactory fac = OMAbstractFactory.getOMFactory();
OMNamespace omNs = fac.createOMNamespace(
tcp://localhost:8080/axis2/services/MyService, example1);
OMElement method = fac.createOMElement(echo, omNs);
OMElement value = fac.createOMElement(Text, omNs);
value.addChild(fac.createText(value, Axis2 Echo String ));
method.addChild(value);
return method;
}
}
Java client array encoding causes troubles for AxisCPP service
I have noticed an inconsistency in the encoding of arrays by Axis Java clients (created using WSDL2Java) and AxisCPP clients (created using WSDL2Ws), and I was hoping someone could give me some advice. In short, I have the following RPC/encoded WSDL snippet that defines the array: types schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace=http://localhost/axis/csaapi/xsd; import namespace = http://schemas.xmlsoap.org/soap/encoding// complexType name=ArrayOfInt complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=int[]/ /restriction /complexContent /complexType /schema /types When I create and run the AxisCPP client, it generates XML that uses item to denote the elements in the array: SOAP-ENV:Body ns1:GetNamesByIds xmlns:ns1=http://localhost/axis/csaapi; objType xsi:type=xsd:int0/objType idsArray xmlns:enc=http://www.w3.org/2001/06/soap-encoding; enc:arrayType=xsd:int[9] item1/item item2/item item3/item /idsArray /ns1:GetNamesByIds /SOAP-ENV:Body My AxisCPP service handles this just fine. BUT, my Java client generates XML that doesn't use the item construct, and it causes my CPP service to fail to parse the data. Here's the Java XML: soapenv:Body ns1:GetNamesByIds soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns1=http://localhost/axis/csaapi; objType xsi:type=xsd:int0/objType ids soapenc:arrayType=xsd:int[9] xsi:type=soapenc:Array xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; ids xsi:type=xsd:int1/ids ids xsi:type=xsd:int2/ids ids xsi:type=xsd:int3/ids /ids /ns1:GetNamesByIds /soapenv:Body Could someone give me advice on the best way to handle this? Note that I've already turned the MULTIREF option off to fix a different set of problems. I'd prefer to keep the RPC/Encoded style if at all possible. Thank you very much in advance! -Jonathan Beakley [EMAIL PROTECTED]
[Axis0.94] Duplicated xmlns= added by StAXSOAPModelBuilder
Hi,I've got an InputStream containing a soap envelope.When I use StAXSOAPModelBuilder to create a SOAPEnvelope object, some extra strings (xmlns=) are added in the resulting envelope!!!What's the problem here? The code is pretty simple: // InputStream soapStream contains the envelope as a stream javax.xml.stream.XMLInputFactory xmlif = javax.xml.stream.XMLInputFactory.newInstance(); javax.xml.stream.XMLStreamReader xmlr = xmlif.createXMLStreamReader(soapStream); StAXSOAPModelBuilder builder = new StAXSOAPModelBuilder(xmlr,null); SOAPEnvelope newEnvelope = builder.getSOAPEnvelope ();My InputStream contains something like this:?xml version=1.0 encoding=UTF-8?soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/soapenv:Header/soapenv:Headersoapenv:BodyDmpPatientRequest xmlns=http://dmp/search/types access xmlns=Acces normal/access/DmpPatientRequest/soapenv:Body/soapenv:EnvelopeBut in the resulting SOAPEnvelope I get: ... access xmlns= xmlns=Acces normal/access ...What is hapening here?
Re: [Axis2] Release plan
We are making solid progress with Axis2 and greatly appreciate the efforts of the developers. I hope that the issues we have addressed in 0.94 and submitted patches for will all be addressed in both 0.95 and 1.0: Support for choice particles Support for recursive data types Support for minOccurs=0 in the 0 case, i.e. both empty arrays and omitted optional parameters Allow subelements to have the same name and a different type than their parent element Correct OMStAXWrapper.getElementText() to obey the general contract of getElementText() in the parser==null case (leave the reader at the END_ELEMENT) I believe at least some of these are addressed in the current code base, but not all are yet; e.g., I think that Ajith is trying to add the choice particle support prior to the 0.95 release. Please allow this to happen if at all possible. FYI, the patches and discussion pertaining to the above are in the attached email. Thanks for the great system, Chuck Franz Fehringer [EMAIL PROTECTED] wrote on 03/20/2006 02:57:25 AM: Will the TCP monitor be factored out (- ws-commons) in release 1.0? Greetings Franz Deepal Jayasinghe schrieb: Hi all; As you all know Axis2 has been around for about two years and we are still patiently waiting for the magical 1.0. As far as I can see Axis2 is feature complete and it seems to me that the time has come to seriously consider the 1.0 release. I had to postpone 0.95 release due to few blockers and I hope that we will be able to fix those soon and will be able to release 0.95 before the end of this week. And there are few dependencies and tasks that need to be fulfilled before we declare 1.0 1.The list dims suggested (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0) 2.AXIOM release , I think its better if we can do Axis2 1.0 with AXIOM release rather than SNAPSHOT 3.JIRA fixing 4.code clean up 5.I18n There is a number of JIRAs on code generation and ADB and I think it is better if we can fix them after 0.95. We will need to do another quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that boils down to the following release plan, 1.Axis2 0.95 in this week (20-25) 2.Axis2 0.96 first week of the April 3.If we dont find any major issues then we mark 0.96 as Axis2 1.0 Comments and suggestions are warmly welcome -- Thanks, Deepal ~Future is Open~ ---BeginMessage--- Thanks Ajith. I need to make progress on my project and so unfortunately have to fix the issues in 0.94 as they arise. We have a fairly complicated set of types in our wsdl to support. If only 0.95 was done with all your fixes in it (including choice)... :-) FYI, there was a bug in my fixes to ADBPullParser to handle minOccurs=0. The changes to next() fully resolve the issues without any change to the constructor. Also, the fixes to deserialization (code generated for the parse() methods) uncovered a bug in OMStAXWrapper.getElementText(). In the case where parser==null (i.e., working directly on an OMElement), it did not obey the proper contract for getElementText(). Specifically, it did not advance itself to the END_ELEMENT. This caused my parse() methods to parse the same element infinitely since they were always at the START_ELEMENT. This case appears to have only occured (in my uses so far) when the entire message body was a single element of simple type (e.g., document/literal message with an xsd:string element payload). In other cases, OMStAXWrapper apparently switched to the parser!=null state, which worked properly. The attached xml.src.patch fixes OMStAXWrapper.getElementText(). The attached adb.patch contains the updated fix to ADBPullParser. I included codegen.patch again just for completeness re. all the issues covered on this thread, although it has not changed from the prior message. Looking forward to 0.95! Chuck "Ajith Ranabahu" [EMAIL PROTECTED] wrote on 03/05/2006 05:53:56 PM: Hi chuck, is this a 0.94 issue ? I've done some (significant) changes to the de-ser code lately so things look different now. We handle the min occurs properly. Unfortunately the current code handles sequence properly but not "choice" or "all" (I'll be working on that soon though) I'll fix the codegen issues but I may not be able to apply your patches directly now Ajith On 3/5/06, Chuck Williams [EMAIL PROTECTED] wrote: Hi Ajith and all, I ran into another code generation problem. minOccurs=0 elements are not supported in the 0 case. I.e., for an optional element that is not present or a zero-length array, the parsing has bugs. The core serialization in adb also fails to handle this case. For the parsing (deserialization), the argumentCount mechanism in the generated parse() methods fails when no elements for a minOccurs=0 property are present. For serialization, the next() method in the ADBPullParser fails to handle zero-length arrays as it
Absolute Newbie Question: how to enable SOAP 1.2 support in the sample userguide code?
I have just started playing with Axis2.0 and I need to know what are required to convert the samples/userguide code to be SOAP1.2 messages. I watched the HTTP traffic and they are still in SOAP1.1 format from the 0.93 source release. I am in dire need for a SOAP1.2 client to test one of our services. So the question is: What do I need to do to implement SOAP1.2 client support using Axis 2.0? Thanks in advance, Yang Xiang Quest Software
Deploying .class files to a symlink directory instead of /web-inf/classes (easy question?)
Title: Deploying .class files to a symlink directory instead of /web-inf/classes (easy question?) Might be an easy one. We're installing Tomcat 5.0.28 and Axis 1.1 on several machines. We usually set up an operations and test version at the same time. Typically, we'll install .html/.jsp/whatever files within the /tomcat/classes directory, but that directory is just a symlink to something like /usr/deployment/classes. I found that when I did this in Axis1.1 I'd get class not found exceptions and the like. 1) Can this be done? Can I put my services and .class files in /usr/classes and just point /axis/WEB-INF/classes/myproject to that area? Did I do something wrong before? 2) Is there another way to simulate this setup? Reason being that we don't want to come along and upgrade Axis to 1.2 or Tomcat to 5.5.x and wipe out our development code. I tried reading through old lists and didn't seem to find an answer. I'm hoping it's something as simple as adding a classpath in the .wsdd file or just that it's not possible. If that is the case it's okay, but wanted to rule it out. Fyi, we're installing on an SGI (not sure it matters). Thanks in advance, Andy
Constructor target
Title: Deploying .class files to a symlink directory instead of /web-inf/classes (easy question?) The usage and choice of the constructor to use with the bean deserializer is chosen as a first found one instead if us being able to specify what to use or as suggested by the XML mapping suggested in JSR109 (mentioned in code). What this is doing is making the constructortarget class being able to create an instance where the constructor has arrays as parameters. An example is A constructor for the Foo class Foo(string, Object[]) Deserialization fails in the ContructorTargets set method with an error stating that No object was found for class type class [Ljava.lang.Object; This is not right and should be fixed. Any comments?
Re: class loader in webservice
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I can solve this problem using application scope Thanks for any help when webservice is executed by several clients concurrently. ¿What is happens with classloader? ¿An only classloader is created for webservice or one by each request? I have a webservice which reads data loaded in memory, and it is more important that all requests reads the same data. Thank you, very much. -- View this message in context: http://www.nabble.com/class-loader-in-webservice-t1310893.html#a3492729 Sent from the Axis - User forum at Nabble.com. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEH0EpE2z3kEWcD6URAu3aAJwL6HgQudqXxbRXx8epRlKCJFHa8wCeJpO9 mqwi6HbyfJSQh9U1v5xvIS4= =uXrt -END PGP SIGNATURE-
Re: [Axis2] Release plan
Most definitely +1! Axis2 is now ready for prime time .. and we need much wider user feedback to make it move to the next level. We won't get that until we release 1.0. I propose we change 0.96 below to the label 1.0RC to signal to everyone that this is our planned 1.0 release. That will get more attention IMO. Sanjiva. On Mon, 2006-03-20 at 17:48 +0600, Deepal Jayasinghe wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all; As you all know Axis2 has been around for about two years and we are still patiently waiting for the magical 1.0. As far as I can see Axis2 is feature complete and it seems to me that the time has come to seriously consider the 1.0 release. I had to postpone 0.95 release due to few blockers and I hope that we will be able to fix those soon and will be able to release 0.95 before the end of this week. And there are few dependencies and tasks that need to be fulfilled before we declare 1.0 1.The list dims suggested (http://wiki.apache.org/ws/FrontPage/Axis2/releases/1.0) 2.AXIOM release , I think its better if we can do Axis2 1.0 with AXIOM release rather than SNAPSHOT 3.JIRA fixing 4.code clean up 5.I18n There is a number of JIRAs on code generation and ADB and I think it is better if we can fix them after 0.95. We will need to do another quick release (say 0.96 or 1.0 RC) before the 1.0 anyway. Finally that boils down to the following release plan, 1.Axis2 0.95 in this week (20-25) 2.Axis2 0.96 first week of the April 3.If we dont find any major issues then we mark 0.96 as Axis2 1.0 Comments and suggestions are warmly welcome - -- Thanks, Deepal ~Future is Open~ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEHpakjOGcXNDx0CARAp0JAJ4gbEUfx8P8VeXuG/i4dlz6ws3z0gCgmpC+ g9YUcE97iKPFKXcjVC7xT8E= =MIjV -END PGP SIGNATURE-
Re: [Axis2] Release plan
On Mon, 2006-03-20 at 13:57 +0100, Franz Fehringer wrote: Will the TCP monitor be factored out (- ws-commons) in release 1.0? This is an excellent idea. However, can someone offer to do the work? Its not a huge amount but it does require refactoring the code to change Java package names etc.. Sanjiva.
Retrieving Context Path from web service implementation
How can I determine the context path (or full URL/URI) where used to invoke a particular web service? I would like to have the same web service deployed under two names: HACService and ONCService. Is it possible to get the context path from the request at the web service implementation level (ie, after the RPC Provider is done with it)? Thanks, Greg
Re: [Axis2] wss4j
Hi Rob, Yes the repository is just a directory with a certain structure as shown below: repo_dir | +- services/ | | | +- foo.aar | +- bar.aar | |- modules/ | | | +- a.mar | +- b.mar | |- conf/ | +-axis2.xml I addition to the above you can have optional 'lib' directories at each service, module and repo level holding the common jars to be used in each scope. Thanks, Ruchith On 3/20/06, Rob Henley [EMAIL PROTECTED] wrote: Hi Ruchith, thanks! I'll try a later version. Just to clarify, I was thinking a repository was just a directory which conformed to a specific structure, for instance with sub-directories called modules, lib etc. It sounds like I haven't understood this properly. Can you tell me where it is described? Many thanks Rob - Original Message - From: Ruchith Fernando [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Monday, March 20, 2006 12:53 PM Subject: Re: [Axis2] wss4j Hi Rob, java.lang.ClassNotFoundException: org.apache.ws.security.transform.STRTransform I can see that this class is in wss4j-SNAPSHOT.jar, which in turn is in my security.mar in the modules directory. Extracting the jar into the lib directory seems to solve the problem, but presumably that isn't the right thing to do? No, you should not have to do that. In your scenario only the security module should contain the wss4j-SNAPSHOT.jar in its 'lib' directory and you should not be required to add it to your classpath separately. This sounds like a module classloading problem Deepal what do you think? Also can you send the complete stack trace of java.lang.ClassNotFoundException: org.apache.ws.security.transform.STRTransform The client code to set the configurationContext seemed to be for a version other than 0.94. My attempt looks like this: ConfigurationContextFactory ccf = new ConfigurationContextFactory(); ConfigurationContext ctx = ccf.createConfigurationContextFromFileSystem(C:/axis2); _serviceClient = new org.apache.axis2.client.ServiceClient(ctx, _service); (Just to get things working, I dropped this straight into the PurchasingStub constructor generated by wsdl2java. C:/axis2 is where I unzipped axis. It contains axis2.xml and subdirectories lib, modules etc.) The client classpath includes all the jars in the lib directory, but I haven't set anything else specifically in the environment when the client runs. To create a configuration context you have to give the path to an axis2 _repository_ to the createConfigurationContextFromFileSystem() method. NOT the place where you extracted Axis2. There has been a considerable amount of changes from 0.94 and I'd strongly recommend you to try the latest SVN head or checkout ht e0.95 release which will be out in a few days. Thanks, Ruchith
Re: array serialization in 1.3
Please also provide the tyoe definition of common:BaseRequest.On 3/20/06, Marc Brette [EMAIL PROTECTED] wrote: Here it is. It is quite complex because there aredozens of operation and .xsd inclusion, so I just extracted the relevant data structures (I can providethe whole WSDL if needed).WSDL:[...]importnamespace=http://search.search.services.v1.wsapi.lexisnexis.com schemaLocation=Search.xsd/[...]message name=Search-SearchReqMsgpart element=search-search:Searchname=SearchRequest/ /messagemessage name=Search-SearchRespMsgpart element=search-search:SearchResponsename=SearchResponse//message[...]portType name=SearchSoapPort operation name=Searchinput message=tns:Search-SearchReqMsg/output message=tns:Search-SearchRespMsg//operation /portType[...]binding name=SearchSoapBindingtype=tns:SearchSoapPortsoap11:binding style=documenttransport= http://schemas.xmlsoap.org/soap/http/operation name=Searchsoap11:operation soapAction=/inputsoap11:body use=literal/ /inputoutputsoap11:body use=literal//output/operationoperation name=NarrowSearch soap11:operation soapAction=/inputsoap11:body use=literal//inputoutput soap11:body use=literal//output/operation/binding[...]Search.xsd:?xml version=1.0 encoding=UTF-8? schema xmlns=http://www.w3.org/2001/XMLSchematargetNamespace=http://search.search.services.v1.wsapi.lexisnexis.com xmlns:tns=http://search.search.services.v1.wsapi.lexisnexis.comxmlns:common= http://common.services.v1.wsapi.lexisnexis.comxmlns:result=http://result.common.services.v1.wsapi.lexisnexis.comxmlns:searchcommon= http://common.search.services.v1.wsapi.lexisnexis.comxmlns:security= http://security.common.services.v1.wsapi.lexisnexis.comelementFormDefault=qualifiedattributeFormDefault=unqualifiedversion=1.0import namespace=http://common.services.v1.wsapi.lexisnexis.comschemaLocation=Common.xsd/importnamespace= http://result.common.services.v1.wsapi.lexisnexis.comschemaLocation=Result.xsd/importnamespace= http://common.search.services.v1.wsapi.lexisnexis.comschemaLocation=SearchCommon.xsd/importnamespace= http://security.common.services.v1.wsapi.lexisnexis.comschemaLocation=Security.xsd/!-- Message elements --element name=Search type=tns:Search annotationdocumentationRepresents a LexisNexis search and retrieval.Many options areexposed to allow a user to customize thesearch request./documentation /annotation/elementelement name=SearchResponsetype=result:SearchResponseannotationdocumentationThe response from a search request is a set of search results,containing document identifiers along withdocuments in thespecified or default output format./documentation/annotation/element !-- Types --complexType name=SearchcomplexContentextension base=common:BaseRequestsequenceelement name=binarySecurityToken type=security:BinarySecurityTokenannotationdocumentationexamplef4348ad8876542bc93748c89fb98a7e/exampleSecurity token that must be provided on all non-authenticationrequests./documentation/annotation/elementelement name=sourceInformation type=searchcommon:SourceInformationChoiceannotationdocumentation Either a list of source identifiers ora single secured source identifier./documentation/annotation/elementelement name=query type=string annotationdocumentationexamplecats and dogs andhamsters/exampleQuery string for the search request, formatted in theappropriate syntax for the selectedsearch method./documentation/annotation/elementelement name=projectId type=common:ProjectId minOccurs=0annotationdocumentationexampleResearch Project 001/example Used for client or project identificationpurposes.Thisidentifier will be associated with eachsearch transactionand will be reported on your organizationapos;s invoice. /documentation/annotation/elementelement name=searchOptionstype=searchcommon:SearchOptions minOccurs=0 annotationdocumentationOptions pertaining to fine-tuning thesearch./documentation/annotation /elementelement name=retrievalOptionstype=result:RetrievalOptions minOccurs=0annotationdocumentation Options pertaining to the view, markup,and range of documents retrieved fromthe result set returned from the search./documentation/annotation /element/sequence/extension/complexContent/complexType/schemaSearchCommon.xsd:?xml version= 1.0 encoding=UTF-8?schema xmlns=http://www.w3.org/2001/XMLSchematargetNamespace= http://common.search.services.v1.wsapi.lexisnexis.comxmlns:tns=http://common.search.services.v1.wsapi.lexisnexis.com xmlns:result=http://result.common.services.v1.wsapi.lexisnexis.comxmlns:common= http://common.services.v1.wsapi.lexisnexis.comelementFormDefault=qualifiedattributeFormDefault=unqualifiedversion=1.0import namespace=http://result.common.services.v1.wsapi.lexisnexis.comschemaLocation=Result.xsd/import namespace=http://common.services.v1.wsapi.lexisnexis.comschemaLocation=Common.xsd/!-- Common search request type definitions -- complexType name=SourceInformationChoicesequenceelement name=sourceIdListtype=common:SourceIdList minOccurs=0annotation documentationA grouping of LexisNexis sources.Mutually
Re: Stateful Web Service
The WSRF specs provide a standard way of implementing/interacting with stateful Web services. I recommend having a look at: http://ws.apache.org/wsrf/- Jyoti On 3/20/06, Nayana Hegde [EMAIL PROTECTED] wrote: Hi, Is it possible to implement a stateful web service using Axis? If yes please do let me know the details. Thanks and Regards, Nayana -- Jyotishman PathakWWW: http://www.cs.iastate.edu/~jpathak
RE: [Axis0.94] Duplicated xmlns= added by StAXSOAPModelBuilder
Well it seems like parser is not namespace aware. Quick glance in the XMLInputFactory and saw isNamespaceAware attribute. Try that out Sajith From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gaël Pouzerate Sent: Monday, March 20, 2006 10:24 PM To: axis-user@ws.apache.org Subject: [Axis0.94] Duplicated xmlns= added by StAXSOAPModelBuilder Hi, I've got an InputStream containing a soap envelope. When I use StAXSOAPModelBuilder to create a SOAPEnvelope object, some extra strings (xmlns=) are added in the resulting envelope!!! What's the problem here? The code is pretty simple: // InputStream soapStream contains the envelope as a stream javax.xml.stream.XMLInputFactory xmlif = javax.xml.stream.XMLInputFactory.newInstance(); javax.xml.stream.XMLStreamReader xmlr = xmlif.createXMLStreamReader(soapStream); StAXSOAPModelBuilder builder = new StAXSOAPModelBuilder(xmlr,null); SOAPEnvelope newEnvelope = builder.getSOAPEnvelope (); My InputStream contains something like this: ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv= http://schemas.xmlsoap.org/soap/envelope/soapenv:Header/soapenv:Header soapenv:Body DmpPatientRequest xmlns=http://dmp/search/types access xmlns=Acces normal/access /DmpPatientRequest /soapenv:Body /soapenv:Envelope But in the resulting SOAPEnvelope I get: ... access xmlns= xmlns=Acces normal/access ... What is hapening here?
Re: differences between axis and axis2 (styles and lit vs enc)
thx. rpc/enc should also be avoided (ws-i). how can I configure the use of doc/lit - rpc/lit? Does somebody know if there's a way to create a service with axis which receives some sort of xml tree inside the java methods? Dominik -Ursprüngliche Nachricht- Von: axis-user@ws.apache.org Gesendet: 21.03.06 06:16:28 An: axis-user@ws.apache.org Betreff: Re: differences between axis and axis2 (styles and lit vs enc) doc/enc is not supported (and doesn't make any sense -- it's not a valid combination). wrapped = doc/lit using a specific convention. It isn't a separate style/use combination. Axis2 currently supports doc/lit and rpc/lit. Anne On 3/20/06, SOA Work [EMAIL PROTECTED] wrote: Hi, I'm looking for the differences between axis and axis2. At the moment I'm trying to find out which styles and encodings are supported. (with document-centric I mean the possibility to get the message as xml tree. in axis2 this is covered via RawXMLMessageReceiver and OMElement) axis: rpc/enc rpc/lit doc/enc doc/lit wrapped all supported no way to create a message-centric web service axis2: rpc/enc (- I read it should be supported) rpc/lit what about the others? easy message-centric services (RawXMLMessageReceiver) And how to I configure the style and the use (- encoded vs literal) thx Dominik __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 __ XXL-Speicher, PC-Virenschutz, Spartarife mehr: Nur im WEB.DE Club! Jetzt gratis testen! http://freemail.web.de/home/landingpad/?mc=021130
