Re: [Axis2] Generating a wrong port address for POJO deployment

Hi all, I'm mostly an observer in this one (and I honestly don't think that the format of the URL matters as long as it is a valid url). Here are some thoughts 1. It seems that this change is sensible in terms of endpoint policy attachment. Some implementations don't do that right now but my gues

Re: [Axis2] Generating a wrong port address for POJO deployment

Hello Everyone, Please find my comments inlined. [1] http://www.mail-archive.com/axis-dev@ws.apache.org/msg26438.html [2] http://www.mail-archive.com/axis-dev@ws.apache.org/msg40047.html Daniel Kulp wrote: Dims, On May 12, 2008, at 11:59 PM, Davanum Srinivas wrote: I was talking about mov

Re: [Axis2] Generating a wrong port address for POJO deployment

ent: Tuesday, May 13, 2008 11:03 AM To: axis-dev@ws.apache.org Subject: Re: [Axis2] Generating a wrong port address for POJO deployment Dims, On May 12, 2008, at 11:59 PM, Davanum Srinivas wrote: I was talking about moving JAXWS services and clients across implementations. Not on the w

RE: [Axis2] Generating a wrong port address for POJO deployment

--Original Message- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 13, 2008 11:03 AM To: axis-dev@ws.apache.org Subject: Re: [Axis2] Generating a wrong port address for POJO deployment Dims, On May 12, 2008, at 11:59 PM, Davanum Srinivas wrote: > I was talking about moving JA

Re: [Axis2] Generating a wrong port address for POJO deployment

Dims, On May 12, 2008, at 11:59 PM, Davanum Srinivas wrote: I was talking about moving JAXWS services and clients across implementations. Not on the wire interop. Sorry it was not clearer. I'm not sure how that applies here. Axis2 is the only JAX-WS implementation that does this funky End

Re: [Axis2] Generating a wrong port address for POJO deployment

Hi Saminda, Please find my comments inlined. Saminda Abeyruwan wrote: Hi Devs, During the Axis2 1.4 evaluating time, I have explicitly asked why this behaviour was introduced. Reason was to get extra information without breaking backward compatibility. The prior semantic has introduce a

Re: [Axis2] Generating a wrong port address for POJO deployment

Hello Everyone, Please find my comments inlined. Davanum Srinivas wrote: Sanka, for one thing, i haven't seen anyone else use it. I am bit confused here. Clients should use the endpoint address which we advertise through the WSDL .. shouldn't they ? In other words new client application

Re: [Axis2] Generating a wrong port address for POJO deployment

