RE: Web service URL
Hi Deepal, I tried by editing the axis2.xml to add my id address - but I still got this error: Unknown exception :::org.apache.axis2.AxisFault: namespace mismatch require http://localhost:8081/NPCWebApp/services/NPCWebService/xsd found http://128.96.190.123:8081/NPCWebApp/services/NPCWebService/xsd org.apache.axis2.AxisFault: namespace mismatch require http://localhost:8081/NPCWebApp/services/NPCWebService/xsd found http://128.96.190.123:8081/NPCWebApp/services/NPCWebService/xsd Please help. Asmita -Original Message- From: Deepal jayasinghe [mailto:[EMAIL PROTECTED] Sent: Monday, November 10, 2008 11:09 AM To: axis-user@ws.apache.org Subject: Re: Web service URL > Hi Deepal, > > Even I provide the URL in targetNamespace and SchemaNamespace of my > services.xml Well targetNamespace and SchemaNamespace are different than the service URL in the WSDL service section. You can have same TagetNameSpace and deploy in multiple servers , then each get different service address. > - can I edit the axis2.xml and it will take in the hostname from axis2.xml > accordingly? > Yes , if you are running behind a proxy then it is good idea to edit he host name in axis2.xml > Is it a good practice to provide the targetNamespace and SchemaNamespace in > services.xml? > Yes , for the service. > Thanks so much, > Asmita > > -Original Message- > From: Deepal jayasinghe [mailto:[EMAIL PROTECTED] > Sent: Monday, November 10, 2008 10:54 AM > To: axis-user@ws.apache.org > Subject: Re: Web service URL > > Attharkar, Asmita wrote: > >> Hi all, >> >> >> >> I would like to know what different factors are accounted when web >> service address URL is created, I do not have my WSDL provided. Axis2 >> generates it for me. >> >> I want to be able to change the hostname IP address dynamically. >> >> > Well the address is generated using the incoming request. You can change > that by editing axis.xml > change the host name parameter. > > Deepal > >> >> Thanks, >> >> Asmita >> >> >> >> >> >> >> >> > > > -- > Thank you! > > > http://blogs.deepal.org > > > - > 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] > > > -- Thank you! http://blogs.deepal.org - 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: Web service URL
Thanks for the responses Deepal, Can I also add the port in the axis2.xml for the transport ins - http so my webservice will be available at: http://hostname:portnumber/MyWebApp/services/MyService where hostname and port number are taken from axis2.xml? [transport receiver for http?] Thanks, Asmita -Original Message- From: Deepal jayasinghe [mailto:[EMAIL PROTECTED] Sent: Monday, November 10, 2008 11:09 AM To: axis-user@ws.apache.org Subject: Re: Web service URL > Hi Deepal, > > Even I provide the URL in targetNamespace and SchemaNamespace of my > services.xml Well targetNamespace and SchemaNamespace are different than the service URL in the WSDL service section. You can have same TagetNameSpace and deploy in multiple servers , then each get different service address. > - can I edit the axis2.xml and it will take in the hostname from axis2.xml > accordingly? > Yes , if you are running behind a proxy then it is good idea to edit he host name in axis2.xml > Is it a good practice to provide the targetNamespace and SchemaNamespace in > services.xml? > Yes , for the service. > Thanks so much, > Asmita > > -Original Message- > From: Deepal jayasinghe [mailto:[EMAIL PROTECTED] > Sent: Monday, November 10, 2008 10:54 AM > To: axis-user@ws.apache.org > Subject: Re: Web service URL > > Attharkar, Asmita wrote: > >> Hi all, >> >> >> >> I would like to know what different factors are accounted when web >> service address URL is created, I do not have my WSDL provided. Axis2 >> generates it for me. >> >> I want to be able to change the hostname IP address dynamically. >> >> > Well the address is generated using the incoming request. You can change > that by editing axis.xml > change the host name parameter. > > Deepal > >> >> Thanks, >> >> Asmita >> >> >> >> >> >> >> >> > > > -- > Thank you! > > > http://blogs.deepal.org > > > - > 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] > > > -- Thank you! http://blogs.deepal.org - 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: Web service URL
Attharkar, Asmita wrote: > > Hi all, > > > > I would like to know what different factors are accounted when web > service address URL is created, I do not have my WSDL provided. Axis2 > generates it for me. > > I want to be able to change the hostname IP address dynamically. > Well the address is generated using the incoming request. You can change that by editing axis.xml change the host name parameter. Deepal > > > > Thanks, > > Asmita > > > > > > > -- Thank you! http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Web service URL
> Hi Deepal, > > Even I provide the URL in targetNamespace and SchemaNamespace of my > services.xml Well targetNamespace and SchemaNamespace are different than the service URL in the WSDL service section. You can have same TagetNameSpace and deploy in multiple servers , then each get different service address. > - can I edit the axis2.xml and it will take in the hostname from axis2.xml > accordingly? > Yes , if you are running behind a proxy then it is good idea to edit he host name in axis2.xml > Is it a good practice to provide the targetNamespace and SchemaNamespace in > services.xml? > Yes , for the service. > Thanks so much, > Asmita > > -Original Message- > From: Deepal jayasinghe [mailto:[EMAIL PROTECTED] > Sent: Monday, November 10, 2008 10:54 AM > To: axis-user@ws.apache.org > Subject: Re: Web service URL > > Attharkar, Asmita wrote: > >> Hi all, >> >> >> >> I would like to know what different factors are accounted when web >> service address URL is created, I do not have my WSDL provided. Axis2 >> generates it for me. >> >> I want to be able to change the hostname IP address dynamically. >> >> > Well the address is generated using the incoming request. You can change > that by editing axis.xml > change the host name parameter. > > Deepal > >> >> Thanks, >> >> Asmita >> >> >> >> >> >> >> >> > > > -- > Thank you! > > > http://blogs.deepal.org > > > - > 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] > > > -- Thank you! http://blogs.deepal.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Web service URL
Hi Deepal, Even I provide the URL in targetNamespace and SchemaNamespace of my services.xml - can I edit the axis2.xml and it will take in the hostname from axis2.xml accordingly? Is it a good practice to provide the targetNamespace and SchemaNamespace in services.xml? Thanks so much, Asmita -Original Message- From: Deepal jayasinghe [mailto:[EMAIL PROTECTED] Sent: Monday, November 10, 2008 10:54 AM To: axis-user@ws.apache.org Subject: Re: Web service URL Attharkar, Asmita wrote: > > Hi all, > > > > I would like to know what different factors are accounted when web > service address URL is created, I do not have my WSDL provided. Axis2 > generates it for me. > > I want to be able to change the hostname IP address dynamically. > Well the address is generated using the incoming request. You can change that by editing axis.xml change the host name parameter. Deepal > > > > Thanks, > > Asmita > > > > > > > -- Thank you! http://blogs.deepal.org - 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]
Web service URL
Hi all, I would like to know what different factors are accounted when web service address URL is created, I do not have my WSDL provided. Axis2 generates it for me. I want to be able to change the hostname IP address dynamically. Thanks, Asmita
Re: web service URL and services.xml
Hi Asmita, Is it mandatory for you to specify service endpoint as the targetnamespace in your services.xml? Regards Charitha http://charithaka.blogspot.com Attharkar, Asmita wrote: Hi, I have a web service which is to be deployed on different machines. And should be ofcourse be accessible from anywhere. However I have to give the service targetNamespace in the services.xml – which is a URL for the webservice. For eg: targetNamespace="http://localhost:8081/MyWebApp/services/MyWebService";> schemaNamespace="http://localhost:8081/MyWebApp/services/MyWebService/xsd"/> are the first two lines in my services.xml. I have my service bundled in aar file and deployed in webapp. When I try to access it using http://128.90.190.123:8081/MyWebApp/services/MyWebService I get the following error: Unknown exception :::org.apache.axis2.AxisFault: namespace mismatch require http://localhost:8081/MyWebApp/services/MyWebService/xsd found http://128.90.190.123:8081/MyWebApp/services/MyWebService/xsd org.apache.axis2.AxisFault: namespace mismatch require http://localhost:8081/MyWebApp/services/MyWebService/xsd found http://128.90.190.123:8081/MyWebApp/services/MyWebService/xsd How is it possible for me to have webservice URL that can be modified based on the Ip address in the URL. Right now the only way I can access this web service is from the localhost. I should be able to access webservice from any machine and should be deployable on any machine irrespective of the URL. Can I edit this webservice URL without editing my services.xml and rebundling the aar file. Any help is appreciated! Thanks, Asmita (Tel) 732-699-4657 | 4B566 | Telcordia Technologies | Piscataway NJ 08854 No virus found in this incoming message. Checked by AVG. Version: 7.5.549 / Virus Database: 270.8.6/1768 - Release Date: 11/4/2008 9:38 PM - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
web service URL and services.xml
Hi, I have a web service which is to be deployed on different machines. And should be ofcourse be accessible from anywhere. However I have to give the service targetNamespace in the services.xml - which is a URL for the webservice. For eg: http://localhost:8081/MyWebApp/services/MyWebService";> http://localhost:8081/MyWebApp/services/MyWebService/xsd"/> are the first two lines in my services.xml. I have my service bundled in aar file and deployed in webapp. When I try to access it using http://128.90.190.123:8081/MyWebApp/services/MyWebService I get the following error: Unknown exception :::org.apache.axis2.AxisFault: namespace mismatch require http://localhost:8081/MyWebApp/services/MyWebService/xsd found http://128.90.190.123:8081/MyWebApp/services/MyWebService/xsd org.apache.axis2.AxisFault: namespace mismatch require http://localhost:8081/MyWebApp/services/MyWebService/xsd found http://128.90.190.123:8081/MyWebApp/services/MyWebService/xsd How is it possible for me to have webservice URL that can be modified based on the Ip address in the URL. Right now the only way I can access this web service is from the localhost. I should be able to access webservice from any machine and should be deployable on any machine irrespective of the URL. Can I edit this webservice URL without editing my services.xml and rebundling the aar file. Any help is appreciated! Thanks, Asmita (Tel) 732-699-4657 | 4B566 | Telcordia Technologies | Piscataway NJ 08854
Re: web service URL
Hey, On Wed, Sep 10, 2008 at 10:49 AM, Attharkar, Asmita <[EMAIL PROTECTED]>wrote: > Ok I got my URL to work .../mycompany/services by renaming the axis2.war > file to mycompany.war and then deploying the service into exploded mycompany > folder. > So got the http://ipaddress:port/mycompany/services/myservice to work. > > The Questions now: > > 1. There are several JSPs and components in axis2-web. > What can be eliminated to still be able to work with web services > properly? You can remove all the jsps and your web service should be fine. > > > 2. The web service works alright with no issues but the URL when typed into > browser - instead of giving 'happy' page it throws error saying No End Point > reference and WSA null. I need to have this URL return no error as this is > the only way to really check on the fly if the service is running or down. What is the url you typed in the browser? The error says, the server couldn't fine the operation. Check here for more information : http://wso2.org/library/176 -- With Mettha, Eran Chinthaka Health is the greatest gift; contentment is the greatest wealth; trusting is the best relationship; nirvana is the highest joy. - Dhammapada
RE: web service URL
Ok I got my URL to work .../mycompany/services by renaming the axis2.war file to mycompany.war and then deploying the service into exploded mycompany folder. So got the http://ipaddress:port/mycompany/services/myservice to work. The Questions now: 1. There are several JSPs and components in axis2-web. What can be eliminated to still be able to work with web services properly? 2. The web service works alright with no issues but the URL when typed into browser - instead of giving 'happy' page it throws error saying No End Point reference and WSA null. I need to have this URL return no error as this is the only way to really check on the fly if the service is running or down. Thanks, Asmita -Original Message- From: Qureshi, Affan [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 09, 2008 4:42 PM To: 'axis-user@ws.apache.org' Subject: RE: web service URL Did you try changing the name of the folder "axis2" to "mycompany" in the webapps dir? There are other ways to map context roots in tomcat too via configuration in server.xml I think. Affan -Original Message- From: Attharkar, Asmita [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 09, 2008 1:54 PM To: axis-user@ws.apache.org Subject: web service URL Hi there, When I deploy the web service in the exploded axis2 in tomcat, The url that I could use with this kind of deployment is http://ipaddress:port/axis2/services/myservice but I want to use (and I am sure most developers do) http://ipaddress:port/mycompany/services/myservice What do I need to do so I can replace 'axis2' in the above URL with 'mycompany'? I still want to use the easy deployment of my webservice in axis2 in tomcat. Thanks so much for you help in this matter. Thanks, Asmita - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail and files transmitted with it are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you are not one of the named recipient(s) or otherwise have reason to believe that you received this message in error, please immediately notify sender by e-mail, and destroy the original message. Thank You. - 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: web service URL
Did you try changing the name of the folder "axis2" to "mycompany" in the webapps dir? There are other ways to map context roots in tomcat too via configuration in server.xml I think. Affan -Original Message- From: Attharkar, Asmita [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 09, 2008 1:54 PM To: axis-user@ws.apache.org Subject: web service URL Hi there, When I deploy the web service in the exploded axis2 in tomcat, The url that I could use with this kind of deployment is http://ipaddress:port/axis2/services/myservice but I want to use (and I am sure most developers do) http://ipaddress:port/mycompany/services/myservice What do I need to do so I can replace 'axis2' in the above URL with 'mycompany'? I still want to use the easy deployment of my webservice in axis2 in tomcat. Thanks so much for you help in this matter. Thanks, Asmita - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail and files transmitted with it are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you are not one of the named recipient(s) or otherwise have reason to believe that you received this message in error, please immediately notify sender by e-mail, and destroy the original message. Thank You. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
web service URL
Hi there, When I deploy the web service in the exploded axis2 in tomcat, The url that I could use with this kind of deployment is http://ipaddress:port/axis2/services/myservice but I want to use (and I am sure most developers do) http://ipaddress:port/mycompany/services/myservice What do I need to do so I can replace 'axis2' in the above URL with 'mycompany'? I still want to use the easy deployment of my webservice in axis2 in tomcat. Thanks so much for you help in this matter. Thanks, Asmita - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 1.4: wsdl2java client, doesn't throw exception on bad service url?
For a Axis (1) wsdl generated stub/proxy to an RPC service anyone guess
why a failure like a bad service URL will log but not throw an exception
from the proxy.serviceMethod() ?
Tnx curt
Curt Smith
[EMAIL PROTECTED]
404-499-7194
From: Smith, Curtis
Sent: Tuesday, September 11, 2007 1:49 PM
To: 'axis-user@ws.apache.org'
Subject: 1.4: wsdl2java client, doesn't throw exception on bad service
url?
Greetings, My need is to drop in a usable SOAP RPC client into a
service that has JAX-WS client calls. I gave up on SOAP-RPC client side
with the 3rd party vendor's wsdl. Axis 1.4 parsed and generated client
stubs and classes no problem.
One problem I noticed is that when testing with a service URL to an up
http service but wrong soap service. The log indicates a bad service
but there's no exception thrown to the bind.serviceCall()?
Any helps or suggestions for smarter approach? Terse client code
below.
Tnx, curt
URL portAddress = new URL(corbaReq.header.url);
binding = (com.twowire.services.LSServicesSoapBindingStub)
new
com.twowire.services.LSServicesServiceLocator().getLSServices(portAddres
s);
try {
// Set the SOAP call parameters and make the call
//
// This service call returns void or exception
binding.createAccount(new java.lang.String(), 0, new
java.lang.String(), new java.lang.String(), new java.lang.String(), new
java.lang.String(), new java.lang.String(), new java.lang.String(), new
java.lang.String(), new java.lang.String(), new java.lang.String(), new
java.lang.String(), new java.lang.String(), new java.lang.String());
//=== This method does not return a message. Just
exception if an error.
}
catch (com.twowire.services.NotUniqueCPEIdentifierException
e1) {
// Handle error, set error status in corba response.
logger.debug("soap error, exc="+e1.dumpToString());
}
catch (com.twowire.services.PermissionDeniedException e2) {
// Handle error, set error status in corba response.
logger.debug("soap error, exc="+e2.dumpToString());
}
catch (com.twowire.services.exception.ServiceException e3) {
// Handle error, set error status in corba response.
logger.debug("soap error, exc="+e3.dumpToString());
}
A bogus portAddress does not throw an exception here.
Thanks, curt
Curt Smith
[EMAIL PROTECTED]
404-499-7194
*
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential, proprietary, and/or privileged
material. Any review, retransmission, dissemination or other use of, or taking
of any action in reliance upon this information by persons or entities other
than the intended recipient is prohibited. If you received this in error,
please contact the sender and delete the material from all computers. GA623
1.4: wsdl2java client, doesn't throw exception on bad service url?
Greetings, My need is to drop in a usable SOAP RPC client into a
service that has JAX-WS client calls. I gave up on SOAP-RPC client side
with the 3rd party vendor's wsdl. Axis 1.4 parsed and generated client
stubs and classes no problem.
One problem I noticed is that when testing with a service URL to an up
http service but wrong soap service. The log indicates a bad service
but there's no exception thrown to the bind.serviceCall()?
Any helps or suggestions for smarter approach? Terse client code
below.
Tnx, curt
URL portAddress = new URL(corbaReq.header.url);
binding = (com.twowire.services.LSServicesSoapBindingStub)
new
com.twowire.services.LSServicesServiceLocator().getLSServices(portAddres
s);
try {
// Set the SOAP call parameters and make the call
//
// This service call returns void or exception
binding.createAccount(new java.lang.String(), 0, new
java.lang.String(), new java.lang.String(), new java.lang.String(), new
java.lang.String(), new java.lang.String(), new java.lang.String(), new
java.lang.String(), new java.lang.String(), new java.lang.String(), new
java.lang.String(), new java.lang.String(), new java.lang.String());
//=== This method does not return a message. Just
exception if an error.
}
catch (com.twowire.services.NotUniqueCPEIdentifierException
e1) {
// Handle error, set error status in corba response.
logger.debug("soap error, exc="+e1.dumpToString());
}
catch (com.twowire.services.PermissionDeniedException e2) {
// Handle error, set error status in corba response.
logger.debug("soap error, exc="+e2.dumpToString());
}
catch (com.twowire.services.exception.ServiceException e3) {
// Handle error, set error status in corba response.
logger.debug("soap error, exc="+e3.dumpToString());
}
A bogus portAddress does not throw an exception here.
Thanks, curt
Curt Smith
[EMAIL PROTECTED]
404-499-7194
*
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential, proprietary, and/or privileged
material. Any review, retransmission, dissemination or other use of, or taking
of any action in reliance upon this information by persons or entities other
than the intended recipient is prohibited. If you received this in error,
please contact the sender and delete the material from all computers. GA622
Re: service url for invoking service
gSOAP should be sending the request to the URL specified in the location attribute in the WSDL service port. Make sure that this attribute value is specified properly. Anne On 10/4/06, Z Chen <[EMAIL PROTECTED]> wrote: Hi, I am deploying several web services with Axis2 and they have different service name. Using Axis2 generated Stub classes, I will give the service url as http://localhost:8080/axis2/services/MyService1 and http://localhost:8080/axis2/services/MyService2, and they all work fine. But we have remote client that use gSOAP library and they are sending request to http://localhost:8080/axis2/services and they are expecting Axis2 to figure out which service to go by the SOAPActionHeader, whose the values is defined in wsdl file. But it looks like Axis2 can not figure it out and nothing happens. Does anybody have a solution for that ? Thanks John __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - 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]
service url for invoking service
Hi, I am deploying several web services with Axis2 and they have different service name. Using Axis2 generated Stub classes, I will give the service url as http://localhost:8080/axis2/services/MyService1 and http://localhost:8080/axis2/services/MyService2, and they all work fine. But we have remote client that use gSOAP library and they are sending request to http://localhost:8080/axis2/services and they are expecting Axis2 to figure out which service to go by the SOAPActionHeader, whose the values is defined in wsdl file. But it looks like Axis2 can not figure it out and nothing happens. Does anybody have a solution for that ? Thanks John __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] How to get the service URL and method in handler?
Samisa Abeysinghe wrote: > Forwarding with correct prefix. > > hi all, > > I want to use handler to log which service the client is accessing, > for example the service URL, name and method, but in the handler > invoke() method, there is only the MessageContext that can be used. > (I tried most the mc.getXXX() method but no one is helpful to get > information above.) > Put a handler after the dispatch phase. Getting service name : msgContext.getServiceContext().getAxisService().getName() Getting Operation name : msgContext.getOperationContext().getAxisOperation().getName() Getting service url : msgContext.getTo().getAddress() -- Chinthaka signature.asc Description: OpenPGP digital signature
Re: How to get the service URL and method in handler?
hi Michele, Thank you for your help. I tried... I think these methods could be used in Axis2 but not Axis1.4. :( Sorry for confused title ! - sukie - Original Message - From: "Michele Mazzucco" <[EMAIL PROTECTED]> To: Sent: Thursday, June 08, 2006 5:41 PM Subject: Re: How to get the service URL and method in handler? > mc.getAxisService() gets the target service (.getEndpoint() returns the > target service endpoint). > mc.getAxisOperation() gets the axis operation > > You have to put your handler after the system handlers, since these > values are filled into the transport/dispatch phase. > > > Michele > > 蘇 軼（CEC） wrote: > > hi all, > > > > I want to use handler to log which service the client is accessing, > > for example the service URL, name and method, but in the handler > > invoke() method, there is only the MessageContext that can be used. > > (I tried most the mc.getXXX() method but no one is helpful to get > > information above.) > > > > I think I can force the client setting these informations to the header > > of soap message, but Is there any better way to implement it? > > > > Any help or web resources would be greatly appreciated ! > > > > - sukie > > > > - > > 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: How to get the service URL and method in handler?
mc.getAxisService() gets the target service (.getEndpoint() returns the target service endpoint). mc.getAxisOperation() gets the axis operation You have to put your handler after the system handlers, since these values are filled into the transport/dispatch phase. Michele 蘇 軼（CEC） wrote: > hi all, > > I want to use handler to log which service the client is accessing, > for example the service URL, name and method, but in the handler > invoke() method, there is only the MessageContext that can be used. > (I tried most the mc.getXXX() method but no one is helpful to get > information above.) > > I think I can force the client setting these informations to the header > of soap message, but Is there any better way to implement it? > > Any help or web resources would be greatly appreciated ! > > - sukie > > - > 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] How to get the service URL and method in handler?
Forwarding with correct prefix. hi all, I want to use handler to log which service the client is accessing, for example the service URL, name and method, but in the handler invoke() method, there is only the MessageContext that can be used. (I tried most the mc.getXXX() method but no one is helpful to get information above.) I think I can force the client setting these informations to the header of soap message, but Is there any better way to implement it? Any help or web resources would be greatly appreciated ! - sukie - 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]
How to get the service URL and method in handler?
hi all, I want to use handler to log which service the client is accessing, for example the service URL, name and method, but in the handler invoke() method, there is only the MessageContext that can be used. (I tried most the mc.getXXX() method but no one is helpful to get information above.) I think I can force the client setting these informations to the header of soap message, but Is there any better way to implement it? Any help or web resources would be greatly appreciated ! - sukie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: service url
On Tue, 30 Aug 2005, Chris Nappin wrote: > > Still, I feel that AXIS should accept any URL that WSDL developer > defines > > as the SOAP address, provided it looks like > > > http://host:unix-port/axis/services//PORT-NAME > > > Perhaps, this could be a feature request! :-) > > > J2EE gets in the way here though. Have you tried simply add extra > mappings for the AxisServlet to your web.xml? > > Are you sure J2EE is getting in the way here ? If you see the URL I propose : http://host:unix-port/axis/services//PORT-NAME this includes "/axis/services/". I think (hope I am not wrong) that this part is enough to direct Tomcat to delegate the incoming message to AXIS. What AXIS does with the rest of the URL "/PORT-NAME" is entirely upto AXIS. regards, Deepak S Patwardhan.
RE: service url
> Still, I feel that AXIS should accept any URL that WSDL developer defines > as the SOAP address, provided it looks like > http://host:unix-port/axis/services//PORT-NAME > Perhaps, this could be a feature request! :-) J2EE gets in the way here though. Have you tried simply add extra mappings for the AxisServlet to your web.xml? CONFIDENTIALITY & PRIVILEGE NOTICE This e-mail is confidential to its intended recipient. It may also be privileged. Neither the confidentiality nor any privilege attaching to this e-mail is waived lost or destroyed by reason that it has been mistakenly transmitted to a person or entity other than its intended recipient. If you are not the intended recipient please notify us immediately by telephone or fax at the numbers provided above or e-mail by Reply To Author and return the printed e-mail to us by post at our expense. We believe, but do not warrant, that this e-mail and any attachments are virus-free, but you should check. We may monitor traffic data of both business and personal e-mails. We are not liable for any opinions expressed by the sender where this is a non-business e-mail. If you do not receive all the message, or if you have difficulty with the transmission, please telephone us immediately.
Re: service url
On Mon, 29 Aug 2005, Javier Gonzalez wrote: > Deploy them using server-config.wsdd, and use your naming hierachy. > > style="message" use="literal"> > ... > > > and you will then have the url > "http:services/foo/bar/myFooBarService" for > accesing your web service. > > Hope that helps, > > Javier. > HI all, Thanks a lot, Javier. I changed the attribute name of element service in deploy.wsdd and undeploy.wsdd and it worked. I also found out that if you define your port itself of the form "xyz/abc" in the service definition, AXIS has no problems. (if you can change the WSDL) Still, I feel that AXIS should accept any URL that WSDL developer defines as the SOAP address, provided it looks like http://host:unix-port/axis/services//PORT-NAME Perhaps, this could be a feature request! :-) thanks, Deepak S Patwardhan. > > > > > -- > > On Mon, 29 Aug 2005, Guy Rixon wrote: > > > > > WS-I basic profile expects developers to define one port per service. I > > > think > > > the underlying philosphy is that each SOAP endpoint has one remote object > > > and > > > all the operations on that endpoint work as methods on that one object. > > > > > > I agree that this is limiting. It's often nice to aggregate ports. > > > > > > On Mon, 29 Aug 2005, Deepak S Patwardhan wrote: > > > > > > > HI all, > > > > > > > > My question is about the way axis makes a service URL. Normally, you > > > > see a > > > > URL like the following : > > > > > > > > http://host:unix-port/axis/services/PORT-NAME > > > > > > > > where, PORT-NAME is a port defined in the service element. > > > > > > > > Is it possible that the service URL be like this : > > > > > > > > http://host:unix-port/axis/services/SERVICE-NAME/PORT-NAME > > > > > > > > where SERVICE-NAME is the name of the service ? (attribute name of > > > > service > > > > element) > > > > > > > > This would look more logical, especially when a service contains > > > > multiple > > > > ports. I tried specifying such URLs in the WSDL but axis overrides it. > > > > (please see the attached WSDL.) > > > > > > > > WHen I deploy my service (service Primality, two ports, a) Prime - to > > > > check whether a number is prime, b) CoPrime - to check whether two > > > > numbers > > > > are coprime), and when I see the list of deployed services, I expected a > > > > listing like this > > > > > > > > * Primality > > > >-Prime > > > > - isPrime > > > >-CoPrime > > > > - areCoPrime > > > > > > > > But, what is displayed is as if there are two services, Prime and > > > > CoPrime. > > > > > > > > * Prime > > > >- isPrime > > > > * CoPrimes > > > >- areCoPrime > > > > > > > > It seems as if axis elevates a PORT to a service. What's the > > > > design decision behind this ? (And if you tell me that AXIS expects > > > > developers to define one port per service, I would be pretty p***ed off) > > > > > > > > thanks, > > > > Deepak S Patwardhan. > > > > > > > > >
Re: service url
> Anyway, so now, my question is how to host two services, which are defined > in two separate WSDL files, which can't be edited (obviously), and happen > to literally share a port name. Deploy them using server-config.wsdd, and use your naming hierachy. ... and you will then have the url "http:services/foo/bar/myFooBarService" for accesing your web service. Hope that helps, Javier. > > thanks, > Deepak S Patwardhan. > -- > On Mon, 29 Aug 2005, Guy Rixon wrote: > > > WS-I basic profile expects developers to define one port per service. I > > think > > the underlying philosphy is that each SOAP endpoint has one remote object > > and > > all the operations on that endpoint work as methods on that one object. > > > > I agree that this is limiting. It's often nice to aggregate ports. > > > > On Mon, 29 Aug 2005, Deepak S Patwardhan wrote: > > > > > HI all, > > > > > > My question is about the way axis makes a service URL. Normally, you see a > > > URL like the following : > > > > > > http://host:unix-port/axis/services/PORT-NAME > > > > > > where, PORT-NAME is a port defined in the service element. > > > > > > Is it possible that the service URL be like this : > > > > > > http://host:unix-port/axis/services/SERVICE-NAME/PORT-NAME > > > > > > where SERVICE-NAME is the name of the service ? (attribute name of service > > > element) > > > > > > This would look more logical, especially when a service contains multiple > > > ports. I tried specifying such URLs in the WSDL but axis overrides it. > > > (please see the attached WSDL.) > > > > > > WHen I deploy my service (service Primality, two ports, a) Prime - to > > > check whether a number is prime, b) CoPrime - to check whether two numbers > > > are coprime), and when I see the list of deployed services, I expected a > > > listing like this > > > > > > * Primality > > >-Prime > > > - isPrime > > >-CoPrime > > > - areCoPrime > > > > > > But, what is displayed is as if there are two services, Prime and CoPrime. > > > > > > * Prime > > >- isPrime > > > * CoPrimes > > >- areCoPrime > > > > > > It seems as if axis elevates a PORT to a service. What's the > > > design decision behind this ? (And if you tell me that AXIS expects > > > developers to define one port per service, I would be pretty p***ed off) > > > > > > thanks, > > > Deepak S Patwardhan. > > > > -- Javier Gonzalez Nicolini
Re: service url
Hi, I can accept, as a convention, to define one port per service. However, my question was about customizing the service url, to reflect a sort of hierarchy. If you say that I'll always get the endpoint url as : http://host:unix-port/axis/services/PORT-NAME then this is a recipe for name collision. Two services, written by two different people, in two different WSDL files, who happen to use the same port name won't run in the same Tomcat+AXIS container. The last service to get deployed grabs that endpoint url (I tested it). Anyway, so now, my question is how to host two services, which are defined in two separate WSDL files, which can't be edited (obviously), and happen to literally share a port name. thanks, Deepak S Patwardhan. -- On Mon, 29 Aug 2005, Guy Rixon wrote: > WS-I basic profile expects developers to define one port per service. I think > the underlying philosphy is that each SOAP endpoint has one remote object and > all the operations on that endpoint work as methods on that one object. > > I agree that this is limiting. It's often nice to aggregate ports. > > On Mon, 29 Aug 2005, Deepak S Patwardhan wrote: > > > HI all, > > > > My question is about the way axis makes a service URL. Normally, you see a > > URL like the following : > > > > http://host:unix-port/axis/services/PORT-NAME > > > > where, PORT-NAME is a port defined in the service element. > > > > Is it possible that the service URL be like this : > > > > http://host:unix-port/axis/services/SERVICE-NAME/PORT-NAME > > > > where SERVICE-NAME is the name of the service ? (attribute name of service > > element) > > > > This would look more logical, especially when a service contains multiple > > ports. I tried specifying such URLs in the WSDL but axis overrides it. > > (please see the attached WSDL.) > > > > WHen I deploy my service (service Primality, two ports, a) Prime - to > > check whether a number is prime, b) CoPrime - to check whether two numbers > > are coprime), and when I see the list of deployed services, I expected a > > listing like this > > > > * Primality > >-Prime > > - isPrime > >-CoPrime > > - areCoPrime > > > > But, what is displayed is as if there are two services, Prime and CoPrime. > > > > * Prime > >- isPrime > > * CoPrimes > >- areCoPrime > > > > It seems as if axis elevates a PORT to a service. What's the > > design decision behind this ? (And if you tell me that AXIS expects > > developers to define one port per service, I would be pretty p***ed off) > > > > thanks, > > Deepak S Patwardhan. > >
Re: service url
WS-I basic profile expects developers to define one port per service. I think the underlying philosphy is that each SOAP endpoint has one remote object and all the operations on that endpoint work as methods on that one object. I agree that this is limiting. It's often nice to aggregate ports. On Mon, 29 Aug 2005, Deepak S Patwardhan wrote: > HI all, > > My question is about the way axis makes a service URL. Normally, you see a > URL like the following : > > http://host:unix-port/axis/services/PORT-NAME > > where, PORT-NAME is a port defined in the service element. > > Is it possible that the service URL be like this : > > http://host:unix-port/axis/services/SERVICE-NAME/PORT-NAME > > where SERVICE-NAME is the name of the service ? (attribute name of service > element) > > This would look more logical, especially when a service contains multiple > ports. I tried specifying such URLs in the WSDL but axis overrides it. > (please see the attached WSDL.) > > WHen I deploy my service (service Primality, two ports, a) Prime - to > check whether a number is prime, b) CoPrime - to check whether two numbers > are coprime), and when I see the list of deployed services, I expected a > listing like this > > * Primality >- Prime > - isPrime >- CoPrime > - areCoPrime > > But, what is displayed is as if there are two services, Prime and CoPrime. > > * Prime >- isPrime > * CoPrimes >- areCoPrime > > It seems as if axis elevates a PORT to a service. What's the > design decision behind this ? (And if you tell me that AXIS expects > developers to define one port per service, I would be pretty p***ed off) > > thanks, > Deepak S Patwardhan. > > --- WSDL - > targetNamespace="http://gridsolv.com/deepak/ws1/"; > xmlns:tns="http://gridsolv.com/deepak/ws1/"; > xmlns:xsd="http://www.w3.org/1999/XMLSchema"; > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/"; > xmlns="http://schemas.xmlsoap.org/wsdl/";> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > > > > > > > > > > transport="http://schemas.xmlsoap.org/soap/http"/> > > > > > > > > > > > > > > > > location="http://localhost:8080/axis/services/Primality/Prime"/> > > > location="http://localhost:8080/axis/services/Primality/CoPrime"/> > > > > > Guy Rixon [EMAIL PROTECTED] Institute of Astronomy Tel: +44-1223-337542 Madingley Road, Cambridge, UK, CB3 0HA Fax: +44-1223-337523
service url
HI all, My question is about the way axis makes a service URL. Normally, you see a URL like the following : http://host:unix-port/axis/services/PORT-NAME where, PORT-NAME is a port defined in the service element. Is it possible that the service URL be like this : http://host:unix-port/axis/services/SERVICE-NAME/PORT-NAME where SERVICE-NAME is the name of the service ? (attribute name of service element) This would look more logical, especially when a service contains multiple ports. I tried specifying such URLs in the WSDL but axis overrides it. (please see the attached WSDL.) WHen I deploy my service (service Primality, two ports, a) Prime - to check whether a number is prime, b) CoPrime - to check whether two numbers are coprime), and when I see the list of deployed services, I expected a listing like this * Primality -Prime - isPrime -CoPrime - areCoPrime But, what is displayed is as if there are two services, Prime and CoPrime. * Prime - isPrime * CoPrimes - areCoPrime It seems as if axis elevates a PORT to a service. What's the design decision behind this ? (And if you tell me that AXIS expects developers to define one port per service, I would be pretty p***ed off) thanks, Deepak S Patwardhan. --- WSDL - http://gridsolv.com/deepak/ws1/"; xmlns:tns="http://gridsolv.com/deepak/ws1/"; xmlns:xsd="http://www.w3.org/1999/XMLSchema"; xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/"; xmlns="http://schemas.xmlsoap.org/wsdl/";> http://schemas.xmlsoap.org/soap/http"/> http://schemas.xmlsoap.org/soap/http"/> http://localhost:8080/axis/services/Primality/Prime"/> http://localhost:8080/axis/services/Primality/CoPrime"/>
