Re: Problems building SVN version
Hello, I downgraded the linux-headers now from version 2.6.21 to version 2.6.17 and it compiles now. Maybe the developers could have a look at this problem since i (and maybe other users) would prefer the newer headers. Thanks again for you help! Regards, Roland On Friday 24 August 2007 09:26:42 Chintana Wilamuna wrote: On 8/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: It's a 32 bit processor and i'm using gcc 4.1.2. Since the file which seems to cause the problem is in /usr/include/linux i searched where these files come from. I found out that the include files in /usr/include/linux should be kernel specific files. It seems that on many linux systems this directory is a symlink to /usr/src/linux/include/linux. In Gentoo this is not so, don't know why. Maybe there is some problem with too old or too new kernel versions. I'm using a 2.6.19 kernel. Which kernel do you use? Hm.. I'm on 2.6.19 too. Linux header files come in another package, linux-headers. I'm guessing the problem lies in there. I have 2.6.17 of linux-headers installed. Since you're on a daily update schedule I think you have a newer version of linux-headers (2.6.21 probably). Could you please try downgrading that package and compiling again? Bye, -Chintana - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems building SVN version
On 8/27/07, Roland Landertshamer [EMAIL PROTECTED] wrote: I downgraded the linux-headers now from version 2.6.21 to version 2.6.17 and it compiles now. Maybe the developers could have a look at this problem since i (and maybe other users) would prefer the newer headers. Sure. Will look into it. Thanks again for you help! You're welcome. Bye, -Chintana -- http://trevet.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] Xml beans databinding with WSDL2java tool improvments.
hi,
I added a new option to wsdl2 java. (-Ewdc -- without databinding code)
When someone put this option with the Xmlbeans data binding then Axis2
generates an dummy schema set with only contain top xml elements
needed to generate other codegen classes.
Then users can generate the xmlbeans correct code (with resources) using the
scomp command comes with the xmlbeans distribution.
eg. scomp test.wsd -d temp -src temp -srconly to generate code for a temp
folder.
Here is the complete set of steps
1. generate the code with wsdl2java. give -d xmlbeans -Ewdc as arguments.
2. generate the code with scomp command -- eg. scomp test.wsd -d temp -src
temp -srconly
3. replace the xmlbeans generated code with the code generated with the
Axis2 .
After that either deploy service or access client in the normal way.
In addition to this.
now it uses the OMDataSource in serializing the xmlbeans generated code.
org.apache.axiom.om.OMDataSource omDataSource = new
org.apache.axiom.om.OMDataSource() {
public void
serialize(javax.xml.stream.XMLStreamWriterxmlStreamWriter)
throws javax.xml.stream.XMLStreamException {
org.apache.axiom.om.impl.MTOMXMLStreamWritermtomxmlStreamWriter =
(
org.apache.axiom.om.impl.MTOMXMLStreamWriter) xmlStreamWriter;
try {
param.save(mtomxmlStreamWriter.getOutputStream
());
mtomxmlStreamWriter.getOutputStream().flush();
} catch (java.io.IOException e) {
throw new
javax.xml.stream.XMLStreamException(Problem
with saving document, e);
}
}
public javax.xml.stream.XMLStreamReader getReader()
throws javax.xml.stream.XMLStreamException {
return param.newXMLStreamReader();
}
};
return new
org.apache.axiom.om.impl.llom.OMSourcedElementImpl(xmlReader.getName(),
org.apache.axiom.om.OMAbstractFactory.getOMFactory
(),
omDataSource);
}
As you can see this improvs the perfornamce and it serialize the xmlbeans
directly using xmlbeans.
Can people have problems with xmlbeans try out with -Ewdc with a nighly
build?
--
Amila Suriarachchi,
WSO2 Inc.
axis2 -- minimum jars required for client??
What are the minimum (must have) jars from axis2 (2.1.3) that are required in the classpath for a Java client program accessing wsdl generated by axis2? Do we need all the 60+ jar files in AXIS2_HOME/lib? The assumption here that the the client stubs are already generated (with wsdl2java) and packaged. - Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more.
Re: axis2-web dependency?
Having axis2 as a webapp name is good to demonstrate axis2, but typically, when a product is packaged, axis2 is under the hood, and need not be a webapp name. The customer accesses the application by its more appropriate name. Nevertheless, there was a typo in my web.xml, which resulted in the ?wsdl going haywire. Thanks Amila Suriarachchi [EMAIL PROTECTED] wrote: http://localhost:8804/xoraapps/services/TimeTrackService31?wsdl why you have rename the axis2 root name normally it should be http://localhost:8804/axis2/services/TimeTrackService31?wsdl can you try without root name and see. Amila. On 8/26/07, Shiv [EMAIL PROTECTED] wrote:I have the latest version of axis2 (2-1-3) running on resin 2.1.10. I am able to get to the HappyAxis page which is under the axis2 webapp. But when I try to access the wsdl of our custom webapp (xoraapp), I get the following error. Why does our custom app have a dependency on axis2-web/listSingleService.jsp. Did not get this error with 2-1-2. 500 Servlet Exception java.io.FileNotFoundException: /xoraapps/axis2-web/listSingleService.jsp at com.caucho.server.http.FilterChainPage.doFilter(FilterChainPage.java :143) at com.caucho.server.http.Invocation.service(Invocation.java:315) at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135) at com.caucho.server.http.QRequestDispatcher.include(QRequestDispatcher.java :362) at com.caucho.server.http.QRequestDispatcher.include(QRequestDispatcher.java:274) at org.apache.axis2.transport.http.AbstractAgent.renderView(AbstractAgent.java:120) at org.apache.axis2.transport.http.ListingAgent.processListService (ListingAgent.java:448) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:229) at javax.servlet.http.HttpServlet.service(HttpServlet.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java :103) at com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:96) at com.xora.apps.util.RequestLogger.doFilter(RequestLogger.java:257) at com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java :88) at com.caucho.server.http.Invocation.service(Invocation.java:315) at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135) at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java :246) at com.caucho.server.http.HttpRequest.handleConnection(HttpRequest.java:163) at com.caucho.server.TcpConnection.run(TcpConnection.java:139) at java.lang.Thread.run(Thread.java:534) Shiv [EMAIL PROTECTED] wrote: resin 2.1.10 Axis2 1.3 RC2 also has the same problem -- it seems to have dependency on the jsps of axis2-web. Deepal jayasinghe [EMAIL PROTECTED] wrote: Hi Shiv , What is the application server are you using ? Thanks Deepal I have the snapshot (nightly build) version as of 4th July. It used to work before (around 4th July); and I am not sure what changed in my env to cause this error. */Deepal jayasinghe /* wrote: Hi Shiv , What is the Axis2 version are you using , if you can please try with Axis2 1.3 RC2. Thanks Deepal We are trying to use axis2 in our application. The appserver is resin. When trying to show the wsdl in the url ( http://localhost:8804/xoraapps/services/TimeTrackService31?wsdl), it is looking for /xoraapps/axis2-web/listSingleService.jsp. Why would there be a dependency on axis2-web for a custom application? 500 Servlet Exception || java.io.FileNotFoundException: /xoraapps/axis2-web/listSingleService.jsp at com.caucho.server.http.FilterChainPage.doFilter(FilterChainPage.java:143) at com.caucho.server.http.Invocation.service(Invocation.java:315) at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java :135) at com.caucho.server.http.QRequestDispatcher.include(QRequestDispatcher.java:362) at com.caucho.server.http.QRequestDispatcher.include(QRequestDispatcher.java:274) at org.apache.axis2.transport.http.AbstractAgent.renderView(AbstractAgent.java:120) at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Got a little couch potato? Check out fun summer activities for kids. - Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. -- Amila Suriarachchi, WSO2 Inc. - Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos more.
Re: Axis client sending multiRef
Do I just have to remove the encodingStyle attribute to switch from encoded to literal? Or are there other modifications to perform? Anne Thomas Manes [EMAIL PROTECTED] 25/08/2007 21:44 Veuillez répondre à axis-user@ws.apache.org A axis-user@ws.apache.org cc Objet Re: Axis client sending multiRef This WSDL is rpc/encoded. You must convert it to rpc/literal. (better yet, your should convert it to document/literal.) Anne On 8/23/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: hello, I've been regenerating the Axis 1.2 code from the wsdl (which is rpc/literal style) and forced the sendMultiRef parameter to false. The client still sends SOAP request causing my WS to crash: soapenv:Body getServiceGeneral soapenv:encodingStyle= http://schemas.xmlsoap.org/soap/encoding/; arg0 xsi:type=ns1:SERVICE_GENERAL_REQUETE_DETAIL xmlns:ns1=http://www.almerys.com/schemas/requete; LOGICIEL EDITEUR=Axilog NOM=Axiam VERSION=1.2/ SERVICE CODE=02 VERSION=00.02.06/ FLUX xsi:type=xsd:base64BinaryPD[...]=/FLUX LISTES DATE_VALIDITE_BLACK_LISTE=2010-01-01 DATE_VALIDITE_WHITE_LISTE=2010-01-01/ /arg0 /getServiceGeneral /soapenv:Body The arg0 tag is the one that makes the WS crash, when I call theRequest.getSERVICE_GENERAL_REQUETE_DETAIL() as it does not find the correct tag. Here is the wsdl of the service: ?xml version=1.0 encoding=UTF-8 ? wsdl:definitions xmlns:reponse= http://www.almerys.com/schemas/reponse; xmlns:requete= http://www.almerys.com/schemas/requete; xmlns:soapenc= http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns= http://www.almerys.com/services/AlmerysWebService; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap= http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xs= http://www.w3.org/2001/XMLSchema; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; targetNamespace= http://www.almerys.com/services/AlmerysWebService; wsdl:import location=SG_00.01.05_REQ.xsd namespace= http://www.almerys.com/schemas/requete; / wsdl:import location=SG_00.01.05_REP.xsd namespace= http://www.almerys.com/schemas/reponse; / wsdl:message name=getServiceGeneralRequest wsdl:part name=SERVICE_GENERAL_REQUETE type=requete:SERVICE_GENERAL_REQUETE_DETAIL / /wsdl:message wsdl:message name=getServiceGeneralResponse wsdl:part name=SERVICE_GENERAL_REPONSE type=reponse:SERVICE_GENERAL_REPONSE_DETAIL / /wsdl:message wsdl:portType name=Interfacage wsdl:operation name=getServiceGeneral parameterOrder=SERVICE_GENERAL_REQUETE wsdl:input message=tns:getServiceGeneralRequest name=getServiceGeneralRequest / wsdl:output message= tns:getServiceGeneralResponse name=getServiceGeneralResponse / /wsdl:operation /wsdl:portType wsdl:binding name=WebServiceSoapBinding type=tns:Interfacage wsdlsoap:binding style=rpc transport= http://schemas.xmlsoap.org/soap/http; / wsdl:operation name=getServiceGeneral wsdlsoap:operation soapAction=getServiceGeneral / wsdl:input name=getServiceGeneralRequest wsdlsoap:body encodingStyle= http://schemas.xmlsoap.org/soap/encoding/; namespace= http://www.almerys.com/services/AlmerysWebService; use=literal / /wsdl:input wsdl:output name=getServiceGeneralResponse wsdlsoap:body encodingStyle= http://schemas.xmlsoap.org/soap/encoding/; namespace= http://www.almerys.com/services/AlmerysWebService; use=literal / /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=InterfacageService wsdl:port binding=tns:WebServiceSoapBinding name=AlmerysWebService wsdlsoap:address location= http://www.preprod.almerys.com/fsa/services/AlmerysWebService; / /wsdl:port /wsdl:service /wsdl:definitions Is there an error in my WSDL?? Another client, based on the same WSDL but using GSOAP is connecting well with the WS. Thanks in advance, Pierre
Re: axis2 -- minimum jars required for client??
This thread might help. http://mail-archives.apache.org/mod_mbox/ws-axis-user/200708.mbox/browser Thanks, Keith. On 8/27/07, Shiv [EMAIL PROTECTED] wrote: What are the minimum (must have) jars from axis2 (2.1.3) that are required in the classpath for a Java client program accessing wsdl generated by axis2? Do we need all the 60+ jar files in AXIS2_HOME/lib? The assumption here that the the client stubs are already generated (with wsdl2java) and packaged. -- Take the Internet to Go: Yahoo!Go puts the Internet in your pocket:http://us.rd.yahoo.com/evt=48253/*http://mobile.yahoo.com/go?refer=1GNXICmail, news, photos more. -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/
java2wsdl extended class support
Hello, Does anybody know if we can generate wsdl that includes the base class public operations for classes that are extended from a base class? ihsan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2-web dependency?
On 8/27/07, Shiv [EMAIL PROTECTED] wrote: Having axis2 as a webapp name is good to demonstrate axis2, but typically, when a product is packaged, axis2 is under the hood, and need not be a webapp name. The customer accesses the application by its more appropriate name. yes that is correct it should work. So does Axis2 work when you change the root name or not? If not please log a jira. thanks, Amila. Nevertheless, there was a typo in my web.xml, which resulted in the ?wsdl going haywire. Thanks *Amila Suriarachchi [EMAIL PROTECTED]* wrote: http://localhost:8804/xoraapps/services/TimeTrackService31?wsdl why you have rename the axis2 root name normally it should be http://localhost:8804/axis2/services/TimeTrackService31?wsdl can you try without root name and see. Amila. On 8/26/07, Shiv [EMAIL PROTECTED] wrote: I have the latest version of axis2 (2-1-3) running on resin 2.1.10. I am able to get to the HappyAxis page which is under the axis2 webapp. But when I try to access the wsdl of our custom webapp (xoraapp), I get the following error. Why does our custom app have a dependency on axis2-web/listSingleService.jsp. Did not get this error with 2-1-2. 500 Servlet Exception java.io.FileNotFoundException: /xoraapps/axis2-web/listSingleService.jsp at com.caucho.server.http.FilterChainPage.doFilter(FilterChainPage.java :143) at com.caucho.server.http.Invocation.service(Invocation.java:315) at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135) at com.caucho.server.http.QRequestDispatcher.include(QRequestDispatcher.java :362) at com.caucho.server.http.QRequestDispatcher.include(QRequestDispatcher.java:274) at org.apache.axis2.transport.http.AbstractAgent.renderView(AbstractAgent.java:120) at org.apache.axis2.transport.http.ListingAgent.processListService (ListingAgent.java:448) at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:229) at javax.servlet.http.HttpServlet.service(HttpServlet.java:126) at javax.servlet.http.HttpServlet.service(HttpServlet.java :103) at com.caucho.server.http.FilterChainServlet.doFilter(FilterChainServlet.java:96) at com.xora.apps.util.RequestLogger.doFilter(RequestLogger.java:257) at com.caucho.server.http.FilterChainFilter.doFilter(FilterChainFilter.java :88) at com.caucho.server.http.Invocation.service(Invocation.java:315) at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135) at com.caucho.server.http.HttpRequest.handleRequest(HttpRequest.java :246) at com.caucho.server.http.HttpRequest.handleConnection(HttpRequest.java:163) at com.caucho.server.TcpConnection.run(TcpConnection.java:139) at java.lang.Thread.run(Thread.java:534) *Shiv [EMAIL PROTECTED]* wrote: resin 2.1.10 Axis2 1.3 RC2 also has the same problem -- it seems to have dependency on the jsps of axis2-web. *Deepal jayasinghe [EMAIL PROTECTED]* wrote: Hi Shiv , What is the application server are you using ? Thanks Deepal I have the snapshot (nightly build) version as of 4th July. It used to work before (around 4th July); and I am not sure what changed in my env to cause this error. */Deepal jayasinghe /* wrote: Hi Shiv , What is the Axis2 version are you using , if you can please try with Axis2 1.3 RC2. Thanks Deepal We are trying to use axis2 in our application. The appserver is resin. When trying to show the wsdl in the url ( http://localhost:8804/xoraapps/services/TimeTrackService31?wsdl), it is looking for /xoraapps/axis2-web/listSingleService.jsp. Why would there be a dependency on axis2-web for a custom application? 500 Servlet Exception || java.io.FileNotFoundException: /xoraapps/axis2-web/listSingleService.jsp at com.caucho.server.http.FilterChainPage.doFilter(FilterChainPage.java :143) at com.caucho.server.http.Invocation.service(Invocation.java:315) at com.caucho.server.http.CacheInvocation.service(CacheInvocation.java:135) at com.caucho.server.http.QRequestDispatcher.include( QRequestDispatcher.java:362) at com.caucho.server.http.QRequestDispatcher.include( QRequestDispatcher.java:274) at org.apache.axis2.transport.http.AbstractAgent.renderView( AbstractAgent.java:120) at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Got a little couch potato? Check out fun summer activities for kids.http://us.rd.yahoo.com/evt=48248/*http://search.yahoo.com/search?fr=oni_on_mailp=summer+activities+for+kidscs=bz -- Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder
Re: Undeclared namespace prefix SOAP-ENV
Ensure you are using SOAP 1.1. !.2 is not supported as of yet.
Nadir K. Amra
Michael Sutter [EMAIL PROTECTED] wrote on 08/21/2007 09:39:15 AM:
Hello list,
I have a problem by accessing a AXISCPP service from an AXIS(2) Java
client. I have a very simple WSDL, having only one method adding two
numbers. I must access this service over a Java client, if it is
possible over a AXIS2 Java client.
The wsdl is generated from a Java Class with java org.apache.axis.
wsdl.Java2WSDL -lhttp://localhost:9090/axis/TestService; -uLITERAL
-yDOCUMENT -nauger org.fzk.auger.MathAdd
When I generate the client stubs and access the service I always get
an Exception:
org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxParsingException:
Undeclared namespace prefix SOAP-ENV
at [row,col {unknown-source}]: [2,19]
at org.apache.axis2.transport.TransportUtils.
createSOAPMessage(TransportUtils.java:81)
at org.apache.axis2.description.OutInAxisOperationClient.
send(OutInAxisOperation.java:356)
at org.apache.axis2.description.OutInAxisOperationClient.
execute(OutInAxisOperation.java:294)
at
org.fzk.auger.MathAddServiceStub.add(MathAddServiceStub.java:151)
at org.fzk.auger.Client.main(Client.java:14)
Does anybody know how I can solve the exception? Or it is not
possible to access a c++ service generated with -uLITERAL -yDOCUMENT
- where I think the problem is from.
You can find the WSDL below - but I dont't think that it is wrong.
Kind regards
Michael
?xml version=1.0 encoding=UTF-8?
wsdl:definitions targetNamespace=http://auger.fzk.org;
xmlns:apachesoap=
http://xml.apache.org/xml-soap; xmlns:impl=http://auger.fzk.org;
xmlns:intf=
http://auger.fzk.org; xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=
http://www.w3.org/2001/XMLSchema;
!--WSDL created by Apache Axis version: 1.4
Built on Apr 22, 2006
(06:55:48 PDT)--
wsdl:types
schema elementFormDefault=qualified
targetNamespace=http://auger.fzk.org
xmlns=http://www.w3.org/2001/XMLSchema;
element name=add
complexType
sequence
element name=a type=xsd:int/
element name=b type=xsd:int/
/sequence
/complexType
/element
element name=addResponse
complexType
sequence
element name=addReturn type=xsd:int/
/sequence
/complexType
/element
/schema
/wsdl:types
wsdl:message name=addResponse
wsdl:part element=impl:addResponse name=parameters/
/wsdl:message
wsdl:message name=addRequest
wsdl:part element=impl:add name=parameters/
/wsdl:message
wsdl:portType name=MathAdd
wsdl:operation name=add
wsdl:input message=impl:addRequest name=addRequest/
wsdl:output message=impl:addResponse name=addResponse/
/wsdl:operation
/wsdl:portType
wsdl:binding name=TestServiceSoapBinding type=impl:MathAdd
wsdlsoap:binding style=document transport=http://schemas.
xmlsoap.org/soap/http/
wsdl:operation name=add
wsdlsoap:operation soapAction=/
wsdl:input name=addRequest
wsdlsoap:body use=literal/
/wsdl:input
wsdl:output name=addResponse
wsdlsoap:body use=literal/
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:service name=MathAddService
wsdl:port binding=impl:TestServiceSoapBinding
name=TestService
wsdlsoap:address
location=http://localhost:9090/axis/TestService/
/wsdl:port
/wsdl:service
/wsdl:definitions
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
-
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]
Timeout
Hi all, I'm usign axis2 1.3 and I could see that one of the changes made was about timeout. Now, while debugging my service, I get timeouts because axis2 removes contexts but I was managing this timeouts myself so I would like to deactivate axis2 timeouts. Is this possible? I thought that maybe I could do it by setting timeout to 0 but it doesn't work. Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
Simple question about MTOM, Rampart and optimize parts
Hi all, I would like to know how does Rampart work with MTOM. I see that when using Rampart, MTOM elements are included as strings in the SOAP message instead of sending them outside the message as MIME parts, even if I don't do any operation with them (not signature, nor encryption), but these MIME parts appear empty in the HTTP message. Why is that? Does optimize parts something about that? I don't understand much about this parameter. If anybody could give me a hint about this, that would be great. Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!.
wsdl2c
Hi, What program is used to convert a wsdl to C classes? Thank you, Marc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Simple question about MTOM, Rampart and optimize parts
Please let me know if you come up with an answer. I am also using MTOM from an Axis2 client. (Axis2 1.1.1 and Rampart 1.1. I am sticking with these version because everything else works. I know Axis2 1.2 did not work with Rampart 1.1 so I stopped testing other combinations.) As soon as I call 'ServiceClient.engageModule(rampart)' Axis2 seems to ignore the statement 'Options.setProperty(Constants.Configuration.ENABLE_MTOM, Constants.VALUE_TRUE)' and puts the attachment as base64 encoded within the SOAP message. I have been avoiding stepping through the Axis2 and Rampart source code to debug. This would either help me identify a property I'm not setting, or I'd find that I have to recompile the Axis2/Rampart code, something that I would not like to do. Thanks in advance. Giao Nguyen --- Jorge Fernandez [EMAIL PROTECTED] wrote: Hi all, I would like to know how does Rampart work with MTOM. I see that when using Rampart, MTOM elements are included as strings in the SOAP message instead of sending them outside the message as MIME parts, even if I don't do any operation with them (not signature, nor encryption), but these MIME parts appear empty in the HTTP message. Why is that? Does optimize parts something about that? I don't understand much about this parameter. If anybody could give me a hint about this, that would be great. Thanks, Jorge Fernández - Sé un Mejor Amante del Cine ¿Quieres saber cómo? ¡Deja que otras personas te ayuden!. Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[axis2-1.1.1] Deriving originating URI from SOAP
Is it possible to derive the originating URI of a sender from a SOAP request message, even if the sender has not explicitly set any message elements with such information? Thanks, Alan J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2-1.1.1] Deriving originating URI from SOAP
This should retrieve the sender: MessageContext.getCurrentMessageContext().getProperty(REMOTE_ADDR).toString() Andrew Jones, Alan R wrote: Is it possible to derive the originating URI of a sender from a SOAP request message, even if the sender has not explicitly set any message elements with such information? Thanks, Alan J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Andrew Martin Computer Programmer Regenstrief Institute, Inc. 410 West 10th Street, Suite 2000 Indianapolis, IN 46202-3012 Phone: (317) 423-5542 Fax: (317) 423-5695 [EMAIL PROTECTED] Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose. If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 1.1 and Rampart 1.1.1
I am using Axis2 1.1 and Rampart 1.1.1 and whenever I send a message to my service, I still end up getting a NullPointerException with the following in the logs: Unknown top level PED found: org.apache.neethi.builders.xml.XmlPrimtiveAssertion Aug 27, 2007 6:27:26 PM org.apache.axis2.transport.http.AxisServlet doPost SEVERE: java.lang.NullPointerException Does anyone have any idea how I can fix this? thanks smime.p7s Description: S/MIME cryptographic signature
Re: axis2 -- minimum jars required for client??
keith chapman wrote: On 8/27/07, *Shiv* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: What are the minimum (must have) jars from axis2 (2.1.3) that are required in the classpath for a Java client program accessing wsdl generated by axis2? Do we need all the 60+ jar files in AXIS2_HOME/lib? The assumption here that the the client stubs are already generated (with wsdl2java) and packaged. This thread might help. http://mail-archives.apache.org/mod_mbox/ws-axis-user/200708.mbox/browser I couldn't find the specific thread in there that you say would help. The only one that seemed to match was http://tinyurl.com/2dql7h But that one doesn't seem to have much in the way of a complete answer. I have the same question, and another similar one, which is what is the minimum set of jar files needed to run WSDL2Java for an XMLBeans binding. Does anyone know how to find that list beyond just trial and error? Thanks, -- Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation
Hi Amila, I tried this with the nightly build jars from axis2-1.3-SNAPSHOT-bin.zip (adb.jar adb-codegen.jar) of Aug. 27 2007 09:33 and in this xsd:anyType is converted into OMElement, not java.lang.Object, but it worked with the nightly build jars from axis2-SNAPSHOT-bin.zip (adb.jar adb-codegen.jar) of Aug. 27 2007 07:44 Which version of the jars should I use? Thanks Raghu From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 21, 2007 10:54 PM To: axis-user@ws.apache.org Subject: Re: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation basically you are asking when is the Axis2 1.4. we have just release Axis2 1.3 so it would be from another 3 or 4 months time. Amila. On 8/22/07, Raghu Upadhyayula [EMAIL PROTECTED] wrote: Hi Amila, It worked with the nightly build jars (adb.jar adb-codegen.jar). When will this change be moved to the main release (I mean which Axis2 version)? Thanks Raghu From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: Monday, August 20, 2007 9:36 PM To: axis-user@ws.apache.org Subject: Re: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation On 8/17/07, Raghu Upadhyayula [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Amila, I'm currently using Axis2 1.3 version, is this bug fixed in that or do I need to get nightly build for the fix. it is only available in trunk. you can try this, get a nighly build and replace adb-codgen.jar and adb.jar with the nightly build jars. Then it should work. And what is the fix? If I define a parameter type as xsd:anyType in my WSDL, does WSDL2Java convert it as java.lang.Object in the generated sources yes, if you use nighly build jars. or does it convert to org.apache.axiom.om.OMElement? Thanks Raghu From: Amila Suriarachchi [mailto: [EMAIL PROTECTED] Sent: Thursday, August 16, 2007 9:36 PM To: axis-user@ws.apache.org Subject: Re: OMElement Vs java.lang.Object for (xsd:anyType) - Axis 1.3 Vs Axis 2 code generation this is a bug in Axis2. It has fixed in the trunk. please have a look at with a nightly build. On 8/11/07, Raghu Upadhyayula [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, In my webservices, I have a method which has a parameter defined as type=xsd:anyType in the WSDL. In Axis 1.3, when I did WSDL2Java for my WSDL that parameter got converted to java.lang.Object. But in Axis2 1.2, when I did WSDL2Java for the same WSDL, that parameter got converted to org.apache.axiom.om.OMElement. My question is, if I need to pass a Java Object to my webservice method, how do I convert it to OMElement and pass it to the method from the client code how do I convert OMElement back to java.lang.Object in my server code? Thanks Raghu -- Amila Suriarachchi, WSO2 Inc. -- Amila Suriarachchi, WSO2 Inc. -- Amila Suriarachchi, WSO2 Inc.
Axis2 newb
Hey folks, I'm wondering if someone can point me in the right direction. I've not really developed web services much other then the intro axis2 code generation/simple comms back and forth. Ok here's the task I have. I have to deal with a messaging protocol that looks like this: request-my web service ack-my web service response-my web service The request,ack, and response are standardized xml messages from a defined protocol that I have to work with. What I have working right now is the request and ack response (standard in/out messaging) via axis2 and standard HTTP. What I'm trying to figure out is how to design my response. I'm going to have a lot of inbound messages so I will need to make this a multithreaded app. I'm thinking of having a thread pool to handle the inbound messages (need to research this more) and send responses to the originating WS (messages contain the response address) as I process them. The response has be to be sent within 30 seconds, which should be ok as there it is simple processing/persistance. What I'm wondering is if there's a response transport solution via axis2 or should use a standard http sender object? Does my design sound alright or is there something built in to axis2 that will make my life easier? Thanks in advance for any feedback and please send me links to good articles and tutorials if you have them or find them. many thanks, Eric -- View this message in context: http://www.nabble.com/Axis2-newb-tf4339167.html#a12360295 Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] org.apache.axis2.util.Base64
Eclipse is telling me that this class is deprecated, is there a replacement? Eben - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis Web service and .NET compact framework client
Hi, I'm a newbie trying to create a web service using Apache Axis 2 version 1.3 I have created a web service which returns an OMElement. Now what is the equivalent data type in .NET compact framework for OMElement, so that I can parse the xml object? Also, is it possible for me to return value objects from my web service rather than a XML object? If so how is it done? One thing to note is my client will be a .NET client. Any help is appreciated. Thanks in advance, Raghavan.V. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
