stub._getServiceClient().getOptions().setTimeOutInMilliSeconds() doesn't work
Hi, I am using axis2 1.4.1 and having problems with the timeout setting. I try to set the timeout value to be 30s by: stub._getServiceClient().getOptions().setTimeOutInMilliSeconds(3); However, it doesn't work. Any method call will still return successfully even long after 30s has passed. Has anyone seen the same problem? Thanks, Chad
RE: stub._getServiceClient().getOptions().setTimeOutInMilliSeconds() doesn't work
Hi,
During an old project, i used a cached httpClient, and i think that httpClient
timeout overrided stub timeout (maybe i'm wrong ?), so i used :
Options optionsStub = this._stub._getServiceClient().getOptions();
MultiThreadedHttpConnectionManager conmgr = new
MultiThreadedHttpConnectionManager();
conmgr.getParams().setDefaultMaxConnectionsPerHost(
numberOfConnectionsKeepAlive );
if ( timeout != null )
{
//override timeouts ?
conmgr.getParams().setConnectionTimeout( timeout.intValue() );
conmgr.getParams().setSoTimeout( timeout.intValue() );
}
HttpClient client = new HttpClient( conmgr );
// Reuse the client
optionsStub.setProperty( HTTPConstants.REUSE_HTTP_CLIENT, true );
// Cache the client
optionsStub.setProperty(
org.apache.axis2.transport.http.HTTPConstants.CACHED_HTTP_CLIENT, client );
optionsStub.setTimeOutInMilliSeconds( timeout );
this._stub._getServiceClient().setOptions( optionsStub );
Yves-Marie
-Message d'origine-
De : Chad Chen [mailto:cc...@cse.ucsc.edu]
Envoyé : mercredi 20 mai 2009 09:37
À : axis-user@ws.apache.org
Objet : stub._getServiceClient().getOptions().setTimeOutInMilliSeconds()
doesn't work
Hi,
I am using axis2 1.4.1 and having problems with the timeout setting. I try to
set the timeout value to be 30s by:
stub._getServiceClient().getOptions().setTimeOutInMilliSeconds(3);
However, it doesn't work. Any method call will still return successfully even
long after 30s has passed.
Has anyone seen the same problem?
Thanks,
Chad
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is
intended only for the person to whom it is addressed. If you are not the
intended recipient, you are not authorized to
read, print, retain, copy, disseminate, distribute, or use this message or any
part thereof. If you receive this message
in error, please notify the sender immediately and delete all copies of this
message.
Web service monitoring tool
Hi, we're using axis/axis2 for some web services with grat satisfaction. Could someone suggest us a web service monitorig tool, especially for response time? Many thanks Best regards. -- Bartolomeo Nicolotti SIAP s.r.l. www.siapcn.it v.S.Albano 13 12049 Trinità(CN) Italy ph:+39 0172 652553 centralino: +39 0172 652511 fax: +39 0172 652519
[AXIS2] Handling XML Document in parameters
Hi all,
I've created a web service which takes a XML document in parameter (more
precisely an OMElement).
This web service has 2 wsdl (message and document type) linked to a XSD.
I've generated stubs for each wsdl and they look fine to me
Then, I needed to test this web service from:
1. a Internet explorer by passing the xml string to the web service
like this:
http://localhost:8080/app/services/service/read?xml=aa/aa
2. a the message stub from a test program
3. a the document stub from a test program
So... :
1. I call the web service from an Internet explorer
2. I wrote a message test program:
...
org.apache.axis.message.SOAPBodyElement soapObjReturn =
(org.apache.axis.message.SOAPBodyElement)messageService.read(xml);
Where xml is a org.w3c.dom.Document
3. I wrote a Document test program in which I've just used the
generated type to call the service
My web service method looks like this :
public OMElement read(OMElement xml){
...
Conversion of OMElement to org.w3c.dom.Document
...
}
So far so good but I've noticed that depending on the way I'm
calling the stub, the OMElement in the web service method is populated
differently
For instance, to get the XML string in order to convert it into a
org.w3c.dom.Document, I had to developp some ugly code
if (!xml.getText().equals()){
xmlToParse=xml.getText();
}else if (!xml.getFirstElement().getText().equals()){
xmlToParse=xml.getFirstElement().getText();
}else if (!xml.toString().equals()){
xmlToParse=xml.toString();
}
It works fine but I think I'm missing something really important on how
to handle org.w3c.dom.Document with OMElement
Does someone have best practices on OMElement and w3c document?
Thanks
Here an extract of the message WSDL (type part)
wsdl:types
schema targetNamespace=http://.com;
xmlns=http://www.w3.org/2001/XMLSchema;
element name=read type=xsd:anyType /
/schema
schema
targetNamespace=http://.com/ws/stub/XXX/message/literal;
xmlns=http://www.w3.org/2001/XMLSchema;
element name=readReturn type=xsd:anyType /
/schema
/wsdl:types
wsdl:message name=readRequest
wsdl:part name=part element=tns1:read/
/wsdl:message
wsdl:message name=readResponse
wsdl:part element=impl:readReturn name=readReturn /
/wsdl:message
wsdl:portType name=XXXPortType
wsdl:operation name=read
wsdl:input message=axis2:readRequest wsaw:Action=urn:read/
wsdl:output message=axis2:readResponse
wsaw:Action=urn:readResponse/
/wsdl:operation
/wsdl:portType
Here the extract for WSDL document wsdl:types part.
wsdl:types
schema xmlns=http://www.w3.org/2001/XMLSchema;
xmlns:xsdXXX=http://.com/schema;
xsd:import namespace=http://.com/schema/;
schemaLocation=X.xsd/
/schema
/wsdl:types
wsdl:message name=readRequest
wsdl:part element=xsdXXX:XXX name=part /
/wsdl:message
wsdl:message name=readResponse
wsdl:part element=xsdXXX:XXX name=readReturn /
/wsdl:message
wsdl:portType name=XXPortType
wsdl:operation name=read
wsdl:input message=axis2:readRequest wsaw:Action=urn:read/
wsdl:output message=axis2:readResponse
wsaw:Action=urn:readResponse/
/wsdl:operation
/wsdl:portType
---
Un geste responsable aujourd hui pour preserver demain.
N imprimez ce message que si necessaire.
Please, consider the environment before printing this email.
begin:vcard
fn:Laurent EVEN
n:EVEN;Laurent
org;quoted-printable:SAB Ing=C3=A9nierie Informatique;Service RIC - Bureau 203
adr;dom:Rue Henri Becquerel;;CP27 - P.I.B.S.;VANNES;;56038
email;internet:laurent-e...@sab2i.com
title;quoted-printable:Ing=C3=A9nieur d'=C3=A9tudes
tel;work:+33 (0)2 97 01 59 59
tel;fax:+33 (0)2 97 01 59 50
url:http://www.sab-tm.com
version:2.1
end:vcard
Re: [AXIS2] soap:address location under a Frontend
p.s. I'm using Axis2 1.2 manub wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService − wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port − wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port − wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23631967.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: [AXIS2] soap:address location under a Frontend
We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: [AXIS2] soap:address location under a Frontend
Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23632085.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: [AXIS2] soap:address location under a Frontend
I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23632085.html Sent from the Axis - User mailing list archive at Nabble.com. winmail.dat
RE: [AXIS2] soap:address location under a Frontend
Maybe I will try it. Thanks. Another question: if I would manually configure the WSDL to use the front-end address (so saving the WSDL and using that modified one instead of automatically generate it), how can I do this? I hope to not being too much OT :) Thanks (I started using Axis2 only some days ago) Neil Youngman wrote: I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23632085.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23633294.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: [AXIS2] soap:address location under a Frontend
There's a suggestion at http://archives.devshed.com/forums/showpost.php?p=6965056postcount=6 but I couldn't get it to work. Neil Youngman -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 12:02 To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Maybe I will try it. Thanks. Another question: if I would manually configure the WSDL to use the front-end address (so saving the WSDL and using that modified one instead of automatically generate it), how can I do this? I hope to not being too much OT :) Thanks (I started using Axis2 only some days ago) Neil Youngman wrote: I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23632085.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23633294.html Sent from the Axis - User mailing list archive at Nabble.com.
portage from Axis-1.3 over to axis2-1.4.1
Hello I'm searching to port a set of web services fonctionning together writen with java language and based on Tomcat5.5.9 and Axis-1.3 over to axis2-1.4.1 and Tomcat6.0.18 these WS turn as well, however, my problem is how could us convert all of the core of web services code and implements them over Axis 2. Especially, both of them (Axis1 and Axis2) have been developed on different architectures and generate also diffrents stub files. on the other hand, my big problem is how to change handler's code since, it has totally diffrent method than these which are used in Axis1 and it's also integrated into an archive module file also, in regards to the link that you might bring to me, it doesn't support the portage from axis1 over to axis2, but it just state the big diffrences which exist between the tow implementation of Axis and make the first one migrate to the second. please help, i'm in a huge issue
RE: [AXIS2] soap:address location under a Frontend
Having some troubles too this way. I hope to be able to patch the jar myself :) Neil Youngman wrote: There's a suggestion at http://archives.devshed.com/forums/showpost.php?p=6965056postcount=6 but I couldn't get it to work. Neil Youngman -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 12:02 To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Maybe I will try it. Thanks. Another question: if I would manually configure the WSDL to use the front-end address (so saving the WSDL and using that modified one instead of automatically generate it), how can I do this? I hope to not being too much OT :) Thanks (I started using Axis2 only some days ago) Neil Youngman wrote: I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/parameter but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23632085.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23633294.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23635646.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: [AXIS2] soap:address location under a Frontend
Hi Manub, You can change the hostname in the soap:address location in your wsdl by specifying the hostname parameter in axis2.xml. Let me know if this is sufficient for you, if not there is also a way to change the hostname parameter programmatically. Thanks Raghu -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wednesday, May 20, 2009 8:40 AM To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Having some troubles too this way. I hope to be able to patch the jar myself :) Neil Youngman wrote: There's a suggestion at http://archives.devshed.com/forums/showpost.php?p=6965056postcount=6 but I couldn't get it to work. Neil Youngman -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 12:02 To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Maybe I will try it. Thanks. Another question: if I would manually configure the WSDL to use the front-end address (so saving the WSDL and using that modified one instead of automatically generate it), how can I do this? I hope to not being too much OT :) Thanks (I started using Axis2 only some days ago) Neil Youngman wrote: I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/paramet er but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23632085.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23633294.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23635646.html Sent from the Axis - User mailing list archive at Nabble.com.
RE: [AXIS2] soap:address location under a Frontend
I tried, before parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/paramet er, to insert a parameter like parameter name=hostname locked=truehttps://myFrontend:myPort//parameter but it still doesn't work. Can you suggest me something? Searching into google I know you addressed same problem as mine, some time ago. Thanks. Raghu Upadhyayula wrote: Hi Manub, You can change the hostname in the soap:address location in your wsdl by specifying the hostname parameter in axis2.xml. Let me know if this is sufficient for you, if not there is also a way to change the hostname parameter programmatically. Thanks Raghu -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wednesday, May 20, 2009 8:40 AM To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Having some troubles too this way. I hope to be able to patch the jar myself :) Neil Youngman wrote: There's a suggestion at http://archives.devshed.com/forums/showpost.php?p=6965056postcount=6 but I couldn't get it to work. Neil Youngman -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 12:02 To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Maybe I will try it. Thanks. Another question: if I would manually configure the WSDL to use the front-end address (so saving the WSDL and using that modified one instead of automatically generate it), how can I do this? I hope to not being too much OT :) Thanks (I started using Axis2 only some days ago) Neil Youngman wrote: I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/paramet er but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23631957.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23632085.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23633294.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-t p23631957p23635646.html Sent from the Axis - User mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/-AXIS2--soap%3Aaddress-location-under-a-Frontend-tp23631957p23635988.html Sent from the Axis - User mailing list archive at Nabble.com.
Re: [AXIS2] soap:address location under a Frontend
While working on AXIS2-3843, I had a closer look at the code and this is what should work and what doesn't work: - httpFrontendHostUrl is not supported, neither by the servlet based HTTP transport, nor by SimpleHTTPServer. It is only used by the JSP pages of the admin console. - hostname, when specified at the global level in axis2.xml should allow to specify the hostname part. This should work with both transports, but it is not sufficient in this case (because http needs to be substituted by https). - hostname, when specified as a parameter of the SimpleHTTPServer transport receiver, allows to specify the URL. This is not supported by the servlet based transport. I think that we should modify both transports to support httpFrontendHostUrl. The hostname parameter as described in the 2nd point should remain because it's scope is not limited to the HTTP transports. The question is what to do with the hostname parameter in the 3rd option. I think that we should eliminate this one (in favor of httpFrontendHostUrl) because it is very misleading, both because of its name (it's not a hostname, but a URL) and because of the existence of another hostname parameter at the global level. Any thoughts? Andreas On Wed, May 20, 2009 at 15:56, manub e.bla...@reply.it wrote: I tried, before parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/paramet er, to insert a parameter like parameter name=hostname locked=truehttps://myFrontend:myPort//parameter but it still doesn't work. Can you suggest me something? Searching into google I know you addressed same problem as mine, some time ago. Thanks. Raghu Upadhyayula wrote: Hi Manub, You can change the hostname in the soap:address location in your wsdl by specifying the hostname parameter in axis2.xml. Let me know if this is sufficient for you, if not there is also a way to change the hostname parameter programmatically. Thanks Raghu -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wednesday, May 20, 2009 8:40 AM To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Having some troubles too this way. I hope to be able to patch the jar myself :) Neil Youngman wrote: There's a suggestion at http://archives.devshed.com/forums/showpost.php?p=6965056postcount=6 but I couldn't get it to work. Neil Youngman -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 12:02 To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Maybe I will try it. Thanks. Another question: if I would manually configure the WSDL to use the front-end address (so saving the WSDL and using that modified one instead of automatically generate it), how can I do this? I hope to not being too much OT :) Thanks (I started using Axis2 only some days ago) Neil Youngman wrote: I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/paramet er but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP? This way, clients using this WSDL cannot connect to the webservice as they've got the internal IP address and not the one they should use. Another thing: why the protocol is http and not https? I'm not so experienced in Axis2. Thanks -- View this message in context:
RE: [AXIS2] soap:address location under a Frontend
In my case I just changed it like this parameter name=hostname locked=truemyFrontEnd/parameter and it worked. Instead of myFrontEnd if I give the value as http://myFrontEnd then that whole string is appearing as it is in the soap:address location and it is showing the soap:address location as http://http://myFrontEnd which is wrong, so I've changed it to just have the hostname. -Raghu -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Wednesday, May 20, 2009 9:12 AM To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend While working on AXIS2-3843, I had a closer look at the code and this is what should work and what doesn't work: - httpFrontendHostUrl is not supported, neither by the servlet based HTTP transport, nor by SimpleHTTPServer. It is only used by the JSP pages of the admin console. - hostname, when specified at the global level in axis2.xml should allow to specify the hostname part. This should work with both transports, but it is not sufficient in this case (because http needs to be substituted by https). - hostname, when specified as a parameter of the SimpleHTTPServer transport receiver, allows to specify the URL. This is not supported by the servlet based transport. I think that we should modify both transports to support httpFrontendHostUrl. The hostname parameter as described in the 2nd point should remain because it's scope is not limited to the HTTP transports. The question is what to do with the hostname parameter in the 3rd option. I think that we should eliminate this one (in favor of httpFrontendHostUrl) because it is very misleading, both because of its name (it's not a hostname, but a URL) and because of the existence of another hostname parameter at the global level. Any thoughts? Andreas On Wed, May 20, 2009 at 15:56, manub e.bla...@reply.it wrote: I tried, before parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/paramet er, to insert a parameter like parameter name=hostname locked=truehttps://myFrontend:myPort//parameter but it still doesn't work. Can you suggest me something? Searching into google I know you addressed same problem as mine, some time ago. Thanks. Raghu Upadhyayula wrote: Hi Manub, You can change the hostname in the soap:address location in your wsdl by specifying the hostname parameter in axis2.xml. Let me know if this is sufficient for you, if not there is also a way to change the hostname parameter programmatically. Thanks Raghu -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wednesday, May 20, 2009 8:40 AM To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Having some troubles too this way. I hope to be able to patch the jar myself :) Neil Youngman wrote: There's a suggestion at http://archives.devshed.com/forums/showpost.php?p=6965056postcount=6 but I couldn't get it to work. Neil Youngman -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 12:02 To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Maybe I will try it. Thanks. Another question: if I would manually configure the WSDL to use the front-end address (so saving the WSDL and using that modified one instead of automatically generate it), how can I do this? I hope to not being too much OT :) Thanks (I started using Axis2 only some days ago) Neil Youngman wrote: I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/paramet er but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address
RE: [AXIS2] soap:address location under a Frontend
I agree with Andreas in principle, but I don't know if anyone out there has a specific use case for the 3rd option? Neil Youngman -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com] Sent: Wed 20-May-09 15:11 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend While working on AXIS2-3843, I had a closer look at the code and this is what should work and what doesn't work: - httpFrontendHostUrl is not supported, neither by the servlet based HTTP transport, nor by SimpleHTTPServer. It is only used by the JSP pages of the admin console. - hostname, when specified at the global level in axis2.xml should allow to specify the hostname part. This should work with both transports, but it is not sufficient in this case (because http needs to be substituted by https). - hostname, when specified as a parameter of the SimpleHTTPServer transport receiver, allows to specify the URL. This is not supported by the servlet based transport. I think that we should modify both transports to support httpFrontendHostUrl. The hostname parameter as described in the 2nd point should remain because it's scope is not limited to the HTTP transports. The question is what to do with the hostname parameter in the 3rd option. I think that we should eliminate this one (in favor of httpFrontendHostUrl) because it is very misleading, both because of its name (it's not a hostname, but a URL) and because of the existence of another hostname parameter at the global level. Any thoughts? Andreas On Wed, May 20, 2009 at 15:56, manub e.bla...@reply.it wrote: I tried, before parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/paramet er, to insert a parameter like parameter name=hostname locked=truehttps://myFrontend:myPort//parameter but it still doesn't work. Can you suggest me something? Searching into google I know you addressed same problem as mine, some time ago. Thanks. Raghu Upadhyayula wrote: Hi Manub, You can change the hostname in the soap:address location in your wsdl by specifying the hostname parameter in axis2.xml. Let me know if this is sufficient for you, if not there is also a way to change the hostname parameter programmatically. Thanks Raghu -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wednesday, May 20, 2009 8:40 AM To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Having some troubles too this way. I hope to be able to patch the jar myself :) Neil Youngman wrote: There's a suggestion at http://archives.devshed.com/forums/showpost.php?p=6965056postcount=6 but I couldn't get it to work. Neil Youngman -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 12:02 To: axis-user@ws.apache.org Subject: RE: [AXIS2] soap:address location under a Frontend Maybe I will try it. Thanks. Another question: if I would manually configure the WSDL to use the front-end address (so saving the WSDL and using that modified one instead of automatically generate it), how can I do this? I hope to not being too much OT :) Thanks (I started using Axis2 only some days ago) Neil Youngman wrote: I went through this quite recently. Nobody was able to give me a solution, so I posted a suggested patch at https://issues.apache.org/jira/browse/AXIS2-3843. Are you comfortable patching the code yourself? Neil -Original Message- From: manub [mailto:e.bla...@reply.it] Sent: Wed 20-May-09 10:35 To: axis-user@ws.apache.org Subject: Re: [AXIS2] soap:address location under a Frontend Thank you Andreas. I saw this issue in Axis2 1.4, but I guess if with older versions this will work (I'm using 1.2). No other ways to get it to work, even manually tweaking something? Thank you. Andreas Veithen-2 wrote: We are working on this. See AXIS2-3843. Andreas On Wed, May 20, 2009 at 11:26, manub e.bla...@reply.it wrote: Hi, I need to expose some webservices via a front-end (using HTTPS). Webservices are pyhsically located on a machine with an internal IP address. I'm autogenerating WSDL. I tried to set parameter name=httpFrontendHostUrlhttps://myFrontend:myPort/myServices/paramet er but in the autogenerated WSDL, still got wsdl:service name=myService - wsdl:port name=myServiceSOAP11port_http binding=axis2:myServiceSOAP11Binding soap:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceSOAP12port_http binding=axis2:myServiceSOAP12Binding soap12:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port - wsdl:port name=myServiceHttpport binding=axis2:myServiceHttpBinding http:address location=http://myInternalIp:myPort/myServices/services/myService/ /wsdl:port /wsdl:service Why isn't the internal IP on the WSDL replaced with the frontend IP?
Problem with MTOM
Hi all.
I've a simlpe pojo class:
public class MyClass
{
public DataHandler getFile()
{
return new DataHandler(new FileDataSource(new File(/tmp/myfile)));
}
}
I've published that pojo as a WebService.
The problem is that, on the client side, the file is always truncated at
12123 bytes.
How can I solve this issue?
Thanks,
Massimiliano
Re: [AXIS2] Handling XML Document in parameters
Hi Laurent,
In performance wise , creating a org.w3c.dom.Document inside the
service method is not much good thing to do. Axiom also full featured
light-weight object model for XML , so i wonder why you want to
convert your incoming message from Axiom to W3C DOM .
BTW if you relay want to do this conversion you can try for DOOM , it
is a OM compatible W3C DOM implementation available with Axiom.
performance wise that is a good option , please refer [1] .
[1] - http://wso2.org/library/2506
Thanks ,
2009/5/20 Laurent Even laurent-e...@sab2i.com:
Hi all,
I've created a web service which takes a XML document in parameter (more
precisely an OMElement).
This web service has 2 wsdl (message and document type) linked to a XSD.
I've generated stubs for each wsdl and they look fine to me
Then, I needed to test this web service from:
a Internet explorer by passing the xml string to the web service like this:
http://localhost:8080/app/services/service/read?xml=aa/aa
a the message stub from a test program
a the document stub from a test program
So... :
I call the web service from an Internet explorer
I wrote a message test program:
...
org.apache.axis.message.SOAPBodyElement soapObjReturn =
(org.apache.axis.message.SOAPBodyElement)messageService.read(xml);
Where xml is a org.w3c.dom.Document
I wrote a Document test program in which I've just used the generated type
to call the service
My web service method looks like this :
public OMElement read(OMElement xml){
...
Conversion of OMElement to org.w3c.dom.Document
...
}
So far so good but I've noticed that depending on the way I'm
calling the stub, the OMElement in the web service method is populated
differently
For instance, to get the XML string in order to convert it into a
org.w3c.dom.Document, I had to developp some ugly code
if (!xml.getText().equals()){
xmlToParse=xml.getText();
}else if (!xml.getFirstElement().getText().equals()){
xmlToParse=xml.getFirstElement().getText();
}else if (!xml.toString().equals()){
xmlToParse=xml.toString();
}
It works fine but I think I'm missing something really important on how to
handle org.w3c.dom.Document with OMElement
Does someone have best practices on OMElement and w3c document?
Thanks
Here an extract of the message WSDL (type part)
wsdl:types
schema targetNamespace=http://.com;
xmlns=http://www.w3.org/2001/XMLSchema;
element name=read type=xsd:anyType /
/schema
schema
targetNamespace=http://.com/ws/stub/XXX/message/literal;
xmlns=http://www.w3.org/2001/XMLSchema;
element name=readReturn type=xsd:anyType /
/schema
/wsdl:types
wsdl:message name=readRequest
wsdl:part name=part element=tns1:read/
/wsdl:message
wsdl:message name=readResponse
wsdl:part element=impl:readReturn name=readReturn /
/wsdl:message
wsdl:portType name=XXXPortType
wsdl:operation name=read
wsdl:input message=axis2:readRequest wsaw:Action=urn:read/
wsdl:output message=axis2:readResponse
wsaw:Action=urn:readResponse/
/wsdl:operation
/wsdl:portType
Here the extract for WSDL document wsdl:types part.
wsdl:types
schema xmlns=http://www.w3.org/2001/XMLSchema;
xmlns:xsdXXX=http://.com/schema;
xsd:import namespace=http://.com/schema/;
schemaLocation=X.xsd/
/schema
/wsdl:types
wsdl:message name=readRequest
wsdl:part element=xsdXXX:XXX name=part /
/wsdl:message
wsdl:message name=readResponse
wsdl:part element=xsdXXX:XXX name=readReturn /
/wsdl:message
wsdl:portType name=XXPortType
wsdl:operation name=read
wsdl:input message=axis2:readRequest wsaw:Action=urn:read/
wsdl:output message=axis2:readResponse
wsaw:Action=urn:readResponse/
/wsdl:operation
/wsdl:portType
---
Un geste responsable aujourd hui pour preserver demain.
N'imprimez ce message que si necessaire.
Please, consider the environment before printing this email.
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://sagaras.awardspace.com/
Re: Access to message context in Password Callback Handler
Hi Sanjay, I have seen lot of post about this requirement, sometimes ago i also faced the same issue. AFAIK still there is no proper solution for this. cant you use following approach for your requirement..? 1. In callback handler save user profile into a database table after successful authentication . ( or persist using any other approach.) 2. In the service method retrieve above user profile from database to access required details. ( I know this is little ugly :) but possible solution) Thanks , On Wed, May 20, 2009 at 9:50 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: Hi Guys, Are there any solution to my problem. This seems like a failry common requirement. I would really appreciate any help or suggestion. Thanks Sanjay From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Friday, May 08, 2009 7:50 AM To: axis-user@ws.apache.org Subject: RE: Access to message context in Password Callback Handler Hi, Can anybody give me some pointers on this issue. Sanjay From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Tuesday, April 21, 2009 8:55 AM To: axis-user@ws.apache.org Subject: Access to message context in Password Callback Handler Hi, I have seen lots on discussion on having access to message context in password callback handler in axis2 but no clear solution. I need to store some user profile information after successful authentication in callback handler so that I can access them in my services(POJO). One option would have been to store them in message context and access them in my service but message context is not available calback hander. I would really appreciate any suggesions. Thanks Sanjay -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://sagaras.awardspace.com/
RE: Problem with MTOM
I had the exact same issue few weeks back and martin gainty helped me. I
haven't tried his solution yet. I have been so busy with other things. See the
thread Sending binary data(not using MTOM) using DataHandler.
Thanks
Sanjay
-Original Message-
From: Andreas Veithen [mailto:andreas.veit...@gmail.com]
Sent: Wednesday, May 20, 2009 8:46 AM
To: axis-user@ws.apache.org
Subject: Re: Problem with MTOM
Massimiliano,
Can you check whether replacing the Axiom JARs with version
1.2.9-SNAPSHOT fixes this issue? You can download them from [1]. If
that doesn't help, can you try to use tcpmon or Wireshark to determine
whether the content is truncated on the server or client side?
Andreas
[1]
http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/commons/axiom/
On Wed, May 20, 2009 at 17:25, Massimiliano Ziccardi
massimiliano.zicca...@gmail.com wrote:
Which version of Axis2
I'm using AXIS2 1.4.1.
and Axiom do you use?
All the jars I use are from the AXIS2 1.4.1 package.
Is the client also Axis2 based?
Both client and server are AXIS2 1.4.1
Thank you very much for you prompt help!
Massimiliano
On Wed, May 20, 2009 at 5:22 PM, Andreas Veithen andreas.veit...@gmail.com
wrote:
Massimiliano,
Which version of Axis2 and Axiom do you use?
Is the client also Axis2 based?
Andreas
On Wed, May 20, 2009 at 17:17, Massimiliano Ziccardi
massimiliano.zicca...@gmail.com wrote:
Hi all.
I've a simlpe pojo class:
public class MyClass
{
public DataHandler getFile()
{
return new DataHandler(new FileDataSource(new
File(/tmp/myfile)));
}
}
I've published that pojo as a WebService.
The problem is that, on the client side, the file is always truncated at
12123 bytes.
How can I solve this issue?
Thanks,
Massimiliano
Re: Problem with MTOM
Which version of Axis2
I'm using AXIS2 1.4.1.
and Axiom do you use?
All the jars I use are from the AXIS2 1.4.1 package.
Is the client also Axis2 based?
Both client and server are AXIS2 1.4.1
Thank you very much for you prompt help!
Massimiliano
On Wed, May 20, 2009 at 5:22 PM, Andreas Veithen
andreas.veit...@gmail.comwrote:
Massimiliano,
Which version of Axis2 and Axiom do you use?
Is the client also Axis2 based?
Andreas
On Wed, May 20, 2009 at 17:17, Massimiliano Ziccardi
massimiliano.zicca...@gmail.com wrote:
Hi all.
I've a simlpe pojo class:
public class MyClass
{
public DataHandler getFile()
{
return new DataHandler(new FileDataSource(new
File(/tmp/myfile)));
}
}
I've published that pojo as a WebService.
The problem is that, on the client side, the file is always truncated at
12123 bytes.
How can I solve this issue?
Thanks,
Massimiliano
Re: Problem with MTOM
Massimiliano,
Which version of Axis2 and Axiom do you use?
Is the client also Axis2 based?
Andreas
On Wed, May 20, 2009 at 17:17, Massimiliano Ziccardi
massimiliano.zicca...@gmail.com wrote:
Hi all.
I've a simlpe pojo class:
public class MyClass
{
public DataHandler getFile()
{
return new DataHandler(new FileDataSource(new File(/tmp/myfile)));
}
}
I've published that pojo as a WebService.
The problem is that, on the client side, the file is always truncated at
12123 bytes.
How can I solve this issue?
Thanks,
Massimiliano
Help Required for SOAP/JMS
Hi, Need help with SOAP/JMS implementation with AXIS2. My scenario is as below I just wanted to ensure I am putting right information in my documents before confirming preferred framework for problem in hand. The component I am developing need to provide access to non tibco client to the services deployed on Tibco ESB. Reference Architecture of the client mandates that all service acess should be through SOAP/JMS and only presentation services should use SOAP/HTTP. Hence I think I will be using just a Axis2 client to send messages using SOAP/JMS transport as below. 1) WSDL will be provided for the service that is deployed on ESB 2) Generate AXIS2 client to use this WSDL and create stubs. 3) I will expose a custom java interface for all non tibco client to access any service on the ESB. 4) This custom java interface will delegate the call to generated axis2 client to send request using transport SOAP/JMS. 5) I am not sure of Axis2's SOAP/JMS implementation if it is synchronous or asynchronous or both (configurable)? I would think it should be transperant to client hence synchronous. 6) If it is asynchronous, do I need to develop a listener (MDB) in my application to receive response or again AXIS2 supports through some sort of JMSReceiver and I just configure for that particular service? 7) With respect to other requirements of security, encryption, message signing etc. I am assuming filter chain and modules will do the trick? Am I correct to assume this. Que: 1) Do I need to do any configuration for queues or topic to be used? or this is taken care by the WSDL and generated stubs. 2) Is Axis2's SOAP/JMS implementation synchronous or asynchronous? 3) If Asynchronous do I have to develop custom components (MDB) to receive response. 4) Other requirements like security, encryption, message signing etc. will be possible to implement using modules and filter chain. Any help is appreciated. If you can point to similar implementation (other JMS provider) it will be really helpful. Sachin
Re: Problem with MTOM
Massimiliano,
Can you check whether replacing the Axiom JARs with version
1.2.9-SNAPSHOT fixes this issue? You can download them from [1]. If
that doesn't help, can you try to use tcpmon or Wireshark to determine
whether the content is truncated on the server or client side?
Andreas
[1]
http://people.apache.org/repo/m2-snapshot-repository/org/apache/ws/commons/axiom/
On Wed, May 20, 2009 at 17:25, Massimiliano Ziccardi
massimiliano.zicca...@gmail.com wrote:
Which version of Axis2
I'm using AXIS2 1.4.1.
and Axiom do you use?
All the jars I use are from the AXIS2 1.4.1 package.
Is the client also Axis2 based?
Both client and server are AXIS2 1.4.1
Thank you very much for you prompt help!
Massimiliano
On Wed, May 20, 2009 at 5:22 PM, Andreas Veithen andreas.veit...@gmail.com
wrote:
Massimiliano,
Which version of Axis2 and Axiom do you use?
Is the client also Axis2 based?
Andreas
On Wed, May 20, 2009 at 17:17, Massimiliano Ziccardi
massimiliano.zicca...@gmail.com wrote:
Hi all.
I've a simlpe pojo class:
public class MyClass
{
public DataHandler getFile()
{
return new DataHandler(new FileDataSource(new
File(/tmp/myfile)));
}
}
I've published that pojo as a WebService.
The problem is that, on the client side, the file is always truncated at
12123 bytes.
How can I solve this issue?
Thanks,
Massimiliano
RE: Access to message context in Password Callback Handler
Hi Guys, Are there any solution to my problem. This seems like a failry common requirement. I would really appreciate any help or suggestion. Thanks Sanjay From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Friday, May 08, 2009 7:50 AM To: axis-user@ws.apache.org Subject: RE: Access to message context in Password Callback Handler Hi, Can anybody give me some pointers on this issue. Sanjay From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Tuesday, April 21, 2009 8:55 AM To: axis-user@ws.apache.org Subject: Access to message context in Password Callback Handler Hi, I have seen lots on discussion on having access to message context in password callback handler in axis2 but no clear solution. I need to store some user profile information after successful authentication in callback handler so that I can access them in my services(POJO). One option would have been to store them in message context and access them in my service but message context is not available calback hander. I would really appreciate any suggesions. Thanks Sanjay
Re: WS Addressing - Include MessageID in response
Is there no way of doing this?? - Original Message - From: Mohannad Hammadeh mohannad.hamma...@orionhealth.com To: axis-user axis-user@ws.apache.org Sent: Wednesday, 20 May, 2009 16:53:55 GMT +12:00 New Zealand Subject: WS Addressing - Include MessageID in response Hi there, I am trying to configure my webservice to include a wsa:MessageID node in the header of the response. I tried setting includeOptionalHeaders in Axis2.xml to true but that didnt help. Am I missing something or is there a different way of doing this? Any help would be appreciated, I am using Axis2 1.4. Regards, -- Mohannad Hammadeh
RE: Access to message context in Password Callback Handler
Hi Sagara, Thanks for your reply and suggestion. Your suggestion would definitely work. I have used this approach in other applications. I am going to try it. Sanjay -Original Message- From: Sagara Gunathunga [mailto:sagara.gunathu...@gmail.com] Sent: Wednesday, May 20, 2009 10:19 AM To: axis-user@ws.apache.org Subject: Re: Access to message context in Password Callback Handler Hi Sanjay, I have seen lot of post about this requirement, sometimes ago i also faced the same issue. AFAIK still there is no proper solution for this. cant you use following approach for your requirement..? 1. In callback handler save user profile into a database table after successful authentication . ( or persist using any other approach.) 2. In the service method retrieve above user profile from database to access required details. ( I know this is little ugly :) but possible solution) Thanks , On Wed, May 20, 2009 at 9:50 PM, Sanjay Gupta sanjay.gu...@billwiseinc.com wrote: Hi Guys, Are there any solution to my problem. This seems like a failry common requirement. I would really appreciate any help or suggestion. Thanks Sanjay From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Friday, May 08, 2009 7:50 AM To: axis-user@ws.apache.org Subject: RE: Access to message context in Password Callback Handler Hi, Can anybody give me some pointers on this issue. Sanjay From: Sanjay Gupta [mailto:sanjay.gu...@billwiseinc.com] Sent: Tuesday, April 21, 2009 8:55 AM To: axis-user@ws.apache.org Subject: Access to message context in Password Callback Handler Hi, I have seen lots on discussion on having access to message context in password callback handler in axis2 but no clear solution. I need to store some user profile information after successful authentication in callback handler so that I can access them in my services(POJO). One option would have been to store them in message context and access them in my service but message context is not available calback hander. I would really appreciate any suggesions. Thanks Sanjay -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://sagaras.awardspace.com/
[AXIS2] - includeOptionalHeaders not working
Hi, I am using Axis2 1.4 and I need my response to have a MessageId. I tried using the following in axis2.xml but it didnt work, am I missing anything? module ref=addressing/ !--Configuring module , providing parameters for modules whether they refer or not-- moduleConfig name=addressing parameter name=includeOptionalHeaders locked=truetrue/parameter /moduleConfig Regards, Mohannad Hammadeh
Re: [AXIS2] - includeOptionalHeaders not working
I found this ticket that mentions a fix to enable MessageID in the response. http://issues.apache.org/jira/browse/AXIS2-3275 Does anyone know what the 'option' is? Regrads, Mohannad - Original Message - Hi, I am using Axis2 1.4 and I need my response to have a MessageId. I tried using the following in axis2.xml but it didnt work, am I missing anything? module ref=addressing/ !--Configuring module , providing parameters for modules whether they refer or not-- moduleConfig name=addressing parameter name=includeOptionalHeaders locked=truetrue/parameter /moduleConfig Regards, Mohannad Hammadeh
