On 3/19/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote:
How about falling back to the earlier naming conventions ,in cases
where the the WSDL has just one port or in the case where user has
specifically mentioned the port..
Ok then lets do it in this way.
i.e. We use only the ServiceName
On 3/19/07, jim ma <[EMAIL PROTECTED]> wrote:
Hi ,
If the the same PortType referenced by mutl service , does
WSDLXXToAllAxisServicesBuilder
cache the portType infromation and only process the same PortType for one
time ?
Regards
Jim
No.
When processing a service we always creates a new Ax
+1
It's a pain to have to change working code when upgrading to a new
version of Axis2.
- Dennis
Thilina Gunarathne wrote:
How about falling back to the earlier naming conventions ,in cases
where the the WSDL has just one port or in the case where user has
specifically mentioned the port.
How about falling back to the earlier naming conventions ,in cases
where the the WSDL has just one port or in the case where user has
specifically mentioned the port..
It might get bit messy and complex.. But the above will make sure we
are backward compatible..
Thanks,
Thilina
On 3/19/07, Am
Hi ,
If the the same PortType referenced by mutl service , does
WSDLXXToAllAxisServicesBuilder
cache the portType infromation and only process the same PortType for one
time ?
Regards
Jim
On 3/19/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
thanks for your reply.
here you have pointed ou
thanks for your reply.
here you have pointed out two problems with the current multi port
implementation
1. backward compatibility
2. Length of the stub class name generated.
so please send what ever your proposals to above problems.
Then we can improve this to minimise any problems which may cau
On 3/16/07, Saminda Abeyruwan <[EMAIL PROTECTED]> wrote:
...
...
...
Now according to the prior discussion, if use wsdl2java, It'll create
FooAStub and FooBStub right?
You are lucky if it was just Foo & A... Kandula2 wsdl's generated
BACoordinatorCompletionParticipantServiceBACoo
Hi,
Sorry not being able to reply earlier.
Assume my wsdl has following service bindings,
...
...
...
...
Now according to the prior discussion, if use wsdl2java, It'll create
FooAStub and FooBStub right?
Now if we have a single service binding [assume service binding name is Foo
I implemented the multi service and multi port support in the following way.
if the user has specified a service and a port (using -sn and -pn) then the
wsdl2java generates the code only for that combination. otherwise it
generates the code for all services and ports.
When Generating code for mul
Amila,
In case you are looking for a use case. Here's yet another one:
http://blog.sweetxml.org/2007/03/trying-to-be-consumer.html
We should be handling this elegantly (when we generate clients)
thanks,
-- dims
On 3/7/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Yes, please.
thanks,
dims
Yes, please.
thanks,
dims
On 3/7/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
On 3/6/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> Amila,
>
> Did you notice the WSDL11ToAllAxisServicesBuilder and
> WSDL20ToAllAxisServicesBuilder? They are supposed to build multiple
> AxisService(s).
On 3/6/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Amila,
Did you notice the WSDL11ToAllAxisServicesBuilder and
WSDL20ToAllAxisServicesBuilder? They are supposed to build multiple
AxisService(s).
As I saw there is no usage for these classes. It generates an axis service
actually per port
Amila,
Did you notice the WSDL11ToAllAxisServicesBuilder and
WSDL20ToAllAxisServicesBuilder? They are supposed to build multiple
AxisService(s).
thanks,
dims
On 3/6/07, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
hi,
currently wsdl2java generates code for one service only. So It will improve
13 matches
Mail list logo