Wally Dennis is out of the office.
Regarding your message: Re: How to turn off stdout messages when using WSDL 2.0 ? I will be out of the office starting 01-May-2009 and will not return until 05-May-2009. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Policy configuration for a signed Request and unsigned Response?
Hello, Is it possible to use the Policy configuration mechanism in Axis2/Rampart to configure a client to send a signed request and get back an unsigned response? If so, any examples or reference material would be most appreciated. Thanks, Wally The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Wally Dennis is out of the office.
Regarding your message: Re: Error in signature with X509Token I will be out of the office starting 09-Feb-2009 and will not return until 10-Feb-2009. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Problem with standalone Axis2 client not undeploying files
Hello, I am experiencing an issue and wanted to see if anyone else has seen this. When I execute an Axis2 client stub in a standalone Java application (ie - similar to the test driver that can be generated using the wsdl2java tool), the deploy() method in the ModuleDeployer class causes copies of the different module files from the repository to be written to my webserver's temporary directory. The problem is, these files are never cleaned up when the application completes, so everytime I run the application I get new copies of the files. It appears as though nothing is ever "undeploying" these modules. Looking at the undeploy() method in the ModuleDeployer class confirms this - the method is empty. Interestingly, I see the same deployment behavior when I use Axis2 client stubs in a web application, except that the files appear to be cleaned up by my webserver (not Axis2 code) when I shut down the server. It appears as though the code is assuming that the webserver will clean up these files, but that won't work if running as a standalone app. Is anyone else seeing this? Thanks, Wally The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: Client handler tutorial
One way to specify the conf and repo for stand-alone clients is to use -D JVM parameters as shown here: -Daxis2.repo=C:\Axis2\repository -Daxis2.xml=C:\Axis2\conf\axis2.xml Wally "Detelin Yordanov" <[EMAIL PROTECTED]> 08/13/2008 10:26 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Client handler tutorial Hi, When using Axis2 client (e.g. ServiceClient) you do not need any servlet container, it just uses Apache HttpClient to send and receive the request (if using HTTP). Underneath the ServiceClient will setup normal Axis2 runtime (as the one on server side) to process messages. The ServiceClient has constructors to specify an Axis2 ConfigurationContext which points to the "client-side" Axis2 configuration file, if no ConfigurationContext is given it will use (I think) a default axis2.xml from the Axis2 kernel jar. So if you need to define any handlers or whatsoever, you can create your axis2-conf for the client side, add your handlers, then create a ConfigurationContext and finally a ServiceClient. Regards, Detelin On Wed, Aug 13, 2008 at 4:19 PM, Franklin, Allen < [EMAIL PROTECTED]> wrote: Where I work we start with a hand-built wsdl and then run WSDL2Java to generate the client and server stubs and skeleton code. When I say 'client side handler' I am talking about a class that that implements AbstractHandler that (I think) I need to write to add a username, password and session id to the SOAP header. I'm still having trouble understanding if I need to deploy a servlet container (eg Tomcat) just to run an axis2 client? From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 9:00 AM To: axis-user@ws.apache.org Subject: RE: Client handler tutorial typical scenario is with the typical HTTP transport scenario you would build the server classes and deploy using the admin tool then use compiled WSDL2Java generated client stub to test I guess I would need to know which 'client side handler' you are referring to for specifics.. JMS/SMTP/Other ? Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Subject: RE: Client handler tutorial Date: Wed, 13 Aug 2008 08:53:17 -0400 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org Do I need to deploy my axis2 client into a servlet container to be able to use client-side handlers? Currently my client does not need a servlet container, it runs stand-alone. From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2008 6:46 PM To: axis-user@ws.apache.org Subject: RE: Client handler tutorial yuo can deploy the client mar from the admin utility try http://localhost:8080/axis2/axis2-admin/ HTH Martin __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission. Subject: Re: Client handler tutorial Date: Tue, 12 Aug 2008 18:34:04 -0400 From: [EMAIL PROTECTED] To: axis-user@ws.apache.org I am having trouble figuring out how to add client-side handlers in axis2. I see the email reply, below, that there is no difference between client and server side. But the configuration must be different since on the client side there is no web container to put the axis2.xml configuration information for the handler and also no place to put the .mar file. Client-side handler configuration remains a mystery to me. Re: Client handler tutorial Deepal Jayasinghe Wed, 16 Apr 2008 22:57:25 -0700 Hi Chau, Are you referring to Axis2 ? if so there is no difference between client side and server side. Thank you! Deepal Anybody knows the link to client handler tutorial? Thanks Reveal your inner athlete and share it with friends on Windows Live. Share now! Your PC, mobile phone, and online services work together like never before. See how Windows® fits your life The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this messag
Re: Axis2 Webservice called from another websiervice
Jay, How exactly have you tried to do this with Axis2? If I am understanding your situation, we are currently doing something like this successfully. We have a centralized service broker based on Axis2 that accepts incoming requests and can then route them to our mainframe, other applications, or other web services as needed. We are not using the standard axis2 war distribution, however. We already had an Enterprise Application (EAR) running on WebSphere 6.0 that already contained a web application, so we simply added a Websphere shared library containing the Axis2 files to the EAR. Then, by enabling the AxisServlet in our web application, we had the inbound support provided by Axis2. We are also using Axis2 stubs to make outbound web service calls from within the application. I'm not sure if there is something specific about our setup that is different than yours, but I can easily process many inbound service requests that in turn make outbound requests to other services and have not had any memory issues. Here is a very simplified model of the application: Inbound Message is received by Service A Message is validated and converted using ADB objects Payload is sent to our Service Controller, which acts as a router If appropriate, we make an outbound web service (Service B) call to obtain data from an external source Response is returned through the Service Controller back as the response to the original service request Wally "Jay Chauhan" <[EMAIL PROTECTED]> 08/07/2008 01:37 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject Re: Axis2 Webservice called from another websiervice Hi Chris, I really appreciate you taking time to share your experiences while calling one webservice from another. I fully agree with you that this issue has never been addressed even when jira says that it is resolved. Furthermore, I also searched all of the mailing list and this issue was raised a few times before but there are no indications of going it anywhere. This is certainly is one of the bigger drawbacks of Axis2 stack and I hope Axis team does something about it before more people move away from Axis2. In the mean time after spending few days and going no where i also went another route and now i am using Messaging Middleware to make the call to second webservice, this is not the most elegant solution, but this it works and it is the only choice I have at this time. Thanks agin for your time Chris, -Jay On Thu, Aug 7, 2008 at 1:36 AM, Chris Richmond <[EMAIL PROTECTED]> wrote: Good luck with that. I had a project a few months ago where I had one proxy webservice in Axis2 hosted in tomcat that called another webservice and could NEVER get it to work. It would crash after 10 calls or so within a minute, create phantom services after calls to the proxy service side, and the method signatures of those "phantom " services exactly matched the methods on my client proxies to the 2nd service?in short..there are MAJOR in memory collisions taking place whereas the Axis2 stack gets confused. All in all, it was a miserable failure for using one service calling another, which is practically SOP in the WS world and I've done it with every other WS stack I've used. In the end I had to retool my middleware layer to use another WS stack. I believe this is a difficult problem or bug as I never got a single answer or hint from many, many mails to this and other lists that was related to the problem. This problem might have been resolved, but I never found a resolution, and the nature of the responses I got indicates to me that no one ever really understood the problem?either from my lack of ability to communicate it in several attempts or due complex systematic nature of the problem(not an easily identifiable defect). If you ever successfully get Axis2 webservice calling another webservice working and working at production levels, I'd love to hear how you did it. Chris From: Jay Chauhan [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2008 9:45 PM To: axis-user@ws.apache.org Subject: Re: Axis2 Webservice called from another websiervice Hi Lars, In order to eliminate that possibility I have created a static method ServiceBClient.callService() which works just fine if i call from stand along program, so the ports and URLs are Okay. Problem, happens only when i call it from within another service. As an interim solution I am using messaging to call one service from another , however, i always why wonder why a webservice should not be callable from each other. Thanks, -Jay On Wed, Aug 6, 2008 at 11:55 PM, Lars Ericsson <[EMAIL PROTECTED]> wrote: Hi Jay! Also, you try run your client from webserviceA and you get those error-messages! The errors are about addressing problem. have you check the if your url, and port are right? /l - Original Message From: Jay Chauhan <[EMAIL
RE: returning meaningful errors for bad xml
Well, how are you constructing the server side of this service? One of the simplest ways it to simply have your service method throw an AxisFault containing all of the Fault details. The AxisEngine will handle returning this information to the client.There are at least a couple of samples provided within the Axis2 distribution (samples/servicelifecycle and samples/userguide) that contain some examples that might be done. In these cases, the server side throws an AxisFault and the client side catches it and then displays the information. "Slepecki, Willie" <[EMAIL PROTECTED]> 07/11/2008 12:31 PM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject RE: returning meaningful errors for bad xml Ok, so how do i set it up so in my example below i tell the client exactly what went wrong, not just the famous microsoft "there was an error" message. -Original Message- From: Wally Dennis [mailto:[EMAIL PROTECTED] Sent: Fri 7/11/2008 12:24 PM To: axis-user@ws.apache.org Subject: Re: returning meaningful errors for bad xml Are you using SOAP 1.1 or 1.2? I couldn't find specific mention of this in the 1.2 spec, but according to section 6.2 of the SOAP 1.1 spec (http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383507), "In case of a SOAP error while processing the request, the SOAP HTTP server MUST issue an HTTP 500 "Internal Server Error" response and include a SOAP message in the response containing a SOAP Fault element (see section 4.4) indicating the SOAP processing error" This basically means that whenever you return a SOAP Fault, in order to conform to the specifications it MUST be done with an HTTP 500. "Slepecki, Willie" <[EMAIL PROTECTED]> 07/11/2008 11:49 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject returning meaningful errors for bad xml im building a web service using axis2 with jibx as the data binder. what i need to do is return meaningful messages when i receive a bad xml document or a doc that doesn't comply with the rules of the schema (values not included in the enumerations, etc). i just spent the past 3 days chasing down classloader issues related to trying to get weblogic-axis2-jibx working together. now, it receives the requests correctly and if something is wrong, it simply returns to the client a 500 error and logs to the log4j something like this 2008-07-11 11:13:20,406 [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' ERROR org.apache.axis2.engine.AxisEngine - Invalid date format org.apache.axis2.AxisFault: Invalid date format at com.jpmc.paycare.its.web.ITSMessageReceiverInOut.fromOM(ITSMessageReceiverInOut.java:307) at com.jpmc.paycare.its.web.ITSMessageReceiverInOut.invokeBusinessLogic(ITSMessageReceiverInOut.java:157) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(Abst bla bla bla bla i would like it to send to the client, a valid http 200, and then i guess a soap fault that indicates what exactly was wrong with the xml that was sent. so the above would return something like: soap:body soap:fault Invalid date format on field systemtime soap:fault soap:body second, using the axis-jibx system, how do i get it to validate the incoming xml with the schema first to make sure that the request fully complies before it tries to parse it out? The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly pro
Re: returning meaningful errors for bad xml
Are you using SOAP 1.1 or 1.2? I couldn't find specific mention of this in the 1.2 spec, but according to section 6.2 of the SOAP 1.1 spec (http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383507), "In case of a SOAP error while processing the request, the SOAP HTTP server MUST issue an HTTP 500 "Internal Server Error" response and include a SOAP message in the response containing a SOAP Fault element (see section 4.4) indicating the SOAP processing error" This basically means that whenever you return a SOAP Fault, in order to conform to the specifications it MUST be done with an HTTP 500. "Slepecki, Willie" <[EMAIL PROTECTED]> 07/11/2008 11:49 AM Please respond to axis-user@ws.apache.org To axis-user@ws.apache.org cc Subject returning meaningful errors for bad xml im building a web service using axis2 with jibx as the data binder. what i need to do is return meaningful messages when i receive a bad xml document or a doc that doesn't comply with the rules of the schema (values not included in the enumerations, etc). i just spent the past 3 days chasing down classloader issues related to trying to get weblogic-axis2-jibx working together. now, it receives the requests correctly and if something is wrong, it simply returns to the client a 500 error and logs to the log4j something like this 2008-07-11 11:13:20,406 [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' ERROR org.apache.axis2.engine.AxisEngine - Invalid date format org.apache.axis2.AxisFault: Invalid date format at com.jpmc.paycare.its.web.ITSMessageReceiverInOut.fromOM(ITSMessageReceiverInOut.java:307) at com.jpmc.paycare.its.web.ITSMessageReceiverInOut.invokeBusinessLogic(ITSMessageReceiverInOut.java:157) at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(Abst bla bla bla bla i would like it to send to the client, a valid http 200, and then i guess a soap fault that indicates what exactly was wrong with the xml that was sent. so the above would return something like: soap:body soap:fault Invalid date format on field systemtime soap:fault soap:body second, using the axis-jibx system, how do i get it to validate the incoming xml with the schema first to make sure that the request fully complies before it tries to parse it out? The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
