RE: AXIS2 and Tomcat 6
Hi, Thanks for your reply. Appreciate it. Apologize forgot to mention the Axis2 version we are currently using. We are still with 1.1. Has 1.1 been tested against Tomcat 6.0? Thanks again. -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: March 13, 2007 11:32 AM To: axis-user@ws.apache.org Subject: Re: AXIS2 and Tomcat 6 Hi, We haven't tested the already releases 1.1.1 with tomcat6. We'll certainly test the upcoming 1.2 with tomcat6 before we release it. thanks, dims On 3/13/07, Ho, Wen Yue <[EMAIL PROTECTED]> wrote: > > > Hi, > > any advice on the compatibility of Axis2 WS in latest Tomcat of 6.0.10 > environment? > We currently use Tomcat 5.5.20 for our Axis2 WS and thinking to > upgrade to Tomcat 6. > > Thanks in advance. > > NOTICE OF CONFIDENTIALITY > This communication including any information transmitted with it is > intended only for the use of the addressees and is confidential. > If you are not an intended recipient or responsible for delivering the > message to an intended recipient, any review, disclosure, conversion > to hard copy, dissemination, reproduction or other use of any part of > this communication is strictly prohibited, as is the taking or > omitting of any action in reliance upon this communication. > If you receive this communication in error or without authorization > please notify us immediately by return e-mail or otherwise and > permanently delete the entire communication from any computer, disk > drive, or other storage medium. > > If the above disclaimer is not properly readable, it can be found at > www.td.com/legal > > AVERTISSEMENT DE CONFIDENTIALITE > Ce courriel, ainsi que tout renseignement ci-inclus, destiné > uniquement aux destinataires susmentionnés, est confidentiel. Si vous > n'êtes pas le destinataire prévu ou un agent responsable de la > livraison de ce courriel, tout examen, divulgation, copie, impression, > reproduction, distribution, ou autre utilisation d'une partie de ce > courriel est strictement interdit de même que toute intervention ou > abstraction à cet égard. Si vous avez reçu ce message par erreur ou > sans autorisation, veuillez en aviser immédiatement l'expéditeur par > retour de courriel ou par un autre moyen et supprimer immédiatement > cette communication entière de tout système électronique. > > Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous > pouvez le consulter à www.td.com/francais/legale > -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - 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 and Tomcat 6
Hi, any advice on the compatibility of Axis2 WS in latest Tomcat of 6.0.10 environment? We currently use Tomcat 5.5.20 for our Axis2 WS and thinking to upgrade to Tomcat 6. Thanks in advance. NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous nêtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation dune partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement lexpéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
To convert OMElement into javax.xml.transform.Source object
Hi, any pointer how to convert an OMElement into an javax.xml.transform.Source object? FYI, the legacy system API only accept Source object and the built Axis2 WS is using Axiom. Thanks in advance. wen NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous nêtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation dune partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement lexpéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
calling Axis2 WebServices from a Microsoft VBA
Hi, Is it possible to call an Axis2 WebServices from a Microsoft VBA code/ script? Or is it better if the calling is made from .NET (C# or VB .Net)? FYI, I build the Axis2 WebService passing AXIOM org.apache.axiom.om.OMElement object. Any examples you can share? Thanks, wen NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous nêtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation dune partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement lexpéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
RE: [Axis2 1.1] Transport level information does not match with SOAP Message namespace URI
Hi,
Submitted to JIRA already with ID: AXIS2-2129
Thanks,
wen
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: February 7, 2007 10:32 AM
To: axis-user@ws.apache.org
Subject: Re: [Axis2 1.1] Transport level information does not match with SOAP
Message namespace URI
Need more info. When exactly are u getting this error
(sending/receiving) on client-side or server side? can you send more logs
specifically the http headers as well? Please create a JIRA bug and add these
information there.
thanks,
dims
On 2/7/07, Ho, Wen Yue <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I got the following error:
>
> 10:10:43,890 [main] DEBUG Wire : << " encoding='UTF-8'?> 10:10:43,890 [main] DEBUG StAXUtils : XMLStreamReader is
> com.sun.xml.stream.XMLReaderImpl
> 10:10:43,905 [main] DEBUG Wire : <<
> "a="http://www.w3.org/2005/08/addressing";
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> de
> r>http://www.w3.org/2005/08/addressing/none<
> r>/w
> sa:Address>urn:uuid:96F2F716A6F976F660117
> 08
> 6104378010http://www.w3.org/2005/08/addres
> si
> ng/soap/fault t> Content type should be one of
> /n text/xml/n application/x-www-form-urlencoded/n multipart/related;
> nested exception is: [\n]"
> 10:10:43,905 [main] DEBUG Wire : << "[0x9]org.apache.axis2.AxisFault:
> Content type should be one of /n text/xml/n
> application/x-www-form-urlencoded/n
> multipart/related />"
> 10:10:43,905 [main] DEBUG StAXOMBuilder : START_ELEMENT:
> {http://schemas.xmlsoap.org/soap/envelope/}Envelope:Envelope
> 10:10:43,921 [main] DEBUG StAXSOAPModelBuilder : Starting to process
> SOAP 1.1 message
> 10:10:43,921 [main] DEBUG StAXSOAPModelBuilder : Build the OMElelment
> EnvelopeBy the StaxSOAPModelBuilder
> org.apache.axis2.AxisFault: Transport level information does not match
> with SOAP Message namespace URI; nested exception is:
> org.apache.axiom.soap.SOAPProcessingException: Transport level
> information does not match with SOAP Message namespace URI
> at
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportU
> ti
> ls.java:126)
> at
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportU
> ti
> ls.java:67)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOp
> er
> ation.java:381)
> at
> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxi
> sO
> peration.java:295)
>
> It looks like the client stub class is creating a SOAP 1.2 envelope
> message, as the following:
> _operationClient.getOptions().getSoapVersionURI() returns
> http://www.w3.org/2003/05/soap-envelope (namespace SOQP1.2)
>
> But the StAXSOAPModelBuilder is trying to process it as SOAP 1.1
> message (?), refer to the above logs.
>
> Any pointers how to solve this?
> Check the wso has article on this, http://wso2.org/library/559.
> But how do you control the
> _operationClient.getOptions().getSoapVersionURI() to return the
> correct SOAP version?
>
> Thanks in advance,
> wen
>
>
>
> NOTICE OF CONFIDENTIALITY
> This communication including any information transmitted with it is
> intended only for the use of the addressees and is confidential.
> If you are not an intended recipient or responsible for delivering the
> message to an intended recipient, any review, disclosure, conversion
> to hard copy, dissemination, reproduction or other use of any part of
> this communication is strictly prohibited, as is the taking or
> omitting of any action in reliance upon this communication.
> If you receive this communication in error or without authorization
> please notify us immediately by return e-mail or otherwise and
> permanently delete the entire communication from any computer, disk
> drive, or other storage medium.
>
> If the above disclaimer is not properly readable, it can be found at
> www.td.com/legal
>
> AVERTISSEMENT DE CONFIDENTIALITE
> Ce courriel, ainsi que tout renseignement ci-inclus, destiné
> uniquement aux destinataires susmentionnés, est confidentiel. Si
> vous n'êtes pas le destinataire prévu ou un agent responsable de la
> livraison de ce courriel, tout examen, divulgation, copie, impression,
> reproduction, distribution, ou autre utilisation d'une partie de ce
> courriel est strictement interdit de même que toute intervention ou
> abstraction à cet égard. Si vous avez reçu ce message par erreur ou
> sans autorisation, veuillez en aviser immédiatement l'expéditeur par
> retour de courriel ou par un autre moyen et supprimer immédiatement
>
[Axis2 1.1] Transport level information does not match with SOAP Message namespace URI
Hi,
I got the following error:
10:10:43,890 [main] DEBUG Wire : << "http://www.w3.org/2005/08/addressing";
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>http://www.w3.org/2005/08/addressing/noneurn:uuid:96F2F716A6F976F66011708
6104378010http://www.w3.org/2005/08/addressi
ng/soap/fault
Content type should be one of /n
text/xml/n application/x-www-form-urlencoded/n multipart/related; nested
exception is: [\n]"
10:10:43,905 [main] DEBUG Wire : << "[0x9]org.apache.axis2.AxisFault:
Content type should be one of /n text/xml/n
application/x-www-form-urlencoded/n
multipart/related"
10:10:43,905 [main] DEBUG StAXOMBuilder : START_ELEMENT:
{http://schemas.xmlsoap.org/soap/envelope/}Envelope:Envelope
10:10:43,921 [main] DEBUG StAXSOAPModelBuilder : Starting to process
SOAP 1.1 message
10:10:43,921 [main] DEBUG StAXSOAPModelBuilder : Build the OMElelment
EnvelopeBy the StaxSOAPModelBuilder
org.apache.axis2.AxisFault: Transport level information does not match
with SOAP Message namespace URI; nested exception is:
org.apache.axiom.soap.SOAPProcessingException: Transport level
information does not match with SOAP Message namespace URI
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti
ls.java:126)
at
org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUti
ls.java:67)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:381)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:295)
It looks like the client stub class is creating a SOAP 1.2 envelope
message, as the following:
_operationClient.getOptions().getSoapVersionURI() returns
http://www.w3.org/2003/05/soap-envelope (namespace SOQP1.2)
But the StAXSOAPModelBuilder is trying to process it as SOAP 1.1 message
(?), refer to the above logs.
Any pointers how to solve this?
Check the wso has article on this, http://wso2.org/library/559.
But how do you control the
_operationClient.getOptions().getSoapVersionURI() to return the correct
SOAP version?
Thanks in advance,
wen
NOTICE OF CONFIDENTIALITY
This communication including any information transmitted with it is
intended only for the use of the addressees and is confidential.
If you are not an intended recipient or responsible for delivering
the message to an intended recipient, any review, disclosure,
conversion to hard copy, dissemination, reproduction or other use
of any part of this communication is strictly prohibited, as is the
taking or omitting of any action in reliance upon this communication.
If you receive this communication in error or without authorization
please notify us immediately by return e-mail or otherwise and
permanently delete the entire communication from any computer,
disk drive, or other storage medium.
If the above disclaimer is not properly readable, it can be found at
www.td.com/legal
AVERTISSEMENT DE CONFIDENTIALITE
Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
aux destinataires susmentionnés, est confidentiel. Si vous
nêtes pas le destinataire prévu ou un agent responsable de la
livraison de ce courriel, tout examen, divulgation, copie, impression,
reproduction, distribution, ou autre utilisation dune partie de ce
courriel est strictement interdit de même que toute intervention ou
abstraction à cet égard. Si vous avez reçu ce message par erreur ou
sans autorisation, veuillez en aviser immédiatement lexpéditeur par
retour de courriel ou par un autre moyen et supprimer immédiatement
cette communication entière de tout système électronique.
Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
pouvez le consulter à www.td.com/francais/legale
Limiting the number of web service instances
Hi, This might be a weird question. Is there a way to limit the number of web service instances? For example, I put my service in the "request" session scope, that means it will instantiate an instance of the service object for every single request. Is there a way to limit this? Thanks, wen NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous nêtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation dune partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement lexpéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
[AXIS2] Error when executing Java2WSDL
Hi, I've got the following error when executing Java2WSDL using AXIS2 CodeGen wizard (eclipse plugin): "an error occurred while completing process -java.lang.reflect.InvocationTargetException" Please kindly assist. Thanks in advance, wen NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous nêtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation dune partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement lexpéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
RE: Session Connection pooling in Axis2 WS
Hi Paul, If my web-service is in Request/ Session scope, which means one instance for every single request. Then if my web service on its process involves creating a singleton object (e.g.: DBConnection Pooling, etc.), will it break the singleton concept, as it will create one singleton for each single request/ service object? What will be the correct way to design this? Separate them as a separate web-services, one set in 'request' session and the singleton one set in 'application' session? Thanks in advance, wen -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: January 26, 2007 7:55 AM To: axis-user@ws.apache.org Subject: Re: Session Connection pooling in Axis2 WS Session scope is simply the lifecycle of the objects and state that Axis2 manages. So if you define request, then each new request will instantiate a new service object. If you define transportsession, then Axis2 will use HTTP cookies. Each client will re-use the same service object. If you define soapsession, it will do the same thing, except using SOAP headers instead of cookies. If you define application, then you will have a single service object for all requests. It is up to you to make sure that youre object can support the right threading model for application. For request you need not worry about thread safety because each request has its own service object. Paul On 1/26/07, Stadelmann Josef <[EMAIL PROTECTED]> wrote: > Sanjiva > > What is session scope? > > you have to define one of > scope=request > scope=transportsession > scope=soapsession > scope=application > > which one do you mean? > Josef > > -Ursprüngliche Nachricht- > Von: Sanjiva Weerawarana [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 25. Januar 2007 06:29 > An: axis-user@ws.apache.org > Betreff: RE: Session Connection pooling in Axis2 WS > > > It depends on the "scope" of the service .. if its deployed in > application scope then only one instance is created. If its in session > scope then its one instance per session and so on. > > See: http://wso2.org/library/231 > > Sanjiva. > > On Wed, 2007-01-24 at 11:45 -0500, Ho, Wen Yue wrote: > > Hi, > > > > I think my question is not clear and confusing. > > Sorry, a newbie here :-) > > > > Please allow me to re-phrase my question. > > How does Axis2 handle multiple request to the webservices? > > AFAIK, Axis2 is a servlet and by default, a (single) servlet should > > be able to handle multiple HTTP requests. > > For each incoming request session, will axis (servlet) instantiate > > just one instance of the websrvice class for multiple requests? > > Or it will instantiate one webservice object for each request? > > > > Your assistance will be highly appreciated. > > Thank you. > > > > > > > > > > > > __ > > From: Ho, Wen Yue [mailto:[EMAIL PROTECTED] > > Sent: January 23, 2007 2:26 PM > > To: axis-user@ws.apache.org > > Subject: Session Connection pooling in Axis2 WS > > > > > > > > Hi, > > > > I have a legacy system that provides an API to access the system > > thru their own Session object. > > I need to pool this session objects within my web services developed > > using Axis2. > > > > Correct me if I'm wrong. > > AFAIK, Axis2 by default will make one thread per request to the web > > service. > > I think this means singleton class won't work, since one thread will > > instantiate one singleton. > > Any advice on how to do this? > > > > Thanks in advance. > > > > > > > > NOTICE OF CONFIDENTIALITY > > This communication including any information transmitted with it is > > intended only for the use of the addressees and is confidential. > > If you are not an intended recipient or responsible for delivering > > the message to an intended recipient, any review, disclosure, > > conversion to hard copy, dissemination, reproduction or other use of > > any part of this communication is strictly prohibited, as is the > > taking or omitting of any action in reliance upon this communication. > > If you receive this communication in error or without authorization > > please notify us immediately by return e-mail or otherwise and > > permanently delete the entire communication from any computer, disk > > drive, or other storage medium. > > > > If the above disclaimer is not properly readable, it can be found at > > www.td.com/legal > > > > AVERTISSEMENT DE CONFIDENTIALITE
RE: Debugging Axis2 in Tomcat
Jeff, Thanks for the tips. I manage debug my Axis2 WS in Tomcat using eclipse now. But I still am having a problem though. When the debugger stopping at the server side code it doesn't highlight the line where it is stopping. The Debug Call stacks is saying "line: not available [local variables unavailable]". Any experience on this issue? Thanks again, Wen -Original Message- From: Jeff Greif [mailto:[EMAIL PROTECTED] Sent: January 24, 2007 5:27 PM To: axis-user@ws.apache.org Subject: Re: Debugging Axis2 in Tomcat Ho, Wen Yue wrote: > Hi, > > Any pointers on how to debug Axis2 WebService Application in Tomcat? > > In Eclipse, you can launch Tomcat for debugging or attach to a running Tomcat. Then you debug the Axis code in the normal way. Google for "eclipse launch tomcat debug" Jeff - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous nêtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation dune partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement lexpéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
Debugging Axis2 in Tomcat
Hi, Any pointers on how to debug Axis2 WebService Application in Tomcat? Sysdeo turns out to be not working anymore,... with the following error message: ERROR: JDWP unable to get necessary JVMTI capabilities. ["debugInit.c",L279] Thanks in advance, wen NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous nêtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation dune partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement lexpéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
RE: Session Connection pooling in Axis2 WS
Hi, I think my question is not clear and confusing. Sorry, a newbie here :-) Please allow me to re-phrase my question. How does Axis2 handle multiple request to the webservices? AFAIK, Axis2 is a servlet and by default, a (single) servlet should be able to handle multiple HTTP requests. For each incoming request session, will axis (servlet) instantiate just one instance of the websrvice class for multiple requests? Or it will instantiate one webservice object for each request? Your assistance will be highly appreciated. Thank you. From: Ho, Wen Yue [mailto:[EMAIL PROTECTED] Sent: January 23, 2007 2:26 PM To: axis-user@ws.apache.org Subject: Session Connection pooling in Axis2 WS Hi, I have a legacy system that provides an API to access the system thru their own Session object. I need to pool this session objects within my web services developed using Axis2. Correct me if I'm wrong. AFAIK, Axis2 by default will make one thread per request to the web service. I think this means singleton class won't work, since one thread will instantiate one singleton. Any advice on how to do this? Thanks in advance. NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous n'êtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation d'une partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement l'expéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
RE: new aar file is not recognized [PROBLEM SOLVED]
please ignore this. I fixed it. Just do some clean-up and it solve the problems. From: Ho, Wen Yue [mailto:[EMAIL PROTECTED] Sent: January 23, 2007 5:38 PM To: axis-user@ws.apache.org Subject: new aar file is not recognized Hi, I (re-) created my aar web services file and dropped it into [TOMCAT_HOME]\webapps\axis2\WEB-INF\services. But after I restarted tomcat, the service is still behaving like the previous version. Any suggestion to refresh start the service? Thanks in advance. NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous n'êtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation d'une partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement l'expéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
new aar file is not recognized
Hi, I (re-) created my aar web services file and dropped it into [TOMCAT_HOME]\webapps\axis2\WEB-INF\services. But after I restarted tomcat, the service is still behaving like the previous version. Any suggestion to refresh start the service? Thanks in advance. NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous nêtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation dune partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement lexpéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
Session Connection pooling in Axis2 WS
Hi, I have a legacy system that provides an API to access the system thru their own Session object. I need to pool this session objects within my web services developed using Axis2. Correct me if I'm wrong. AFAIK, Axis2 by default will make one thread per request to the web service. I think this means singleton class won't work, since one thread will instantiate one singleton. Any advice on how to do this? Thanks in advance. NOTICE OF CONFIDENTIALITY This communication including any information transmitted with it is intended only for the use of the addressees and is confidential. If you are not an intended recipient or responsible for delivering the message to an intended recipient, any review, disclosure, conversion to hard copy, dissemination, reproduction or other use of any part of this communication is strictly prohibited, as is the taking or omitting of any action in reliance upon this communication. If you receive this communication in error or without authorization please notify us immediately by return e-mail or otherwise and permanently delete the entire communication from any computer, disk drive, or other storage medium. If the above disclaimer is not properly readable, it can be found at www.td.com/legal AVERTISSEMENT DE CONFIDENTIALITE Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement aux destinataires susmentionnés, est confidentiel. Si vous nêtes pas le destinataire prévu ou un agent responsable de la livraison de ce courriel, tout examen, divulgation, copie, impression, reproduction, distribution, ou autre utilisation dune partie de ce courriel est strictement interdit de même que toute intervention ou abstraction à cet égard. Si vous avez reçu ce message par erreur ou sans autorisation, veuillez en aviser immédiatement lexpéditeur par retour de courriel ou par un autre moyen et supprimer immédiatement cette communication entière de tout système électronique. Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous pouvez le consulter à www.td.com/francais/legale
