Re: Axis2 as messages proxy
Hi, Have you tried out Apache Synapse? http://synapse.apache.org/ I think this does what you want. Check the samples http://synapse.apache.org/Synapse_Samples.html. You may find something useful. Upul On Feb 6, 2008 10:17 AM, Sukma Agung Verdianto <[EMAIL PROTECTED]> wrote: > Hi All, > Is it possible to make Axis2 as a WS proxy. > I mean Axis2 receive a plain soap messages from other soap sender, and > this Axis2 will forward the messages wrapped with RM & Security things. > Is this possible? > > Regards, > Sukma >
Re: clien side custom axis2.xml file
Please give the full path and try again , I tried providing system property and it worked fine for me. -Deepal ataud wrote: I try -Daxis2.xml=axis2.xml (my custom axis2.xml is in the root directory), but it does not work. Deepal Jayasinghe-2 wrote: In client side, how to overload a custom axis2.xml file in spite of default axis2.xml file ? It is depend on how you create the serviceClient , if you create ServiceClient with creating a configuratonContext. Then you can pass your axis2.xml when you create configuratonContext. However if you create a ServiceClient using its default constructor , then you can pass system property as follows -Daxis2.xml="Location of your axis2.xml" Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 as messages proxy
Hi All, Is it possible to make Axis2 as a WS proxy. I mean Axis2 receive a plain soap messages from other soap sender, and this Axis2 will forward the messages wrapped with RM & Security things. Is this possible? Regards, Sukma
Size of Message
Hello, Is there a way I can measure the size of the message that gets on the wire? I want to figure out how much pressure I'm gonna be putting on the network. Thanks
Re: Axis & Tomcat on a server which requires proxy settings
Ok. Then i will try to create an Axis2 client and set the proxy you just told me too. Thanks. On 05/02/2008, Michele Mazzucco <[EMAIL PROTECTED]> wrote: > > On Tue, 2008-02-05 at 19:10 +0100, Elisei Rotaru wrote: > > On another matter, can i access axis1 webservice with axis2? > > If you mean by using an axis2 client, yes. > > Michele > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
WSDL2Java & List elements
Hello,
Let's say I have a simple public class Student {private List
courses; /*getter, setter*/}...
I was wondering is there a way I can instruct WSDL2Java to map arrays into
List.
Currently, I have a service operation Student[] getStudents(); WSDL2Java -u
-uw creates a very clean stub. So that on the client side I can do
something like Student[] students = stub.getStudents(). Nice!
However, things get a bit strange, when I do student.getCourses() I get back
an OMElement. Is there a way I can instruct WSDL2Java to create the stubs
so that on the client side I can do something like: List courses =
student.getCourses();?
Thanks in advance
Re: [axis2] SimpleHTTPServer as transport listener causes too many connections to stay in TIME_WAIT state
On 5 Feb 2008, at 20:24, Asankha C. Perera wrote: Michele my WS runs inside tomcat, but there are some ServiceClient(s) instances running in it. So I guess incoming requests are handled by the tomcat connector while outgoing messages are handled by the synapse sender, right? Not if you are using the NIO listener on the server side and sending requests on the NIO listeners' port.. No, calls were made to the tomcat port. On the client side, instead, I used the nio transport for both incoming and outgoing messages. No.. the NIO client / Sender is optimized for a server environment - like Synapse - and thus not recommended for a simple client, as it starts a NIO reactor and a thread pool for handling IO requests with dedicated IO threads etc. So, this will be good for your server side if you are making many outgoing calls from the server side.. What about if the client is a load generator? BTW.. I think you are developing something like an ESB?? Something like that, but with some smart forwarding/throttling policies No, the client is on a remote machine. I've tried to use both blocking and non blocking sender/listener on the client side, and the bottleneck seems to be the server. This could very well be due to a weakness on the client side.. for example even if you used ApacheBench you will could bad performance for some cases as it doesn't support HTTP 1.1! No, I've written the client, and it's pretty optimized. I think the client uses the transports defined in axis2.xml, it should not matter which kind of properties you define into the Options. What do you suggest?, I don't think the problem is the tomcat connector (I've tried both tomcat 5.5.23 with blocking connector and 6.0.14 with non blocking one) Again, if you use the NIO listener on the server side, nothing will use the Tomcat connector asankha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] SimpleHTTPServer as transport listener causes too many connections to stay in TIME_WAIT state
Michele my WS runs inside tomcat, but there are some ServiceClient(s) instances running in it. So I guess incoming requests are handled by the tomcat connector while outgoing messages are handled by the synapse sender, right? Not if you are using the NIO listener on the server side and sending requests on the NIO listeners' port.. On the client side, instead, I used the nio transport for both incoming and outgoing messages. No.. the NIO client / Sender is optimized for a server environment - like Synapse - and thus not recommended for a simple client, as it starts a NIO reactor and a thread pool for handling IO requests with dedicated IO threads etc. So, this will be good for your server side if you are making many outgoing calls from the server side.. BTW.. I think you are developing something like an ESB?? No, the client is on a remote machine. I've tried to use both blocking and non blocking sender/listener on the client side, and the bottleneck seems to be the server. This could very well be due to a weakness on the client side.. for example even if you used ApacheBench you will could bad performance for some cases as it doesn't support HTTP 1.1! I think the client uses the transports defined in axis2.xml, it should not matter which kind of properties you define into the Options. What do you suggest?, I don't think the problem is the tomcat connector (I've tried both tomcat 5.5.23 with blocking connector and 6.0.14 with non blocking one) Again, if you use the NIO listener on the server side, nothing will use the Tomcat connector asankha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: XmlBeans version with Axis 1.3?
Sorry, looks like I found the answer to my question. From the file name "xbeans-2.2.0.jar", I can see XmlBeans 2.2.0 is still being used. From: Vinh Nguyen (vinguye2) Sent: Tuesday, February 05, 2008 10:57 AM To: axis-user@ws.apache.org Subject: XmlBeans version with Axis 1.3? Hi, What version of XmlBeans does Axis2 1.3 use? When following the samples, I noticed that using the "-d xmlbeans" option in the Ant task generates some org.xmlsoap.schemas.* artifacts which I'm not sure if they are used by Axis2 or XmlBeans. XmlBeans 2.2.0 doesn't have these artifacts. Aloha, -Vinh
XmlBeans version with Axis 1.3?
Hi, What version of XmlBeans does Axis2 1.3 use? When following the samples, I noticed that using the "-d xmlbeans" option in the Ant task generates some org.xmlsoap.schemas.* artifacts which I'm not sure if they are used by Axis2 or XmlBeans. XmlBeans 2.2.0 doesn't have these artifacts. Aloha, -Vinh
Re: [axis2] SimpleHTTPServer as transport listener causes too many connections to stay in TIME_WAIT state
On Tue, 2008-02-05 at 23:40 +0530, Asankha C. Perera wrote: > Michele > > I did the following: > > - updated tomcat from 5.5 to 6.0.14 > > - enabled and tuned the tomcat NIO connector > The above are ok - but does not affect the synapse-transports-1.1.1.jar > at all... > > - upgraded the NIO listener and sender to synapse 1.1.1 (I had to > > upgrade the http-core library from alpha5 to beta1) > > - enabled the NIO sender on the server side (as I said I have some > > ServiceClient instances running on the server too) > ok.. > > but it didn't fix the problem. Indeed, about 50% of the connections in > > TIME_WAIT state are due to the tomcat connector and the other 50% to > > the axis2 sender. > what do you mean "tomcat" connector? If you changed your axis2.xml to > enable the o.a.synapse.transport.nhttp package, then *all* of your > messages should only be handled by it and not by Tomcat anymore.. you > cannot have a mix.. Asankha, my WS runs inside tomcat, but there are some ServiceClient(s) instances running in it. So I guess incoming requests are handled by the tomcat connector while outgoing messages are handled by the synapse sender, right? On the client side, instead, I used the nio transport for both incoming and outgoing messages. > > So I enabled the NIO sender and NIO receiver on the client side. > > My scenario is composed by about 80% of asynchronous interactions and > > 20% of very fast blocking in-out MEPs. Now the latter fail this way: > For optimal usage of server resources you should tune your OS (refer > http://wso2.org/library/1721) i.e. at a minimum; > /etc/sysctl.conf > net.ipv4.ip_local_port_range = 1024 65535 > net.ipv4.tcp_fin_timeout = 30 > fs.file-max = 2097152 > net.ipv4.tcp_tw_recycle = 1 > net.ipv4.tcp_tw_reuse = 1 > > /etc/security/limits.conf > * soft nofile 4096 > * hard nofile 65535 Ok, thanks. Another link I've found useful is this http://www.webhostingtalk.com/archive/index.php/t-257654.html The settings which seem to solve the TIME_WAIT state are the following net.ipv4.tcp_tw_recycle=1 net.ipv4.tcp_tw_reuse=1 # Disables packet forwarding net.ipv4.ip_forward=0 # Decrease the time default value for tcp_fin_timeout connection net.ipv4.tcp_fin_timeout=25 # Decrease the time default value for tcp_keepalive_time connection net.ipv4.tcp_keepalive_time=1800 # Turn on the tcp_window_scaling net.ipv4.tcp_window_scaling=1 > > Also ensure you give enough heap to the Java process, and use HTTP 1.1 > and Keepalives as much as possible. > > ERROR 19:44:03,967 (QueueController.java:192) - Unable to add stream > > for queue Service2 > > > > > > The executed statements (related to axis2) are: > > final OMElement payload = createPayload(); > > > > ServiceClient sender = new > > ServiceClient(AddStreamConfiguration.getConfigurationContext(), null); > > sender.setOptions(getOptions()); > > OMElement result = sender.sendReceive(payload); > > > > where the options are > > options.setTransportInProtocol(Constants.TRANSPORT_HTTP); > > options.setCallTransportCleanup(true); > > options.setTo(StreamClient.getRouterEpr()); > > options.setAction(TestConstants.ADD_STREAM_SOAP_ACTION); > > options.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI); > > options.setProperty(HTTPConstants.CHUNKED, Boolean.TRUE); > > options.setProperty(HTTPConstants.AUTO_RELEASE_CONNECTION, Boolean.TRUE); > > > > and the configuration context differs from the default one because of > > the http connection manager with cached http client. > I believe the above if for your client - and note that some of the above > used properties does not apply to the NIO transport.. However, are you > running your client and the server (and anything else related to the > test scenario) on the same machine? If so, make sure that the culprit is > not the client - No, the client is on a remote machine. I've tried to use both blocking and non blocking sender/listener on the client side, and the bottleneck seems to be the server. > I think the above code uses the default HTTP transport > that uses the HttpClient codebase.. that may have properties for tuning > which I am not fully familiar with.. I think the client uses the transports defined in axis2.xml, it should not matter which kind of properties you define into the Options. What do you suggest?, I don't think the problem is the tomcat connector (I've tried both tomcat 5.5.23 with blocking connector and 6.0.14 with non blocking one) > Michele > asankha > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis & Tomcat on a server which requires proxy settings
On Tue, 2008-02-05 at 19:10 +0100, Elisei Rotaru wrote: > On another matter, can i access axis1 webservice with axis2? If you mean by using an axis2 client, yes. Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] SimpleHTTPServer as transport listener causes too many connections to stay in TIME_WAIT state
Michele I did the following: - updated tomcat from 5.5 to 6.0.14 - enabled and tuned the tomcat NIO connector The above are ok - but does not affect the synapse-transports-1.1.1.jar at all... - upgraded the NIO listener and sender to synapse 1.1.1 (I had to upgrade the http-core library from alpha5 to beta1) - enabled the NIO sender on the server side (as I said I have some ServiceClient instances running on the server too) ok.. but it didn't fix the problem. Indeed, about 50% of the connections in TIME_WAIT state are due to the tomcat connector and the other 50% to the axis2 sender. what do you mean "tomcat" connector? If you changed your axis2.xml to enable the o.a.synapse.transport.nhttp package, then *all* of your messages should only be handled by it and not by Tomcat anymore.. you cannot have a mix.. So I enabled the NIO sender and NIO receiver on the client side. My scenario is composed by about 80% of asynchronous interactions and 20% of very fast blocking in-out MEPs. Now the latter fail this way: For optimal usage of server resources you should tune your OS (refer http://wso2.org/library/1721) i.e. at a minimum; /etc/sysctl.conf net.ipv4.ip_local_port_range = 1024 65535 net.ipv4.tcp_fin_timeout = 30 fs.file-max = 2097152 net.ipv4.tcp_tw_recycle = 1 net.ipv4.tcp_tw_reuse = 1 /etc/security/limits.conf * soft nofile 4096 * hard nofile 65535 Also ensure you give enough heap to the Java process, and use HTTP 1.1 and Keepalives as much as possible. ERROR 19:44:03,967 (QueueController.java:192) - Unable to add stream for queue Service2 The executed statements (related to axis2) are: final OMElement payload = createPayload(); ServiceClient sender = new ServiceClient(AddStreamConfiguration.getConfigurationContext(), null); sender.setOptions(getOptions()); OMElement result = sender.sendReceive(payload); where the options are options.setTransportInProtocol(Constants.TRANSPORT_HTTP); options.setCallTransportCleanup(true); options.setTo(StreamClient.getRouterEpr()); options.setAction(TestConstants.ADD_STREAM_SOAP_ACTION); options.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI); options.setProperty(HTTPConstants.CHUNKED, Boolean.TRUE); options.setProperty(HTTPConstants.AUTO_RELEASE_CONNECTION, Boolean.TRUE); and the configuration context differs from the default one because of the http connection manager with cached http client. I believe the above if for your client - and note that some of the above used properties does not apply to the NIO transport.. However, are you running your client and the server (and anything else related to the test scenario) on the same machine? If so, make sure that the culprit is not the client - I think the above code uses the default HTTP transport that uses the HttpClient codebase.. that may have properties for tuning which I am not fully familiar with.. asankha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis & Tomcat on a server which requires proxy settings
Hi Michele,
This is how i can set ProxyProperties when i access a webservice with axis2.
In axis1 the ProxyProperties are set somehow else (i dont really know how
and where).
Another Question perhaps:
If there is a webservice running with axis1, and i generate my stub classes
from the wsdl file with wsdl2java from axis2, will that work?
On another matter, can i access axis1 webservice with axis2?
Thanks,
On 05/02/2008, Michele Mazzucco <[EMAIL PROTECTED]> wrote:
>
> Elis,
>
> try with HttpTransportProperties.ProxyProperties.
> Once you have such an object, set it to the options with
>
> options.setProperty(HTTPConstants.PROXY, proxy);
>
>
> HTH,
> Michele
>
> On 5 Feb 2008, at 16:46, Elisei Rotaru wrote:
>
> > Hello,
> >
> > I run an axis2 1.3 webservice on a server which requires proxy
> > settings to connect to the Internet.
> >
> > I try to access with my webservice an axis1 webservice. And to
> > access this axis1 webservice i have to tell my axis2 webservice
> > that he should connect to the axis1 webservice through a proxy.
> >
> > This works with System wide settings like:
> >
> > System.setProperty("http.proxyHost",);
> > System.setProperty("http.proxyPort",);
> >
> > Only that other service get an http transport error afterwards.
> >
> > How can i set http proxy only for that webservice when he calls the
> > axis1 service?
> >
> > Thanks a lot.
> >
> > Elis,
> >
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Re: Axis & Tomcat on a server which requires proxy settings
Elis,
try with HttpTransportProperties.ProxyProperties.
Once you have such an object, set it to the options with
options.setProperty(HTTPConstants.PROXY, proxy);
HTH,
Michele
On 5 Feb 2008, at 16:46, Elisei Rotaru wrote:
Hello,
I run an axis2 1.3 webservice on a server which requires proxy
settings to connect to the Internet.
I try to access with my webservice an axis1 webservice. And to
access this axis1 webservice i have to tell my axis2 webservice
that he should connect to the axis1 webservice through a proxy.
This works with System wide settings like:
System.setProperty("http.proxyHost",);
System.setProperty("http.proxyPort",);
Only that other service get an http transport error afterwards.
How can i set http proxy only for that webservice when he calls the
axis1 service?
Thanks a lot.
Elis,
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: clien side custom axis2.xml file
Can you provide the complete path and see what happens Azeez On Feb 5, 2008 6:29 PM, ataud <[EMAIL PROTECTED]> wrote: > > I try -Daxis2.xml=axis2.xml (my custom axis2.xml is in the root > directory), > but it does not work. > > > Deepal Jayasinghe-2 wrote: > > > > > >> In client side, how to overload a custom axis2.xml file in spite of > >> default > >> axis2.xml file ? > >> > > It is depend on how you create the serviceClient , if you create > > ServiceClient with creating a configuratonContext. Then you can pass > > your axis2.xml when you create configuratonContext. However if you > > create a ServiceClient using its default constructor , then you can pass > > system property as follows > > > > -Daxis2.xml="Location of your axis2.xml" > > > > > > Thanks > > Deepal > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/clien-side-custom-axis2.xml-file-tp15289252p15289615.html > Sent from the Axis - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Thanks Afkham Azeez http://azeez78.blogspot.com http://www.wso2.org GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
Integration with Director?
I know that this is perhaps a touch off-topic, so please forgive me. I'm trying to develop web services in axis that will be primarily consumed by a Director client and I am wanting to check for any pitfalls to avoid and bits of advice to try to ensure that the two talk seamlessly. I can take this off the list if it goes too far into Director conversation. Regards, Jeff
Re: [axis2] is it possible to generate unwrapped client code using the maven plugin?
Seems that the documentation is wrong...
The mojo does support the unwrap parameter.
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/tool/axis2-wsdl2code-maven-plugin/src/main/java/org/apache/axis2/maven2/wsdl2code/WSDL2CodeMojo.java
Adrian Herscu wrote:
I have used the -uw switch with command line tool:
wsdl2java -or -uw -o ${project_loc} -uri ${string_prompt:WSDL URL}
Any parallel in the Maven plugin?
Adrian Herscu wrote:
Hi all,
I am trying to integrate the axis2-wsdl2code-maven-plugin into my
Maven 2 build and the compilation fails because the stubs have
different signatures than those generated with command line tool.
Is there a hidden option to make it generate unwrapped stubs?
TIA,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Axis & Tomcat on a server which requires proxy settings
Hello,
I run an axis2 1.3 webservice on a server which requires proxy settings to
connect to the Internet.
I try to access with my webservice an axis1 webservice. And to access this
axis1 webservice i have to tell my axis2 webservice that he should connect
to the axis1 webservice through a proxy.
This works with System wide settings like:
System.setProperty("http.proxyHost",);
System.setProperty("http.proxyPort",);
Only that other service get an http transport error afterwards.
How can i set http proxy only for that webservice when he calls the axis1
service?
Thanks a lot.
Elis,
Question about faults
Hi,
I have a web service client and server based based on the axiom API. The WSDL
for this web service has an operation with input, output and fault parts.
On the server side I generate a fault by doing the following:
public void invokeBusinessLogic(
MessageContext requestCtx,
MessageContext responseCtx)
throws AxisFault
{
[...]
SOAPEnvelope envelope = soapFactory.getDefaultEnvelope();
OMElement body = envelope.getBody();
if (isThisAFault()) {
SOAPFault fault = soapFactory.createSOAPFault();
envelope.getBody().addFault(fault);
body = fault;
}
OMElement payload = buildMessage(body,...);
responseCtx.setProcessingFault(true); // is this required?
responseCtx.setEnvelope(envelope);
}
On the client side the onError method of the AxisCallback class is invoked, but
I was expecting that the onFault method would be invoked. The stacktrace of the
exception in the onError method is this:
org.apache.axis2.AxisFault
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:414)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Am I generating the fault properly? Could you please give me a hint about where
the problem is located?
Many thanks in advance,
jms.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] SimpleHTTPServer as transport listener causes too many connections to stay in TIME_WAIT state
Paul, I've attache some test cases here https://issues.apache.org/jira/ browse/AXIS2-3428 Michele On 1 Feb 2008, at 14:42, Paul Fremantle wrote: Michele If you can post some test cases, we will do our best to improve the NIO transport. You also should try the NIO transport code from the Synapse 1.1.1 release if you haven't already because that had a number of fixes in it. Thanks Paul On Feb 1, 2008 1:35 PM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: On 1 Feb 2008, at 03:15, robert lazarski wrote: Me == clueless . Just some general advice though. Have you thought about submitting patches to fix the NIO issues? I notice that someone from the synapse team (IIRC), three weeks ago, asked you to submit a test case for your failure in one of the jira's you posted. Robert, I know. I'll do that as soon as I find some time. As I've said before Michele, you easily have some of the most complex and long going use cases for axis2 as a non-committer. Your involvement via patches certainly have a better chance of getting developer attention. In respect to this issue, I can at least try to be a bit helpful: 1) Have you tried running your code on anything else besides OSX to see if these socket issues are OS related? I've run into several socket and nio issues specific to linux for example. Yes. Indeed my problem occurs on a 4 CPUs linux box 2) Have you tried running http 1.0 instead of 1.1 ? Yes, it doesn't make any difference. 3) SimpleHTTPServer has never been meant for production use, so stop trying to use it like that. Fixing the nio issues seem to me to be the better path. Yes, but the nio code comes from Synapse... and this would mean digging into the Synapse code (which I don't know). My understanding of TIME_WAIT, via an old usenet post of mine, was best explained to me this way: "After the connection is closed, there might still be some stray packets that were delayed and could still arrive. The TIME_WAIT status retains a record of a recent connection, so that the system can recognize these as delay packets." Are these connections going from CLOSE_WAIT to TIME_WAIT? Can you do a 'netstat -anp' and show the transition states? Well, netstat doesn't show me any transition, only the current state What issue do you have with TIME_WAIT exactly? The number of connections in TIME_WAIT state grows very fast to a value > 500, and after that the my app. hangs (without crashing, it just freezes) Anyways, since SimpleHTTPServer is deep involved into the several hundred unit / integration tests, I don't see major changes happening at this point. 4) Obviously try the latest axis2 nightlies and post questions to the http commons / reactor list. Its possible the latest snapshot of reactor fixes your issue and can be promoted to the upcomming axis2 1.4 . I'll try. HTH, Robert Michele On Jan 31, 2008 7:48 PM, Michele Mazzucco <[EMAIL PROTECTED]> wrote: Hello again, I've tried to write a TransportListener which uses Jetty as http server -- but I had no success: when requests come I get the following error http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsa="http://www.w3.org/2005/08/ addressing">http://www.w3.org/2005/08/ addressing/soap/faultsoapenv:Header>soapenv:Serv er java.lang.NullPointerExceptionorg.apache.axis2.AxisFault: java.lang.NullPointerException at org.apache.axis2.transport.http.AxisServlet.doPost (AxisServlet.java:182) at javax.servlet.http.HttpServlet.service(HttpServlet.java: 709) at javax.servlet.http.HttpServlet.service(HttpServlet.java: 802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service (CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol $Http11ConnectionHandler.processConnection(Http11BaseProtocol.java: 664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket (PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt (LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool $ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException at nc
Re: Basic tips for a newbie, problems with really complex types
Thanks for your new answer... the URL you give me there is what I was looking for. I understood that xsd:anyType means literally that, it's just that I happen to know what will that anyType be, and expected to be able to build it using the generated classes... anyway, it will be easier to read that tutorial to get some ideas clear. Regards, David Philipp Leitner escribió: "I was just wondering if there were any other kind of diagram more useful for this purpose" Well, if the issue is having a number of classes (data structures) and trying to understand how they relate to each other then I would say class diagrams are basically the best visualization you can currently have. "> I've read http://ws.apache.org/axis2/1_3/userguide-creatingclients.html#createclients but there aren't many details like, for example, this issue with OMElement. Where could I find a deeper explanation about using Axis2 and it's databinding capabilities, and maybe more examples?" I probably should have explained that in more detail. Your xsd:anyType is basically a placeholder for some undefined XML content. Compare it to a Java interface like 'Object invoke(Object parameter)'. Just from looking at the interface (or, in your case, the WSDL description) neither you nor any tool in the world can tell what /kind of/ object you will be passed. Basically, you would have to ask the original developer what he actually wanted to do with this method. From the point of static type safety this method is entirely undefined. The same goes for your WSDL description - xsd:anyType says 'there's gonna be some XML content here, but I am not going to tell you what it looks like'. Therefore Axis2 is unable to create a Java type for this content. The only thing Axis2 is able to do is to hand /you/ (i.e., the client) the XML document and hope that you know (for instance, because you have talked offline to the service provider) what to do with this undefined bunch of data. And this is exactly what happens - you can receive a OMElement (an OMElement is just a AXIOM representation of a XML (sub-)tree), but unlike other fields you would have to deal with the XML data yourself in this special case. Have a look at http://ws.apache.org/axis2/1_0/OMTutorial.html for a tutorial on how to work with AXIOM. /philipp Original-Nachricht Datum: Tue, 05 Feb 2008 14:15:41 +0100 Von: [EMAIL PROTECTED] An: axis-user@ws.apache.org Betreff: Re: Basic tips for a newbie, problems with really complex types It's my fault for not having explained a bit more... I had thougth about making UML diagrams... I was just wondering if there were any other kind of diagram more useful for this purpose... thanks for your advice regarding this anyway... I've read http://ws.apache.org/axis2/1_3/userguide-creatingclients.html#createclients but there aren't many details like, for example, this issue with OMElement. Where could I find a deeper explanation about using Axis2 and it's databinding capabilities, and maybe more examples? Thanks for your answers. Philipp Leitner <[EMAIL PROTECTED]> wrote: "1º The types are a bit too complex and I find sometimes lost" You could use some kind of 'source code to class diagram' wizard to visualize your data structures after you have generated your stubs using wsdl2java (I think there is a good one as plugin for Ecipse). Or you could use a tool such as Altova XMLSpy to directly visualize your XSD files. "2º In one of the xsd I have this definition:" Your XSD file represents an xsd:anyType type. Basically that means that about everything can come along at this point in the Web service message. Axis2 has no way whatsoever of figuring out what this data will look like BEFORE it actually receives a request. That's bad news, because it means that you cannot cast it to a class. You have to directly deal with this data on XML (or more accurately, on AXIOM) level. hth, philipp " Hi, I've just started a WS client and I chose axis2 because I had to do a little web service server and client and I used axis 1.4 with no troubles at all. This is something a bit bigger, since I'm not at college anymore, and I have two problems. I've been given a huge wsdl and two xsd files defining some types used for the ws. I've used wsdl2java to generate code (using adb bindings... I could switch to something a bit more complex if there were any advantates regarding my current issues), but: 1º The types are a bit too complex and I find sometimes lost, not knowing how to build a single object for a request... Do you make any kind of diagrams when dealing with such a large hierarchy of types? 2º In one of the xsd I have this definition: and the generated class QueryExpressionType has an attribute: /** * field for ExtraElement */ protected org.apache.axiom.om.OMElement localE
Re: How can I test the endpoint validity with axis2 at client side ?
I try MyStub stub = new MyStub("http://aninvalidurl";); but does not throw an
exception
The axis version is 2.1.3
Normaly it should throw an exception without http or other prefix !!
Charitha Kankanamge wrote:
>
> Hi ataud,
> If you insert 'http' in front of your url ("http://aninvalidurl";), you
> should get java.net.UnknownHostException: aninvalidurl. I just checked
> it with Axis2 snapshot.
>
> regards
> Charitha
>
> ataud wrote:
>
>>At client side, I generate an Axis2 stub (WSDL2Java). When I populate an
>>invalid URL, it does not throw an exception !!!
>>
>>...
>>MyStub stub = new MyStub("aninvalidurl");
>>...
>>
>>It should throw an exception, but it does not !!!
>>
>>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/How-can-I-test-the-endpoint-validity-with-axis2-at-client-side---tp15290664p15291425.html
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How can I test the endpoint validity with axis2 at client side ?
Hi ataud,
If you insert 'http' in front of your url ("http://aninvalidurl";), you
should get java.net.UnknownHostException: aninvalidurl. I just checked
it with Axis2 snapshot.
regards
Charitha
ataud wrote:
At client side, I generate an Axis2 stub (WSDL2Java). When I populate an
invalid URL, it does not throw an exception !!!
...
MyStub stub = new MyStub("aninvalidurl");
...
It should throw an exception, but it does not !!!
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How can I test the endpoint validity with axis2 at client side ?
At client side, I generate an Axis2 stub (WSDL2Java). When I populate an
invalid URL, it does not throw an exception !!!
...
MyStub stub = new MyStub("aninvalidurl");
...
It should throw an exception, but it does not !!!
--
View this message in context:
http://www.nabble.com/How-can-I-test-the-endpoint-validity-with-axis2-at-client-side---tp15290664p15290664.html
Sent from the Axis - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Basic tips for a newbie, problems with really complex types
"I was just wondering if there were any other kind > of diagram more useful for this purpose" Well, if the issue is having a number of classes (data structures) and trying to understand how they relate to each other then I would say class diagrams are basically the best visualization you can currently have. "> I've read > http://ws.apache.org/axis2/1_3/userguide-creatingclients.html#createclients > but there aren't many details like, for example, this issue with > OMElement. Where could I find a deeper explanation about using Axis2 and > it's databinding capabilities, and maybe more examples?" I probably should have explained that in more detail. Your xsd:anyType is basically a placeholder for some undefined XML content. Compare it to a Java interface like 'Object invoke(Object parameter)'. Just from looking at the interface (or, in your case, the WSDL description) neither you nor any tool in the world can tell what /kind of/ object you will be passed. Basically, you would have to ask the original developer what he actually wanted to do with this method. From the point of static type safety this method is entirely undefined. The same goes for your WSDL description - xsd:anyType says 'there's gonna be some XML content here, but I am not going to tell you what it looks like'. Therefore Axis2 is unable to create a Java type for this content. The only thing Axis2 is able to do is to hand /you/ (i.e., the client) the XML document and hope that you know (for instance, because you have talked offline to the service provider) what to do with this undefined bunch of data. And this is exactly what happens - you can receive a OMElement (an OMElement is just a AXIOM representation of a XML (sub-)tree), but unlike other fields you would have to deal with the XML data yourself in this special case. Have a look at http://ws.apache.org/axis2/1_0/OMTutorial.html for a tutorial on how to work with AXIOM. /philipp Original-Nachricht > Datum: Tue, 05 Feb 2008 14:15:41 +0100 > Von: [EMAIL PROTECTED] > An: axis-user@ws.apache.org > Betreff: Re: Basic tips for a newbie, problems with really complex types > > It's my fault for not having explained a bit more... I had thougth > about making UML diagrams... I was just wondering if there were any > other kind of diagram more useful for this purpose... thanks for your > advice regarding this anyway... > > I've read > http://ws.apache.org/axis2/1_3/userguide-creatingclients.html#createclients > > but there aren't many details like, for example, this issue with > OMElement. Where could I find a deeper explanation about using Axis2 > and it's databinding capabilities, and maybe more examples? > > Thanks for your answers. > > > > Philipp Leitner <[EMAIL PROTECTED]> wrote: > > > "1º The types are a bit too complex and I find sometimes lost" > > > > You could use some kind of 'source code to class diagram' wizard to > > visualize your data structures after you have generated your stubs > > using wsdl2java (I think there is a good one as plugin for Ecipse). > > Or you could use a tool such as Altova XMLSpy to directly visualize > > your XSD files. > > > > "2º In one of the xsd I have this definition:" > > > > Your XSD file represents an xsd:anyType type. Basically that means > > that about everything can come along at this point in the Web > > service message. Axis2 has no way whatsoever of figuring out what > > this data will look like BEFORE it actually receives a request. > > That's bad news, because it means that you cannot cast it to a > > class. You have to directly deal with this data on XML (or more > > accurately, on AXIOM) level. > > > > hth, philipp > > > > " > > Hi, I've just started a WS client and I chose axis2 because I had to do > > a little web service server and client and I used axis 1.4 with no > > troubles at all. > > > > This is something a bit bigger, since I'm not at college anymore, and I > > have two problems. I've been given a huge wsdl and two xsd files > > defining some types used for the ws. I've used wsdl2java to generate > > code (using adb bindings... I could switch to something a bit more > > complex if there were any advantates regarding my current issues), but: > > > > 1º The types are a bit too complex and I find sometimes lost, not > > knowing how to build a single object for a request... Do you make any > > kind of diagrams when dealing with such a large hierarchy of types? > > > > 2º In one of the xsd I have this definition: > > > > > > > > > > > use="required"/> > > > > > > and the generated class QueryExpressionType has an attribute: > > > > /** > > * field for ExtraElement > > */ > >protected org.apache.axiom.om.OMElement localExtraElement; > > > > How can I cast this to the class representing the actual data in the > > message? > > > > Thanks for your time. > > > > I think I should add the files I
Re: Basic tips for a newbie, problems with really complex types
It's my fault for not having explained a bit more... I had thougth about making UML diagrams... I was just wondering if there were any other kind of diagram more useful for this purpose... thanks for your advice regarding this anyway... I've read http://ws.apache.org/axis2/1_3/userguide-creatingclients.html#createclients but there aren't many details like, for example, this issue with OMElement. Where could I find a deeper explanation about using Axis2 and it's databinding capabilities, and maybe more examples? Thanks for your answers. Philipp Leitner <[EMAIL PROTECTED]> wrote: "1º The types are a bit too complex and I find sometimes lost" You could use some kind of 'source code to class diagram' wizard to visualize your data structures after you have generated your stubs using wsdl2java (I think there is a good one as plugin for Ecipse). Or you could use a tool such as Altova XMLSpy to directly visualize your XSD files. "2º In one of the xsd I have this definition:" Your XSD file represents an xsd:anyType type. Basically that means that about everything can come along at this point in the Web service message. Axis2 has no way whatsoever of figuring out what this data will look like BEFORE it actually receives a request. That's bad news, because it means that you cannot cast it to a class. You have to directly deal with this data on XML (or more accurately, on AXIOM) level. hth, philipp " Hi, I've just started a WS client and I chose axis2 because I had to do a little web service server and client and I used axis 1.4 with no troubles at all. This is something a bit bigger, since I'm not at college anymore, and I have two problems. I've been given a huge wsdl and two xsd files defining some types used for the ws. I've used wsdl2java to generate code (using adb bindings... I could switch to something a bit more complex if there were any advantates regarding my current issues), but: 1º The types are a bit too complex and I find sometimes lost, not knowing how to build a single object for a request... Do you make any kind of diagrams when dealing with such a large hierarchy of types? 2º In one of the xsd I have this definition: and the generated class QueryExpressionType has an attribute: /** * field for ExtraElement */ protected org.apache.axiom.om.OMElement localExtraElement; How can I cast this to the class representing the actual data in the message? Thanks for your time. I think I should add the files I mentioned before: --- I omit the files in this reply because of the size of the message - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: clien side custom axis2.xml file
I try -Daxis2.xml=axis2.xml (my custom axis2.xml is in the root directory), but it does not work. Deepal Jayasinghe-2 wrote: > > >> In client side, how to overload a custom axis2.xml file in spite of >> default >> axis2.xml file ? >> > It is depend on how you create the serviceClient , if you create > ServiceClient with creating a configuratonContext. Then you can pass > your axis2.xml when you create configuratonContext. However if you > create a ServiceClient using its default constructor , then you can pass > system property as follows > > -Daxis2.xml="Location of your axis2.xml" > > > Thanks > Deepal > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/clien-side-custom-axis2.xml-file-tp15289252p15289615.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: clien side custom axis2.xml file
In client side, how to overload a custom axis2.xml file in spite of default axis2.xml file ? It is depend on how you create the serviceClient , if you create ServiceClient with creating a configuratonContext. Then you can pass your axis2.xml when you create configuratonContext. However if you create a ServiceClient using its default constructor , then you can pass system property as follows -Daxis2.xml="Location of your axis2.xml" Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
clien side custom axis2.xml file
In client side, how to overload a custom axis2.xml file in spite of default axis2.xml file ? -- View this message in context: http://www.nabble.com/clien-side-custom-axis2.xml-file-tp15289252p15289252.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 changes the content of my static WSDL
The other option would be to set your cluster IP address in the axis2.xml as follows (by adding a parameter): my.cluster.ip Now, all generated port addresses will have your cluster IP. Azeez On Feb 5, 2008 3:26 PM, Upul Godage <[EMAIL PROTECTED]> wrote: > There is another parameter. modifyUserWSDLPortAddress Try adding this > parameter also with the value false. > > true > false > > Upul > > > On Feb 5, 2008 3:20 PM, Jan Philipp Seng <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I am using Axis2 1.3 and have a problem with the static WSDL in my > > service > > archiv. > > When retrieving the WSDL for my service > > (http://IP:Port/axis2/services/MyService?wsdl), Axis changes the IPs in > > section > > / / althought > > all > > other static changes I made appear correctly. This is a problem because > > I > > need to put the cluster IP here, not the server IP. Does anybody know > > how I > > can do this? > > In service.xml I switched to static WSDL in this way: > > true > > I dont understand why Axis changes my static WSDL instead of just > > delivering > > it as it is. > > > > Thanks a lot, > > Jan > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Thanks Afkham Azeez http://azeez78.blogspot.com http://www.wso2.org GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
Re: [axis2] is it possible to generate unwrapped client code using the maven plugin?
I have used the -uw switch with command line tool:
wsdl2java -or -uw -o ${project_loc} -uri ${string_prompt:WSDL URL}
Any parallel in the Maven plugin?
Adrian Herscu wrote:
Hi all,
I am trying to integrate the axis2-wsdl2code-maven-plugin into my Maven
2 build and the compilation fails because the stubs have different
signatures than those generated with command line tool.
Is there a hidden option to make it generate unwrapped stubs?
TIA,
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[axis2] is it possible to generate unwrapped client code using the maven plugin?
Hi all, I am trying to integrate the axis2-wsdl2code-maven-plugin into my Maven 2 build and the compilation fails because the stubs have different signatures than those generated with command line tool. Is there a hidden option to make it generate unwrapped stubs? TIA, Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Axis2 changes the content of my static WSDL
Thank you for you help. My problem is resolved now. Jan _ From: Upul Godage [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 05, 2008 10:56 AM To: axis-user@ws.apache.org Subject: Re: Axis2 changes the content of my static WSDL There is another parameter. modifyUserWSDLPortAddress Try adding this parameter also with the value false. true false Upul On Feb 5, 2008 3:20 PM, Jan Philipp Seng <[EMAIL PROTECTED]> wrote: Hi, I am using Axis2 1.3 and have a problem with the static WSDL in my service archiv. When retrieving the WSDL for my service (http://IP:Port/axis2/services/MyService?wsdl), Axis changes the IPs in section / / althought all other static changes I made appear correctly. This is a problem because I need to put the cluster IP here, not the server IP. Does anybody know how I can do this? In service.xml I switched to static WSDL in this way: true I dont understand why Axis changes my static WSDL instead of just delivering it as it is. Thanks a lot, Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JAXWS and soap 1.2
Hello,
I am trying to get a jaxws service working, am having troubles with the
jaxws-calculator sample. I have built and deployed the aar file using maven
after updating the pom to remove the SNAPSHOT versions.
I then add the aar file to the axis2/WEB-INF/services/ directory and also seem
to need to unpack the aar into axis2/WEB-INF/classes, to avoid a class not
found exception.
Then I have created a new client using:
wsdl2java.sh -uri http://localhost:8080/axis2/services/CalculatorService?wsdl
ant
---
import org.apache.axis2.jaxws.calculator.*;
public class CalcClient
{
public static void main(String[] args) throws Exception
{
CalculatorServiceStub stub = new CalculatorServiceStub();
CalculatorServiceStub.Add add = new CalculatorServiceStub.Add();
add.setValue1(1);
add.setValue2(1);
System.out.println(stub.add(add));
}
}
---
Then compile the test client with a class path of:
build/classes, AXIS2_HOME/lib/*.jar and the
build/lib/CalculatorService-test-client.jar
Then running the client with the same classpath I get the error:
Exception in thread "main" org.apache.axis2.AxisFault: Incoming SOAP message
protocol is version 1.2, but endpoint is configured for SOAP 1.1
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
at
org.apache.axis2.jaxws.calculator.CalculatorServiceStub.add(CalculatorServiceStub.java:294)
at CalcClient.main(CalcClient.java:11)
Can anyone help with this please or point me in the right direction. I am
guessing that I shouldn't need to unpack the aar to get this working?
Thanks
Neil
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[axis2]Re: Problem with Retrieving the Values from the Client
Hello Again, I have just tried changing the wsdl from rpc to literal support but it only gives out this error. The error happens when I try to call WSDL2Java for generating the skeleton. Could there be a conflict since I tried to generate the WSDL with Java2WSDL using apache axis? [ERROR] No element type is defined for message addUserRequest org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException: No element type is defined for message addUserRequest so I looked around for an answer and one of the possible solutions was appending the elements with xsd like this: http://xml.apache.org/xml-soap"; xmlns:impl="urn:voxsant" xmlns:intf="urn:voxsant" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:tns1="http://model.voxsant"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://model.voxsant"; xmlns="http://www.w3.org/2001/XMLSchema";> http://schemas.xmlsoap.org/soap/encoding/"/> name="virtualNumbers" nillable="true" type="xsd:string"/> name="addUserResponse"/> type="impl:VoxsantService"> transport="http://schemas.xmlsoap.org/soap/http"/> name="VoxsantService"> location="http://localhost:8080/axis2/services/VoxsantService"/> But still it gives out the same error problem. Is there a particular point here that I am missing because right now I am stumped? Would really appreciate any help. Thanks again in advance. Carlo Fabian Anne Thomas Manes wrote: Are you working with Axis or Axis2? (I'm guessing Axis) Which version? Older versions of Axis had some trouble supporting rpc/literal. You might want to use wrapped document/literal instead. One problem I see in the WSDL: You must remove the soapEncoding attribute from the elements in your binding definitions. (You use that attribute only if use="encoded"). Anne On Feb 4, 2008 4:31 AM, Jose Carlo Fabian <[EMAIL PROTECTED]> wrote: Hello everyone. I am a beginner when it comes to creating web services and I have encountered a problem that I cannot seem to find a solution to. I have created a simple web service that adds a user based on the parameters passed by the client. Now I can receive the xml(server side) and can parse it but the problem is, the elements that I have declared nillable=true, even if I have entered values in them, arrives to the server without any values. Here is the wsdl for reference: http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:apachesoap="http://xml.apache.org/xml-soap"; xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; xmlns:tns1="http://model.voxsant";> http://model.voxsant"; xmlns="http://www.w3.org/2001/XMLSchema";> http://schemas.xmlsoap.org/soap/encoding/"/> http://schemas.xmlsoap.org/soap/http"/> http://schemas.xmlsoap.org/soap/encoding/"; namespace="urn:voxsant"/> http://schemas.xmlsoap.org/soap/encoding/"; namespace="urn:voxsant"/> http://localhost:8080/axis2/services/VoxsantService"/> For the entries wherein I did not enter a nillable=true, their values arrive, but for the other entries(country, state, virtual numbers etc), I do not get the values even if my test client passes it to the ws. Does anyone know where I went wrong? Would really appreciate any help, thanks Carlo F. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ServiceName in envelope and not URL, is it possible?
Hi All, I have to develop a web service using Axis2 that have a single endpoint address, but provide multiple services. Is it possible to use ServiceName in soap WS-addressing header instead of URL? current supported by Axis2: HTTP: http://example.com/axis2/services/ServiceA Mail : mailto:[EMAIL PROTECTED]/axis2/services/ServiceA I want it to be: HTTP: http://example.com/ep Mail : mailto:[EMAIL PROTECTED] But the SOAP header inside messages sent by client must have a wsa:ServiceName element which will distinguish which service will be used. I see that there is AddressingConstant.EPR_SERVICE_NAME constant. When should I use that constant? Any Idea? Regards, Sukma
Re: FW: Consuming a .NET Windows Integrated Security protected web service
Yes it works.
On Tue, 2008-02-05 at 12:53 +0200, Asaf Lahav wrote:
> Did anyone get my email? (If you did please reply to it… I'm not sure
> my news group registration works)
>
>
>
> From: Asaf Lahav [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 04, 2008 8:26 PM
> To: 'axis-user@ws.apache.org'
> Subject: Consuming a .NET Windows Integrated Security protected web
> service
>
>
>
>
> Hello everybody,
>
> I need your help in consuming a .NET Windows Integrated Security
> protected web service.
>
> I followed the instructions on the following link:
> http://people.etango.com/~markm/archives/2005/11/21/using_apache_axis_with_integrated_windows_security.html
>
>
>
> And I'm still unable to consume the WS.
>
> This is the code I'm using:
>
>
>
> import org.apache.axis.EngineConfiguration;
>
> import org.apache.axis.client.Call;
>
> import org.apache.axis.client.Service;
>
> import org.apache.axis.configuration.FileProvider;
>
>
>
> public class Test1 {
>
> public static void main(String[] args) {
>
>
>
>try {
>
> EngineConfiguration config = new
> FileProvider(Test1.class
>
>
> .getResourceAsStream("AxisClientDeployment.wsdd"));
>
>
>
> try {
>
> String endpoint =
> "http://MyServer/wsApp/WebService.asmx";;
>
>
>
> Service service = new Service(config);
>
> Call call = (Call) service.createCall();
>
>
>
>
> call.setSOAPActionURI("http://tempuri.org/MyOperation1";);
>
> call.setUsername("MyDomain\\MyUser");
>
> call.setPassword("MyPassword123456");
>
>
>
> call.setTargetEndpointAddress(new
> java.net.URL(endpoint));
>
> call.setOperationName(new
> QName("http://tempuri.org/";,
>
>" MyOperation1"));
>
>
>
> Object ret = call.invoke(new Object[]
> { "app","usr","ctxt" });
>
>
>
> System.out.println("Response'" + ret + "'");
>
> } catch (Exception e) {
>
> e.printStackTrace();
>
> }
>
>
>
> } catch (Exception e) {
>
>
>
> }
>
> }
>
> }
>
>
>
<
>
<
>
> Any help would be highly appreciated.
>
> Best,
>
> Asaf
>
>
==
DISCLAIMER: The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message by
anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or omission
taken by you in reliance on it, is prohibited and may be unlawful. Please
immediately contact the sender if you have received this message in error.
Further, this e-mail may contain viruses and all reasonable precaution to
minimize the risk arising there from is taken by OnMobile. OnMobile is not
liable for any damage sustained by you as a result of any virus in this e-mail.
All applicable virus checks should be carried out by you before opening this
e-mail or any attachment thereto.
Thank you - OnMobile Global Limited.
==
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
FW: Consuming a .NET Windows Integrated Security protected web service
Did anyone get my email? (If you did please reply to it. I'm not sure my
news group registration works)
From: Asaf Lahav [mailto:[EMAIL PROTECTED]
Sent: Monday, February 04, 2008 8:26 PM
To: 'axis-user@ws.apache.org'
Subject: Consuming a .NET Windows Integrated Security protected web service
Hello everybody,
I need your help in consuming a .NET Windows Integrated Security protected
web service.
I followed the instructions on the following link:
http://people.etango.com/~markm/archives/2005/11/21/using_apache_axis_with_i
ntegrated_windows_security.html
And I'm still unable to consume the WS.
This is the code I'm using:
import org.apache.axis.EngineConfiguration;
import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
import org.apache.axis.configuration.FileProvider;
public class Test1 {
public static void main(String[] args) {
try {
EngineConfiguration config = new FileProvider(Test1.class
.getResourceAsStream("AxisClientDeployment.wsdd"));
try {
String endpoint =
"http://MyServer/wsApp/WebService.asmx";;
Service service = new Service(config);
Call call = (Call) service.createCall();
call.setSOAPActionURI("http://tempuri.org/MyOperation1";);
call.setUsername("MyDomain\\MyUser");
call.setPassword("MyPassword123456");
call.setTargetEndpointAddress(new
java.net.URL(endpoint));
call.setOperationName(new
QName("http://tempuri.org/";,
" MyOperation1"));
Object ret = call.invoke(new Object[] {
"app","usr","ctxt" });
System.out.println("Response'" + ret + "'");
} catch (Exception e) {
e.printStackTrace();
}
} catch (Exception e) {
}
}
}
Any help would be highly appreciated.
Best,
Asaf
Re: Axis2 changes the content of my static WSDL
There is another parameter. modifyUserWSDLPortAddress Try adding this parameter also with the value false. true false Upul On Feb 5, 2008 3:20 PM, Jan Philipp Seng <[EMAIL PROTECTED]> wrote: > Hi, > > I am using Axis2 1.3 and have a problem with the static WSDL in my service > archiv. > When retrieving the WSDL for my service > (http://IP:Port/axis2/services/MyService?wsdl), Axis changes the IPs in > section > / / althought > all > other static changes I made appear correctly. This is a problem because I > need to put the cluster IP here, not the server IP. Does anybody know how > I > can do this? > In service.xml I switched to static WSDL in this way: > true > I dont understand why Axis changes my static WSDL instead of just > delivering > it as it is. > > Thanks a lot, > Jan > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Axis2 changes the content of my static WSDL
Hi, I am using Axis2 1.3 and have a problem with the static WSDL in my service archiv. When retrieving the WSDL for my service (http://IP:Port/axis2/services/MyService?wsdl), Axis changes the IPs in section / / althought all other static changes I made appear correctly. This is a problem because I need to put the cluster IP here, not the server IP. Does anybody know how I can do this? In service.xml I switched to static WSDL in this way: true I dont understand why Axis changes my static WSDL instead of just delivering it as it is. Thanks a lot, Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Log of request/response on transport level
Your explication is true for Axis2 v1.3, but unfortunately we are using Axis2 v1.1.1. In this version the MessageContext is only initialized with the HTTP Request, but not with the HTTP Response. I'll have a look if we can migrate to Axis2 v1.3. Regards, Stefan Lecho. Afkham Azeez wrote: > > In the AxisServlet, for each request received, the HTTP Request & Response > are set in the MessageContext; > > msgContext.setProperty(HTTPConstants.MC_HTTP_SERVLETREQUEST, request); > msgContext.setProperty(HTTPConstants.MC_HTTP_SERVLETRESPONSE, response); > > So I believe that you can have a custom handler in the MessageOut phase, > and > log the HTTP request & response. > > HTH > Azeez > > On Feb 4, 2008 7:18 PM, stlecho <[EMAIL PROTECTED]> wrote: > >> >> Hi, >> >> When using Axis2 as a client, the logging of the HTTP requests and >> responses >> messages can be activated by using the "httpclient" package in the log4j >> configuration. When calling a webservice, the Axis2 client uses an HTTP >> connection for the communication with the server. Activating the logging >> allows us to see the "raw" SOAP message and some additional information >> (>> >> "POST /fourthway/1.0/NoticeRequesterInterface HTTP/1.0[\r][\n]", >> >> "SOAPAction: "http://..."[\r][\n]";, ...). Once the webservice has been >> called, a synchronous HTTP response is received that contains for >> instance: >> "HTTP/1.1 200 OK". >> >> I have tried to achieve the same logging information when using Axis2 as >> a >> server, but without success :-(. What I would like to achieve, is the >> following: log every HTTP request to my Axis2 server on the HTTP level, >> i.e. >> the "raw" SOAP message that traverses the wire and log every HTTP >> response >> that my Axis2 server sends to the client. I suppose that - similar as in >> the >> client scenario - when a client calls my Axis2 server, an HTTP connection >> is >> established that allows the transport of the SOAP message. Activating the >> "httpclient" package in the log4j configuration of my Axis2 server, is >> not >> sufficient to log this kind of information. >> >> I've seen some posts and the explanation on how to add LoggingHandlers in >> the Axis2 process flow, but I think that this kind of logging does not >> log >> on the HTTP request/response level. >> >> What's the best way to log HTTP requests and responses when using Axis2 >> as >> a >> server ? >> >> Regards, Stefan Lecho. >> -- >> View this message in context: >> http://www.nabble.com/Log-of-request-response-on-transport-level-tp15268442p15268442.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Thanks > Afkham Azeez > > http://azeez78.blogspot.com > http://www.wso2.org > GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760 > > -- View this message in context: http://www.nabble.com/Log-of-request-response-on-transport-level-tp15268442p15285517.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Stateful Services
Pardon me for my lack of knowledge on this subject, but can Axis2 Stateful Web Services be used with non-Axis2 clients, or are they meant only for Axis2 to Axis2 communication? No , session like transport can be used across different SOAP engines. Thanks, Nadeem - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal "The highest tower is built one brick at a time" - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: programmatic deployment of an archive file on axis2 server
I am unable to deploy programmatically an archive file on axis soap server. I am using following api.. ConfigurationContext context = ConfigurationContextFactory.createConfigurationContextFromFileSystem( "location of Web-inf directory of axis2 soapserver, "path of ".WEB-INF/conf/axis2.xml") AxisServiceGroup serviceGroup = DeploymentEngine.loadServiceGroup(aarFile, context); AxisConfiguration xConfig = context.getAxisConfiguration(); xConfig.addServiceGroup(serviceGroup); hmm , I am sure this worked fine in Axis2 1.3 release. Anyway could you please create a JIRA and attach your aar file and the code, I will looking to that. Thanks Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