Amila, I was talking about moving JAXWS services and clients across implementations. Not on the wire interop. Sorry it was not clearer. thanks, -- dims On Mon, May 12, 2008 at 11:56 PM, Amila Suriarachchi <[EMAIL PROTECTED]> wrote: > > > > On Mon, May 12, 2008 at 5:48 PM, Davanum Srinivas <[EMAI

Re: [Axis2] Generating a wrong port address for POJO deployment

On Mon, May 12, 2008 at 5:48 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Sanka, > > for one thing, i haven't seen anyone else use it. another thing, makes > it *slightly* more difficult for interop work and for tck work. I don't have any experience with the tck. But I think it should not h

Re: [Axis2] Generating a wrong port address for POJO deployment

Hi Devs, During the Axis2 1.4 evaluating time, I have explicitly asked why this behaviour was introduced. Reason was to get extra information without breaking backward compatibility. The prior semantic has introduce a hidden information in WSDL. WSDL shows [service].[port] and it does work for [s

Re: [Axis2] Generating a wrong port address for POJO deployment

Keith, That would be good, but remember the JAXWS services don't have service.xml's :) they specify the expected service name in the annotation. -- dims On Mon, May 12, 2008 at 10:53 AM, keith chapman <[EMAIL PROTECTED]> wrote: > Dims, > > How about making it flexible. Introduce a service.xml pr

Re: [Axis2] Generating a wrong port address for POJO deployment

Dims, How about making it flexible. Introduce a service.xml property where you can set a aliases for the endpoint urls? We may need three properties for the tree default bindings. That way the user can have very nice URLs... Thanks, Keith. On Mon, May 12, 2008 at 5:48 PM, Davanum Srinivas <[EMAI

Re: [Axis2] Generating a wrong port address for POJO deployment

Sanka, for one thing, i haven't seen anyone else use it. another thing, makes it *slightly* more difficult for interop work and for tck work. It also makes it more difficult for people who want to design their own URI's for their web services and need complete control (yes, there are a few of thos

Re: [Axis2] Generating a wrong port address for POJO deployment

Deepal jayasinghe wrote: When I deploy a very simple POJO service it generates following as the service section in WSDL. As I know this is not nice and we need to fix this as soon as possible. Why is it not nice? This gives us the ability to apply binding level security correct

Re: [Axis2] Generating a wrong port address for POJO deployment

When I deploy a very simple POJO service it generates following as the service section in WSDL. As I know this is not nice and we need to fix this as soon as possible. Why is it not nice? This gives us the ability to apply binding level security correctly which is not possible w

Re: [Axis2] Generating a wrong port address for POJO deployment

Deepal Jayasinghe wrote: My suggestion would be to have the wsdl which look like before , meaning when we do not have then do not do any changes to port address. Sorry .. I can't understand what you are trying to say .. can you please explain a bit :-) Thanks & Regards, Sanka If user pu

Re: [Axis2] Generating a wrong port address for POJO deployment

Hello Everyone, Please find my comments inlined. Deepal Jayasinghe wrote: Hi Deepal, See comments inline On Fri, May 9, 2008 at 11:49 AM, Deepal jayasinghe <[EMAIL PROTECTED] > wrote: Hi Sanka and all, When I deploy a very simple POJO service it gener

Re: [Axis2] Generating a wrong port address for POJO deployment

Hi Deepal, See comments inline On Fri, May 9, 2008 at 11:49 AM, Deepal jayasinghe <[EMAIL PROTECTED] > wrote: Hi Sanka and all, When I deploy a very simple POJO service it generates following as the service section in WSDL. As I know this is not nice

Re: [Axis2] Generating a wrong port address for POJO deployment

Hi Dims, I agree with Sanka that this would not effect any existing code. For e.g if I can a service called foo it does not really matter if I send a request to http://localhost:8080/axis2/services/foo or http://localhost:8080/axis2/services/foo.SOAP11Endpoint. Both should work. The latte

Re: [Axis2] Generating a wrong port address for POJO deployment

Hi Deepal, See comments inline On Fri, May 9, 2008 at 11:49 AM, Deepal jayasinghe <[EMAIL PROTECTED]> wrote: > Hi Sanka and all, > > > When I deploy a very simple POJO service it generates following as the > service section in WSDL. As I know this is not nice and we need to fix this > as soon as

Re: [Axis2] Generating a wrong port address for POJO deployment

Hi Dims, I agree with Sanka that this would not effect any existing code. For e.g if I can a service called foo it does not really matter if I send a request to http://localhost:8080/axis2/services/foo or http://localhost:8080/axis2/services/foo.SOAP11Endpoint. Both should work. The latter gibes y

Re: [Axis2] Generating a wrong port address for POJO deployment

:s/10.100.1.205/localhost On Fri, May 9, 2008 at 4:16 PM, Sanka Samaranayake <[EMAIL PROTECTED]> wrote: > > On Fri, May 9, 2008 at 3:56 PM, Davanum Srinivas <[EMAIL PROTECTED]> > wrote: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Sanka, >> >> #1: I specifically requested in that t

Re: [Axis2] Generating a wrong port address for POJO deployment

On Fri, May 9, 2008 at 3:56 PM, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Sanka, > > #1: I specifically requested in that thread that existing code should work > as-is. With this change it did not. > Specifically if one had existing clients i

Re: [Axis2] Generating a wrong port address for POJO deployment

My suggestion would be to have the wsdl which look like before , meaning when we do not have then do not do any changes to port address. If user put a wsdl file then I do not mind doing anything. -Deepal Sanka, #1: I specifically requested in that thread that existing code should work as-is

Re: [Axis2] Generating a wrong port address for POJO deployment

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sanka, #1: I specifically requested in that thread that existing code should work as-is. With this change it did not. Specifically if one had existing clients in another language, they needed to be updated with a fresh endpoint since the same servi

Re: [Axis2] Generating a wrong port address for POJO deployment

Hi, We discussed about that in a mailing thread[1] sometime back. Why do you think we should change that? IMO it is desirable to have [service].[port] in the service address since it makes valuable binding information available for request processing at service side. Sanka [1] http://www.mail-a

[Axis2] Generating a wrong port address for POJO deployment

Hi Sanka and all, When I deploy a very simple POJO service it generates following as the service section in WSDL. As I know this is not nice and we need to fix this as soon as possible. It is not good to have "SampleService.SampleServiceHttpSoap12Endpoint" as the service address. We did not