Re: WSDL Parser java

[Sagara Gunathunga]

WSDL parsers only support for WSDL content, to read Schema you have to
use a Schema parser try for Apache XmlSchema [1].

[1] - http://ws.apache.org/commons/XmlSchema/

Thanks,

On Wed, Nov 11, 2009 at 3:27 PM, Stefano Tranquillini
 wrote:
> i'm using now wsdl4j.
> also axis2 used wsdl4j, but:
> how can i read the xsd inside the wsdl?
> i'm able to read all the informations, but not the types of the
> message, i will explain better:
>
> a snippet of a wsdl:
>
>  
>     http://www.example.org/NewWSDLFile/";>
>   
>     
>   
>     
>   
>     
>   
>   
>     
>   
>     
>   
>     
>   
>     
>   
>   
>     
>   
>   
>     
>   
>
>
> i'm able to read the message :
>
> SchemaExtensibilityElement ({http://www.w3.org/2001/XMLSchema}schema):
> required=null
> element=[xsd:schema: null]
> Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
> Part: name=parameters
> elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse
> Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
> Part: name=parameters
> elementName={http://www.example.org/NewWSDLFile/}NewOperation
> PortType: name={http://www.example.org/NewWSDLFile/}NewWSDLFile
> Operation: name=NewOperation
> style=REQUEST_RESPONSE
> Input: name=null
> Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
> Part: name=parameters
> elementName={http://www.example.org/NewWSDLFile/}NewOperation
> Output: name=null
> Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
> Part: name=parameters
> elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse
>
>
> but i'm not able to read the definition of the content of message like
> the lines inside 
>
> any hints about that?
>
> thanks all
>
> --
> Stefano
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: WSDL Parser java

[Stefano Tranquillini]

i'm using now wsdl4j.
also axis2 used wsdl4j, but:
how can i read the xsd inside the wsdl?
i'm able to read all the informations, but not the types of the
message, i will explain better:

a snippet of a wsdl:

 
    http://www.example.org/NewWSDLFile/";>
  
    
  
    
  
    
  
  
    
  
    
  
    
  
    
  
  
    
  
  
    
  


i'm able to read the message :

SchemaExtensibilityElement ({http://www.w3.org/2001/XMLSchema}schema):
required=null
element=[xsd:schema: null]
Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse
Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperation
PortType: name={http://www.example.org/NewWSDLFile/}NewWSDLFile
Operation: name=NewOperation
style=REQUEST_RESPONSE
Input: name=null
Message: name={http://www.example.org/NewWSDLFile/}NewOperationRequest
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperation
Output: name=null
Message: name={http://www.example.org/NewWSDLFile/}NewOperationResponse
Part: name=parameters
elementName={http://www.example.org/NewWSDLFile/}NewOperationResponse


but i'm not able to read the definition of the content of message like
the lines inside 

any hints about that?

thanks all

--
Stefano

Re: WSDL Parser java

[Stefano Tranquillini]

i found that there's already smt done in java library:
javax.wsdl.xml.WSDLReader

On Sat, Nov 7, 2009 at 16:31, Sagara Gunathunga  wrote:

> If you plan to write a class from the scratch to read the WSDL and get
> those details you can use JWSDL API [1] with  WSDL4J [2].
>
>
> [1] - wsdl4j.sourceforge.net/downloads/JSR110_proposed_final_draft.pdf
> [2] - http://sourceforge.net/projects/wsdl4j/
>
> Thanks,
>
> On Sat, Nov 7, 2009 at 10:10 AM, Stefano Tranquillini
>  wrote:
> > i'm reading and trying the WSDL2AxisServiceBuilder but i'm not able to
> know
> > the operation name and type.
> >
> > there's no class that read the wsdl and has method that returns
> operations
> > name operations parameters and so on?
> >
> > thanks
> >
> > On Fri, Nov 6, 2009 at 18:46, Stefano Tranquillini
> >  wrote:
> >>
> >> thanks, i take a look.
> >> but, i can use this class and doing what i want or the license of apache
> >> blocks me for somethings i.e. use for business applications?
> >>
> >> On Fri, Nov 6, 2009 at 18:20, Deepal jayasinghe 
> wrote:
> >>>
> >>> Is this about Axis2 or Axis1? if it is in Axis2 look at
> WSDL2AxisService
> >>> Builder class.
> >>>
> >>> Thanks,
> >>> Deepal
> >>> > Hi all.
> >>> > in the code of the project there's a class that parse the wsdl? which
> >>> > one?
> >>> > i need to know all the things inside the wsdl, in particular i'm
> >>> > interested in the name of the operations and smt else.
> >>> > thanks in advance.
> >>> >
> >>> >
> >>> > --
> >>> > Stefano
> >>>
> >>>
> >>> --
> >>> Thank you!
> >>>
> >>>
> >>> http://blogs.deepal.org
> >>> http://deepal.org
> >>>
> >>
> >>
> >>
> >> --
> >> Stefano
> >
> >
> >
> > --
> > Stefano
> >
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
>



-- 
Stefano

Re: WSDL Parser java

[Sagara Gunathunga]

If you plan to write a class from the scratch to read the WSDL and get
those details you can use JWSDL API [1] with  WSDL4J [2].


[1] - wsdl4j.sourceforge.net/downloads/JSR110_proposed_final_draft.pdf
[2] - http://sourceforge.net/projects/wsdl4j/

Thanks,

On Sat, Nov 7, 2009 at 10:10 AM, Stefano Tranquillini
 wrote:
> i'm reading and trying the WSDL2AxisServiceBuilder but i'm not able to know
> the operation name and type.
>
> there's no class that read the wsdl and has method that returns operations
> name operations parameters and so on?
>
> thanks
>
> On Fri, Nov 6, 2009 at 18:46, Stefano Tranquillini
>  wrote:
>>
>> thanks, i take a look.
>> but, i can use this class and doing what i want or the license of apache
>> blocks me for somethings i.e. use for business applications?
>>
>> On Fri, Nov 6, 2009 at 18:20, Deepal jayasinghe  wrote:
>>>
>>> Is this about Axis2 or Axis1? if it is in Axis2 look at WSDL2AxisService
>>> Builder class.
>>>
>>> Thanks,
>>> Deepal
>>> > Hi all.
>>> > in the code of the project there's a class that parse the wsdl? which
>>> > one?
>>> > i need to know all the things inside the wsdl, in particular i'm
>>> > interested in the name of the operations and smt else.
>>> > thanks in advance.
>>> >
>>> >
>>> > --
>>> > Stefano
>>>
>>>
>>> --
>>> Thank you!
>>>
>>>
>>> http://blogs.deepal.org
>>> http://deepal.org
>>>
>>
>>
>>
>> --
>> Stefano
>
>
>
> --
> Stefano
>



-- 
Sagara Gunathunga

Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/

Re: WSDL Parser java

[Stefano Tranquillini]

i'm reading and trying the WSDL2AxisServiceBuilder but i'm not able to know
the operation name and type.

there's no class that read the wsdl and has method that returns operations
name operations parameters and so on?

thanks

On Fri, Nov 6, 2009 at 18:46, Stefano Tranquillini <
stefano.tranquill...@gmail.com> wrote:

> thanks, i take a look.
> but, i can use this class and doing what i want or the license of apache
> blocks me for somethings i.e. use for business applications?
>
>
> On Fri, Nov 6, 2009 at 18:20, Deepal jayasinghe  wrote:
>
>> Is this about Axis2 or Axis1? if it is in Axis2 look at WSDL2AxisService
>> Builder class.
>>
>> Thanks,
>> Deepal
>> > Hi all.
>> > in the code of the project there's a class that parse the wsdl? which
>> one?
>> > i need to know all the things inside the wsdl, in particular i'm
>> > interested in the name of the operations and smt else.
>> > thanks in advance.
>> >
>> >
>> > --
>> > Stefano
>>
>>
>> --
>> Thank you!
>>
>>
>> http://blogs.deepal.org
>> http://deepal.org
>>
>>
>
>
> --
> Stefano
>



-- 
Stefano

Re: WSDL client generation. Problem with more than one part and binding style "document"

[error3]

Le vendredi 25 septembre 2009 à 10:35 +0530, Amila Suriarachchi a
écrit : 
> 
> How to develop the fastest way an operational client and set
> the whole soap envelop
>  you want to send ? 
> 
> Please see here[1]
> 
> thanks,
> Amila.
> 
> [1]
> http://amilachinthaka.blogspot.com/2009/09/sending-arbitrary-soap-message-with.html


Thank you very much Amila, it works perfectly ! 

Re: WSDL client generation. Problem with more than one part and binding style "document"

[Amila Suriarachchi]

On Thu, Sep 24, 2009 at 3:58 PM,  wrote:

>
> - "Amila Suriarachchi"  a écrit :
>
> > [...]
> > 
> > theName
> > 
> > 
> > [...]
> >
> > How can I modify the WSDL to make axis2 generating a client which can
> > produce the above request I want ? Is it possible ? Do I need to change
> the
> > style to rpc ? If it's not possible, do you know an opensource project
> > which know how to deal with my wsdl ?
> >
> >
> > I think this is not possible with Axis2 unless you write an
> > operational client and set the whole soap envelop
> > you want to send.
>
> Thanks Amila,
> But why doesn't Axis2 know how to generate such a message ?
> I saw nothing in w3.org/TR/wsdl saying that multi parts inside soap:body
> is prohibited... I've only see this
> limitation (for compatibility if I've correctly understood) on ws-i.org.
>
> Axis2 only how to generate WS-I ? Not wsdl in general ?
>
This is to solve the problem now you have faced :). If soap stacks do not
follow WS-I it is
very difficult to interoperate between them.


>
> How to develop the fastest way an operational client and set the whole soap
> envelop
>  you want to send ?
>

Please see here[1]

thanks,
Amila.

[1]
http://amilachinthaka.blogspot.com/2009/09/sending-arbitrary-soap-message-with.html

>
> Thanx again for help and informations
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: WSDL client generation. Problem with more than one part and binding style "document"

[error3]

- "Amila Suriarachchi"  a écrit :

> [...]
> 
> theName
> 
> 
> [...]
> 
> How can I modify the WSDL to make axis2 generating a client which can
> produce the above request I want ? Is it possible ? Do I need to change the
> style to rpc ? If it's not possible, do you know an opensource project
> which know how to deal with my wsdl ?
> 
> 
> I think this is not possible with Axis2 unless you write an
> operational client and set the whole soap envelop
> you want to send.

Thanks Amila,
But why doesn't Axis2 know how to generate such a message ?
I saw nothing in w3.org/TR/wsdl saying that multi parts inside soap:body is 
prohibited... I've only see this
limitation (for compatibility if I've correctly understood) on ws-i.org.

Axis2 only how to generate WS-I ? Not wsdl in general ?

How to develop the fastest way an operational client and set the whole soap 
envelop
 you want to send ?

Thanx again for help and informations

Re: WSDL client generation. Problem with more than one part and binding style "document"

[Amila Suriarachchi]

On Thu, Sep 24, 2009 at 5:46 AM, error3  wrote:

> Hello,
>
> with the attached wsdl file (it's an simplified version of mine), I'm
> trying to generate WS client (in eclipse, and with Axis2).
>
> while trying to generate the client, I have an error saying that "more
> than one part" in the message... (I do not have the message nor my
> development environment at that time).
>
> Googlin' and found that "document" binding style shouldn't have multiple
> parts message in the body.
> Ok.
>
> So I know that, to querying the webservice (I can't modify it, it's an
> application one) I must send something like :
>
> [...]
>
> theName
> 
>
> [...]
>
> How can I modify the WSDL to make axis2 generating a client which can
> produce the request I want ? Is it possible ? Do I need to change the
> style to rpc ? If it's not possible, do you know an opensource project
> which know how to deal with my wsdl ?
>

I think this is not possible with Axis2 unless you write an operational
client and set the whole soap envelop
you want to send.

thanks,
Amila.


> thank you very much for any help,
>
> --
> Martin
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: WSDL URL is Changing

[Amila Suriarachchi]

On Thu, Sep 17, 2009 at 3:27 PM, E Shanaka Jayasundera  wrote:

>  Axis 2 version is 1.4.1
>
>
>
> What is the parameter to that we need to change?
>



thanks,
Amila.

>
>
> Thanks in advance.
>
>
>
> *From:* Amila Suriarachchi [mailto:amilasuriarach...@gmail.com]
> *Sent:* Thursday, September 17, 2009 11:21 AM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: WSDL URL is Changing
>
>
>
> what is the axis2 version you use?
>
> there is a commented parameter in axis2.xml. try changing that.
>
> thanks,
> Amila.
>
> On Wed, Sep 16, 2009 at 5:52 PM, E Shanaka Jayasundera <
> shan...@aeturnum.com> wrote:
>
> My Application is deployed on JBOSS Application server (SSL enabled) and
> WSDL access URL is https://localhost:9002/web/services/WS?wsdl
>
> For some reason its going to redirect to
> https://localhost:9002/axis2/services/WS?wsdl<https://localhost:9002/axis2/services/PayfoneWS?wsdl>
>
>
>
> I haven’t specify /axis2/ any were and also my filter in web.xml is as
> follows,
>
>
>
> 
>
> AxisServlet
>
>
> org.apache.axis2.transport.http.AxisServlet
>
> 1
>
> 
>
>
>
> 
>
> AxisServlet
>
> /services/*
>
> 
>
>
>
>
>
> Also, in the later time some home client end point change to
> https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this
> end point is not working
>
>
>
> Thanks in advance.
>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

RE: WSDL URL is Changing

[E Shanaka Jayasundera]

Axis 2 version is 1.4.1

 

What is the parameter to that we need to change?

 

Thanks in advance.

 

From: Amila Suriarachchi [mailto:amilasuriarach...@gmail.com] 
Sent: Thursday, September 17, 2009 11:21 AM
To: axis-user@ws.apache.org
Subject: Re: WSDL URL is Changing

 

what is the axis2 version you use?

there is a commented parameter in axis2.xml. try changing that.

thanks,
Amila.

On Wed, Sep 16, 2009 at 5:52 PM, E Shanaka Jayasundera
 wrote:

My Application is deployed on JBOSS Application server (SSL enabled) and
WSDL access URL is https://localhost:9002/web/services/WS?wsdl

For some reason its going to redirect to
https://localhost:9002/axis2/services/WS?wsdl
<https://localhost:9002/axis2/services/PayfoneWS?wsdl> 

 

I haven't specify /axis2/ any were and also my filter in web.xml is as
follows,

 



AxisServlet

 
org.apache.axis2.transport.http.AxisServlet

1







AxisServlet

/services/*



 

 

Also, in the later time some home client end point change to
https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this end
point is not working

 

Thanks in advance.




-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: WSDL URL is Changing

[Amila Suriarachchi]

what is the axis2 version you use?

there is a commented parameter in axis2.xml. try changing that.

thanks,
Amila.

On Wed, Sep 16, 2009 at 5:52 PM, E Shanaka Jayasundera  wrote:

>  My Application is deployed on JBOSS Application server (SSL enabled) and
> WSDL access URL is https://localhost:9002/web/services/PayfoneWS?wsdl
>
> For some reason its going to redirect to
> https://localhost:9002/axis2/services/PayfoneWS?wsdl
>
>
>
> I haven’t specify /axis2/ any were and also my filter in web.xml is as
> follows,
>
>
>
> 
>
> AxisServlet
>
>
> org.apache.axis2.transport.http.AxisServlet
>
> 1
>
> 
>
>
>
> 
>
> AxisServlet
>
> /services/*
>
> 
>
>
>
>
>
> Also, in the later time some home client end point change to
> https://localhost:9002/web/services/PayfoneWS?wsdl and fails since this
> end point is not working
>
>
>
> Thanks in advance.
>



-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: Wsdl comments get lost in Axis2.1.4

[Andreas Veithen]

Kristof,

Comments are indeed probably lost in the WSDL. Please note that the
correct way to add documentation to a WSDL is not with comments, but
using  and  elements.

Regards,

Andreas

On Mon, Jul 27, 2009 at 12:55, Werling, Kristof wrote:
> Hello,
>
> When generating the AAR file the existing WSDL contains comments in the form 
> of 
>
> The useOriginalWsdl parameter is set to "true"
>
> However, when the WSDL is pulled like this:  http:///...?wsdl
>
> Then the comments are lost.
>
> I tried this with wsdl in that location in the aar file:                      
>   META-INF/.wsdl
>
> And I tried it with a wsdl file name like this in the aar file:         
> META-INF/service.wsdl
>
> The result stayed the same.
>
> What am I doing wrong here?
>
> Thanks,
> Kristof
>

Re: WSDL gen error

[Demetris G]

In case it helps the case here is the exception I get on the client side -

[java] WSDLException (at /wsdl:definitions/types): 
faultCode=INVALID_WSDL: Encountered illegal
extension element 'types' in the context of a 'javax.wsdl.Definition'. 
Extension elements must be in a namespace

other than WSDL's.:
[java] at 
com.ibm.wsdl.xml.WSDLReaderImpl.parseExtensibilityElement(Unknown Source)
[java] at 
com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)

[java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
[java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
[java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
[java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
[java] at Utils.myWSDLParser.parseWSDL(myWSDLParser.java:46)

Any ideas greatly appreciated - thanks.

Demetris G wrote:


And one more pt -

If most likely we need to have entities in the WSDL file namespace 
qualified, and the
WSDL parsers on the client side complain if they are not (as in the 
case of 
vs. ) then is this an exceptional case that should not occur? 
Why would Axis

generate WSDL tags that the corresponding WSDL parsers cannot handle??

Lars Ericsson wrote:

HI Demtirs!

I couldn't understand what is your problem, please describe more 
about your problem.
The namespace  can be anything, and it is nothing to do whit network, 
connection or anything else.

Please read more about namespace.
but if you get two different wsdl from two different environment, 
sound strange, alse i suppose you have the same axis-version 
same-java version and so on.
Please check manually call any service on those two service, if you 
don't get the same respons, it is some thing you should be worried 
about it. otherwise the differences between those two wsdl-s is not 
importent.




*From:* Demetris G 
*To:* axis-user@ws.apache.org
*Sent:* Sunday, July 12, 2009 7:32:32 AM
*Subject:* Re: WSDL gen error


Hi again,

  I am beginning to worry that (a) I am either asking a really stupid 
question here
and in the thread that is listed further down in my email that is not 
worth wasting
any time on (b) a really complicated question (I doubt it) (c) I am 
in the wrong

list ... should I move these two questions to the axis-dev you think?

  If axis is giving me a different WSDL file in two different Linux 
machines while
the configuration and version is the same, is that a bug I need to 
worry about?
And at least any information on how to manipulate the IP address in 
the WSDL

would be greatly appreciated.

Anyone??

Thanks once again
Demetris

Demetris G wrote:
>
> Hi all,
>
> Calling a service on the same machine as the axis server will set 
the namespace

> http://127.0.0.1:8080/axis/services/
>
> However, calling it from another node in the same network behind a 
NAT still

> returns the same IP address in the name space - is that normal?
>
> Also, how can the IP address in the first case (calling it from the 
same machine)

> be set to the true IP address of the machine?
>
> Also if anyone has any more info on my email below it will be 
greatly appreciated.

>
> Thanks
> Demetris
>
> Demetris G wrote:
>>
>> And scanning through the two WSDL files I see also other diffs -
>>
>> 
>> 
>> 
>>
>> vs.
>>
>> 
>> 
>> 
>>
>> So it seems to me that it treats the same service a bit 
differently on a separate

>> machine even though the setup/config etc of the server is identical.
>>
>> Demetris G wrote:
>>>
>>> At least someone may know this - what would cause the Axis engine 
to generate WSDLs
>>> with  instead of ? If I know that then I can 
probably figure out why
>>> the same Axis engine distribution on two different Linux boxes 
would generate two different

>>> types of WSDLs - I am using the same browser to issue the request:
>>> http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl
>>>
>>> One engine gives this:
>>> 
>>>
>>> ...
>>> 
>>>
>>> and the other:
>>> 
>>> http://xml.apache.org/xml-soap";>
>>> ...
>>> 
>>>
>>> Any ideas?
>>>
>>> Thanks
>>>
>>>
>>>> Demetris G wrote:
>>>>>
>>>>> And a follow up -
>>>>>
>>>>> same Axis engine (running in exactly same OSGi containers, same 
services, on one
>>>>> Linux machine it generates the WSDL file with  and the 
other with  !

>>>>> Why is that the case? This is a bit puzzling.
>>>>>
>

Re: WSDL gen error

[Demetris G]

And one more pt -

If most likely we need to have entities in the WSDL file namespace 
qualified, and the
WSDL parsers on the client side complain if they are not (as in the case 
of 
vs. ) then is this an exceptional case that should not occur? Why 
would Axis

generate WSDL tags that the corresponding WSDL parsers cannot handle??

Lars Ericsson wrote:

HI Demtirs!

I couldn't understand what is your problem, please describe more about 
your problem.
The namespace  can be anything, and it is nothing to do whit network, 
connection or anything else.

Please read more about namespace.
but if you get two different wsdl from two different environment, 
sound strange, alse i suppose you have the same axis-version same-java 
version and so on.
Please check manually call any service on those two service, if you 
don't get the same respons, it is some thing you should be worried 
about it. otherwise the differences between those two wsdl-s is not 
importent.




*From:* Demetris G 
*To:* axis-user@ws.apache.org
*Sent:* Sunday, July 12, 2009 7:32:32 AM
*Subject:* Re: WSDL gen error


Hi again,

  I am beginning to worry that (a) I am either asking a really stupid 
question here
and in the thread that is listed further down in my email that is not 
worth wasting
any time on (b) a really complicated question (I doubt it) (c) I am in 
the wrong

list ... should I move these two questions to the axis-dev you think?

  If axis is giving me a different WSDL file in two different Linux 
machines while
the configuration and version is the same, is that a bug I need to 
worry about?
And at least any information on how to manipulate the IP address in 
the WSDL

would be greatly appreciated.

Anyone??

Thanks once again
Demetris

Demetris G wrote:
>
> Hi all,
>
> Calling a service on the same machine as the axis server will set 
the namespace

> http://127.0.0.1:8080/axis/services/
>
> However, calling it from another node in the same network behind a 
NAT still

> returns the same IP address in the name space - is that normal?
>
> Also, how can the IP address in the first case (calling it from the 
same machine)

> be set to the true IP address of the machine?
>
> Also if anyone has any more info on my email below it will be 
greatly appreciated.

>
> Thanks
> Demetris
>
> Demetris G wrote:
>>
>> And scanning through the two WSDL files I see also other diffs -
>>
>> 
>> 
>> 
>>
>> vs.
>>
>> 
>> 
>> 
>>
>> So it seems to me that it treats the same service a bit differently 
on a separate

>> machine even though the setup/config etc of the server is identical.
>>
>> Demetris G wrote:
>>>
>>> At least someone may know this - what would cause the Axis engine 
to generate WSDLs
>>> with  instead of ? If I know that then I can 
probably figure out why
>>> the same Axis engine distribution on two different Linux boxes 
would generate two different

>>> types of WSDLs - I am using the same browser to issue the request:
>>> http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl
>>>
>>> One engine gives this:
>>> 
>>>
>>> ...
>>> 
>>>
>>> and the other:
>>> 
>>> http://xml.apache.org/xml-soap";>
>>> ...
>>> 
>>>
>>> Any ideas?
>>>
>>> Thanks
>>>
>>>
>>>> Demetris G wrote:
>>>>>
>>>>> And a follow up -
>>>>>
>>>>> same Axis engine (running in exactly same OSGi containers, same 
services, on one
>>>>> Linux machine it generates the WSDL file with  and the 
other with  !

>>>>> Why is that the case? This is a bit puzzling.
>>>>>
>>>>> Thanks very much in advance
>>>>>
>>>>> Demetris G wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>>this may have been asked a while back - what would cause the 
Axis engine to generate
>>>>>> WSDLs that carry  instead of : This causes 
the WSDL parser I use

>>>>>> to throw:
>>>>>>
>>>>>> [java] WSDLException (at /wsdl:definitions/types): 
faultCode=INVALID_WSDL:
>>>>>> Encountered illegal extension element 'types' in the context of 
a 'javax.wsdl.Definition'.

>>>>>> Extension elements must be in a namespace other than WSDL's.:
>>>>>>
>>>>>> Using Axis 1.4 over java 1.5.
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>
>>>>
>>>
>>
>

Re: WSDL gen error

[Demetris G]

Hi Lars,

   thanks for  the response and the info regarding the namespace. My 
issue is the following -


We have the Axis (1.4) bundles running in the OSGi container on a set of 
Linux machines with
no issues. Web Services can be published and invoked upon - the WSDL 
files that are generated
by these Axis bundles are correct and they can generate correct 
operational stubs.
We needed to run a few of these on some powerful mobile devices that can 
actually run Jalimo,
a full version (for fhe most part) of Java 1.5 based on the GNU 
libraries. So we simply installed
the same OSGi container and Axis (1.4) bundles on them and ran them. The 
Axis servers work
as they should, the generate WSDL files when invoked - however, the WSDL 
file they generate
encaplsulate the scheme definitions in  tags instead of 
 ! This is an issue
because  the XML parsers that process  tags nicely have a 
problem with the 

tags.
After hours of searching I came upon this - 
http://issues.apache.org/jira/browse/AXIS-2336.
Others a while back have encountered the same issue when running Axis on 
particular containers.
However, (a) their resolution is specific to their container (b) my 
issue is not the type of container
since the OSGi container works fine with Axis. My issue is that I moved 
more a Linux desktop
to a Linux mobile device, even though the executables and runtime 
remained the same.


I know that Axis 1.4 is ancient, however, there are still many of them 
in production and migration
for us is in our future plans but for now we need to get this to work. 
Any ideas would be greatly

appreciated.


Regards

Lars Ericsson wrote:

HI Demtirs!

I couldn't understand what is your problem, please describe more about 
your problem.
The namespace  can be anything, and it is nothing to do whit network, 
connection or anything else.

Please read more about namespace.
but if you get two different wsdl from two different environment, 
sound strange, alse i suppose you have the same axis-version same-java 
version and so on.
Please check manually call any service on those two service, if you 
don't get the same respons, it is some thing you should be worried 
about it. otherwise the differences between those two wsdl-s is not 
importent.




*From:* Demetris G 
*To:* axis-user@ws.apache.org
*Sent:* Sunday, July 12, 2009 7:32:32 AM
*Subject:* Re: WSDL gen error


Hi again,

  I am beginning to worry that (a) I am either asking a really stupid 
question here
and in the thread that is listed further down in my email that is not 
worth wasting
any time on (b) a really complicated question (I doubt it) (c) I am in 
the wrong

list ... should I move these two questions to the axis-dev you think?

  If axis is giving me a different WSDL file in two different Linux 
machines while
the configuration and version is the same, is that a bug I need to 
worry about?
And at least any information on how to manipulate the IP address in 
the WSDL

would be greatly appreciated.

Anyone??

Thanks once again
Demetris

Demetris G wrote:
>
> Hi all,
>
> Calling a service on the same machine as the axis server will set 
the namespace

> http://127.0.0.1:8080/axis/services/
>
> However, calling it from another node in the same network behind a 
NAT still

> returns the same IP address in the name space - is that normal?
>
> Also, how can the IP address in the first case (calling it from the 
same machine)

> be set to the true IP address of the machine?
>
> Also if anyone has any more info on my email below it will be 
greatly appreciated.

>
> Thanks
> Demetris
>
> Demetris G wrote:
>>
>> And scanning through the two WSDL files I see also other diffs -
>>
>> 
>> 
>> 
>>
>> vs.
>>
>> 
>> 
>> 
>>
>> So it seems to me that it treats the same service a bit differently 
on a separate

>> machine even though the setup/config etc of the server is identical.
>>
>> Demetris G wrote:
>>>
>>> At least someone may know this - what would cause the Axis engine 
to generate WSDLs
>>> with  instead of ? If I know that then I can 
probably figure out why
>>> the same Axis engine distribution on two different Linux boxes 
would generate two different

>>> types of WSDLs - I am using the same browser to issue the request:
>>> http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl
>>>
>>> One engine gives this:
>>> 
>>>
>>> ...
>>> 
>>>
>>> and the other:
>>> 
>>> http://xml.apache.org/xml-soap";>
>>> ...
>>> 
>>>
>>> Any ideas?
>>>
>>> Thanks
>>>
>>>
>>>> Demetris G wrote:
>>>>>
>&

Re: WSDL gen error

[Lars Ericsson]

HI Demtirs!

I couldn't understand what is your problem, please describe more about your 
problem.
The namespace  can be anything, and it is nothing to do whit network, 
connection or anything else.
Please read more about namespace.
but if you get two different wsdl from two different environment, sound 
strange, alse i suppose you have the same axis-version same-java version and so 
on.
Please check manually call any service on those two service, if you don't get 
the same respons, it is some thing you should be worried about it. otherwise 
the differences between those two wsdl-s is not importent.






From: Demetris G 
To: axis-user@ws.apache.org
Sent: Sunday, July 12, 2009 7:32:32 AM
Subject: Re: WSDL gen error


Hi again,

   I am beginning to worry that (a) I am either asking a really stupid question 
here
and in the thread that is listed further down in my email that is not worth 
wasting
any time on (b) a really complicated question (I doubt it) (c) I am in the wrong
list ... should I move these two questions to the axis-dev you think?

   If axis is giving me a different WSDL file in two different Linux machines 
while
the configuration and version is the same, is that a bug I need to worry about?
And at least any information on how to manipulate the IP address in the WSDL
would be greatly appreciated.

Anyone??

Thanks once again
Demetris

Demetris G wrote:
> 
> Hi all,
> 
> Calling a service on the same machine as the axis server will set the 
> namespace
> http://127.0.0.1:8080/axis/services/
> 
> However, calling it from another node in the same network behind a NAT still
> returns the same IP address in the name space - is that normal?
> 
> Also, how can the IP address in the first case (calling it from the same 
> machine)
> be set to the true IP address of the machine?
> 
> Also if anyone has any more info on my email below it will be greatly 
> appreciated.
> 
> Thanks
> Demetris
> 
> Demetris G wrote:
>> 
>> And scanning through the two WSDL files I see also other diffs -
>> 
>> 
>> 
>> 
>> 
>> vs.
>> 
>> 
>> 
>> 
>> 
>> So it seems to me that it treats the same service a bit differently on a 
>> separate
>> machine even though the setup/config etc of the server is identical.
>> 
>> Demetris G wrote:
>>> 
>>> At least someone may know this - what would cause the Axis engine to 
>>> generate WSDLs
>>> with  instead of ? If I know that then I can probably 
>>> figure out why
>>> the same Axis engine distribution on two different Linux boxes would 
>>> generate two different
>>> types of WSDLs - I am using the same browser to issue the request:
>>> http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl
>>> 
>>> One engine gives this:
>>> 
>>> 
>>> ...
>>> 
>>> 
>>> and the other:
>>> 
>>> http://xml.apache.org/xml-soap";>
>>> ...
>>> 
>>> 
>>> Any ideas?
>>> 
>>> Thanks
>>> 
>>> 
>>>> Demetris G wrote:
>>>>> 
>>>>> And a follow up -
>>>>> 
>>>>> same Axis engine (running in exactly same OSGi containers, same services, 
>>>>> on one
>>>>> Linux machine it generates the WSDL file with  and the other with 
>>>>>  !
>>>>> Why is that the case? This is a bit puzzling.
>>>>> 
>>>>> Thanks very much in advance
>>>>> 
>>>>> Demetris G wrote:
>>>>>> 
>>>>>> Hi all,
>>>>>> 
>>>>>>this may have been asked a while back - what would cause the Axis 
>>>>>> engine to generate
>>>>>> WSDLs that carry  instead of : This causes the WSDL 
>>>>>> parser I use
>>>>>> to throw:
>>>>>> 
>>>>>> [java] WSDLException (at /wsdl:definitions/types): 
>>>>>> faultCode=INVALID_WSDL:
>>>>>> Encountered illegal extension element 'types' in the context of a 
>>>>>> 'javax.wsdl.Definition'.
>>>>>> Extension elements must be in a namespace other than WSDL's.:
>>>>>> 
>>>>>> Using Axis 1.4 over java 1.5.
>>>>>> 
>>>>>> Any ideas?
>>>>>> 
>>>>>> Thanks
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
> 



  

Re: WSDL gen error

[Demetris G]

Hi again,

   I am beginning to worry that (a) I am either asking a really stupid 
question here
and in the thread that is listed further down in my email that is not 
worth wasting
any time on (b) a really complicated question (I doubt it) (c) I am in 
the wrong

list ... should I move these two questions to the axis-dev you think?

   If axis is giving me a different WSDL file in two different Linux 
machines while
the configuration and version is the same, is that a bug I need to worry 
about?

And at least any information on how to manipulate the IP address in the WSDL
would be greatly appreciated.

Anyone??

Thanks once again
Demetris

Demetris G wrote:


Hi all,

Calling a service on the same machine as the axis server will set the 
namespace

http://127.0.0.1:8080/axis/services/

However, calling it from another node in the same network behind a NAT 
still

returns the same IP address in the name space - is that normal?

Also, how can the IP address in the first case (calling it from the 
same machine)

be set to the true IP address of the machine?

Also if anyone has any more info on my email below it will be greatly 
appreciated.


Thanks
Demetris

Demetris G wrote:


And scanning through the two WSDL files I see also other diffs -





vs.





So it seems to me that it treats the same service a bit differently 
on a separate

machine even though the setup/config etc of the server is identical.

Demetris G wrote:


At least someone may know this - what would cause the Axis engine to 
generate WSDLs
with  instead of ? If I know that then I can 
probably figure out why
the same Axis engine distribution on two different Linux boxes would 
generate two different

types of WSDLs - I am using the same browser to issue the request:
http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl

One engine gives this:

http://xml.apache.org/xml-soap";>
...


and the other:

http://xml.apache.org/xml-soap";>
...


Any ideas?

Thanks



Demetris G wrote:


And a follow up -

same Axis engine (running in exactly same OSGi containers, same 
services, on one
Linux machine it generates the WSDL file with  and the 
other with  !

Why is that the case? This is a bit puzzling.

Thanks very much in advance

Demetris G wrote:


Hi all,

   this may have been asked a while back - what would cause the 
Axis engine to generate
WSDLs that carry  instead of : This causes the 
WSDL parser I use

to throw:

[java] WSDLException (at /wsdl:definitions/types): 
faultCode=INVALID_WSDL:
Encountered illegal extension element 'types' in the context of a 
'javax.wsdl.Definition'.

Extension elements must be in a namespace other than WSDL's.:

Using Axis 1.4 over java 1.5.

Any ideas?

Thanks

Re: WSDL gen error

[Demetris G]

Hi all,

Calling a service on the same machine as the axis server will set the 
namespace

http://127.0.0.1:8080/axis/services/

However, calling it from another node in the same network behind a NAT still
returns the same IP address in the name space - is that normal?

Also, how can the IP address in the first case (calling it from the same 
machine)

be set to the true IP address of the machine?

Also if anyone has any more info on my email below it will be greatly 
appreciated.


Thanks
Demetris

Demetris G wrote:


And scanning through the two WSDL files I see also other diffs -





vs.





So it seems to me that it treats the same service a bit differently on 
a separate

machine even though the setup/config etc of the server is identical.

Demetris G wrote:


At least someone may know this - what would cause the Axis engine to 
generate WSDLs
with  instead of ? If I know that then I can 
probably figure out why
the same Axis engine distribution on two different Linux boxes would 
generate two different

types of WSDLs - I am using the same browser to issue the request:
http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl

One engine gives this:

http://xml.apache.org/xml-soap";>
...


and the other:

http://xml.apache.org/xml-soap";>
...


Any ideas?

Thanks



Demetris G wrote:


And a follow up -

same Axis engine (running in exactly same OSGi containers, same 
services, on one
Linux machine it generates the WSDL file with  and the other 
with  !

Why is that the case? This is a bit puzzling.

Thanks very much in advance

Demetris G wrote:


Hi all,

   this may have been asked a while back - what would cause the 
Axis engine to generate
WSDLs that carry  instead of : This causes the 
WSDL parser I use

to throw:

[java] WSDLException (at /wsdl:definitions/types): 
faultCode=INVALID_WSDL:
Encountered illegal extension element 'types' in the context of a 
'javax.wsdl.Definition'.

Extension elements must be in a namespace other than WSDL's.:

Using Axis 1.4 over java 1.5.

Any ideas?

Thanks

Re: WSDL gen error

[Demetris G]

And scanning through the two WSDL files I see also other diffs -





vs.





So it seems to me that it treats the same service a bit differently on a 
separate

machine even though the setup/config etc of the server is identical.

Demetris G wrote:


At least someone may know this - what would cause the Axis engine to 
generate WSDLs
with  instead of ? If I know that then I can 
probably figure out why
the same Axis engine distribution on two different Linux boxes would 
generate two different

types of WSDLs - I am using the same browser to issue the request:
http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl

One engine gives this:

http://xml.apache.org/xml-soap";>
...


and the other:

http://xml.apache.org/xml-soap";>
...


Any ideas?

Thanks



Demetris G wrote:


And a follow up -

same Axis engine (running in exactly same OSGi containers, same 
services, on one
Linux machine it generates the WSDL file with  and the other 
with  !

Why is that the case? This is a bit puzzling.

Thanks very much in advance

Demetris G wrote:


Hi all,

   this may have been asked a while back - what would cause the 
Axis engine to generate
WSDLs that carry  instead of : This causes the 
WSDL parser I use

to throw:

[java] WSDLException (at /wsdl:definitions/types): 
faultCode=INVALID_WSDL:
Encountered illegal extension element 'types' in the context of a 
'javax.wsdl.Definition'.

Extension elements must be in a namespace other than WSDL's.:

Using Axis 1.4 over java 1.5.

Any ideas?

Thanks

Re: WSDL gen error

[Demetris G]

At least someone may know this - what would cause the Axis engine to 
generate WSDLs
with  instead of ? If I know that then I can probably 
figure out why
the same Axis engine distribution on two different Linux boxes would 
generate two different

types of WSDLs - I am using the same browser to issue the request:
http://xxx.xxx.xxx.xxx:8080/axis/services/remoteBooks?wsdl

One engine gives this:

http://xml.apache.org/xml-soap";>
...


and the other:

http://xml.apache.org/xml-soap";>
...


Any ideas?

Thanks



Demetris G wrote:


And a follow up -

same Axis engine (running in exactly same OSGi containers, same 
services, on one
Linux machine it generates the WSDL file with  and the other 
with  !

Why is that the case? This is a bit puzzling.

Thanks very much in advance

Demetris G wrote:


Hi all,

   this may have been asked a while back - what would cause the Axis 
engine to generate
WSDLs that carry  instead of : This causes the 
WSDL parser I use

to throw:

[java] WSDLException (at /wsdl:definitions/types): 
faultCode=INVALID_WSDL:
Encountered illegal extension element 'types' in the context of a 
'javax.wsdl.Definition'.

Extension elements must be in a namespace other than WSDL's.:

Using Axis 1.4 over java 1.5.

Any ideas?

Thanks

Re: WSDL gen error

[Demetris G]

I am still stuck on this one - any hints would be greatly appreciated.

Thanks again

Demetris G wrote:


And a follow up -

same Axis engine (running in exactly same OSGi containers, same 
services, on one
Linux machine it generates the WSDL file with  and the other 
with  !

Why is that the case? This is a bit puzzling.

Thanks very much in advance

Demetris G wrote:


Hi all,

   this may have been asked a while back - what would cause the Axis 
engine to generate
WSDLs that carry  instead of : This causes the 
WSDL parser I use

to throw:

[java] WSDLException (at /wsdl:definitions/types): 
faultCode=INVALID_WSDL:
Encountered illegal extension element 'types' in the context of a 
'javax.wsdl.Definition'.

Extension elements must be in a namespace other than WSDL's.:

Using Axis 1.4 over java 1.5.

Any ideas?

Thanks

Re: WSDL gen error

[Demetris G]

And a follow up -

same Axis engine (running in exactly same OSGi containers, same 
services, on one
Linux machine it generates the WSDL file with  and the other with 
 !

Why is that the case? This is a bit puzzling.

Thanks very much in advance

Demetris G wrote:


Hi all,

   this may have been asked a while back - what would cause the Axis 
engine to generate
WSDLs that carry  instead of : This causes the WSDL 
parser I use

to throw:

[java] WSDLException (at /wsdl:definitions/types): 
faultCode=INVALID_WSDL:
Encountered illegal extension element 'types' in the context of a 
'javax.wsdl.Definition'.

Extension elements must be in a namespace other than WSDL's.:

Using Axis 1.4 over java 1.5.

Any ideas?

Thanks

Re: WSDL attachment example

[Nan Null]

Thanks to Amila, he responded to my previous same question, but I
missed it.  This example is just what I need.
Thank you very much!

http://amilachinthaka.blogspot.com/2009/01/using-mtom-with-axis2.html


On Wed, Mar 11, 2009 at 12:49 AM, Nan Null  wrote:
> I am developing a WSDL for a web service.  However, I don't know what
> is the standard way of having an attachment or two in web service
> calls (with other data).  The problem is that I saw some example, but
> in the WSDL, there is no mention of the attachment.  I also use the
> Axis2 example of attachment, and then view the WSDL, again, there is
> no mention of the attachment.  In the client and server code, the
> attachment is there (manually added into the code).
> After the WSDL is created, it will be sent to another unit for
> development.  Therefore, if I need 1 or more attachment in an
> operation, I need a way to specify it exactly (as input, output or
> both).
>
> Please point me to the right location or give me a snippet of code.
> It cannot be this hard.  Please use standard code only.  Thanks.
>

Re: WSDL Specs

[Amila Suriarachchi]

On Tue, Feb 10, 2009 at 3:25 AM, Harshad Chavan wrote:

> Hi all,
>
> Does anybody know about any book/article, which explains WSDL and SOAP in
> detail (Not necessarily in Axis context). I went to w3c site, but the
> information is too cryptic.


Following articles explains the  wsdl  and soap basics[1][2]. After
following this you may read the corresponding specifications for more
information.

thanks,
Amila.

[1] http://wso2.org/library/2873
[2] http://wso2.org/node/2935/

>
>
> What we want to do is consume web services by third party, by reading the
> WSDLs from third party servers.
>
> Any help will be great.
>
> Thanks
> Harshad
>
> LongJump - Platform as a Service 
>
>
>


-- 
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/

Re: WSDL Specs

[Pradeep Fernando]

the following article from W3C , still it explains all the aspects of
WSDL2.0 using examples. i myself learned WSDL2.0 using this primer. hope
this is useful  :)

http://www.w3.org/TR/wsdl20-primer/

Re: WSDL Specs

[Harshad Chavan]

Thanks Michael.

LongJump - Platform as a Service 

--- On Mon, 2/9/09, Michael  wrote:

From: Michael 
Subject: Re: WSDL Specs
To: axis-user@ws.apache.org
Date: Monday, February 9, 2009, 2:52 PM



 
 

Try Web Services Essentials by Ethan Cerami, 
published by O'Reilly 2002

  - Original Message - 
  From: 
  Harshad 
  Chavan 
  To: axis-user@ws.apache.org 
  Sent: Monday, February 09, 2009 4:55 
  PM
  Subject: WSDL Specs
  

  


  Hi all,

Does anybody know about any book/article, 
which explains WSDL and SOAP in detail (Not necessarily in Axis 
context). I went to w3c site, but the information is too 
cryptic.

What we want to do is consume web services by third 
party, by reading the WSDLs from third party servers.

Any help 
will be great.

Thanks
Harshad

LongJump - Platform as a Service 




  
  

  
No virus found in this incoming message.
Checked by AVG - 
  www.avg.com 
Version: 8.0.233 / Virus Database: 270.10.19/1942 - Release 
  Date: 02/08/09 17:57:00



  

Re: WSDL Specs

[Michael]

Try Web Services Essentials by Ethan Cerami, published by O'Reilly 2002
  - Original Message - 
  From: Harshad Chavan 
  To: axis-user@ws.apache.org 
  Sent: Monday, February 09, 2009 4:55 PM
  Subject: WSDL Specs


Hi all,

Does anybody know about any book/article, which explains WSDL and SOAP 
in detail (Not necessarily in Axis context). I went to w3c site, but the 
information is too cryptic.

What we want to do is consume web services by third party, by reading 
the WSDLs from third party servers.

Any help will be great.

Thanks
Harshad

LongJump - Platform as a Service 

   




--



  No virus found in this incoming message.
  Checked by AVG - www.avg.com 
  Version: 8.0.233 / Virus Database: 270.10.19/1942 - Release Date: 02/08/09 
17:57:00

Re: WSDL version issue

[Anne Thomas Manes]

The WSDL namespace URI indicates the WSDL version.

Anne

On 1/19/09, Shah Asrani  wrote:
> Hi,
> Is the any way in Axis2 to find out the version of WSDL file
> programmatically,  I need to find ouf if a given WSDL file is version
> 1.1 or 2.0?
>
> Best Regards
>

RE: WSDL Generation has incorrect port

[Kevin Witten]

I downloaded and build the latest trunk and gave it a try. Still does not work.

The useOriginalwsdl parameter in the services.xml has no affect at all.

The modifyUserWSDLPortAddress parameter, if set to true, in the services.xml 
causes the wsdl writer to change both the hostname and the port.
So I get



https://67.130.148.13:80/axis2/services/ACSService.ACSServiceSOAP/"/>



Notice the port is 80.

What I need is



https://67.130.148.13/axis2/services/ACSService.ACSServiceSOAP/"/>




Because Apache is configured to only accept https connections on the default 
port.
Alternatively, this would also work



https://67.130.148.13:443/axis2/services/ACSService.ACSServiceSOAP/"/>



Any other ideas?
Kevin Witten
Software Engineer
Nomadix, Inc.  *  1100 Business Center Circle, Suite 100, Newbury Park, CA 
91320  *  USA
direct +1 (818) 575-2421  *  main +1-818-597-1500  *  fax
interTouch Group of Companies  *  a NTT DoCoMo Group company
Enhancing Guest Experience
www.inter-touch.com<http://www.inter-touch.com/> *  
www.maginet.net<http://www.maginet.net/> *  
www.percipia.com<http://www.percipia.com/> *  www.nomadix.com 
<http://www.nomadix.com/>  *  www.azure.com.au<http://www.azure.com.au/>
From: Nandana Mihindukulasooriya [mailto:nandana@gmail.com]
Sent: Tuesday, January 06, 2009 8:09 PM
To: axis-user@ws.apache.org
Subject: Re: WSDL Generation has incorrect port

Hi Kevin,
   Did you try this with the trunk ? There were few changes with respect to 
this in the trunk.

thanks,
nandana
On Wed, Jan 7, 2009 at 3:45 AM, Kevin Witten 
mailto:kevin.wit...@nomadix.com>> wrote:

Hello,



I am using Axis2 1.4.1 with Tomcat 6.0 and Apache2.2 httpd.



I setup Apache httpd to only support SSL and to connect to Tomcat via a proxy 
(AJP), via port 8009.



Apache httpd.conf has



SSLProxyEngine On

ProxyRequests Off

ProxyPass /  ajp://localhost:8009/

ProxyPassReverse  /  ajp://localhost:8009/

ProxyPreserveHost On



Tomcat server.xml has the following connector









Now I deploy an Axis2 service (ACSService.aar) in the 
webapps\axis2\WEB-INF\services directory.

Restart Tomcat and Apache.



This service includes a WSDL file with the following port:









https://localhost/axis2/services/ACSService"/>







I have changed the services.xml file to include

true



Now when I run get the WSDL from the service (i.e. 
https://67.130.148.13/axis2/services/ACSService?wsdl) The URL in the port is 
not correct.

Notice the port 80. This is not correct as the only way to access this service 
is through SSL (port 443) as Apache is configured.







https://67.130.148.13:80/axis2/services/ACSService/"/>







Next I tried adding the following to services.xml

false



But this did not do what I expected. I would have expected the hostname up get 
updated to 67.130.148.13. Instead the URL was not changed at all.

So the output was as follows, which is the unmodified URL form the original 
WSDL.







https://localhost/axis2/services/ACSService/"/>







This seems like a bug, as the modifyUserWSDLPortAddress controls updating of 
the hostname and port.



How do I get the WSDL to update to the hostname with no port, or as a second 
choice port 443?







https://67.130.148.13/axis2/services/ACSService/"/>









Thanks in advanced for the help.



Kevin Witten
Software Engineer
Nomadix, Inc.  *  1100 Business Center Circle, Suite 100, Newbury Park, CA 
91320  *  USA
direct +1 (818) 575-2421  *  main +1-818-597-1500  *  fax

interTouch Group of Companies  *  a NTT DoCoMo Group company
Enhancing Guest Experience

www.inter-touch.com<http://www.inter-touch.com/> *  
www.maginet.net<http://www.maginet.net/> *  
www.percipia.com<http://www.percipia.com/> *  www.nomadix.com 
<http://www.nomadix.com/>  *  www.azure.com.au<http://www.azure.com.au/>


Notice● The information and attachment(s) contained in this communication are 
intended for the addressee only, and may be confidential and/or legally 
privileged. If you have received this communication in error, please contact 
the sender immediately, and delete this communication from any computer or 
network system. Any interception, review, printing, copying, re-transmission, 
dissemination, or other use of, or taking of any action upon this information 
by persons or entities other than the intended recipient is strictly prohibited 
by law and may subject them to criminal or civil liability. None of the 
interTouch Group of Companies shall be liable for the improper and/or 
incomplete transmission of the information contained in this communication or 
for any delay in its receipt.


Notice● The information and attachment(s) contained in this communication are 
intended for the addressee only, and may be confidential and/or lega

RE: WSDL Generation has incorrect port

[Kevin Witten]

Hello Nandana,

Thanks for the reply.

Is there a nightly build I can download?
Or do I need to get the latest code from the trunk and build it? And where do I 
get the trunk from?

Thanks,

Kevin Witten
Software Engineer
Nomadix, Inc.  *  1100 Business Center Circle, Suite 100, Newbury Park, CA 
91320  *  USA
direct +1 (818) 575-2421  *  main +1-818-597-1500  *  fax
interTouch Group of Companies  *  a NTT DoCoMo Group company
Enhancing Guest Experience
www.inter-touch.com<http://www.inter-touch.com/> *  
www.maginet.net<http://www.maginet.net/> *  
www.percipia.com<http://www.percipia.com/> *  www.nomadix.com 
<http://www.nomadix.com/>  *  www.azure.com.au<http://www.azure.com.au/>
From: Nandana Mihindukulasooriya [mailto:nandana@gmail.com]
Sent: Tuesday, January 06, 2009 8:09 PM
To: axis-user@ws.apache.org
Subject: Re: WSDL Generation has incorrect port

Hi Kevin,
   Did you try this with the trunk ? There were few changes with respect to 
this in the trunk.

thanks,
nandana
On Wed, Jan 7, 2009 at 3:45 AM, Kevin Witten 
mailto:kevin.wit...@nomadix.com>> wrote:

Hello,



I am using Axis2 1.4.1 with Tomcat 6.0 and Apache2.2 httpd.



I setup Apache httpd to only support SSL and to connect to Tomcat via a proxy 
(AJP), via port 8009.



Apache httpd.conf has



SSLProxyEngine On

ProxyRequests Off

ProxyPass /  ajp://localhost:8009/

ProxyPassReverse  /  ajp://localhost:8009/

ProxyPreserveHost On



Tomcat server.xml has the following connector









Now I deploy an Axis2 service (ACSService.aar) in the 
webapps\axis2\WEB-INF\services directory.

Restart Tomcat and Apache.



This service includes a WSDL file with the following port:









https://localhost/axis2/services/ACSService"/>







I have changed the services.xml file to include

true



Now when I run get the WSDL from the service (i.e. 
https://67.130.148.13/axis2/services/ACSService?wsdl) The URL in the port is 
not correct.

Notice the port 80. This is not correct as the only way to access this service 
is through SSL (port 443) as Apache is configured.







https://67.130.148.13:80/axis2/services/ACSService/"/>







Next I tried adding the following to services.xml

false



But this did not do what I expected. I would have expected the hostname up get 
updated to 67.130.148.13. Instead the URL was not changed at all.

So the output was as follows, which is the unmodified URL form the original 
WSDL.







https://localhost/axis2/services/ACSService/"/>







This seems like a bug, as the modifyUserWSDLPortAddress controls updating of 
the hostname and port.



How do I get the WSDL to update to the hostname with no port, or as a second 
choice port 443?







https://67.130.148.13/axis2/services/ACSService/"/>









Thanks in advanced for the help.



Kevin Witten
Software Engineer
Nomadix, Inc.  *  1100 Business Center Circle, Suite 100, Newbury Park, CA 
91320  *  USA
direct +1 (818) 575-2421  *  main +1-818-597-1500  *  fax

interTouch Group of Companies  *  a NTT DoCoMo Group company
Enhancing Guest Experience

www.inter-touch.com<http://www.inter-touch.com/> *  
www.maginet.net<http://www.maginet.net/> *  
www.percipia.com<http://www.percipia.com/> *  www.nomadix.com 
<http://www.nomadix.com/>  *  www.azure.com.au<http://www.azure.com.au/>


Notice● The information and attachment(s) contained in this communication are 
intended for the addressee only, and may be confidential and/or legally 
privileged. If you have received this communication in error, please contact 
the sender immediately, and delete this communication from any computer or 
network system. Any interception, review, printing, copying, re-transmission, 
dissemination, or other use of, or taking of any action upon this information 
by persons or entities other than the intended recipient is strictly prohibited 
by law and may subject them to criminal or civil liability. None of the 
interTouch Group of Companies shall be liable for the improper and/or 
incomplete transmission of the information contained in this communication or 
for any delay in its receipt.


Notice● The information and attachment(s) contained in this communication are 
intended for the addressee only, and may be confidential and/or legally 
privileged. If you have received this communication in error, please contact 
the sender immediately, and delete this communication from any computer or 
network system. Any interception, review, printing, copying, re-transmission, 
dissemination, or other use of, or taking of any action upon this information 
by persons or entities other than the intended recipient is strictly prohibited 
by law and may subject them to criminal or civil liability. None of the 
interTouch Group of Companies shall be liable for the improper and/or 
i

Re: WSDL Generation has incorrect port

[Nandana Mihindukulasooriya]

Hi Kevin,
   Did you try this with the trunk ? There were few changes with respect
to this in the trunk.

thanks,
nandana

On Wed, Jan 7, 2009 at 3:45 AM, Kevin Witten wrote:

>  Hello,
>
>
>
> I am using Axis2 1.4.1 with Tomcat 6.0 and Apache2.2 httpd.
>
>
>
> I setup Apache httpd to only support SSL and to connect to Tomcat via a
> proxy (AJP), via port 8009.
>
>
>
> Apache httpd.conf has
>
>
>
> SSLProxyEngine On
>
> ProxyRequests Off
>
> ProxyPass /  ajp://localhost:8009/
>
> ProxyPassReverse  /  ajp://localhost:8009/
>
> ProxyPreserveHost On
>
>
>
> Tomcat server.xml has the following connector
>
>
>
> 
>
>
>
>
>
> Now I deploy an Axis2 service (ACSService.aar) in the
> webapps\axis2\WEB-INF\services directory.
>
> Restart Tomcat and Apache.
>
>
>
> This service includes a WSDL file with the following port:
>
>
>
> 
>
> 
>
> 
>name="ACSServiceSOAP">
>
> 
> location="https://localhost/axis2/services/ACSService
> "/>
>
> 
>
> 
>
>
>
> I have changed the services.xml file to include
>
> true
>
>
>
> Now when I run get the WSDL from the service (i.e.
> https://67.130.148.13/axis2/services/ACSService?wsdl) The URL in the port
> is not correct.
>
> Notice the port 80. This is not correct as the only way to access this
> service is through SSL (port 443) as Apache is configured.
>
>
>
> 
>
> 
>
> https://67.130.148.13:80/axis2/services/ACSService/"/>
>
> 
>
> 
>
>
>
> Next I tried adding the following to services.xml
>
> false
>
>
>
> But this did not do what I expected. I would have expected the hostname up
> get updated to 67.130.148.13. Instead the URL was not changed at all.
>
> So the output was as follows, which is the unmodified URL form the original
> WSDL.
>
>
>
> 
>
> 
>
> https://localhost/axis2/services/ACSService/"/>
>
> 
>
> 
>
>
>
> This seems like a bug, as the modifyUserWSDLPortAddress controls updating
> of the hostname and port.
>
>
>
> How do I get the WSDL to update to the hostname with no port, or as a
> second choice port 443?
>
>
>
> 
>
> 
>
> https://67.130.148.13/axis2/services/ACSService/
> "/>
>
> 
>
> 
>
>
>
>
>
> Thanks in advanced for the help.
>
>
>
> *Kevin Witten*
> Software Engineer
> Nomadix, Inc.  *  1100 Business Center Circle, Suite 100, Newbury Park, CA
> 91320  *  USA
> direct +1 (818) 575-2421  *  main +1-818-597-1500  *  fax
>
> *interTouch Group of Companies  *  a NTT DoCoMo Group company
> *Enhancing Guest Experience
>
> www.inter-touch.com *  www.maginet.net *  www.percipia.com *  www.nomadix.com
>  *  www.azure.com.au
>
> --
> Notice● The information and attachment(s) contained in this communication
> are intended for the addressee only, and may be confidential and/or legally
> privileged. If you have received this communication in error, please contact
> the sender immediately, and delete this communication from any computer or
> network system. Any interception, review, printing, copying,
> re-transmission, dissemination, or other use of, or taking of any action
> upon this information by persons or entities other than the intended
> recipient is strictly prohibited by law and may subject them to criminal or
> civil liability. None of the interTouch Group of Companies shall be liable
> for the improper and/or incomplete transmission of the information contained
> in this communication or for any delay in its receipt.
>

Re: wsdl problem

[Andreas Veithen]

Miguel,

Did you try this also with a more recent version of Axis2?

Andreas

On Tue, Dec 9, 2008 at 05:11,  <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> I have the following wsdl error
>
> when i deploy my web service project in a soalris server i get this
> information via
>
> http://ipserver:8080/MileniaServices/services/wsMilenia?wsdl
>
>
> - 
> -  binding="axis2:wsMileniaSOAP11Binding">
>location="http://ipserver:8080/MileniaServices/services/wsMilenia"; />
>   
> -  binding="axis2:wsMileniaSOAP12Binding">
>location="http://ipserver:8080/MileniaServices/services/wsMilenia"; />
>   
> - 
>location="http://ipserver:8080/MileniaServices/rest/wsMilenia"; />
>   
>   
>
>
> but suddenly or when i restart the tomcat server y get the following
> information in the wsdl via
> http://ipserver:8080/MileniaServices/services/wsMilenia?wsdl
>
> - 
> -  binding="axis2:wsMileniaSOAP11Binding">
>   http://ipserver:8080/axis2/services/wsMilenia"; />
>   
> -  binding="axis2:wsMileniaSOAP12Binding">
>   http://ipserver:8080/axis2/services/wsMilenia";
> />
>   
> - 
>   http://ipserver:8080/axis2/rest/wsMilenia"; />
>   
>   
>
>
> it is, the context name changes from MileniaServices to axis2 in the address
> attribute of the soap,soap12 and http tag of the wsdl
>
> so, i have to restart tomcat sometimes several times to it changes to the
> context i want (MileniaServices), it affects to my .net web services
> clients, because this reference is changing
>
> i've tried with  true  in the
> services.xml file but it gets me confused if axis2 really take it or not
>
> i really will be appreciate you be able to help me
>
> axis version axis2-1.1.1
> tomcat versiontomcat 5.0.28
>
> thanks!!!
>
> Miguel

Re: wsdl-level client side compatibility between Axis 2 and Axis 1

[keith chapman]

Axis2 does not support soap-encoding (whereas Axis does), but soap-encoding
is actually deprecated. Other then that you should be just fine. And its
much better for you to go with Axis2 than Axis.

Thanks,
Keith.

On Tue, Sep 30, 2008 at 2:55 AM, Steve Cohen <[EMAIL PROTECTED]> wrote:

> Will a WSDL written and recommended to be used with Axis 1 definitely be
> usable with Axis 2 on the client side?  We have no investment in Axis 1 so
> if the switch is possible, we should probably make it now.  My group is
> going to be incorporating several web service clients into an application
> that currently has none, so my question is geared toward selecting the best
> client side technology going forward.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

Re: wsdl port address uses incorrect port number for https

[keith chapman]

Would you mind opening a JIRA issue please. That way it will be tracked.

Thanks,
Keith.

On Thu, Sep 25, 2008 at 7:34 AM, Pugalia, Jai P (JP) <[EMAIL PROTECTED]>wrote:

>  Hi Keith,
>
> For now, I had solved the problem by writing my own Listener by
> implementing the TransportListener class. I like your suggestion of
> extending the existing Listener so I am going to try it out.
>
> I also tried by adding the proxyPort to the Connector configuration in the
> server.xml of Tomcat, however looks like Axis2 does not use it and instead
> takes a value of  80. I hope this gets fixed in future versions of Axis2.
>
> Thanks,
> JP
>
>  --
> *From:* keith chapman [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, September 24, 2008 6:53 PM
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: wsdl port address uses incorrect port number for https
>
>  You could easily extend the Listener shipped with Axis2 and override its
> getEPRsForService method. This is the method that generates the endpoint
> address, so you could handle it the way you want it to be by simple
> extending it.
>
> Thanks,
> Keith.
>
> On Wed, Sep 24, 2008 at 10:11 PM, Pugalia, Jai P (JP) <[EMAIL 
> PROTECTED]>wrote:
>
>>  Hi,
>>
>> Does Axis2 include a class for transport listener which supports https?
>>
>> Is it possible to configure Axis2 to not include any port number when
>> generating the soap address?
>>
>> Thanks,
>> JP
>>
>>  ------
>>  *From:* Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED]
>> *Sent:* Monday, September 22, 2008 4:10 PM
>> *To:* axis-user@ws.apache.org
>>  *Subject:* RE: wsdl port address uses incorrect port number for https
>>
>>   Hi,
>>
>> The proxyPort does not help us as we are not using Apache as a proxy
>> server.
>>
>> If I configure the axis2.xml as below:
>>
>> > class="org.apache.axis2.transport.http.SimpleHTTPServer">
>> 8080
>> 
>>  
>> 8443
>> 
>>
>> then the soap address for http includes the port 8080 and the soap address
>> for https includes the port 8443 but the soap address itself is http and not
>> https.
>>
>> When should the class for transportReceiver be set to for https?
>>
>> If I do not specify the transportReceiver for https in axis2.xml, the the
>> default value of the port is taken as 80 instead of 443 which is the default
>> port for https.
>>
>> Thanks,
>> JP
>>
>>  --
>> *From:* keith chapman [mailto:[EMAIL PROTECTED]
>> *Sent:* Sunday, September 21, 2008 9:09 PM
>> *To:* axis-user@ws.apache.org
>> *Subject:* Re: wsdl port address uses incorrect port number for https
>>
>>  It should be specified in the http transport listener of the axis2.xml.
>> You can have a look at
>> https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xmlfor
>>  an example usage. This is the axis2.xml used in the WSO2 Mashup Server
>> [1]
>>
>> Look for the following.
>>
>> 
>> 
>>
>>
>> Thanks,
>> Keith.
>>
>> [1] http://wso2.org/projects/mashup
>>
>> On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) <[EMAIL 
>> PROTECTED]>wrote:
>>
>>>  Hi Keith,
>>>
>>> Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml,
>>> the http transport receiver has a port parameter is set to 8080 and the
>>> https transport receiver is commented out in axis2.xml. Am I heading in the
>>> right direction?
>>>
>>> Thanks,
>>> Jai
>>>
>>>  --
>>> *From:* keith chapman [mailto:[EMAIL PROTECTED]
>>> *Sent:* Sunday, September 21, 2008 10:02 AM
>>> *To:* axis-user@ws.apache.org
>>> *Subject:* Re: wsdl port address uses incorrect port number for https
>>>
>>>   Hi,
>>>
>>> When its going through Apache you can use the following parameter in the
>>> transport listener to set the port address,
>>>
>>> 80
>>>
>>> For the https listener you can set it to 443.
>>>
>>> Thanks,
>>> Keith.
>>>
>>> On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu <[EMAIL PROTECTED]>wrote:
>>>
>>>> JP, We have had similar challenges with our service where Axis2 (1.2)
>>>> resolves to port 80 instead of a custom port where we have our services
>>>>

RE: wsdl port address uses incorrect port number for https

[Pugalia, Jai P (JP)]

Hi Keith,
 
For now, I had solved the problem by writing my own Listener by
implementing the TransportListener class. I like your suggestion of
extending the existing Listener so I am going to try it out. 
 
I also tried by adding the proxyPort to the Connector configuration in
the server.xml of Tomcat, however looks like Axis2 does not use it and
instead takes a value of  80. I hope this gets fixed in future versions
of Axis2.
 
Thanks,
JP



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 24, 2008 6:53 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for https


You could easily extend the Listener shipped with Axis2 and override its
getEPRsForService method. This is the method that generates the endpoint
address, so you could handle it the way you want it to be by simple
extending it.

Thanks,
Keith.


On Wed, Sep 24, 2008 at 10:11 PM, Pugalia, Jai P (JP)
<[EMAIL PROTECTED]> wrote:


Hi,
 
Does Axis2 include a class for transport listener which supports
https? 
 
Is it possible to configure Axis2 to not include any port number
when generating the soap address?
 
Thanks,
JP




From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] 

Sent: Monday, September 22, 2008 4:10 PM 

To: axis-user@ws.apache.org

Subject: RE: wsdl port address uses incorrect port number for
https


Hi,
 
The proxyPort does not help us as we are not using Apache as a
proxy server.
 
If I configure the axis2.xml as below: 
 

8080



8443

 
then the soap address for http includes the port 8080 and the
soap address for https includes the port 8443 but the soap address
itself is http and not https.
 
When should the class for transportReceiver be set to for https?
 
If I do not specify the transportReceiver for https in
axis2.xml, the the default value of the port is taken as 80 instead of
443 which is the default port for https.
 
Thanks,
JP
 


From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 21, 2008 9:09 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for
https


It should be specified in the http transport listener of the
axis2.xml.  You can have a look at
https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis
2.xml for an example usage. This is the axis2.xml used in the WSO2
Mashup Server [1]

Look for the following.







Thanks,
Keith.

[1] http://wso2.org/projects/mashup


On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP)
<[EMAIL PROTECTED]> wrote:


Hi Keith,
 
Where do I specify this parameter? I am guessing
axis2.xml. In axis2.xml, the http transport receiver has a port
parameter is set to 8080 and the https transport receiver is commented
out in axis2.xml. Am I heading in the right direction?
 
Thanks,
Jai



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 21, 2008 10:02 AM 

To: axis-user@ws.apache.org

    Subject: Re: wsdl port address uses incorrect port
number for https


Hi,

When its going through Apache you can use the following
parameter in the transport listener to set the port address,

80

For the https listener you can set it to 443.

Thanks,
Keith.


On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu
<[EMAIL PROTECTED]> wrote:


JP, We have had similar challenges with our
service where Axis2 (1.2) resolves to port 80 instead of a custom port
where we have our services available on Jboss. One reason for that is
our client goes thru apache web server in the middle and hence the port
is always resolved to 80. Hence we had to hardcode the EPR in the WSDL
and set the following parameters as Charitha outlined. 
 
Did you try accessing the same services thru
SOAPUI and see if it is also doing the same?.
 
regards

Re: wsdl port address uses incorrect port number for https

[keith chapman]

You could easily extend the Listener shipped with Axis2 and override its
getEPRsForService method. This is the method that generates the endpoint
address, so you could handle it the way you want it to be by simple
extending it.

Thanks,
Keith.

On Wed, Sep 24, 2008 at 10:11 PM, Pugalia, Jai P (JP) <[EMAIL PROTECTED]>wrote:

>  Hi,
>
> Does Axis2 include a class for transport listener which supports https?
>
> Is it possible to configure Axis2 to not include any port number when
> generating the soap address?
>
> Thanks,
> JP
>
>  --
> *From:* Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED]
> *Sent:* Monday, September 22, 2008 4:10 PM
> *To:* axis-user@ws.apache.org
> *Subject:* RE: wsdl port address uses incorrect port number for https
>
>  Hi,
>
> The proxyPort does not help us as we are not using Apache as a proxy
> server.
>
> If I configure the axis2.xml as below:
>
>  class="org.apache.axis2.transport.http.SimpleHTTPServer">
> 8080
> 
>  
> 8443
> 
>
> then the soap address for http includes the port 8080 and the soap address
> for https includes the port 8443 but the soap address itself is http and not
> https.
>
> When should the class for transportReceiver be set to for https?
>
> If I do not specify the transportReceiver for https in axis2.xml, the the
> default value of the port is taken as 80 instead of 443 which is the default
> port for https.
>
> Thanks,
> JP
>
>  ------
> *From:* keith chapman [mailto:[EMAIL PROTECTED]
> *Sent:* Sunday, September 21, 2008 9:09 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: wsdl port address uses incorrect port number for https
>
>  It should be specified in the http transport listener of the axis2.xml.
> You can have a look at
> https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xmlfor
>  an example usage. This is the axis2.xml used in the WSO2 Mashup Server
> [1]
>
> Look for the following.
>
> 
> 
>
> Thanks,
> Keith.
>
> [1] http://wso2.org/projects/mashup
>
> On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) <[EMAIL PROTECTED]>wrote:
>
>>  Hi Keith,
>>
>> Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml,
>> the http transport receiver has a port parameter is set to 8080 and the
>> https transport receiver is commented out in axis2.xml. Am I heading in the
>> right direction?
>>
>> Thanks,
>> Jai
>>
>>  --
>> *From:* keith chapman [mailto:[EMAIL PROTECTED]
>> *Sent:* Sunday, September 21, 2008 10:02 AM
>> *To:* axis-user@ws.apache.org
>> *Subject:* Re: wsdl port address uses incorrect port number for https
>>
>>   Hi,
>>
>> When its going through Apache you can use the following parameter in the
>> transport listener to set the port address,
>>
>> 80
>>
>> For the https listener you can set it to 443.
>>
>> Thanks,
>> Keith.
>>
>> On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu <[EMAIL PROTECTED]>wrote:
>>
>>> JP, We have had similar challenges with our service where Axis2 (1.2)
>>> resolves to port 80 instead of a custom port where we have our services
>>> available on Jboss. One reason for that is our client goes thru apache web
>>> server in the middle and hence the port is always resolved to 80. Hence we
>>> had to hardcode the EPR in the WSDL and set the following parameters as
>>> Charitha outlined.
>>>
>>> Did you try accessing the same services thru SOAPUI and see if it is also
>>> doing the same?.
>>>
>>> regards
>>> Madhav
>>>
>>>
>>>
>>>
>>> --
>>>
>>> Subject: RE: wsdl port address uses incorrect port number for https
>>> Date: Sun, 21 Sep 2008 09:51:13 -0600
>>> From: [EMAIL PROTECTED]
>>> To: axis-user@ws.apache.org; axis-user@ws.apache.org
>>>
>>>
>>>
>>> Hi,
>>>
>>> My Axis2 web service is deployed for secure access and the URL is of the
>>> form "https:// /axis2/services/Version?wsdl".
>>> However when the WSDL is returned, port number 80 is specified in the soap
>>> address instead of port 443 (default port for https).
>>>
>>> I have verified that the port number in the request object is also 443.
>>> Is this a bug in Axis2?
>>>
>>> Regards,
>>> Jai
>>>
>>> -Original

RE: wsdl port address uses incorrect port number for https

[Pugalia, Jai P (JP)]

Yes, I agree doesn't make sense to use the SimpleHTTPServer class for
http and https. 
 
Looks like Axis2 uses a HTTPSListener internally if https configuration
is not available in the axis2.xml. However this class is private and not
exposed to general use.
 
I noticed the SSL configuration about configuring non-blocking https
transport based on SSL-NIO extensions. But to use it I need to configure
keystore and truststore. 
 
All I am looking for is that the soap address generated in the WSDL has
either no port number or the correct port number for https.
 
JP



From: Martin Gainty [mailto:[EMAIL PROTECTED] 
Sent: Monday, September 22, 2008 6:53 PM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect port number for https


doesnt make sense to use the same
org.apache.axis2.transport.http.SimpleHTTPServer
class for both http and https transport
this is the SSL configuration  I see for configuring
HttpCoreNIOSSLListener in axis2.xml





//the default behaviour is to  have your service engage Rampart module
as in this definition in services.xml



  
Timestamp Signature
service.properties
  



  
Timestamp Signature
service
 
org.apache.rampart.samples.sample04.PWCBHandler
service.properties
DirectReference
  

..

HTH
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official
business of Sender. This transmission is of a confidential nature and
Sender does not endorse distribution to any party other than intended
recipient. Sender does not necessarily endorse content contained within
this transmission. 





Subject: RE: wsdl port address uses incorrect port number for https
Date: Mon, 22 Sep 2008 17:10:22 -0600
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org


Hi,
 
The proxyPort does not help us as we are not using Apache as a proxy
server.
 
If I configure the axis2.xml as below: 
 

8080


8443

 
then the soap address for http includes the port 8080 and the soap
address for https includes the port 8443 but the soap address itself is
http and not https.
 
When should the class for transportReceiver be set to for https?
 
If I do not specify the transportReceiver for https in axis2.xml, the
the default value of the port is taken as 80 instead of 443 which is the
default port for https.
 
Thanks,
JP
 


From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 21, 2008 9:09 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for https


It should be specified in the http transport listener of the axis2.xml.
You can have a look at
https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis
2.xml for an example usage. This is the axis2.xml used in the WSO2
Mashup Server [1]

Look for the following.






Thanks,
Keith.

[1] http://wso2.org/projects/mashup


On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP)
<[EMAIL PROTECTED]> wrote:


Hi Keith,
 
Where do I specify this parameter? I am guessing axis2.xml. In
axis2.xml, the http transport receiver has a port parameter is set to
8080 and the https transport receiver is commented out in axis2.xml. Am
I heading in the right direction?
 
Thanks,
Jai



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 21, 2008 10:02 AM 

To: axis-user@ws.apache.org

    Subject: Re: wsdl port address uses incorrect port number for
https


Hi,

When its going through Apache you can use the following
parameter in the transport listener to set the port address,

80

For the https listener you can set it to 443.

Thanks,
Keith.


On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu
<[EMAIL PROTECTED]> wrote:


JP, We have had similar challenges with our service
where Axis2 (1.2) resolves to port 80 instead of a custom port where we
have our services available on Jboss. One reason for that is our client
goes thru apache web server in the middle and hence the port is always
resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the
following parameters as Charitha outlined. 
 
Did you try accessing the same services thru SOAPUI and
see if it is also doing the same?.
 
regards
Madhav 








    Subject: RE: wsdl port address uses incorrect port

RE: wsdl port address uses incorrect port number for https

[Pugalia, Jai P (JP)]

Hi,
 
Does Axis2 include a class for transport listener which supports https? 
 
Is it possible to configure Axis2 to not include any port number when
generating the soap address?
 
Thanks,
JP



From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] 
Sent: Monday, September 22, 2008 4:10 PM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect port number for https


Hi,
 
The proxyPort does not help us as we are not using Apache as a proxy
server.
 
If I configure the axis2.xml as below: 
 

8080


8443

 
then the soap address for http includes the port 8080 and the soap
address for https includes the port 8443 but the soap address itself is
http and not https.
 
When should the class for transportReceiver be set to for https?
 
If I do not specify the transportReceiver for https in axis2.xml, the
the default value of the port is taken as 80 instead of 443 which is the
default port for https.
 
Thanks,
JP
 


From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 21, 2008 9:09 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for https


It should be specified in the http transport listener of the axis2.xml.
You can have a look at
https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis
2.xml for an example usage. This is the axis2.xml used in the WSO2
Mashup Server [1]

Look for the following.






Thanks,
Keith.

[1] http://wso2.org/projects/mashup


On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP)
<[EMAIL PROTECTED]> wrote:


Hi Keith,
 
Where do I specify this parameter? I am guessing axis2.xml. In
axis2.xml, the http transport receiver has a port parameter is set to
8080 and the https transport receiver is commented out in axis2.xml. Am
I heading in the right direction?
 
Thanks,
Jai



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 21, 2008 10:02 AM 

To: axis-user@ws.apache.org

Subject: Re: wsdl port address uses incorrect port number for
https


Hi,

When its going through Apache you can use the following
parameter in the transport listener to set the port address,

80

For the https listener you can set it to 443.

Thanks,
Keith.


On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu
<[EMAIL PROTECTED]> wrote:


JP, We have had similar challenges with our service
where Axis2 (1.2) resolves to port 80 instead of a custom port where we
have our services available on Jboss. One reason for that is our client
goes thru apache web server in the middle and hence the port is always
resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the
following parameters as Charitha outlined. 
 
Did you try accessing the same services thru SOAPUI and
see if it is also doing the same?.
 
regards
Madhav 








    Subject: RE: wsdl port address uses incorrect port
number for https
Date: Sun, 21 Sep 2008 09:51:13 -0600
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org; axis-user@ws.apache.org 



Hi,

My Axis2 web service is deployed for secure access and
the URL is of the form "https:// 
/axis2/services/Version?wsdl". However when the WSDL is
returned, port number 80 is specified in the soap address instead of
port 443 (default port for https).

I have verified that the port number in the request
object is also 443. Is this a bug in Axis2?

Regards,
Jai

-Original Message-
From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED]
Sent: Fri 9/19/2008 8:52 AM
To: axis-user@ws.apache.org
        Subject: RE: wsdl port address uses incorrect port
number

Hi Charitha,

I am not including the wsdl with the aar file. Including
the wsdl
causing other problems. (There is a separate email chain
on this issue).

I do want the hostname to be updated to the machine name
or ip address
of the installed machine. The issue is port number is
being set to a
wrong value. How does Axis2 determine what the port
number should be set
to? Is there some way we can specify what the

RE: wsdl port address uses incorrect port number for https

[Martin Gainty]

doesnt make sense to use the same 
org.apache.axis2.transport.http.SimpleHTTPServer
class for both http and https transport
this is the SSL configuration  I see for configuring HttpCoreNIOSSLListener in 
axis2.xml





//the default behaviour is to  have your service engage Rampart module as in 
this definition in services.xml



  
Timestamp Signature
service.properties
  



  
Timestamp Signature
service

org.apache.rampart.samples.sample04.PWCBHandler
service.properties
DirectReference
  

..

HTH
Martin 
__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


Subject: RE: wsdl port address uses incorrect port number for https
Date: Mon, 22 Sep 2008 17:10:22 -0600
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org








Hi,
 
The proxyPort does not help us as we are not using Apache 
as a proxy server.
 
If I configure the axis2.xml as below: 
 


8080





8443


 
then the soap address for 
http includes the port 8080 and the soap address for https includes the port 
8443 but the soap address itself is http and not https.
 
When should the class for 
transportReceiver be set to for https?
 
If I do not specify the 
transportReceiver for https in axis2.xml, the the default value of the port is 
taken as 80 instead of 443 which is the default port for https.
 
Thanks,
JP
 


From: keith chapman 
[mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 21, 2008 
9:09 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port 
address uses incorrect port number for https



It should be specified in the http transport listener of the 
axis2.xml.  You can have a look at 
https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xml 
for an example usage. This is the axis2.xml used in the WSO2 Mashup Server 
[1]

Look for the following.





Thanks,
Keith.

[1] http://wso2.org/projects/mashup


On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) 
<[EMAIL PROTECTED]> wrote:


  
  Hi 
  Keith,
   
  Where do I 
  specify this parameter? I am guessing axis2.xml. In axis2.xml, the http 
  transport receiver has a port parameter is set to 8080 and the https 
  transport receiver is commented out in axis2.xml. Am I heading in the 
  right direction?
   
  Thanks,
  Jai

  
  
  From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 
  21, 2008 10:02 AM
  
To: axis-user@ws.apache.org
Subject: Re: wsdl 
  port address uses incorrect port number for https


  
  
  
  
  Hi,

When its going through Apache you can use the 
  following parameter in the transport listener to set the port 
  address,

80

For the https listener you can 
  set it to 443.

Thanks,
Keith.


  On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M 
  Naidu <[EMAIL PROTECTED]> wrote:

  
JP, We have had similar challenges with our service where Axis2 (1.2) 
resolves to port 80 instead of a custom port where we have our services 
available on Jboss. One reason for that is our client goes thru apache web 
server in the middle and hence the port is always resolved to 80. Hence we 
had to hardcode the EPR in the WSDL and set the following parameters as 
Charitha outlined. 
 
Did you try accessing the same 
services thru SOAPUI and see if it is also doing the 
same?.
 
regards
Madhav 






    
Subject: RE: wsdl port address uses incorrect port number for 
https
Date: Sun, 21 Sep 2008 09:51:13 -0600
From: [EMAIL PROTECTED]
To: 
axis-user@ws.apache.org; axis-user@ws.apache.org 





Hi,

My Axis2 web service is deployed 
for secure access and the URL is of the form 
"https:///axis2/services/Version?wsdl". 
However when the WSDL is returned, port number 80 is specified in the soap 
address instead of port 443 (default port for https).

I have verified 
that the port number in the request object is also 443. Is this a bug in 
Axis2?

Regards,
Jai

-Original Message-
From: 
Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED]
Sent: Fri 9/19/2008 8:52 
AM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address 
uses incorrect port number

Hi Charitha,

I am not including the 
wsdl with the aar file. Including the wsdl
causing other problems. (There 
is a separate email chain on this issue).

I do want the hostname to 
be updated to the machine name or ip address
of the installed machine. 
The issue is port number is being set to a
wrong value. How does Axis2 
determine what the port number should be set
to? Is there some way we

RE: wsdl port address uses incorrect port number for https

[Pugalia, Jai P (JP)]

Hi,
 
The proxyPort does not help us as we are not using Apache as a proxy
server.
 
If I configure the axis2.xml as below: 
 

8080


8443

 
then the soap address for http includes the port 8080 and the soap
address for https includes the port 8443 but the soap address itself is
http and not https.
 
When should the class for transportReceiver be set to for https?
 
If I do not specify the transportReceiver for https in axis2.xml, the
the default value of the port is taken as 80 instead of 443 which is the
default port for https.
 
Thanks,
JP
 


From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 21, 2008 9:09 PM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for https


It should be specified in the http transport listener of the axis2.xml.
You can have a look at
https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis
2.xml for an example usage. This is the axis2.xml used in the WSO2
Mashup Server [1]

Look for the following.






Thanks,
Keith.

[1] http://wso2.org/projects/mashup


On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP)
<[EMAIL PROTECTED]> wrote:


Hi Keith,
 
Where do I specify this parameter? I am guessing axis2.xml. In
axis2.xml, the http transport receiver has a port parameter is set to
8080 and the https transport receiver is commented out in axis2.xml. Am
I heading in the right direction?
 
Thanks,
Jai



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 21, 2008 10:02 AM 

To: axis-user@ws.apache.org

Subject: Re: wsdl port address uses incorrect port number for
https


Hi,

When its going through Apache you can use the following
parameter in the transport listener to set the port address,

80

For the https listener you can set it to 443.

Thanks,
Keith.


On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu
<[EMAIL PROTECTED]> wrote:


JP, We have had similar challenges with our service
where Axis2 (1.2) resolves to port 80 instead of a custom port where we
have our services available on Jboss. One reason for that is our client
goes thru apache web server in the middle and hence the port is always
resolved to 80. Hence we had to hardcode the EPR in the WSDL and set the
following parameters as Charitha outlined. 
 
Did you try accessing the same services thru SOAPUI and
see if it is also doing the same?.
 
regards
Madhav 








    Subject: RE: wsdl port address uses incorrect port
number for https
Date: Sun, 21 Sep 2008 09:51:13 -0600
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org; axis-user@ws.apache.org 



Hi,

My Axis2 web service is deployed for secure access and
the URL is of the form "https:// 
/axis2/services/Version?wsdl". However when the WSDL is
returned, port number 80 is specified in the soap address instead of
port 443 (default port for https).

I have verified that the port number in the request
object is also 443. Is this a bug in Axis2?

Regards,
Jai

-Original Message-
From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED]
Sent: Fri 9/19/2008 8:52 AM
To: axis-user@ws.apache.org
        Subject: RE: wsdl port address uses incorrect port
number

Hi Charitha,

I am not including the wsdl with the aar file. Including
the wsdl
causing other problems. (There is a separate email chain
on this issue).

I do want the hostname to be updated to the machine name
or ip address
of the installed machine. The issue is port number is
being set to a
wrong value. How does Axis2 determine what the port
number should be set
to? Is there some way we can specify what the port
number should be?

Regards,
Jai

-Original Message-
From: charitha kankanamge [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2008 8:24 AM
To: axis-user@ws.apache.org
        Subject: Re: wsdl port address uses incorrect port
number

Hi,
 

Re: wsdl port address uses incorrect port number for https

[keith chapman]

It should be specified in the http transport listener of the axis2.xml.  You
can have a look at
https://svn.wso2.org/repos/wso2/trunk/mashup/java/modules/core/conf/axis2.xmlfor
an example usage. This is the axis2.xml used in the WSO2 Mashup Server
[1]

Look for the following.




Thanks,
Keith.

[1] http://wso2.org/projects/mashup

On Mon, Sep 22, 2008 at 7:31 AM, Pugalia, Jai P (JP) <[EMAIL PROTECTED]>wrote:

>  Hi Keith,
>
> Where do I specify this parameter? I am guessing axis2.xml. In axis2.xml,
> the http transport receiver has a port parameter is set to 8080 and the
> https transport receiver is commented out in axis2.xml. Am I heading in the
> right direction?
>
> Thanks,
> Jai
>
>  --
> *From:* keith chapman [mailto:[EMAIL PROTECTED]
> *Sent:* Sunday, September 21, 2008 10:02 AM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: wsdl port address uses incorrect port number for https
>
>  Hi,
>
> When its going through Apache you can use the following parameter in the
> transport listener to set the port address,
>
> 80
>
> For the https listener you can set it to 443.
>
> Thanks,
> Keith.
>
> On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu <[EMAIL PROTECTED]>wrote:
>
>> JP, We have had similar challenges with our service where Axis2 (1.2)
>> resolves to port 80 instead of a custom port where we have our services
>> available on Jboss. One reason for that is our client goes thru apache web
>> server in the middle and hence the port is always resolved to 80. Hence we
>> had to hardcode the EPR in the WSDL and set the following parameters as
>> Charitha outlined.
>>
>> Did you try accessing the same services thru SOAPUI and see if it is also
>> doing the same?.
>>
>> regards
>> Madhav
>>
>>
>>
>>
>> --
>>
>> Subject: RE: wsdl port address uses incorrect port number for https
>> Date: Sun, 21 Sep 2008 09:51:13 -0600
>> From: [EMAIL PROTECTED]
>> To: axis-user@ws.apache.org; axis-user@ws.apache.org
>>
>>
>>
>> Hi,
>>
>> My Axis2 web service is deployed for secure access and the URL is of the
>> form "https:// /axis2/services/Version?wsdl".
>> However when the WSDL is returned, port number 80 is specified in the soap
>> address instead of port 443 (default port for https).
>>
>> I have verified that the port number in the request object is also 443. Is
>> this a bug in Axis2?
>>
>> Regards,
>> Jai
>>
>> -Original Message-
>> From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>
>> ]
>> Sent: Fri 9/19/2008 8:52 AM
>> To: axis-user@ws.apache.org
>> Subject: RE: wsdl port address uses incorrect port number
>>
>> Hi Charitha,
>>
>> I am not including the wsdl with the aar file. Including the wsdl
>> causing other problems. (There is a separate email chain on this issue).
>>
>> I do want the hostname to be updated to the machine name or ip address
>> of the installed machine. The issue is port number is being set to a
>> wrong value. How does Axis2 determine what the port number should be set
>> to? Is there some way we can specify what the port number should be?
>>
>> Regards,
>> Jai
>>
>> -Original Message-
>> From: charitha kankanamge [mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>]
>> Sent: Friday, September 19, 2008 8:24 AM
>> To: axis-user@ws.apache.org
>> Subject: Re: wsdl port address uses incorrect port number
>>
>> Hi,
>> You may set modifyUserWsdlPortAddress parameter to false in your
>> services.xml.
>>
>> false
>>
>> If you set this parameter to false and useoriginalWsdl set to true, the
>> port address specified in the original wsdl (wsdl included in META-INF
>> directory of your service archive) will be unchanged.
>>
>> regards
>> Charitha
>>
>> http://charithaka.blogspot.com
>> http://www.wso2.org
>>
>> Pugalia, Jai P (JP) wrote:
>>
>> > Hi,
>> >
>> > Looks like the wsdl port numbers being populated in the wsdl port
>> > address by Axis2 is incorrect.
>> >
>> > 
>> > > > binding="ns0:VersionSOAP11Binding">
>> > > > location="https://1.2.3.4:80/axis2/services/Version
>> > <https://1.2.3.4:80/axis2/services/Version>" />
>> > 
>> > > > binding="ns0:VersionSOAP11Binding">
>> > > > location="

RE: wsdl port address uses incorrect port number for https

[Pugalia, Jai P (JP)]

Hi Keith,
 
Where do I specify this parameter? I am guessing axis2.xml. In
axis2.xml, the http transport receiver has a port parameter is set to
8080 and the https transport receiver is commented out in axis2.xml. Am
I heading in the right direction?
 
Thanks,
Jai



From: keith chapman [mailto:[EMAIL PROTECTED] 
Sent: Sunday, September 21, 2008 10:02 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number for https


Hi,

When its going through Apache you can use the following parameter in the
transport listener to set the port address,

80

For the https listener you can set it to 443.

Thanks,
Keith.


On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu <[EMAIL PROTECTED]>
wrote:


JP, We have had similar challenges with our service where Axis2
(1.2) resolves to port 80 instead of a custom port where we have our
services available on Jboss. One reason for that is our client goes thru
apache web server in the middle and hence the port is always resolved to
80. Hence we had to hardcode the EPR in the WSDL and set the following
parameters as Charitha outlined. 
 
Did you try accessing the same services thru SOAPUI and see if
it is also doing the same?.
 
regards
Madhav 








Subject: RE: wsdl port address uses incorrect port number for
https
Date: Sun, 21 Sep 2008 09:51:13 -0600
From: [EMAIL PROTECTED]
To: axis-user@ws.apache.org; axis-user@ws.apache.org 



Hi,

My Axis2 web service is deployed for secure access and the URL
is of the form "https:// 
/axis2/services/Version?wsdl". However when the WSDL is
returned, port number 80 is specified in the soap address instead of
port 443 (default port for https).

I have verified that the port number in the request object is
also 443. Is this a bug in Axis2?

Regards,
Jai

-Original Message-
From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED]
Sent: Fri 9/19/2008 8:52 AM
To: axis-user@ws.apache.org
        Subject: RE: wsdl port address uses incorrect port number

Hi Charitha,

I am not including the wsdl with the aar file. Including the
wsdl
causing other problems. (There is a separate email chain on this
issue).

I do want the hostname to be updated to the machine name or ip
address
of the installed machine. The issue is port number is being set
to a
wrong value. How does Axis2 determine what the port number
should be set
to? Is there some way we can specify what the port number should
be?

Regards,
Jai

-Original Message-
From: charitha kankanamge [mailto:[EMAIL PROTECTED]
Sent: Friday, September 19, 2008 8:24 AM
To: axis-user@ws.apache.org
        Subject: Re: wsdl port address uses incorrect port number

Hi,
You may set modifyUserWsdlPortAddress parameter to false in your
services.xml.

false

If you set this parameter to false and useoriginalWsdl set to
true, the
port address specified in the original wsdl (wsdl included in
META-INF
directory of your service archive) will be unchanged.

regards
Charitha

http://charithaka.blogspot.com <http://charithaka.blogspot.com/>

http://www.wso2.org <http://www.wso2.org/> 

Pugalia, Jai P (JP) wrote:

> Hi,
> 
> Looks like the wsdl port numbers being populated in the wsdl
port
> address by Axis2 is incorrect.
> 
> 
>  binding="ns0:VersionSOAP11Binding">
>  location="https://1.2.3.4:80/axis2/services/Version
> <https://1.2.3.4:80/axis2/services/Version>" />
> 
>  binding="ns0:VersionSOAP11Binding">
>  location="http://1.2.3.4:8080/axis2/services/Version
> <http://1.2.3.4:8080/axis2/services/Version>" />
> 
> 
> 
> In our situation, the port number for https should be 443 and
port for

> http should be 80. Is there any configuration which needs to
be
> modified such that the right port number is included in the
wsdl when
> it is retrieved using ?wsdl option.
> 
> Thanks,
> Jai
> 
> 
>

>---
>-

Re: wsdl port address uses incorrect port number for https

[keith chapman]

Hi,

When its going through Apache you can use the following parameter in the
transport listener to set the port address,

80

For the https listener you can set it to 443.

Thanks,
Keith.

On Sun, Sep 21, 2008 at 10:21 PM, Enaganti M Naidu <[EMAIL PROTECTED]>wrote:

> JP, We have had similar challenges with our service where Axis2 (1.2)
> resolves to port 80 instead of a custom port where we have our services
> available on Jboss. One reason for that is our client goes thru apache web
> server in the middle and hence the port is always resolved to 80. Hence we
> had to hardcode the EPR in the WSDL and set the following parameters as
> Charitha outlined.
>
> Did you try accessing the same services thru SOAPUI and see if it is also
> doing the same?.
>
> regards
> Madhav
>
>
>
>
> --
>
> Subject: RE: wsdl port address uses incorrect port number for https
> Date: Sun, 21 Sep 2008 09:51:13 -0600
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org; axis-user@ws.apache.org
>
>
>
> Hi,
>
> My Axis2 web service is deployed for secure access and the URL is of the
> form "https:// /axis2/services/Version?wsdl". However
> when the WSDL is returned, port number 80 is specified in the soap address
> instead of port 443 (default port for https).
>
> I have verified that the port number in the request object is also 443. Is
> this a bug in Axis2?
>
> Regards,
> Jai
>
> -Original Message-
> From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>]
> Sent: Fri 9/19/2008 8:52 AM
> To: axis-user@ws.apache.org
> Subject: RE: wsdl port address uses incorrect port number
>
> Hi Charitha,
>
> I am not including the wsdl with the aar file. Including the wsdl
> causing other problems. (There is a separate email chain on this issue).
>
> I do want the hostname to be updated to the machine name or ip address
> of the installed machine. The issue is port number is being set to a
> wrong value. How does Axis2 determine what the port number should be set
> to? Is there some way we can specify what the port number should be?
>
> Regards,
> Jai
>
> -Original Message-
> From: charitha kankanamge [mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>]
> Sent: Friday, September 19, 2008 8:24 AM
> To: axis-user@ws.apache.org
> Subject: Re: wsdl port address uses incorrect port number
>
> Hi,
> You may set modifyUserWsdlPortAddress parameter to false in your
> services.xml.
>
> false
>
> If you set this parameter to false and useoriginalWsdl set to true, the
> port address specified in the original wsdl (wsdl included in META-INF
> directory of your service archive) will be unchanged.
>
> regards
> Charitha
>
> http://charithaka.blogspot.com
> http://www.wso2.org
>
> Pugalia, Jai P (JP) wrote:
>
> > Hi,
> >
> > Looks like the wsdl port numbers being populated in the wsdl port
> > address by Axis2 is incorrect.
> >
> > 
> >  > binding="ns0:VersionSOAP11Binding">
> >  > location="https://1.2.3.4:80/axis2/services/Version
> > <https://1.2.3.4:80/axis2/services/Version>" />
> > 
> >  > binding="ns0:VersionSOAP11Binding">
> >  > location="http://1.2.3.4:8080/axis2/services/Version
> > <http://1.2.3.4:8080/axis2/services/Version>" />
> > 
> > 
> >
> > In our situation, the port number for https should be 443 and port for
>
> > http should be 80. Is there any configuration which needs to be
> > modified such that the right port number is included in the wsdl when
> > it is retrieved using ?wsdl option.
> >
> > Thanks,
> > Jai
> >
> >
> >
> >---
> >-
> >
> >No virus found in this incoming message.
> >Checked by AVG.
> >Version: 7.5.524 / Virus Database: 270.7.0/1679 - Release Date:
> >9/18/2008 5:03 PM
> >
> >
>
>
> -
> 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]
>
>
>
>
> --
> Stay up to date on your PC, the Web, and your mobile phone with Windows
> Live. See Now<http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/>
>



-- 
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

RE: wsdl port address uses incorrect port number for https

[Enaganti M Naidu]

JP, We have had similar challenges with our service where Axis2 (1.2) resolves 
to port 80 instead of a custom port where we have our services available on 
Jboss. One reason for that is our client goes thru apache web server in the 
middle and hence the port is always resolved to 80. Hence we had to hardcode 
the EPR in the WSDL and set the following parameters as Charitha outlined. 
 
Did you try accessing the same services thru SOAPUI and see if it is also doing 
the same?.
 
regards
Madhav 



Subject: RE: wsdl port address uses incorrect port number for httpsDate: Sun, 
21 Sep 2008 09:51:13 -0600From: [EMAIL PROTECTED]: axis-user@ws.apache.org; 
axis-user@ws.apache.org

Hi,My Axis2 web service is deployed for secure access and the URL is of the 
form "https:///axis2/services/Version?wsdl". However when the WSDL is 
returned, port number 80 is specified in the soap address instead of port 443 
(default port for https).I have verified that the port number in the request 
object is also 443. Is this a bug in Axis2?Regards,Jai-Original 
Message-From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED]: Fri 9/19/2008 
8:52 AMTo: [EMAIL PROTECTED]: RE: wsdl port address uses incorrect port 
numberHi Charitha,I am not including the wsdl with the aar file. Including the 
wsdlcausing other problems. (There is a separate email chain on this issue).I 
do want the hostname to be updated to the machine name or ip addressof the 
installed machine. The issue is port number is being set to awrong value. How 
does Axis2 determine what the port number should be setto? Is there some way we 
can specify what the port number should be?Regards,Jai-Original 
Message-From: charitha kankanamge [mailto:[EMAIL PROTECTED]: Friday, 
September 19, 2008 8:24 AMTo: [EMAIL PROTECTED]: Re: wsdl port address uses 
incorrect port numberHi,You may set modifyUserWsdlPortAddress parameter to 
false in yourservices.xml.falseIf you set this parameter 
to false and useoriginalWsdl set to true, theport address specified in the 
original wsdl (wsdl included in META-INFdirectory of your service archive) will 
be 
unchanged.regardsCharithahttp://charithaka.blogspot.comhttp://www.wso2.orgPugalia,
 Jai P (JP) wrote:> Hi,> > Looks like the wsdl port numbers being populated in 
the wsdl port> address by Axis2 is incorrect.> > > 
 
binding="ns0:VersionSOAP11Binding">>  
location="https://1.2.3.4:80/axis2/services/Version> 
<https://1.2.3.4:80/axis2/services/Version>" />> > 
 binding="ns0:VersionSOAP11Binding">> 
 location="http://1.2.3.4:8080/axis2/services/Version> 
<http://1.2.3.4:8080/axis2/services/Version>" />> > 
> > In our situation, the port number for https should be 443 
and port for> http should be 80. Is there any configuration which needs to be> 
modified such that the right port number is included in the wsdl when> it is 
retrieved using ?wsdl option.> > Thanks,> Jai> > 
>>--->->>No 
virus found in this incoming message.>Checked by AVG.>Version: 7.5.524 / Virus 
Database: 270.7.0/1679 - Release Date:>9/18/2008 5:03 PM> 
>-To 
unsubscribe, e-mail: [EMAIL PROTECTED] additional commands, e-mail: [EMAIL 
PROTECTED] unsubscribe, e-mail: [EMAIL PROTECTED] additional commands, e-mail: 
[EMAIL PROTECTED]
_
Stay up to date on your PC, the Web, and your mobile phone with Windows Live.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/

RE: wsdl port address uses incorrect port number for https

[Pugalia, Jai P (JP)]

Hi,

My Axis2 web service is deployed for secure access and the URL is of the form 
"https:///axis2/services/Version?wsdl". However when the WSDL is 
returned, port number 80 is specified in the soap address instead of port 443 
(default port for https). 

I have verified that the port number in the request object is also 443. Is this 
a bug in Axis2?

Regards,
Jai

-Original Message-
From: Pugalia, Jai P (JP) [mailto:[EMAIL PROTECTED]
Sent: Fri 9/19/2008 8:52 AM
To: axis-user@ws.apache.org
Subject: RE: wsdl port address uses incorrect port number
 
Hi Charitha,

I am not including the wsdl with the aar file. Including the wsdl
causing other problems. (There is a separate email chain on this issue).

I do want the hostname to be updated to the machine name or ip address
of the installed machine. The issue is port number is being set to a
wrong value. How does Axis2 determine what the port number should be set
to? Is there some way we can specify what the port number should be?

Regards,
Jai

-Original Message-
From: charitha kankanamge [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 19, 2008 8:24 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number

Hi,
You may set modifyUserWsdlPortAddress parameter to false in your
services.xml.

false

If you set this parameter to false and useoriginalWsdl set to true, the
port address specified in the original wsdl (wsdl included in META-INF
directory of your service archive) will be unchanged.

regards
Charitha

http://charithaka.blogspot.com
http://www.wso2.org

Pugalia, Jai P (JP) wrote:

> Hi,
>  
> Looks like the wsdl port numbers being populated in the wsdl port 
> address by Axis2 is incorrect.
>  
> 
>  binding="ns0:VersionSOAP11Binding">
>  location="https://1.2.3.4:80/axis2/services/Version
> <https://1.2.3.4:80/axis2/services/Version>" /> 
> 
>  binding="ns0:VersionSOAP11Binding">
>  location="http://1.2.3.4:8080/axis2/services/Version
> <http://1.2.3.4:8080/axis2/services/Version>" /> 
> 
> 
>  
> In our situation, the port number for https should be 443 and port for

> http should be 80. Is there any configuration which needs to be 
> modified such that the right port number is included in the wsdl when 
> it is retrieved using ?wsdl option.
>  
> Thanks,
> Jai
>  
>  
>
>---
>-
>
>No virus found in this incoming message.
>Checked by AVG. 
>Version: 7.5.524 / Virus Database: 270.7.0/1679 - Release Date: 
>9/18/2008 5:03 PM
>  
>


-
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: wsdl port address uses incorrect port number

[Pugalia, Jai P (JP)]

Hi Charitha,

I am not including the wsdl with the aar file. Including the wsdl
causing other problems. (There is a separate email chain on this issue).

I do want the hostname to be updated to the machine name or ip address
of the installed machine. The issue is port number is being set to a
wrong value. How does Axis2 determine what the port number should be set
to? Is there some way we can specify what the port number should be?

Regards,
Jai

-Original Message-
From: charitha kankanamge [mailto:[EMAIL PROTECTED] 
Sent: Friday, September 19, 2008 8:24 AM
To: axis-user@ws.apache.org
Subject: Re: wsdl port address uses incorrect port number

Hi,
You may set modifyUserWsdlPortAddress parameter to false in your
services.xml.

false

If you set this parameter to false and useoriginalWsdl set to true, the
port address specified in the original wsdl (wsdl included in META-INF
directory of your service archive) will be unchanged.

regards
Charitha

http://charithaka.blogspot.com
http://www.wso2.org

Pugalia, Jai P (JP) wrote:

> Hi,
>  
> Looks like the wsdl port numbers being populated in the wsdl port 
> address by Axis2 is incorrect.
>  
> 
>  binding="ns0:VersionSOAP11Binding">
>  location="https://1.2.3.4:80/axis2/services/Version
> <https://1.2.3.4:80/axis2/services/Version>" /> 
> 
>  binding="ns0:VersionSOAP11Binding">
>  location="http://1.2.3.4:8080/axis2/services/Version
> <http://1.2.3.4:8080/axis2/services/Version>" /> 
> 
> 
>  
> In our situation, the port number for https should be 443 and port for

> http should be 80. Is there any configuration which needs to be 
> modified such that the right port number is included in the wsdl when 
> it is retrieved using ?wsdl option.
>  
> Thanks,
> Jai
>  
>  
>
>---
>-
>
>No virus found in this incoming message.
>Checked by AVG. 
>Version: 7.5.524 / Virus Database: 270.7.0/1679 - Release Date: 
>9/18/2008 5:03 PM
>  
>


-
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: wsdl port address uses incorrect port number

[charitha kankanamge]

Hi,
You may set modifyUserWsdlPortAddress parameter to false in your 
services.xml.


false

If you set this parameter to false and useoriginalWsdl set to true, the 
port address specified in the original wsdl (wsdl included in META-INF 
directory of your service archive) will be unchanged.


regards
Charitha

http://charithaka.blogspot.com
http://www.wso2.org

Pugalia, Jai P (JP) wrote:


Hi,
 
Looks like the wsdl port numbers being populated in the wsdl port 
address by Axis2 is incorrect. 
 

binding="ns0:VersionSOAP11Binding">
location="https://1.2.3.4:80/axis2/services/Version 
" /> 

binding="ns0:VersionSOAP11Binding">
location="http://1.2.3.4:8080/axis2/services/Version 
" /> 



 
In our situation, the port number for https should be 443 and port for 
http should be 80. Is there any configuration which needs to be 
modified such that the right port number is included in the wsdl when 
it is retrieved using ?wsdl option.
 
Thanks,

Jai
 
 




No virus found in this incoming message.
Checked by AVG. 
Version: 7.5.524 / Virus Database: 270.7.0/1679 - Release Date: 9/18/2008 5:03 PM
 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: wsdl "exploder"

[Jon Seymour]

Lawrence,

Thanks for that. I tried a simplistic:

WSDLFactory factory = WSDLFactory.newInstance();
WSDLReader reader = factory.newWSDLReader();
Definition def = reader.readWSDL("http://myserver/mywsdl.wsdl";);
WSDLWriter writer = factory.newWSDLWriter();
writer.writeWSDL(def, System.out);

but the definition isn't exploded. On serialization, the output file only
contained the top-level file. Not the "explosion" which included all
referenced files. Presumably I could iterate over the imports and types to
create a merged definition that would do what I want, but I haven't tried to
do that yet.

Regards,

jon seymour.

On Sat, Sep 13, 2008 at 4:37 AM, Lawrence Mandel <[EMAIL PROTECTED]> wrote:

> I think WSDL4J [1] will do what you want. Simply read in the WSDL and then
> serialize it out. AFAIK, WSDL will serialize to a single file.
>
> John Kaputin should know for sure whether WSDL4J will suit your purpose.
>
> [1] http://sourceforge.net/projects/wsdl4j
>
> Lawrence
>
>
>
>
>
> From:
> "Jon Seymour" <[EMAIL PROTECTED]>
> To:
> axis-user@ws.apache.org
> Date:
> 09/12/2008 07:47 AM
> Subject:
> wsdl "exploder"
>
>
>
> Has anyone ever come across a WSDL-exploder that converts a logical WSDL
> entity that spans multiple files (via the WSDL and XML schema import
> mechanisms) into a single entity that contains all the referenced entities
> inline?
>
> I need such a beast to help support a client whose ability to properly
> keep track of schema locations in a multi-file entity is somewhat suspect.
>
>
> jon seymour.
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: wsdl "exploder"

[Lawrence Mandel]

I think WSDL4J [1] will do what you want. Simply read in the WSDL and then 
serialize it out. AFAIK, WSDL will serialize to a single file.

John Kaputin should know for sure whether WSDL4J will suit your purpose.

[1] http://sourceforge.net/projects/wsdl4j

Lawrence





From:
"Jon Seymour" <[EMAIL PROTECTED]>
To:
axis-user@ws.apache.org
Date:
09/12/2008 07:47 AM
Subject:
wsdl "exploder"



Has anyone ever come across a WSDL-exploder that converts a logical WSDL 
entity that spans multiple files (via the WSDL and XML schema import 
mechanisms) into a single entity that contains all the referenced entities 
inline?

I need such a beast to help support a client whose ability to properly 
keep track of schema locations in a multi-file entity is somewhat suspect. 


jon seymour.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL for attachments and WSDL2Java

[Ian Ashley]

For some reason Keith¹s and my replies to my original article jumped thread.
So here they are to see if anyone can help.

Hi Keith,

Thanks for the suggestion. Changing the WSDL as described (shown below)
causes the error

java.lang.RuntimeException: Cannot find part [asset] for operation
[GetAsset] using MIMEContent type [application/octet-stream]

to be returned from the Axis1 WSDL2Java tool. Is there a way to change the
multi-part MIME definitions to refer to an element rather than a part or is
a different solution required?



http://schemas.xmlsoap.org/wsdl/";
  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
  xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/";
  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
  xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/";
  xmlns:http="http://schemas.xmlsoap.org/wsdl/http/";
  xmlns:s="http://www.w3.org/2001/XMLSchema";
  xmlns:tns="~/WebServices/"
  targetNamespace="~/WebServices/">



















































































http://schemas.xmlsoap.org/soap/http"/>



































http://localhost:8080/axis/services/VersionCueService"/>





Thanks,
Ian



From: keith chapman <[EMAIL PROTECTED]>
Reply-To: <[EMAIL PROTECTED]>
Date: Tue, 2 Sep 2008 18:15:56 +0530
To: <[EMAIL PROTECTED]>
Subject: Re: WSDL for attachments and WSDL2Java

Hi,

I guess the problem is caused by the following messages in your WSDL,

   








Modifying it to something like

   

   


   

and making asset a element of GetAssetResponse and StoreAsset should fix the
issue (At least from the point of Axis2. I'm not sure weather this would
break Axis1, but I doubt it will).

Thanks,
Keith.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__

__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: wsdl string pattern

[Jeff Greif]

You should consult the various Internet RFCs for allowed MIME typenames 
to get the allowed syntax, but your pattern will need to include hyphens 
at least, for such MIME types as application/octet-stream or 
message/external-body or x-application/my-experimental-app.


Jeff

Shehan Simen wrote:


Hi,

I want to have a pattern for a string in wsdl.

The pattern is like: string/string

e.g. : image/jpeg

Is the following pattern correct?



I want to introduce this pattern for MIME types.

 


Is it correct? Please help me.

 

 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: wsdl

[Jyotsna Varma]

Thanks Paul. Now I think I am able to build stub classes. 
Thank you very much for your help.

--- On Wed, 4/6/08, Paul Fremantle <[EMAIL PROTECTED]> wrote:

From: Paul Fremantle <[EMAIL PROTECTED]>
Subject: Re: wsdl
To: axis-user@ws.apache.org, [EMAIL PROTECTED]
Date: Wednesday, 4 June, 2008, 5:01 PM

Sorry, I was assuming you had Axis2 (the latest version).

I'm not up to speed on Axis1 so I can't help out with that. Basically
if you get Axis2-bin zipfile, unzip it, and it should become clear. If
you are calling a webservice from your webapp you just need to include
the axis2 libs in the webapp\lib directory.

Paul

On Wed, Jun 4, 2008 at 12:26 PM, Jyotsna Varma <[EMAIL PROTECTED]>
wrote:
>
> Thanks Paul for the quick reply.
>
> I have got axis-bin-1_4. In which directory I should run this ?  I have
done
> an advnced installation
>
http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp
>
>
>
> Thank you very much,
>
>
>
> --- On Wed, 4/6/08, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
> From: Paul Fremantle <[EMAIL PROTECTED]>
> Subject: Re: wsdl
> To: axis-user@ws.apache.org, [EMAIL PROTECTED]
> Date: Wednesday, 4 June, 2008, 4:23 PM
>
> You need to run
>
> bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o
> directory\where\you\want\the\code\generated
>
> This will create a "stub" which is a class you can embed in your
> application. You simply need to create a new instance of this class
> and then call methods on it, those methods will call the remote
> service.
>
> Paul
>
> On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma
<[EMAIL PROTECTED]>
> wrote:
>> Hi,
>>
>>
>>
>> I am new to the web services and so as to axis. Please help me.
>>
>> I have to show something this week. I have been working to sort this
out
>> since last 4 days.
>>
>> I am sorry to say this.
>>
>>
>>
>> I have an existing web application. To use axis in existing
application,
>>
>> I have done :
>>
>> 1.copy all jars from axis.lib directory
>>
>> 2.copy axis's web.xml servlet params and mapping to to my web.xml
>>
>>
>>
>> I have got a wsdl url from an external application (to be integrated
with
> my
>> application)
>>
>> Now what should I do to use this wsdl to access the external
application ?
>>
>> Please kind enough to me.
>>
>>
>>
>> Many Thanks,
>>
>>
>>
>>
>>
>> 
>> Sent from Yahoo! Mail.
>> A Smarter Email.
>
>
>
> --
> Paul Fremantle
> Co-Founder and CTO, WSO2
> Apache Synapse PMC Chair
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> 
> Sent from Yahoo! Mail.
> A Smarter Email.



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  __
Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html

RE: wsdl

[Jyotsna Varma]

Thank you. I run wsdl2java in Axis2 1.3 version. But I am getting error :-
 
Caused by: javax.wsdl.WSDLException: WSDLException (at /html): 
faultCode=INVALID_WSDL: Expected element '{http://schemas
.xmlsoap.org/wsdl/}definitions'.
    at 
com.ibm.wsdl.xml.WSDLReaderImpl.checkElementName(Unknown Source)
    at 
com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
    at 
com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at 
com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at 
com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(CodeGenerationEngine.java:286)
    at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerationEngine.java:105)
    ... 2 more

I don't understand whats the cause of this error ? Is something missing in wsdl 
document?

--- On Wed, 4/6/08, Martin Gainty <[EMAIL PROTECTED]> wrote:

From: Martin Gainty <[EMAIL PROTECTED]>
Subject: RE: wsdl
To: [EMAIL PROTECTED], axis-user@ws.apache.org
Date: Wednesday, 4 June, 2008, 5:20 PM




#yiv112315369 .hmmessage P
{
margin:0px;padding:0px;}
#yiv112315369  .hmmessage
{
FONT-SIZE:10pt;FONT-FAMILY:Tahoma;}

There are many reasons to adopt Axis2
Ability to use Axis Object Model to represent all of your entities (Axiom)
Ability to incorporate more databinding types ADB, XMLBEANS, JIBX, JAXBRI
Ability to engage or disengage AOP modules security, addressing, logging
Ability to upload services without disrupting other services

Martin Gainty 

__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 





Date: Wed, 4 Jun 2008 11:37:09 +
From: [EMAIL PROTECTED]
Subject: Re: wsdl
To: axis-user@ws.apache.org





Thanks Paul. I am downloading it. But I am not sure whether the external system 
accepts axis2. I will try. External system's documentation tells that it works 
with Axis 1.3. But it is an old documant. They must have updated it. Let me 
come back.


--- On Wed, 4/6/08, Paul Fremantle <[EMAIL PROTECTED]> wrote:


From: Paul Fremantle <[EMAIL PROTECTED]>
Subject: Re: wsdl
To: axis-user@ws.apache.org, [EMAIL PROTECTED]
Date: Wednesday, 4 June, 2008, 5:01 PM

Sorry, I was assuming you had Axis2 (the latest version).

I'm not up to speed on Axis1 so I can't help out with that. Basically
if you get Axis2-bin zipfile, unzip it, and it should become clear. If
you are calling a webservice from your webapp you just need to include
the axis2 libs in the webapp\lib directory.

Paul

On Wed, Jun 4, 2008 at 12:26 PM, Jyotsna Varma <[EMAIL PROTECTED]>
wrote:
>
> Thanks Paul for the quick reply.
>
> I have got axis-bin-1_4. In which directory I should run this ?  I have
done
> an advnced installation
>
http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp
>
>
>
> Thank you very much,
>
>
>
> --- On Wed, 4/6/08, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
> From: Paul Fremantle <[EMAIL PROTECTED]>
> Subject: Re: wsdl
> To: axis-user@ws.apache.org, [EMAIL PROTECTED]
> Date: Wednesday, 4 June, 2008, 4:23 PM
>
> You need to run
>
> bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o
> directory\where\you\want\the\code\generated
>
> This will create a "stub" which is a class you can embed in your
> application. You simply need to create a new instance of this class
> and then call methods on it, those methods will call the remote
> service.
>
> Paul
>
> On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma
<[EMAIL PROTECTED]>
> wrote:
>> Hi,
>>
>>
>>
>> I am new to the web services and so as to axis. Please help me.
>>
>> I have to show something this week. I have been working to sort this
out
>> since last 4 days.
>>
>> I am sorry to say this.
>>
>>
>>
>> I have an existing web application. To use axis in existing
application,
>>
>> I have done :
>>
>> 1.copy all jars from axis.lib directory
>>
>> 2.copy axis's web.xml servlet params and mapping to to my web.xml
>>
>>
>>
>> I have got a wsdl url from an external application (to be integrated
with
> my
>> application)
>>
>> Now what should I do to use this wsdl to access the external
application ?
>>
>> Please kind enough to me.
>>
>>
>>
>> Many Thanks,
>>
>>
>>
>>
&g

RE: wsdl

[Martin Gainty]

There are many reasons to adopt Axis2
Ability to use Axis Object Model to represent all of your entities (Axiom)
Ability to incorporate more databinding types ADB, XMLBEANS, JIBX, JAXBRI
Ability to engage or disengage AOP modules security, addressing, logging
Ability to upload services without disrupting other services

Martin Gainty 

__ 
Disclaimer and confidentiality note 
Everything in this e-mail and any attachments relates to the official business 
of Sender. This transmission is of a confidential nature and Sender does not 
endorse distribution to any party other than intended recipient. Sender does 
not necessarily endorse content contained within this transmission. 


Date: Wed, 4 Jun 2008 11:37:09 +
From: [EMAIL PROTECTED]
Subject: Re: wsdl
To: axis-user@ws.apache.org

Thanks Paul. I am downloading it. But I am not sure whether the external system 
accepts axis2. I will try. External system's documentation tells that it works 
with Axis 1.3. But it is an old documant. They must have updated it. Let me 
come back.


--- On Wed, 4/6/08, Paul Fremantle <[EMAIL PROTECTED]> wrote:

From: Paul Fremantle <[EMAIL PROTECTED]>
Subject: Re: wsdl
To: axis-user@ws.apache.org, [EMAIL PROTECTED]
Date: Wednesday, 4 June, 2008, 5:01 PM

Sorry, I was assuming you had Axis2 (the latest version).

I'm not up to speed on Axis1 so I can't help out with that. Basically
if you get Axis2-bin zipfile, unzip it, and it should become clear. If
you are calling a webservice from your webapp you just need to include
the axis2 libs in the webapp\lib directory.

Paul

On Wed, Jun 4, 2008 at 12:26 PM, Jyotsna Varma <[EMAIL PROTECTED]>
wrote:
>
> Thanks Paul for the quick reply.
>
> I have got axis-bin-1_4. In which directory I should run this ?  I have
done
> an advnced installation
>
http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp
>
>
>
> Thank you very much,
>
>
>
> --- On Wed, 4/6/08, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
> From: Paul Fremantle <[EMAIL PROTECTED]>
> Subject: Re: wsdl
> To: axis-user@ws.apache.org, [EMAIL PROTECTED]
> Date: Wednesday, 4 June, 2008, 4:23 PM
>
> You need to run
>
> bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o
> directory\where\you\want\the\code\generated
>
> This will create a "stub" which is a class you can embed in your
> application. You simply need to create a new instance of this class
> and then call methods on it, those methods will call the remote
> service.
>
> Paul
>
> On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma
<[EMAIL PROTECTED]>
> wrote:
>> Hi,
>>
>>
>>
>> I am new to the web services and so as to axis. Please help me.
>>
>> I have to show something this week. I have been working to sort this
out
>> since last 4 days.
>>
>> I am sorry to say this.
>>
>>
>>
>> I have an existing web application. To use axis in existing
application,
>>
>> I have done :
>>
>> 1.copy all jars from axis.lib directory
>>
>> 2.copy axis's web.xml servlet params and mapping to to my web.xml
>>
>>
>>
>> I have got a wsdl url from an external application (to be integrated
with
> my
>> application)
>>
>> Now what should I do to use this wsdl to access the external
application ?
>>
>> Please kind enough to me.
>>
>>
>>
>> Many Thanks,
>>
>>
>>
>>
>>
>> 
>> Sent from Yahoo! Mail.
>> A Smarter Email.
>
>
>
> --
> Paul Fremantle
> Co-Founder and CTO, WSO2
> Apache Synapse PMC Chair
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> 
> Sent from Yahoo! Mail.
> A Smarter Email.



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




  
Sent from Yahoo! Mail.


A Smarter Email.
_
Now you can invite friends from Facebook and other groups to join you on 
Windows Live™ Messenger. Add now.
https://www.invite2messenger.net/im/?source=TXT_EML_WLH_AddNow_Now

Re: wsdl

[Jyotsna Varma]

Thanks Paul. I am downloading it. But I am not sure whether the external system 
accepts axis2. I will try. External system's documentation tells that it works 
with Axis 1.3. But it is an old documant. They must have updated it. Let me 
come back.


--- On Wed, 4/6/08, Paul Fremantle <[EMAIL PROTECTED]> wrote:

From: Paul Fremantle <[EMAIL PROTECTED]>
Subject: Re: wsdl
To: axis-user@ws.apache.org, [EMAIL PROTECTED]
Date: Wednesday, 4 June, 2008, 5:01 PM

Sorry, I was assuming you had Axis2 (the latest version).

I'm not up to speed on Axis1 so I can't help out with that. Basically
if you get Axis2-bin zipfile, unzip it, and it should become clear. If
you are calling a webservice from your webapp you just need to include
the axis2 libs in the webapp\lib directory.

Paul

On Wed, Jun 4, 2008 at 12:26 PM, Jyotsna Varma <[EMAIL PROTECTED]>
wrote:
>
> Thanks Paul for the quick reply.
>
> I have got axis-bin-1_4. In which directory I should run this ?  I have
done
> an advnced installation
>
http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp
>
>
>
> Thank you very much,
>
>
>
> --- On Wed, 4/6/08, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
> From: Paul Fremantle <[EMAIL PROTECTED]>
> Subject: Re: wsdl
> To: axis-user@ws.apache.org, [EMAIL PROTECTED]
> Date: Wednesday, 4 June, 2008, 4:23 PM
>
> You need to run
>
> bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o
> directory\where\you\want\the\code\generated
>
> This will create a "stub" which is a class you can embed in your
> application. You simply need to create a new instance of this class
> and then call methods on it, those methods will call the remote
> service.
>
> Paul
>
> On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma
<[EMAIL PROTECTED]>
> wrote:
>> Hi,
>>
>>
>>
>> I am new to the web services and so as to axis. Please help me.
>>
>> I have to show something this week. I have been working to sort this
out
>> since last 4 days.
>>
>> I am sorry to say this.
>>
>>
>>
>> I have an existing web application. To use axis in existing
application,
>>
>> I have done :
>>
>> 1.copy all jars from axis.lib directory
>>
>> 2.copy axis's web.xml servlet params and mapping to to my web.xml
>>
>>
>>
>> I have got a wsdl url from an external application (to be integrated
with
> my
>> application)
>>
>> Now what should I do to use this wsdl to access the external
application ?
>>
>> Please kind enough to me.
>>
>>
>>
>> Many Thanks,
>>
>>
>>
>>
>>
>> 
>> Sent from Yahoo! Mail.
>> A Smarter Email.
>
>
>
> --
> Paul Fremantle
> Co-Founder and CTO, WSO2
> Apache Synapse PMC Chair
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> 
> Sent from Yahoo! Mail.
> A Smarter Email.



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  __
Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html

Re: wsdl

[Paul Fremantle]

Sorry, I was assuming you had Axis2 (the latest version).

I'm not up to speed on Axis1 so I can't help out with that. Basically
if you get Axis2-bin zipfile, unzip it, and it should become clear. If
you are calling a webservice from your webapp you just need to include
the axis2 libs in the webapp\lib directory.

Paul

On Wed, Jun 4, 2008 at 12:26 PM, Jyotsna Varma <[EMAIL PROTECTED]> wrote:
>
> Thanks Paul for the quick reply.
>
> I have got axis-bin-1_4. In which directory I should run this ?  I have done
> an advnced installation
> http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp
>
>
>
> Thank you very much,
>
>
>
> --- On Wed, 4/6/08, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
> From: Paul Fremantle <[EMAIL PROTECTED]>
> Subject: Re: wsdl
> To: axis-user@ws.apache.org, [EMAIL PROTECTED]
> Date: Wednesday, 4 June, 2008, 4:23 PM
>
> You need to run
>
> bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o
> directory\where\you\want\the\code\generated
>
> This will create a "stub" which is a class you can embed in your
> application. You simply need to create a new instance of this class
> and then call methods on it, those methods will call the remote
> service.
>
> Paul
>
> On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma <[EMAIL PROTECTED]>
> wrote:
>> Hi,
>>
>>
>>
>> I am new to the web services and so as to axis. Please help me.
>>
>> I have to show something this week. I have been working to sort this out
>> since last 4 days.
>>
>> I am sorry to say this.
>>
>>
>>
>> I have an existing web application. To use axis in existing application,
>>
>> I have done :
>>
>> 1.copy all jars from axis.lib directory
>>
>> 2.copy axis's web.xml servlet params and mapping to to my web.xml
>>
>>
>>
>> I have got a wsdl url from an external application (to be integrated with
> my
>> application)
>>
>> Now what should I do to use this wsdl to access the external application ?
>>
>> Please kind enough to me.
>>
>>
>>
>> Many Thanks,
>>
>>
>>
>>
>>
>> 
>> Sent from Yahoo! Mail.
>> A Smarter Email.
>
>
>
> --
> Paul Fremantle
> Co-Founder and CTO, WSO2
> Apache Synapse PMC Chair
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> 
> Sent from Yahoo! Mail.
> A Smarter Email.



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: wsdl

[Jyotsna Varma]

I am using netbeans with ant to build the web application. 

--- On Wed, 4/6/08, Jyotsna Varma <[EMAIL PROTECTED]> wrote:

From: Jyotsna Varma <[EMAIL PROTECTED]>
Subject: Re: wsdl
To: axis-user@ws.apache.org
Date: Wednesday, 4 June, 2008, 4:56 PM








Thanks Paul for the quick reply.
I have got axis-bin-1_4. In which directory I should run this ?  I have 
done an advnced installation 
http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp
 
Thank you very much,
 

--- On Wed, 4/6/08, Paul Fremantle <[EMAIL PROTECTED]> wrote:

From: Paul Fremantle <[EMAIL PROTECTED]>
Subject: Re: wsdl
To: axis-user@ws.apache.org, [EMAIL PROTECTED]
Date: Wednesday, 4 June, 2008, 4:23 PM

You need to run

bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o
directory\where\you\want\the\code\generated

This will create a "stub" which is a class you can embed in your
application. You simply need to create a new instance of this class
and then call methods on it, those methods will call the remote
service.

Paul

On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma <[EMAIL PROTECTED]>
wrote:
> Hi,
>
>
>
> I am new to the web services and so as to axis. Please help me.
>
> I have to show something this week. I have been working to sort this out
> since last 4 days.
>
> I am sorry to say this.
>
>
>
> I have an existing web application. To use axis in existing application,
>
> I have done :
>
> 1.copy all jars from axis.lib directory
>
> 2.copy axis's web.xml servlet params and mapping to to my web.xml
>
>
>
> I have got a wsdl url from an external application (to be integrated with
my
> application)
>
> Now what should I do to use this wsdl to access the external application ?
>
> Please kind enough to me.
>
>
>
> Many Thanks,
>
>
>
>
>
> 
> Sent from Yahoo! Mail.
> A Smarter Email.



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Sent from Yahoo! Mail. 
A Smarter Email.


  __
Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html

Re: wsdl

[Jyotsna Varma]

Thanks Paul for the quick reply.
I have got axis-bin-1_4. In which directory I should run this ?  I have 
done an advnced installation 
http://ws.apache.org/axis/java/install.html#AdvancedInstallationAddingAxisToYourOwnWebapp
 
Thank you very much,
 

--- On Wed, 4/6/08, Paul Fremantle <[EMAIL PROTECTED]> wrote:

From: Paul Fremantle <[EMAIL PROTECTED]>
Subject: Re: wsdl
To: axis-user@ws.apache.org, [EMAIL PROTECTED]
Date: Wednesday, 4 June, 2008, 4:23 PM

You need to run

bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o
directory\where\you\want\the\code\generated

This will create a "stub" which is a class you can embed in your
application. You simply need to create a new instance of this class
and then call methods on it, those methods will call the remote
service.

Paul

On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma <[EMAIL PROTECTED]>
wrote:
> Hi,
>
>
>
> I am new to the web services and so as to axis. Please help me.
>
> I have to show something this week. I have been working to sort this out
> since last 4 days.
>
> I am sorry to say this.
>
>
>
> I have an existing web application. To use axis in existing application,
>
> I have done :
>
> 1.copy all jars from axis.lib directory
>
> 2.copy axis's web.xml servlet params and mapping to to my web.xml
>
>
>
> I have got a wsdl url from an external application (to be integrated with
my
> application)
>
> Now what should I do to use this wsdl to access the external application ?
>
> Please kind enough to me.
>
>
>
> Many Thanks,
>
>
>
>
>
> 
> Sent from Yahoo! Mail.
> A Smarter Email.



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  __
Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html

Re: wsdl

[Paul Fremantle]

You need to run

bin\wsdl2java -uw -uri http:///url/of/the/.wsdl -o
directory\where\you\want\the\code\generated

This will create a "stub" which is a class you can embed in your
application. You simply need to create a new instance of this class
and then call methods on it, those methods will call the remote
service.

Paul

On Wed, Jun 4, 2008 at 11:48 AM, Jyotsna Varma <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
>
> I am new to the web services and so as to axis. Please help me.
>
> I have to show something this week. I have been working to sort this out
> since last 4 days.
>
> I am sorry to say this.
>
>
>
> I have an existing web application. To use axis in existing application,
>
> I have done :
>
> 1.copy all jars from axis.lib directory
>
> 2.copy axis's web.xml servlet params and mapping to to my web.xml
>
>
>
> I have got a wsdl url from an external application (to be integrated with my
> application)
>
> Now what should I do to use this wsdl to access the external application ?
>
> Please kind enough to me.
>
>
>
> Many Thanks,
>
>
>
>
>
> 
> Sent from Yahoo! Mail.
> A Smarter Email.



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL security

[Sukma Agung Verdianto]

Hi,

It is more like transport level security.You need to set it up on your HTTP
server, or servlet/appserver container. Use basic/digest auhentication.
If you;re using tomcat, please check Apache Tomcat Realm Configuration.

Regards,
Sukma

On Wed, May 21, 2008 at 2:13 AM, sultanat <[EMAIL PROTECTED]> wrote:

>
> How can I protect a user from accessing or viewing a WSDL without
> authorization.
> I would like to implement something which the link below does when we try
> to
> view the WSDL.
> https://webservices.oit.umn.edu/axis2/services/AdvisingService?wsdl
>
> Thanks.
> --
> View this message in context:
> http://www.nabble.com/WSDL-security-tp17348404p17348404.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: .wsdl to soap template generator

[Charitha Kankanamge]

Hi Micheal,
SOAPUI can easily be used to generate a template for request soap envelope
Have a look http://www.soapui.org/

regards
Charitha

Michael Potter wrote:


Axi2 crew,

Is there a script that will read .wsdl file and output a soap message
template much like wsdl2java reads .wsdl and outputs a java template.

The reason I am hoping to find this is: I have some slightly complex
data structures in in my .wsdl that do not lend themselves to a
generic routine.  I will need to write a routine for each message.  If
I had a script that will output a soap message template, then I could
run the script and cut and paste it into my code.

By code, I mean some javascript that will be invoking the webservice.

 





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL

[Anne Thomas Manes]

A byte array is not a simple type. Can you use a different type?

On Wed, Mar 12, 2008 at 6:05 AM, shams jawaid <[EMAIL PROTECTED]> wrote:
>
>  Hi Anne,
>
>  thanks for your reply, i managed to generate a document/literal WSDL file
> (with java2wsdl), to use in the J2ME Wireless Toolkit Stub generator, but it
> seems i am getting the error:
>
>  "error: found unknown simple type: byte[]" . I read that this error could
> be overcome with using a document/literal WSDL file, but it hasnt.
>  Any idea on how to overcome this error?
>
>  Thanks!
>
>  ps, SAMS Securing Web Services with WS-Security, great book! :D
>
> > Date: Tue, 11 Mar 2008 08:35:04 -0400
>
>
> > From: [EMAIL PROTECTED]
> > To: axis-user@ws.apache.org
> > Subject: Re: WSDL
> >
> > Using the "style" parameter. See
> > http://ws.apache.org/axis/java/ant/axis-java2wsdl.html and
> > http://ws.apache.org/axis/java/reference.html#Java2WSDLReference.
> >
> > Anne
> >
> > On Sun, Mar 9, 2008 at 3:55 PM, shams jawaid <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi Anne,
> > >
> > > thanks for your reply. How exactly would i specify the "wrapped" (for
> j2me)
> > > style while using the java2wsdl tool? currently i type:
> > >
> > > java2wsdl -cn packagename.mainclass
> > >
> > > > Date: Sun, 9 Mar 2008 15:39:38 -0400
> > > > From: [EMAIL PROTECTED]
> > >
> > >
> > > > To: axis-user@ws.apache.org
> > > > Subject: Re: WSDL
> > > >
> > > > The Axis2 java2wsdl tool generates doc/literal -- but my guess is that
> > > > it generates too much other stuff -- e.g., WS-Addressing, SOAP 1.2,
> > > > etc. I suggest you use the Axis java2wsdl tool and specify "wrapped"
> > > > style. The resulting WSDL should be acceptable to J2ME. You can then
> > > > use that WSDL as input to the Axis2 wsdl2java tool.
> > > >
> > > > Anne
> > > >
> > > > On Sun, Mar 2, 2008 at 3:50 PM, shams jawaid <[EMAIL PROTECTED]>
> wrote:
> > > > >
> > > > > hi,
> > > > >
> > > > > thanks for your reply, but
> > > > >
> > > > > i've used the java2wsdl tool from axis2, but this does not create a
> > > > > compatible WSDL (document/literal) for J2ME stub generator,
> > > > >
> > > > > which i need to create it for.
> > > > >
> > > > > has anyone used the WSDP tools, specifically wsgen, to create a
> > > > > document/literal WSDL? (from java/class files)
> > > > > i've searched google, but i cant manage to get wsgen to work.
> > > > >
> > > > >
> > > > > thanks
> > > > >
> > > > >
> > > > >
> > > > > 
> > > > > Date: Sun, 2 Mar 2008 23:13:24 +0800
> > > > > From: [EMAIL PROTECTED]
> > > > > To: axis-user@ws.apache.org
> > > > > Subject: Re: WSDL
> > > > >
> > > > >
> > > > >
> > > > > dude
> > > > > http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html
> > > > >
> > > > > i used that link to help me out.
> > > > >
> > > > > or if you're not contented with that.. google.. ;)
> > > > >
> > > > >
> > > > > On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid <[EMAIL PROTECTED]>
> > > wrote:
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > does anyone know how to generate a document/literal WSDL file from
> > > .class
> > > > > files (or .java files)?
> > > > > or if anyone knows how to use the 'wscompile' tool, please can you
> help
> > > me
> > > > > out and tell me what commands i need to follow
> > > > >
> > > > > it's urgent
> > > > >
> > > > > thanks
> > > > >
> > > > > 
> > > > > Think you know your TV, music and film? Try Search Charades!
> > > > >
> > > > >
> > > > > --
> > > > > Website: http://chitgoks.freehostia.com
> > > > > Java Casino Games: http://chitgoks.tripod.com
> > > > > My Blogs:
> > > > > http://chitgoks.blogspot.com
> > > > > http://wuhtevah.blogspot.com
> > > > > 
> > > > > Everything in one place. All new Windows Live!
> > > >
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > > >
> > >
> > >
> > > 
> > > Think you know your TV, music and film? Try Search Charades!
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> 
> Sounds like? How many syllables? Guess and win prizes with Search Charades!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: WSDL

[shams jawaid]

Hi Anne, 
 
thanks for your reply, i managed to generate a document/literal WSDL file (with 
java2wsdl), to use in the J2ME Wireless Toolkit Stub generator, but it seems i 
am getting the error:
 
"error: found unknown simple type: byte[]" . I read that this error could be 
overcome with using a document/literal WSDL file, but it hasnt. 
Any idea on how to overcome this error?
 
Thanks!
 
ps, SAMS Securing Web Services with WS-Security, great book! :D> Date: Tue, 11 
Mar 2008 08:35:04 -0400> From: [EMAIL PROTECTED]> To: axis-user@ws.apache.org> 
Subject: Re: WSDL> > Using the "style" parameter. See> 
http://ws.apache.org/axis/java/ant/axis-java2wsdl.html and> 
http://ws.apache.org/axis/java/reference.html#Java2WSDLReference.> > Anne> > On 
Sun, Mar 9, 2008 at 3:55 PM, shams jawaid <[EMAIL PROTECTED]> wrote:> >> > Hi 
Anne,> >> > thanks for your reply. How exactly would i specify the "wrapped" 
(for j2me)> > style while using the java2wsdl tool? currently i type:> >> > 
java2wsdl -cn packagename.mainclass> >> > > Date: Sun, 9 Mar 2008 15:39:38 
-0400> > > From: [EMAIL PROTECTED]> >> >> > > To: axis-user@ws.apache.org> > > 
Subject: Re: WSDL> > >> > > The Axis2 java2wsdl tool generates doc/literal -- 
but my guess is that> > > it generates too much other stuff -- e.g., 
WS-Addressing, SOAP 1.2,> > > etc. I suggest you use the Axis java2wsdl tool 
and specify "wrapped"> > > style. The resulting WSDL should be acceptable to 
J2ME. You can then> > > use that WSDL as input to the Axis2 wsdl2java tool.> > 
>> > > Anne> > >> > > On Sun, Mar 2, 2008 at 3:50 PM, shams jawaid <[EMAIL 
PROTECTED]> wrote:> > > >> > > > hi,> > > >> > > > thanks for your reply, but> 
> > >> > > > i've used the java2wsdl tool from axis2, but this does not create 
a> > > > compatible WSDL (document/literal) for J2ME stub generator,> > > >> > 
> > which i need to create it for.> > > >> > > > has anyone used the WSDP 
tools, specifically wsgen, to create a> > > > document/literal WSDL? (from 
java/class files)> > > > i've searched google, but i cant manage to get wsgen 
to work.> > > >> > > >> > > > thanks> > > >> > > >> > > >> > > > 
> > > > Date: Sun, 2 Mar 2008 23:13:24 +0800> > 
> > From: [EMAIL PROTECTED]> > > > To: axis-user@ws.apache.org> > > > Subject: 
Re: WSDL> > > >> > > >> > > >> > > > dude> > > > 
http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html> > > >> > > > i used 
that link to help me out.> > > >> > > > or if you're not contented with that.. 
google.. ;)> > > >> > > >> > > > On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid 
<[EMAIL PROTECTED]>> > wrote:> > > >> > > >> > > > Hi,> > > >> > > > does 
anyone know how to generate a document/literal WSDL file from> > .class> > > > 
files (or .java files)?> > > > or if anyone knows how to use the 'wscompile' 
tool, please can you help> > me> > > > out and tell me what commands i need to 
follow> > > >> > > > it's urgent> > > >> > > > thanks> > > >> > > > 
> > > > Think you know your TV, music and film? 
Try Search Charades!> > > >> > > >> > > > --> > > > Website: 
http://chitgoks.freehostia.com> > > > Java Casino Games: 
http://chitgoks.tripod.com> > > > My Blogs:> > > > 
http://chitgoks.blogspot.com> > > > http://wuhtevah.blogspot.com> > > > 
> > > > Everything in one place. All new 
Windows Live!> > >> > > 
-> > > To 
unsubscribe, e-mail: [EMAIL PROTECTED]> > > For additional commands, e-mail: 
[EMAIL PROTECTED]> >> > >> >> >> > > > Think 
you know your TV, music and film? Try Search Charades!> > 
-> To 
unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: [EMAIL 
PROTECTED]> 
_
Who's friends with who and co-starred in what?
http://www.searchgamesbox.com/celebrityseparation.shtml

Re: WSDL

[Anne Thomas Manes]

Using the "style" parameter. See
http://ws.apache.org/axis/java/ant/axis-java2wsdl.html and
http://ws.apache.org/axis/java/reference.html#Java2WSDLReference.

Anne

On Sun, Mar 9, 2008 at 3:55 PM, shams jawaid <[EMAIL PROTECTED]> wrote:
>
>  Hi Anne,
>
>  thanks for your reply. How exactly would i specify the "wrapped" (for j2me)
> style while using the java2wsdl tool? currently i type:
>
>  java2wsdl -cn packagename.mainclass
>
> > Date: Sun, 9 Mar 2008 15:39:38 -0400
> > From: [EMAIL PROTECTED]
>
>
> > To: axis-user@ws.apache.org
> > Subject: Re: WSDL
> >
> > The Axis2 java2wsdl tool generates doc/literal -- but my guess is that
> > it generates too much other stuff -- e.g., WS-Addressing, SOAP 1.2,
> > etc. I suggest you use the Axis java2wsdl tool and specify "wrapped"
> > style. The resulting WSDL should be acceptable to J2ME. You can then
> > use that WSDL as input to the Axis2 wsdl2java tool.
> >
> > Anne
> >
> > On Sun, Mar 2, 2008 at 3:50 PM, shams jawaid <[EMAIL PROTECTED]> wrote:
> > >
> > > hi,
> > >
> > > thanks for your reply, but
> > >
> > > i've used the java2wsdl tool from axis2, but this does not create a
> > > compatible WSDL (document/literal) for J2ME stub generator,
> > >
> > > which i need to create it for.
> > >
> > > has anyone used the WSDP tools, specifically wsgen, to create a
> > > document/literal WSDL? (from java/class files)
> > > i've searched google, but i cant manage to get wsgen to work.
> > >
> > >
> > > thanks
> > >
> > >
> > >
> > > 
> > > Date: Sun, 2 Mar 2008 23:13:24 +0800
> > > From: [EMAIL PROTECTED]
> > > To: axis-user@ws.apache.org
> > > Subject: Re: WSDL
> > >
> > >
> > >
> > > dude
> > > http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html
> > >
> > > i used that link to help me out.
> > >
> > > or if you're not contented with that.. google.. ;)
> > >
> > >
> > > On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid <[EMAIL PROTECTED]>
> wrote:
> > >
> > >
> > > Hi,
> > >
> > > does anyone know how to generate a document/literal WSDL file from
> .class
> > > files (or .java files)?
> > > or if anyone knows how to use the 'wscompile' tool, please can you help
> me
> > > out and tell me what commands i need to follow
> > >
> > > it's urgent
> > >
> > > thanks
> > >
> > > 
> > > Think you know your TV, music and film? Try Search Charades!
> > >
> > >
> > > --
> > > Website: http://chitgoks.freehostia.com
> > > Java Casino Games: http://chitgoks.tripod.com
> > > My Blogs:
> > > http://chitgoks.blogspot.com
> > > http://wuhtevah.blogspot.com
> > > 
> > > Everything in one place. All new Windows Live!
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> >
>
>
> 
> Think you know your TV, music and film? Try Search Charades!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: WSDL

[shams jawaid]

Hi Anne, 
 
thanks for your reply. How exactly would i specify the "wrapped" (for j2me) 
style while using the java2wsdl tool? currently i type:
 
java2wsdl -cn packagename.mainclass> Date: Sun, 9 Mar 2008 15:39:38 -0400> 
From: [EMAIL PROTECTED]> To: axis-user@ws.apache.org> Subject: Re: WSDL> > The 
Axis2 java2wsdl tool generates doc/literal -- but my guess is that> it 
generates too much other stuff -- e.g., WS-Addressing, SOAP 1.2,> etc. I 
suggest you use the Axis java2wsdl tool and specify "wrapped"> style. The 
resulting WSDL should be acceptable to J2ME. You can then> use that WSDL as 
input to the Axis2 wsdl2java tool.> > Anne> > On Sun, Mar 2, 2008 at 3:50 PM, 
shams jawaid <[EMAIL PROTECTED]> wrote:> >> > hi,> >> > thanks for your reply, 
but> >> > i've used the java2wsdl tool from axis2, but this does not create a> 
> compatible WSDL (document/literal) for J2ME stub generator,> >> > which i 
need to create it for.> >> > has anyone used the WSDP tools, specifically 
wsgen, to create a> > document/literal WSDL? (from java/class files)> > i've 
searched google, but i cant manage to get wsgen to work.> >> >> > thanks> >> >> 
>> > > > Date: Sun, 2 Mar 2008 23:13:24 +0800> 
> From: [EMAIL PROTECTED]> > To: axis-user@ws.apache.org> > Subject: Re: WSDL> 
>> >> >> > dude> > http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html> >> 
> i used that link to help me out.> >> > or if you're not contented with that.. 
google.. ;)> >> >> > On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid <[EMAIL 
PROTECTED]> wrote:> >> >> > Hi,> >> > does anyone know how to generate a 
document/literal WSDL file from .class> > files (or .java files)?> > or if 
anyone knows how to use the 'wscompile' tool, please can you help me> > out and 
tell me what commands i need to follow> >> > it's urgent> >> > thanks> >> > 
> > Think you know your TV, music and film? Try 
Search Charades!> >> >> > --> > Website: http://chitgoks.freehostia.com> > Java 
Casino Games: http://chitgoks.tripod.com> > My Blogs:> > 
http://chitgoks.blogspot.com> > http://wuhtevah.blogspot.com> > 
> > Everything in one place. All new Windows 
Live!> > -> 
To unsubscribe, e-mail: [EMAIL PROTECTED]> For additional commands, e-mail: 
[EMAIL PROTECTED]> 
_
Get Hotmail on your mobile, text MSN to 63463!
http://mobile.uk.msn.com/pc/mail.aspx

Re: WSDL

[Anne Thomas Manes]

The Axis2 java2wsdl tool generates doc/literal -- but my guess is that
it generates too much other stuff -- e.g., WS-Addressing, SOAP 1.2,
etc. I suggest you use the Axis java2wsdl tool and specify "wrapped"
style. The resulting WSDL should be acceptable to J2ME. You can then
use that WSDL as input to the Axis2 wsdl2java tool.

Anne

On Sun, Mar 2, 2008 at 3:50 PM, shams jawaid <[EMAIL PROTECTED]> wrote:
>
>  hi,
>
>  thanks for your reply, but
>
>  i've used the java2wsdl tool from axis2, but this does not create a
> compatible WSDL (document/literal) for J2ME stub generator,
>
>  which i need to create it for.
>
>  has anyone used the WSDP tools, specifically wsgen, to create a
> document/literal WSDL? (from java/class files)
>  i've searched google, but i cant manage to get wsgen to work.
>
>
>  thanks
>
>
>
>  
>  Date: Sun, 2 Mar 2008 23:13:24 +0800
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: Re: WSDL
>
>
>
> dude
> http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html
>
> i used that link to help me out.
>
> or if you're not contented with that.. google.. ;)
>
>
> On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid <[EMAIL PROTECTED]> wrote:
>
>
> Hi,
>
> does anyone know how to generate a document/literal WSDL file from .class
> files (or .java files)?
> or if anyone knows how to use the 'wscompile' tool, please can you help me
> out and tell me what commands i need to follow
>
> it's urgent
>
> thanks
>
>  
>  Think you know your TV, music and film? Try Search Charades!
>
>
> --
> Website: http://chitgoks.freehostia.com
> Java Casino Games: http://chitgoks.tripod.com
> My Blogs:
> http://chitgoks.blogspot.com
> http://wuhtevah.blogspot.com
> 
> Everything in one place. All new Windows Live!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL element restrictions

[Amila Suriarachchi]

Please try with a nighly build. I build with the current code base.
And the generated EndUserIdenfier class has the following method

 public void setEndUserIdentifier(java.lang.String param) {

if ((1 <= java.lang.String.valueOf(param).length()) && (
java.lang.String.valueOf(param).length() <= 255)) {
this.localEndUserIdentifier = param;
} else {
throw new java.lang.RuntimeException();
}


}

so this is checked at the setter method.
thanks,
Amila.

On Thu, Mar 6, 2008 at 6:21 AM, David Bunzli <[EMAIL PROTECTED]>
wrote:

>  Hi all,
>
> I haven't been able to get restrictions to consistently work -
> enumerations work, but not length restrictions. I've tried both Axis2
> v1.1.1 (my production version) and Axis2 v1.3 (just in case v1.3 fixed
> this) with no success. Does anyone have any ideas why?
>
> To help, here are the relevant types...
>
>
>
> 
>  
>  
>  
> 
>
>
>
>
> 
>  
>  
> 
>
>
> Here is the complete WSDL...
> 
>   xmlns:eSig="urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au"
>  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>  xmlns:xmime="http://www.w3.org/2005/05/xmlmime";
>  name="SigningServices_v1_0_0"
>
>  
> targetNamespace="urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au">
>  
>   
>
> targetNamespace="urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au"
>
>xmlns:eSig="urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au">
>http://www.w3.org/2005/05/xmlmime";
> schemaLocation="xmlmime.xsd" />
>
>
>
> 
>  
>  
>  
> 
>
>
>
>
> 
>  
>  
> 
>
>
>
> 
>   />
>   maxOccurs="1" xmime:expectedContentTypes="application/binary" />
>   maxOccurs="1" />
> 
>
>
>
> 
>   maxOccurs="1" />
>   maxOccurs="1" />
>   maxOccurs="1" />
>   maxOccurs="1" />
>   maxOccurs="1" />
> 
>
>
>
> 
>  
>maxOccurs="1" />
>minOccurs="1" maxOccurs="1" />
>maxOccurs="2" />
>minOccurs="0" maxOccurs="1" />
>minOccurs="0" maxOccurs="1" />
>  
> 
>
>
>
> 
>  
>maxOccurs="1" />
>maxOccurs="1" />
>maxOccurs="1" />
>maxOccurs="1" minOccurs="0" />
>  
> 
>
>
>
>
> 
>   type="xsd:string" />
>   type="xsd:string" />
>   type="xsd:dateTime" />
> 
>
>
>
>
>   
>  
>
>  
>   
>  
>  
>   
>  
>  
>   
>  
>  
>   
>  
>
>  
>   
>
>
>
>
>   
>  
>
>   type="eSig:SigningServices_v1_0_0">
>   http://schemas.xmlsoap.org/soap/http"; />
>   
> soapAction="urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au/Verify"
> />
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>   
>  
>
>  
>   
>This web service facilitates the digital signing and
>verification of content while avoiding the need to implement
>the technical, as well as physical and procedural,
>complexities within user applications.
>   
>name="SigningServices_v1_0_0SOAP">
>http://localhost:8080/SecureServices/Services/Signing_v1_0_0"; />
>   
>  
> 
>
>
> >>> "David Bunzli" [EMAIL PROTECTED]> 25/02/2008 3:51 pm >><[EMAIL 
> >>> PROTECTED]/02/2008+3:51+pm+%3E%3E>
> Hi,
>
> Where does Axis2 enforce WSDL element restrictions? For example, if you
> wish a string element to have a minLength of 1 and maxLength of 3, are
> requests rejected by Schema validation if they don't conform? Or are these
> restrictions in the generated classes from Wsdl2Java?
>
> Regards,
> David
>
> *
>
> This email, including any attachments sent with it, is
>
> confidential and for the sole use of the intended recipient(s).
>
> This confidentiality is not waived or lost, if you receive it and
>
> you are not the intended recipient(s), or if it is transmitted/
>
> received in error.
>
>
>
> Any unauthorised use, alteration, disclosure, distribution or
>
> review of this email is strictly prohibited. The information
>
> contained in this email, including any attachment sent with
>
> it, may be subject to a statutory duty of confidentiality if it
>
> relates to health service matters.
>
>
>
> If you are not the intended recipient(s), or if you have
>
> received this email in error, you are asked to immediately
>
> notify the sender by telephone collect on Australia
>
> +61 1800 198 175 or by return email. You should also
>
> delete this email, and any copies, from your computer
>
> system network and destroy any hard copies produced.
>
>
>
> If not an intended recipient of this email, you must not copy,
>
> distribute or take any action(s) that relies on it; any form of
>
> disclosure, modification, distribution and/or publication of th

Re: WSDL

[chitgoks]

ah sorry
cant say with j2me since ive used it for webapp

On Mon, Mar 3, 2008 at 3:50 AM, shams jawaid <[EMAIL PROTECTED]> wrote:

>  hi,
>
> thanks for your reply, but
>
> i've used the java2wsdl tool from axis2, but this does not create a
> compatible WSDL (document/literal) for J2ME stub generator,
>
> which i need to create it for.
>
> has anyone used the WSDP tools, specifically wsgen, to create a
> document/literal WSDL? (from java/class files)
> i've searched google, but i cant manage to get wsgen to work.
>
>
> thanks
>
>
>  --
> Date: Sun, 2 Mar 2008 23:13:24 +0800
> From: [EMAIL PROTECTED]
> To: axis-user@ws.apache.org
> Subject: Re: WSDL
>
> dude
> http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html
>
> i used that link to help me out.
>
> or if you're not contented with that.. google.. ;)
>
> On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> does anyone know how to generate a document/literal WSDL file from .class
> files (or .java files)?
> or if anyone knows how to use the 'wscompile' tool, please can you help me
> out and tell me what commands i need to follow
>
> it's urgent
>
> thanks
>
> --
> Think you know your TV, music and film? Try Search 
> Charades!<https://www.searchcharades.com/>
>
>
>
>
> --
> Website: http://chitgoks.freehostia.com
> Java Casino Games: http://chitgoks.tripod.com
> My Blogs:
> http://chitgoks.blogspot.com
> http://wuhtevah.blogspot.com
>
>
> --
> Everything in one place. All new Windows 
> Live!<http://www.windowslive.co.uk/get-live>
>



-- 
Website: http://chitgoks.freehostia.com
Java Casino Games: http://chitgoks.tripod.com
My Blogs:
http://chitgoks.blogspot.com
http://wuhtevah.blogspot.com

RE: WSDL

[shams jawaid]

hi, 
 
thanks for your reply, but 
 
i've used the java2wsdl tool from axis2, but this does not create a compatible 
WSDL (document/literal) for J2ME stub generator, 
 
which i need to create it for. 
 
has anyone used the WSDP tools, specifically wsgen, to create a 
document/literal WSDL? (from java/class files)
i've searched google, but i cant manage to get wsgen to work.
 
 
thanks


Date: Sun, 2 Mar 2008 23:13:24 +0800From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: 
Re: WSDLdudehttp://www.onjava.com/pub/a/onjava/2002/06/05/axis.htmli used that 
link to help me out.or if you're not contented with that.. google.. ;)
On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid <[EMAIL PROTECTED]> wrote:

Hi,  does anyone know how to generate a document/literal WSDL file from .class 
files (or .java files)?or if anyone knows how to use the 'wscompile' tool, 
please can you help me out and tell me what commands i need to follow it's 
urgent thanks

Think you know your TV, music and film? Try Search Charades!-- Website: 
http://chitgoks.freehostia.comJava Casino Games: http://chitgoks.tripod.comMy 
Blogs: http://chitgoks.blogspot.comhttp://wuhtevah.blogspot.com 
_
Share what Santa brought you
https://www.mycooluncool.com

Re: WSDL

[chitgoks]

dude
http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html

i used that link to help me out.

or if you're not contented with that.. google.. ;)

On Sun, Mar 2, 2008 at 7:10 PM, shams jawaid <[EMAIL PROTECTED]> wrote:

>  Hi,
>
> does anyone know how to generate a document/literal WSDL file from .class
> files (or .java files)?
> or if anyone knows how to use the 'wscompile' tool, please can you help me
> out and tell me what commands i need to follow
>
> it's urgent
>
> thanks
>
> --
> Think you know your TV, music and film? Try Search 
> Charades!
>



-- 
Website: http://chitgoks.freehostia.com
Java Casino Games: http://chitgoks.tripod.com
My Blogs:
http://chitgoks.blogspot.com
http://wuhtevah.blogspot.com

Re: WSDL element restrictions

[Amila Suriarachchi]

if you generated classes with ADB these restrictions are forced within the
classes.
you can see these codes from the generated classes.

thanks,
Amila.

On Mon, Feb 25, 2008 at 11:21 AM, David Bunzli <
[EMAIL PROTECTED]> wrote:

>  Hi,
>
> Where does Axis2 enforce WSDL element restrictions? For example, if you
> wish a string element to have a minLength of 1 and maxLength of 3, are
> requests rejected by Schema validation if they don't conform? Or are these
> restrictions in the generated classes from Wsdl2Java?
>
> Regards,
> David
>
> *
>
> This email, including any attachments sent with it, is
>
> confidential and for the sole use of the intended recipient(s).
>
> This confidentiality is not waived or lost, if you receive it and
>
> you are not the intended recipient(s), or if it is transmitted/
>
> received in error.
>
>
>
> Any unauthorised use, alteration, disclosure, distribution or
>
> review of this email is strictly prohibited. The information
>
> contained in this email, including any attachment sent with
>
> it, may be subject to a statutory duty of confidentiality if it
>
> relates to health service matters.
>
>
>
> If you are not the intended recipient(s), or if you have
>
> received this email in error, you are asked to immediately
>
> notify the sender by telephone collect on Australia
>
> +61 1800 198 175 or by return email. You should also
>
> delete this email, and any copies, from your computer
>
> system network and destroy any hard copies produced.
>
>
>
> If not an intended recipient of this email, you must not copy,
>
> distribute or take any action(s) that relies on it; any form of
>
> disclosure, modification, distribution and/or publication of this
>
> email is also prohibited.
>
>
>
> Although Queensland Health takes all reasonable steps to
>
> ensure this email does not contain malicious software,
>
> Queensland Health does not accept responsibility for the
>
> consequences if any person's computer inadvertently suffers
>
> any disruption to services, loss of information, harm or is
>
> infected with a virus, other malicious computer programme or
>
> code that may occur as a consequence of receiving this
>
> email.
>
>
>
> Unless stated otherwise, this email represents only the views
>
> of the sender and not the views of the Queensland Government.
>
> 
>
>
>



-- 
Amila Suriarachchi,
WSO2 Inc.

Re: WSDL parser

[Sukma Agung Verdianto]

Hi Demetris,
To read a local file you could simply use "file:///path/to/wsdl/file.wsdl"
as readWSDL argument -> reader.readWSDL("file:///path/to/your/wsdl");,
Or if you have a WSDL serialized in String, you could use reader.readWSDL(
null, new InputSource(new StringReader(wsdlString)));

Regards,
Sukma

On Fri, Feb 22, 2008 at 1:22 PM, Demetris G <[EMAIL PROTECTED]> wrote:

>
> Hi all,
>
>does anyone know of a piece of code similar to the one below that
> can read/parse  a local WSDL file
> serialized in a string rather than a remote WSDL given by a URI?
>
> Thanks
>
> Sukma Agung Verdianto wrote:
> > Hi Demetris,
> >
> > You can try to use wsdl4j (http://sourceforge.net/projects/wsdl4j) to
> > get the operations of specified wsdl file. (AFAIK, Axis2 uses this in
> > their wsdl2java code)
> >
> > public static void main(String[] args) throws Exception {
> >
> > WSDLFactory fac = WSDLFactoryImpl.newInstance();
> >
> > WSDLReader reader = fac.newWSDLReader();
> >
> > Definition def =
> > reader.readWSDL("http://api.google.com/GoogleSearch.wsdl";);
> >
> > Map services = def.getServices();
> >
> > for(Object serviceKey : services.keySet()) {
> >
> > QName serviceQName = (QName) serviceKey;
> >
> > Service service = (Service) services.get(serviceQName);
> >
> > System.out.println("Namespace: " +
> > service.getQName().getNamespaceURI() + ", Service Name: " +
> > service.getQName().getLocalPart());
> >
> > Map ports = service.getPorts();
> >
> > for(Object portKey : ports.keySet()) {
> >
> > String portName = (String) portKey;
> >
> > Port port = (Port) ports.get(portName);
> >
> > System.out.println("  Namespace: " +
> > port.getBinding().getQName().getNamespaceURI() + ", Binding Name: " +
> > port.getBinding().getQName().getLocalPart());
> >
> > List operations = port.getBinding().getBindingOperations();
> >
> > for(Object operation : operations) {
> >
> > BindingOperation op = (BindingOperation) operation;
> >
> > System.out.print("Operation Name: " + op.getName());
> >
> > List ll = op.getExtensibilityElements();
> >
> > for(Object soap : ll) {
> >
> > if(SOAPOperation.class.isInstance(soap)) {
> >
> > System.out.print(" (" + ((SOAPOperation)soap).getSoapActionURI() + ")");
> >
> > }
> >
> > }
> >
> > System.out.println();
> >
> > }
> >
> > }
> >
> > }
> >
> > }
> >
> >
> > Above code read remote wsdl, and extract its information.
> >
> > Regards,
> > Sukma
> >
> > On Feb 17, 2008 2:09 PM, Demetris G <[EMAIL PROTECTED]
> > > wrote:
> >
> >
> > Hi all,
> >
> >I am trying to use the wsdlParser from the Axis API to parse
> > the methods
> > out of an incoming WSDL file - does anyone who has used this
> > before have
> > any info on how to use this tool? OR any other way I could get the
> > operations
> > of the remote service out of the WSDL file? I would appreciate it.
> >
> > Thanks
> >
> >
> >
> -
> > 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: WSDL parser

[Demetris G]

Hey Sukma,

   thanks for the response - I oringally went with the second option 
but I was getting an exception
on the StringReader. I think I know what the problem is - at least you 
verified for me that I am on

the right path. I appreciate it.

Many regards once again

Sukma Agung Verdianto wrote:

Hi Demetris,

To read a local file you could simply use 
"file:///path/to/wsdl/file.wsdl" as readWSDL argument 
-> reader.readWSDL("file:///path/to/your/wsdl");,
Or if you have a WSDL serialized in String, you could 
use reader.readWSDL(null, new InputSource(new StringReader(wsdlString)));


Regards,
Sukma

On Fri, Feb 22, 2008 at 1:22 PM, Demetris G <[EMAIL PROTECTED] 
> wrote:



Hi all,

   does anyone know of a piece of code similar to the one below that
can read/parse  a local WSDL file
serialized in a string rather than a remote WSDL given by a URI?

Thanks

Sukma Agung Verdianto wrote:
> Hi Demetris,
>
> You can try to use wsdl4j
(http://sourceforge.net/projects/wsdl4j) to
> get the operations of specified wsdl file. (AFAIK, Axis2 uses
this in
> their wsdl2java code)
>
> public static void main(String[] args) throws Exception {
>
> WSDLFactory fac = WSDLFactoryImpl.newInstance();
>
> WSDLReader reader = fac.newWSDLReader();
>
> Definition def =
> reader.readWSDL("http://api.google.com/GoogleSearch.wsdl";);
>
> Map services = def.getServices();
>
> for(Object serviceKey : services.keySet()) {
>
> QName serviceQName = (QName) serviceKey;
>
> Service service = (Service) services.get(serviceQName);
>
> System.out.println("Namespace: " +
> service.getQName().getNamespaceURI() + ", Service Name: " +
> service.getQName().getLocalPart());
>
> Map ports = service.getPorts();
>
> for(Object portKey : ports.keySet()) {
>
> String portName = (String) portKey;
>
> Port port = (Port) ports.get(portName);
>
> System.out.println("  Namespace: " +
> port.getBinding().getQName().getNamespaceURI() + ", Binding
Name: " +
> port.getBinding().getQName().getLocalPart());
>
> List operations = port.getBinding().getBindingOperations();
>
> for(Object operation : operations) {
>
> BindingOperation op = (BindingOperation) operation;
>
> System.out.print("Operation Name: " + op.getName());
>
> List ll = op.getExtensibilityElements();
>
> for(Object soap : ll) {
>
> if(SOAPOperation.class.isInstance(soap)) {
>
> System.out.print(" (" + ((SOAPOperation)soap).getSoapActionURI()
+ ")");
>
> }
>
> }
>
> System.out.println();
>
> }
>
> }
>
> }
>
> }
>
>
> Above code read remote wsdl, and extract its information.
>
> Regards,
> Sukma
>
> On Feb 17, 2008 2:09 PM, Demetris G <[EMAIL PROTECTED]

> >> wrote:
>
>
> Hi all,
>
>I am trying to use the wsdlParser from the Axis API to parse
> the methods
> out of an incoming WSDL file - does anyone who has used this
> before have
> any info on how to use this tool? OR any other way I could
get the
> operations
> of the remote service out of the WSDL file? I would
appreciate it.
>
> Thanks
>
>
>
-

> 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: WSDL parser

[Demetris G]

Hi all,

   does anyone know of a piece of code similar to the one below that 
can read/parse  a local WSDL file

serialized in a string rather than a remote WSDL given by a URI?

Thanks

Sukma Agung Verdianto wrote:

Hi Demetris,

You can try to use wsdl4j (http://sourceforge.net/projects/wsdl4j) to 
get the operations of specified wsdl file. (AFAIK, Axis2 uses this in 
their wsdl2java code)


public static void main(String[] args) throws Exception {

WSDLFactory fac = WSDLFactoryImpl.newInstance();

WSDLReader reader = fac.newWSDLReader();

Definition def = 
reader.readWSDL("http://api.google.com/GoogleSearch.wsdl";);


Map services = def.getServices();

for(Object serviceKey : services.keySet()) {

QName serviceQName = (QName) serviceKey;

Service service = (Service) services.get(serviceQName);

System.out.println("Namespace: " + 
service.getQName().getNamespaceURI() + ", Service Name: " + 
service.getQName().getLocalPart());


Map ports = service.getPorts();

for(Object portKey : ports.keySet()) {

String portName = (String) portKey;

Port port = (Port) ports.get(portName);

System.out.println("  Namespace: " + 
port.getBinding().getQName().getNamespaceURI() + ", Binding Name: " + 
port.getBinding().getQName().getLocalPart());


List operations = port.getBinding().getBindingOperations();

for(Object operation : operations) {

BindingOperation op = (BindingOperation) operation;

System.out.print("Operation Name: " + op.getName());

List ll = op.getExtensibilityElements();

for(Object soap : ll) {

if(SOAPOperation.class.isInstance(soap)) {

System.out.print(" (" + ((SOAPOperation)soap).getSoapActionURI() + ")");

}

}

System.out.println();

}

}

}

}


Above code read remote wsdl, and extract its information.

Regards,
Sukma

On Feb 17, 2008 2:09 PM, Demetris G <[EMAIL PROTECTED] 
> wrote:



Hi all,

   I am trying to use the wsdlParser from the Axis API to parse
the methods
out of an incoming WSDL file - does anyone who has used this
before have
any info on how to use this tool? OR any other way I could get the
operations
of the remote service out of the WSDL file? I would appreciate it.

Thanks


-
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: WSDL parser

[Demetris G]

Hi Sukma -

once again thanks for the quick response - much appreciated -
I tried #1 but not #3. I am migrating to SOAP 1.2 so I will also
look into the second option you list. I will let the list know how that
one goes as well.

Regards

Sukma Agung Verdianto wrote:

Hi Demitris,

Sorry for this late response,
I'm not sure if there is a 'ready to use' parser to extract 
information out of SOAP message. But I guess Axis2 have it.


Extracting information from soap message is quite complex.
There are several ways to get those information (eg: operations, to, 
replyto):
1. If you use older SOAP version (1.1) and HTTP transport - operation 
name is defined as HTTP attribute (Could not remember the name, 
"Action" or "Operation")
2. In SOAP (1.2) and HTTP transport there is also an extra HTTP 
attribute (not sure where, you can check by capturing using tcpmon)
3. This is more difficult, if your soap use WS_Addressing standard, 
you may read the SOAP header and look for wsa:Action element value.


Example of SOAP with WS-Addressing header. (see http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; 
soapenv:mustUnderstand="1" 
wsu:Id="Id-13283276">http://localhost:/axis2/services/CalculatorService?wsdl
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; 
soapenv:mustUnderstand="1" wsu:Id="Id-14395294">

http://www.w3.org/2005/08/addressing/anonymous
 
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; 
soapenv:mustUnderstand="1" 
wsu:Id="Id-14264518">urn:uuid:0E4DF98317F35D31DE1179281210189
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; 
soapenv:mustUnderstand="1" wsu:Id="Id-14123379">urn:Divide
  

I hope this will help. :)

Regards,
Sukma

On Feb 19, 2008 11:46 AM, Demetris G <[EMAIL PROTECTED] 
> wrote:



Hey Sukma,

   the code below worked fine - I can get the operations out of the
WSDL. Is there
a similar parser for identifying and extracting the methods out of
outgoing (from the
stubs) SOAP messages? I capture the SOAP message and I can parse
it manually
but is there a standard way (like the code below) for identifying the
methods the
SOAP message is destined to?

Thanks much once again

Sukma Agung Verdianto wrote:
> Hi Demetris,
>
> You can try to use wsdl4j
(http://sourceforge.net/projects/wsdl4j) to
> get the operations of specified wsdl file. (AFAIK, Axis2 uses
this in
> their wsdl2java code)
>
> public static void main(String[] args) throws Exception {
>
> WSDLFactory fac = WSDLFactoryImpl.newInstance();
>
> WSDLReader reader = fac.newWSDLReader();
>
> Definition def =
> reader.readWSDL("http://api.google.com/GoogleSearch.wsdl";);
>
> Map services = def.getServices();
>
> for(Object serviceKey : services.keySet()) {
>
> QName serviceQName = (QName) serviceKey;
>
> Service service = (Service) services.get(serviceQName);
>
> System.out.println("Namespace: " +
> service.getQName().getNamespaceURI() + ", Service Name: " +
> service.getQName().getLocalPart());
>
> Map ports = service.getPorts();
>
> for(Object portKey : ports.keySet()) {
>
> String portName = (String) portKey;
>
> Port port = (Port) ports.get(portName);
>
> System.out.println("  Namespace: " +
> port.getBinding().getQName().getNamespaceURI() + ", Binding
Name: " +
> port.getBinding().getQName().getLocalPart());
>
> List operations = port.getBinding().getBindingOperations();
>
> for(Object operation : operations) {
>
> BindingOperation op = (BindingOperation) operation;
>
> System.out.print("Operation Name: " + op.getName());
>
> List ll = op.getExtensibilityElements();
>
> for(Object soap : ll) {
>
> if(SOAPOperation.class.isInstance(soap)) {
>
> System.out.print(" (" + ((SOAPOperation)soap).getSoapActionURI()
+ ")");
>
> }
>
> }
>
> System.out.println();
>
> }
>
> }
>
> }
>
> }
>
>
> Above code read remote wsdl, and extract its information.
>
> Regards,
> Sukma
>
> On Feb 17, 2008 2:09 PM, Demetris G <[EMAIL PROTECTED]

> >> wrote:
>
>
> Hi all,
>
>I am trying to use the wsdlParser from the Axis API to parse
> the methods
> out of an incoming WSDL file - does anyone who has used this
> before have
> any info on how to use this tool? OR any other way I could
get the
> operations
> of the remote service out of the WSDL file? I would
appreciate it.
>
> Thanks
>
>
>

Re: WSDL parser

[Sukma Agung Verdianto]

Hi Demitris,
Sorry for this late response,
I'm not sure if there is a 'ready to use' parser to extract information out
of SOAP message. But I guess Axis2 have it.

Extracting information from soap message is quite complex.
There are several ways to get those information (eg: operations, to,
replyto):
1. If you use older SOAP version (1.1) and HTTP transport - operation name
is defined as HTTP attribute (Could not remember the name, "Action" or
"Operation")
2. In SOAP (1.2) and HTTP transport there is also an extra HTTP attribute
(not sure where, you can check by capturing using tcpmon)
3. This is more difficult, if your soap use WS_Addressing standard, you may
read the SOAP header and look for wsa:Action element value.

Example of SOAP with WS-Addressing header. (see http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
soapenv:mustUnderstand="1"
wsu:Id="Id-13283276">http://localhost:/axis2/services/CalculatorService?wsdl
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
soapenv:mustUnderstand="1" wsu:Id="Id-14395294">

http://www.w3.org/2005/08/addressing/anonymous
 
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
soapenv:mustUnderstand="1"
wsu:Id="Id-14264518">urn:uuid:0E4DF98317F35D31DE1179281210189
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
soapenv:mustUnderstand="1"
wsu:Id="Id-14123379">urn:Divide  


I hope this will help. :)

Regards,
Sukma

On Feb 19, 2008 11:46 AM, Demetris G <[EMAIL PROTECTED]> wrote:

>
> Hey Sukma,
>
>the code below worked fine - I can get the operations out of the
> WSDL. Is there
> a similar parser for identifying and extracting the methods out of
> outgoing (from the
> stubs) SOAP messages? I capture the SOAP message and I can parse it
> manually
> but is there a standard way (like the code below) for identifying the
> methods the
> SOAP message is destined to?
>
> Thanks much once again
>
> Sukma Agung Verdianto wrote:
> > Hi Demetris,
> >
> > You can try to use wsdl4j (http://sourceforge.net/projects/wsdl4j) to
> > get the operations of specified wsdl file. (AFAIK, Axis2 uses this in
> > their wsdl2java code)
> >
> > public static void main(String[] args) throws Exception {
> >
> > WSDLFactory fac = WSDLFactoryImpl.newInstance();
> >
> > WSDLReader reader = fac.newWSDLReader();
> >
> > Definition def =
> > reader.readWSDL("http://api.google.com/GoogleSearch.wsdl";);
> >
> > Map services = def.getServices();
> >
> > for(Object serviceKey : services.keySet()) {
> >
> > QName serviceQName = (QName) serviceKey;
> >
> > Service service = (Service) services.get(serviceQName);
> >
> > System.out.println("Namespace: " +
> > service.getQName().getNamespaceURI() + ", Service Name: " +
> > service.getQName().getLocalPart());
> >
> > Map ports = service.getPorts();
> >
> > for(Object portKey : ports.keySet()) {
> >
> > String portName = (String) portKey;
> >
> > Port port = (Port) ports.get(portName);
> >
> > System.out.println("  Namespace: " +
> > port.getBinding().getQName().getNamespaceURI() + ", Binding Name: " +
> > port.getBinding().getQName().getLocalPart());
> >
> > List operations = port.getBinding().getBindingOperations();
> >
> > for(Object operation : operations) {
> >
> > BindingOperation op = (BindingOperation) operation;
> >
> > System.out.print("Operation Name: " + op.getName());
> >
> > List ll = op.getExtensibilityElements();
> >
> > for(Object soap : ll) {
> >
> > if(SOAPOperation.class.isInstance(soap)) {
> >
> > System.out.print(" (" + ((SOAPOperation)soap).getSoapActionURI() + ")");
> >
> > }
> >
> > }
> >
> > System.out.println();
> >
> > }
> >
> > }
> >
> > }
> >
> > }
> >
> >
> > Above code read remote wsdl, and extract its information.
> >
> > Regards,
> > Sukma
> >
> > On Feb 17, 2008 2:09 PM, Demetris G <[EMAIL PROTECTED]
> > > wrote:
> >
> >
> > Hi all,
> >
> >I am trying to use the wsdlParser from the Axis API to parse
> > the methods
> > out of an incoming WSDL file - does anyone who has used this
> > before have
> > any info on how to use this tool? OR any other way I could get the
> > operations
> > of the remote service out of the WSDL file? I would appreciate it.
> >
> > Thanks
> >
> >
> >
> -
> > 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: WSDL parser

[Demetris G]

Hey Sukma,

   the code below worked fine - I can get the operations out of the 
WSDL. Is there
a similar parser for identifying and extracting the methods out of 
outgoing (from the

stubs) SOAP messages? I capture the SOAP message and I can parse it manually
but is there a standard way (like the code below) for identifying the 
methods the

SOAP message is destined to?

Thanks much once again

Sukma Agung Verdianto wrote:

Hi Demetris,

You can try to use wsdl4j (http://sourceforge.net/projects/wsdl4j) to 
get the operations of specified wsdl file. (AFAIK, Axis2 uses this in 
their wsdl2java code)


public static void main(String[] args) throws Exception {

WSDLFactory fac = WSDLFactoryImpl.newInstance();

WSDLReader reader = fac.newWSDLReader();

Definition def = 
reader.readWSDL("http://api.google.com/GoogleSearch.wsdl";);


Map services = def.getServices();

for(Object serviceKey : services.keySet()) {

QName serviceQName = (QName) serviceKey;

Service service = (Service) services.get(serviceQName);

System.out.println("Namespace: " + 
service.getQName().getNamespaceURI() + ", Service Name: " + 
service.getQName().getLocalPart());


Map ports = service.getPorts();

for(Object portKey : ports.keySet()) {

String portName = (String) portKey;

Port port = (Port) ports.get(portName);

System.out.println("  Namespace: " + 
port.getBinding().getQName().getNamespaceURI() + ", Binding Name: " + 
port.getBinding().getQName().getLocalPart());


List operations = port.getBinding().getBindingOperations();

for(Object operation : operations) {

BindingOperation op = (BindingOperation) operation;

System.out.print("Operation Name: " + op.getName());

List ll = op.getExtensibilityElements();

for(Object soap : ll) {

if(SOAPOperation.class.isInstance(soap)) {

System.out.print(" (" + ((SOAPOperation)soap).getSoapActionURI() + ")");

}

}

System.out.println();

}

}

}

}


Above code read remote wsdl, and extract its information.

Regards,
Sukma

On Feb 17, 2008 2:09 PM, Demetris G <[EMAIL PROTECTED] 
> wrote:



Hi all,

   I am trying to use the wsdlParser from the Axis API to parse
the methods
out of an incoming WSDL file - does anyone who has used this
before have
any info on how to use this tool? OR any other way I could get the
operations
of the remote service out of the WSDL file? I would appreciate it.

Thanks


-
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: WSDL parser

[Demetris G]

Thanks Martin and Sukma - I will try the two methods you send me and see
how they work. I will share on the list the results on anything I find

Regards

Martin Gainty wrote:

$AXIS2_HOME/bin/wsdl2java -uri NameOfWsdl.wsdl

M-
- Original Message -
From: "Demetris G" <[EMAIL PROTECTED]>
To: 
Sent: Sunday, February 17, 2008 2:09 AM
Subject: WSDL parser


  

Hi all,

I am trying to use the wsdlParser from the Axis API to parse the


methods
  

out of an incoming WSDL file - does anyone who has used this before have
any info on how to use this tool? OR any other way I could get the
operations
of the remote service out of the WSDL file? I would appreciate it.

Thanks


-
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: WSDL / SOAP reply namespaces problem.

[Anne Thomas Manes]

Amila is correct. A valid response would look semantically equivalent to this:

http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>

http://server.ws.te0.com";
xmlns:ns1="http://ws.apache.org/axis1/xsd";>

39 
20080211084047 
1-01-01 
N 
MASTER 

SECURITY 
MAS 
12027 






Anne

On Feb 14, 2008 12:11 AM, Amila Suriarachchi
<[EMAIL PROTECTED]> wrote:
> According to your wsdl, the following elements under the complex type User
> belongs to
> http://ws.apache.org/axis1/xsd namespace.
>
>
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> But According to the response they belongs to a different namesapce. So the
> response is invalid.
>
> thanks,
> Amila.
>
>
> On Feb 12, 2008 12:26 AM, <[EMAIL PROTECTED]> wrote:
>
> >
> > Paul,
> > Thanks for the reply
> >
> > I get this wsdl from the server i am suppused to connect to.
> > How does the http://ws.apache.org/axis1/xsd namespace come to play?
> >
> > "http://ws.apache.org/axis1/xsd";>
> > xmlns="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified">"
> >
> > My generated client code is trying to locate the reply elements in this
> namespace.
> > ( ireformatted the generated code for better readability )
> >
> > if (reader.isStartElement() && new
> javax.xml.namespace.QName("http://ws.apache.org/axis1/xsd","daysValid";).equals(reader.getName()))
> > {
> >nillableValue =
> reader.getAttributeValue("http://www.w3.org/2001/XMLSchema-instance","nil";);
> >if (!"true".equals(nillableValue) && !"1".equals(nillableValue))
> >{
> >java.lang.String content = reader.getElementText();
> >
> object.setDaysValid(org.apache.axis2.databinding.utils.ConverterUtil.convertToString(content));
> >}
> >else
> >{
> >reader.getElementText(); // throw away text nodes if any.
> >}
> >reader.next();
> > }  // End of if for expected property start element
> > else
> > {
> >// A start element we are not expecting indicates an invalid parameter
> was passed
> >throw new org.apache.axis2.databinding.ADBException("Unexpected
> subelement " + reader.getLocalName());
> > }
> >
> > thanks
> > LF
> >
> >
> > 
> Leonid Flom · The Bank of New York Mellon
> > Treasury Systems - CA$H-Register Plus · Tel 212.815.7023 · Fax
> 212.815.8200 · [EMAIL PROTECTED]
> >
> >
> >
> >
> > "Paul Fremantle" <[EMAIL PROTECTED]>
> >
> > 02/11/2008 01:46 PM
> >
> > Please respond to
> > axis-user@ws.apache.org
> >
> >
> > To axis-user@ws.apache.org
> >
> > cc
> >
> > Subject Re: WSDL / SOAP reply namespaces problem.
> >
> >
> >
> >
> >
> >
> >
> >
> > Leonid
> >
> > The response element is defined in the second schema which has the
> > http://server.ws.te0.com";>
> >
> > So the response matches the WSDL as far as I can see.
> > To be honest its a really strange WSDL! Wouldn't it make sense to clean it
> up?
> >
> > Paul
> >
> >
> >
> > On Feb 11, 2008 6:15 PM,  <[EMAIL PROTECTED]> wrote:
> > >
> > >
> > > hello, everybody
> > >
> > >  Can anybody tell me if this SOAP reply message is valid for the given
> wsdl?
> > >  I am using Axis2 to generate the client stub and when running the
> client I
> > > get the
> > >  "org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
> > > Unexpected subelement" exception.
> > >  WSDL is generated by Axis1.
> > >
> > >  It seems that the problem is the namespace of the nested elements of
> the
> > > .
> > >  In wsdl they are defined to be in the "http://ws.apache.org/axis1/xsd";
> > > namespace, but the reply has them in the "http://server.ws.te0.com";.
> > >  I traced the generated source code it is exactly where it is failing.
> > >
> > >  Thanks
> > >  LF
> > >
> > >  SOAP reply:
> > >
> > >   xmlns:

Re: WSDL parser

[Martin Gainty]

$AXIS2_HOME/bin/wsdl2java -uri NameOfWsdl.wsdl

M-
- Original Message -
From: "Demetris G" <[EMAIL PROTECTED]>
To: 
Sent: Sunday, February 17, 2008 2:09 AM
Subject: WSDL parser


>
> Hi all,
>
> I am trying to use the wsdlParser from the Axis API to parse the
methods
> out of an incoming WSDL file - does anyone who has used this before have
> any info on how to use this tool? OR any other way I could get the
> operations
> of the remote service out of the WSDL file? I would appreciate it.
>
> Thanks
>
>
> -
> 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: WSDL parser

[Sukma Agung Verdianto]

Hi Demetris,
You can try to use wsdl4j (http://sourceforge.net/projects/wsdl4j) to get
the operations of specified wsdl file. (AFAIK, Axis2 uses this in their
wsdl2java code)

public static void main(String[] args) throws Exception {

WSDLFactory fac = WSDLFactoryImpl.newInstance();

WSDLReader reader = fac.newWSDLReader();

 Definition def = reader.readWSDL("http://api.google.com/GoogleSearch.wsdl";
);

 Map services = def.getServices();

for(Object serviceKey : services.keySet()) {

QName serviceQName = (QName) serviceKey;

Service service = (Service) services.get(serviceQName);

System.out.println("Namespace: " + service.getQName().getNamespaceURI() + ",
Service Name: " + service.getQName().getLocalPart());

 Map ports = service.getPorts();

for(Object portKey : ports.keySet()) {

String portName = (String) portKey;

Port port = (Port) ports.get(portName);

System.out.println("  Namespace: " +
port.getBinding().getQName().getNamespaceURI()
+ ", Binding Name: " + port.getBinding().getQName().getLocalPart());

 List operations = port.getBinding().getBindingOperations();

for(Object operation : operations) {

BindingOperation op = (BindingOperation) operation;

System.out.print("Operation Name: " + op.getName());

List ll = op.getExtensibilityElements();

for(Object soap : ll) {

if(SOAPOperation.class.isInstance(soap)) {

System.out.print(" (" + ((SOAPOperation)soap).getSoapActionURI() + ")");

}

}

System.out.println();

}

}

}

}

Above code read remote wsdl, and extract its information.

Regards,
Sukma

On Feb 17, 2008 2:09 PM, Demetris G <[EMAIL PROTECTED]> wrote:

>
> Hi all,
>
>I am trying to use the wsdlParser from the Axis API to parse the
> methods
> out of an incoming WSDL file - does anyone who has used this before have
> any info on how to use this tool? OR any other way I could get the
> operations
> of the remote service out of the WSDL file? I would appreciate it.
>
> Thanks
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: WSDL / SOAP reply namespaces problem.

[Amila Suriarachchi]

According to your wsdl, the following elements under the complex type User
belongs to
http://ws.apache.org/axis1/xsd namespace.











But According to the response they belongs to a different namesapce. So the
response is invalid.

thanks,
Amila.

On Feb 12, 2008 12:26 AM, <[EMAIL PROTECTED]> wrote:

>
> Paul,
> Thanks for the reply
>
> I get this wsdl from the server i am suppused to connect to.
> How does the http://ws.apache.org/axis1/xsd namespace come to play?
> "http://ws.apache.org/axis1/xsd*";>
> xmlns="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified">"
>
> My generated client code is trying to locate the reply elements in this
> namespace.
> ( ireformatted the generated code for better readability )
>
> if (reader.isStartElement() && new javax.xml.namespace.QName(*"
> http://ws.apache.org/axis1/xsd","daysValid"*).equals(reader.getName()))
> {
>nillableValue = reader.getAttributeValue("
> http://www.w3.org/2001/XMLSchema-instance","nil";);
>if (!"true".equals(nillableValue) && !"1".equals(nillableValue))
>{
>java.lang.String content = reader.getElementText();
>   object.setDaysValid(
> org.apache.axis2.databinding.utils.ConverterUtil.convertToString
> (content));
>}
>else
>{
>reader.getElementText(); // throw away text nodes if any.
>}
>reader.next();
> }  // End of if for expected property start element
> else
> {
>// A start element we are not expecting indicates an invalid parameter
> was passed
>throw new org.apache.axis2.databinding.ADBException("Unexpected
> subelement " + reader.getLocalName());
> }
>
> thanks
> LF
>
> --
> *Leonid Flom · *The Bank of New York Mellon
> Treasury Systems - CA$H-Register Plus* ·* Tel 212.815.7023* ·* Fax
> 212.815.8200* ·* [EMAIL PROTECTED] <[EMAIL PROTECTED]>* *
>
>
>
>  *"Paul Fremantle" <[EMAIL PROTECTED]>*
>
> 02/11/2008 01:46 PM
>  Please respond to
> axis-user@ws.apache.org
>
>   To
> axis-user@ws.apache.org  cc
>   Subject
> Re: WSDL / SOAP reply namespaces problem.
>
>
>
>
> Leonid
>
> The response element is defined in the second schema which has the
> http://server.ws.te0.com";>
>
> So the response matches the WSDL as far as I can see.
> To be honest its a really strange WSDL! Wouldn't it make sense to clean it
> up?
>
> Paul
>
>
>
> On Feb 11, 2008 6:15 PM,  <[EMAIL PROTECTED]> wrote:
> >
> >
> > hello, everybody
> >
> >  Can anybody tell me if this SOAP reply message is valid for the given
> wsdl?
> >  I am using Axis2 to generate the client stub and when running the
> client I
> > get the
> >  "org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
> > Unexpected subelement" exception.
> >  WSDL is generated by Axis1.
> >
> >  It seems that the problem is the namespace of the nested elements of
> the
> > .
> >  In wsdl they are defined to be in the "http://ws.apache.org/axis1/xsd";
> > namespace, but the reply has them in the "http://server.ws.te0.com";.
> >  I traced the generated source code it is exactly where it is failing.
> >
> >  Thanks
> >  LF
> >
> >  SOAP reply:
> >
> >  http://schemas.xmlsoap.org/soap/envelope/";
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> >  
> >  http://server.ws.te0.com";>
> > 
> > 39 
> > 20080211084047 
> > 1-01-01 
> > N 
> > MASTER 
> > 
> > SECURITY 
> > MAS 
> > 12027 
> > 
> >  
> >  
> >  
> >
> >  WSDL:
> >
> >  
> >   > targetNamespace="
> https://www-nr.qa.thebank.com/services/EntitlementWebServices";
> >  xmlns="http://schemas.xmlsoap.org/wsdl/";
> >  xmlns:apachesoap="http://xml.apache.org/xml-soap";
> >  xmlns:impl="
> https://www-nr.qa.thebank.com/services/EntitlementWebServices";
> >  xmlns:intf="
> https://www-nr.qa.thebank.com/services/EntitlementWebServices";
> >  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
> >  xmlns:tns1="http://ws.apache.org/axis1/xsd";

Re: WSDL / SOAP reply namespaces problem.

[leonid . flom]

Paul,
Thanks for the reply

I get this wsdl from the server i am suppused to connect to. 
How does the http://ws.apache.org/axis1/xsd namespace come to play?
"http://ws.apache.org/axis1/xsd";> 
xmlns="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified">"

My generated client code is trying to locate the reply elements in this 
namespace.
( ireformatted the generated code for better readability )

if (reader.isStartElement() && new javax.xml.namespace.QName(
"http://ws.apache.org/axis1/xsd","daysValid";).equals(reader.getName()))
{
   nillableValue = 
reader.getAttributeValue("http://www.w3.org/2001/XMLSchema-instance","nil";);
   if (!"true".equals(nillableValue) && !"1".equals(nillableValue))
   {
java.lang.String content = reader.getElementText();
 
object.setDaysValid(org.apache.axis2.databinding.utils.ConverterUtil.convertToString(content));
   }
   else
   {
   reader.getElementText(); // throw away text nodes if any.
   }
   reader.next();
}  // End of if for expected property start element
else
{
   // A start element we are not expecting indicates an invalid parameter 
was passed
   throw new org.apache.axis2.databinding.ADBException("Unexpected 
subelement " + reader.getLocalName());
}
 
thanks
LF

Leonid Flom · The Bank of New York Mellon 
Treasury Systems - CA$H-Register Plus · Tel 212.815.7023 · Fax 
212.815.8200 · [EMAIL PROTECTED] 




"Paul Fremantle" <[EMAIL PROTECTED]> 
02/11/2008 01:46 PM
Please respond to
axis-user@ws.apache.org


To
axis-user@ws.apache.org
cc

Subject
Re: WSDL / SOAP reply namespaces problem.






Leonid

The response element is defined in the second schema which has the
http://server.ws.te0.com";>

So the response matches the WSDL as far as I can see.
To be honest its a really strange WSDL! Wouldn't it make sense to clean it 
up?

Paul



On Feb 11, 2008 6:15 PM,  <[EMAIL PROTECTED]> wrote:
>
>
> hello, everybody
>
>  Can anybody tell me if this SOAP reply message is valid for the given 
wsdl?
>  I am using Axis2 to generate the client stub and when running the 
client I
> get the
>  "org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
> Unexpected subelement" exception.
>  WSDL is generated by Axis1.
>
>  It seems that the problem is the namespace of the nested elements of 
the
> .
>  In wsdl they are defined to be in the "http://ws.apache.org/axis1/xsd";
> namespace, but the reply has them in the "http://server.ws.te0.com";.
>  I traced the generated source code it is exactly where it is failing.
>
>  Thanks
>  LF
>
>  SOAP reply:
>
>  http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>  
>  http://server.ws.te0.com";>
> 
> 39 
> 20080211084047 
> 1-01-01 
> N 
> MASTER 
> 
> SECURITY 
> MAS 
> 12027 
> 
>  
>  
>  
>
>  WSDL:
>
>  
>   targetNamespace="
https://www-nr.qa.thebank.com/services/EntitlementWebServices";
>  xmlns="http://schemas.xmlsoap.org/wsdl/";
>  xmlns:apachesoap="http://xml.apache.org/xml-soap";
>  xmlns:impl="
https://www-nr.qa.thebank.com/services/EntitlementWebServices";
>  xmlns:intf="
https://www-nr.qa.thebank.com/services/EntitlementWebServices";
>  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
>  xmlns:tns1="http://ws.apache.org/axis1/xsd";
>  xmlns:tns2="http://server.ws.te0.com";
>  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>  xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
>  
>  http://ws.apache.org/axis1/xsd";
> xmlns="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified">
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  http://server.ws.te0.com";
> xmlns="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified">
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> 
>   
>type="impl:EntReadWebServices">
>  transport="http://schemas.xmlsoap.org/soap/http"/&g

Re: WSDL / SOAP reply namespaces problem.

[Paul Fremantle]

Leonid

The response element is defined in the second schema which has the
http://server.ws.te0.com";>

So the response matches the WSDL as far as I can see.
To be honest its a really strange WSDL! Wouldn't it make sense to clean it up?

Paul



On Feb 11, 2008 6:15 PM,  <[EMAIL PROTECTED]> wrote:
>
>
> hello, everybody
>
>  Can anybody tell me if this SOAP reply message is valid for the given wsdl?
>  I am using Axis2 to generate the client stub and when running the client I
> get the
>  "org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException:
> Unexpected subelement" exception.
>  WSDL is generated by Axis1.
>
>  It seems that the problem is the namespace of the nested elements of the
> .
>  In wsdl they are defined to be in the "http://ws.apache.org/axis1/xsd";
> namespace, but the reply has them in the "http://server.ws.te0.com";.
>  I traced the generated source code it is exactly where it is failing.
>
>  Thanks
>  LF
>
>  SOAP reply:
>
>  http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>  
>  http://server.ws.te0.com";>
> 
> 39 
> 20080211084047 
> 1-01-01 
> N 
> MASTER 
> 
> SECURITY 
> MAS 
> 12027 
> 
>  
>  
>  
>
>  WSDL:
>
>  
>   targetNamespace="https://www-nr.qa.thebank.com/services/EntitlementWebServices";
>  xmlns="http://schemas.xmlsoap.org/wsdl/";
>  xmlns:apachesoap="http://xml.apache.org/xml-soap";
>  xmlns:impl="https://www-nr.qa.thebank.com/services/EntitlementWebServices";
>  xmlns:intf="https://www-nr.qa.thebank.com/services/EntitlementWebServices";
>  xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
>  xmlns:tns1="http://ws.apache.org/axis1/xsd";
>  xmlns:tns2="http://server.ws.te0.com";
>  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>  xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/";
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>
>  
>  http://ws.apache.org/axis1/xsd";
> xmlns="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified">
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  http://server.ws.te0.com";
> xmlns="http://www.w3.org/2001/XMLSchema"; elementFormDefault="qualified">
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>  
>
>   
> 
>   
>   
> 
>   
>   
> 
>   
>   
> 
>   
>type="impl:EntReadWebServices">
>  transport="http://schemas.xmlsoap.org/soap/http"/>
> 
>   
>   
> 
>   
>   
> 
>   
> 
>   
>   
>  name="EntitlementWebServices">
>location="https://www-nr.qa.thebank.com/services/EntitlementWebServices"/>
> 
>   
>  
>
>  
> Leonid Flom · The Bank of New York Mellon
>  Treasury Systems - CA$H-Register Plus · Tel 212.815.7023 · Fax 212.815.8200
> · [EMAIL PROTECTED]
>
>  The information contained in this e-mail, and any attachment, is
> confidential and is intended solely for the use of the intended recipient.
> Access, copying or re-use of the e-mail or any attachment, or any
> information contained therein, by any other person is not authorized. If you
> are not the intended recipient please return the e-mail to the sender and
> delete it from your computer. Although we attempt to sweep e-mail and
> attachments for viruses, we do not guarantee that either are virus-free and
> accept no liability for any damage sustained as a result of viruses.
>
>  Please refer to http://disclaimer.bankofny.com/eu.htm for certain
> disclosures relating to European legal entities.
>



-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL import and schemaLocation

[prasad c iyer]

Hard coded values did the trick.
But it is not good for me. I ran into other problem my xsd imports many 
other schema which uses the relative path. Even my WSDL file uses many 
schema.
It is very error prone to edit the location. I might have to think something 
different.


Any help would be highly appreciated.
regards



- Original Message - 
From: "prasad c iyer" <[EMAIL PROTECTED]>

To: 
Sent: Wednesday, January 16, 2008 9:28 AM
Subject: Re: WSDL import and schemaLocation



Yeah maybe I should try that.
Want to know one more thing is there a specific reason why it is 
implemented that way. Coz in real life WSDL files and schema would be 
developed by some other parties which you would use it. If they implement 
schema location with the relative path there is a problem.


One more thing if I set useOriginalWSDL parameter to false, the generated 
WSDL should have entire path to the schema file. I have not tried doing 
it.


many thanks

- Original Message - 
From: "keith chapman" <[EMAIL PROTECTED]>

To: 
Sent: Tuesday, January 15, 2008 6:16 PM
Subject: Re: WSDL import and schemaLocation



If you need an absolute URI in there you can try saving the WSDL to
your hard disk, Update it manually to have an absolute URI and then
add it to the META-INF folder of your aar. Also add the parameter
useOriginalWSDL="true" to your services.xml.

Thanks,
Keith.

On Jan 16, 2008 5:18 AM, prasad c iyer <[EMAIL PROTECTED]> wrote:



I did used WSDL2Java tool.
What I'm trying to do is consume the service using PHP. But when I query 
the

WSDL file it returns me the following schema location.

I don't think it takes care of this.
regards







- Original Message -
From: Amila Suriarachchi
To: axis-user@ws.apache.org
Sent: Monday, January 14, 2008 8:04 PM
Subject: Re: WSDL import and schemaLocation




On Jan 15, 2008 9:08 AM, prasad c iyer <[EMAIL PROTECTED]> wrote:

>
>
> Hi,
> I am creating the client for an existing web service. My problem is 
> the

schemaLocation is points to the relative path. Is there a way to resolve
this. So that my client can download the schema.


Are you using wsdl2java with  Axis2?  it can  handle the relative
schemaLocations. I think any tool would do this.

thanks,
Amila.

>
>
>
>
> 
> http://localhost:8080/my-app/services/BankServices "
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:tns="http://localhost:8080/my-app/services/BankServices";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:bank="http://localhost:8080/my-app/services/BankServices/types";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";>
>   
> 
>http://localhost:8080/my-app/services/BankServices/types";
schemaLocation="BankServices?xsd=xsd0.xsd"/>
>   
>   
>
>
>
> regards
>



--
Amila Suriarachchi,
WSO2 Inc.




--
Keith Chapman
Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.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]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL import and schemaLocation

[prasad c iyer]

Yeah maybe I should try that.
Want to know one more thing is there a specific reason why it is implemented 
that way. Coz in real life WSDL files and schema would be developed by some 
other parties which you would use it. If they implement schema location with 
the relative path there is a problem.


One more thing if I set useOriginalWSDL parameter to false, the generated 
WSDL should have entire path to the schema file. I have not tried doing it.


many thanks

- Original Message - 
From: "keith chapman" <[EMAIL PROTECTED]>

To: 
Sent: Tuesday, January 15, 2008 6:16 PM
Subject: Re: WSDL import and schemaLocation



If you need an absolute URI in there you can try saving the WSDL to
your hard disk, Update it manually to have an absolute URI and then
add it to the META-INF folder of your aar. Also add the parameter
useOriginalWSDL="true" to your services.xml.

Thanks,
Keith.

On Jan 16, 2008 5:18 AM, prasad c iyer <[EMAIL PROTECTED]> wrote:



I did used WSDL2Java tool.
What I'm trying to do is consume the service using PHP. But when I query 
the

WSDL file it returns me the following schema location.

I don't think it takes care of this.
regards







- Original Message -
From: Amila Suriarachchi
To: axis-user@ws.apache.org
Sent: Monday, January 14, 2008 8:04 PM
Subject: Re: WSDL import and schemaLocation




On Jan 15, 2008 9:08 AM, prasad c iyer <[EMAIL PROTECTED]> wrote:

>
>
> Hi,
> I am creating the client for an existing web service. My problem is the
schemaLocation is points to the relative path. Is there a way to resolve
this. So that my client can download the schema.


Are you using wsdl2java with  Axis2?  it can  handle the relative
schemaLocations. I think any tool would do this.

thanks,
Amila.

>
>
>
>
> 
> http://localhost:8080/my-app/services/BankServices "
xmlns="http://schemas.xmlsoap.org/wsdl/";
xmlns:tns="http://localhost:8080/my-app/services/BankServices";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:bank="http://localhost:8080/my-app/services/BankServices/types";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";>
>   
> 
>http://localhost:8080/my-app/services/BankServices/types";
schemaLocation="BankServices?xsd=xsd0.xsd"/>
>   
>   
>
>
>
> regards
>



--
Amila Suriarachchi,
WSO2 Inc.




--
Keith Chapman
Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.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: WSDL import and schemaLocation

[keith chapman]

If you need an absolute URI in there you can try saving the WSDL to
your hard disk, Update it manually to have an absolute URI and then
add it to the META-INF folder of your aar. Also add the parameter
useOriginalWSDL="true" to your services.xml.

Thanks,
Keith.

On Jan 16, 2008 5:18 AM, prasad c iyer <[EMAIL PROTECTED]> wrote:
>
>
> I did used WSDL2Java tool.
> What I'm trying to do is consume the service using PHP. But when I query the
> WSDL file it returns me the following schema location.
>
> I don't think it takes care of this.
> regards
>
>
>
>
>
>
>
> - Original Message -
> From: Amila Suriarachchi
> To: axis-user@ws.apache.org
> Sent: Monday, January 14, 2008 8:04 PM
> Subject: Re: WSDL import and schemaLocation
>
>
>
>
> On Jan 15, 2008 9:08 AM, prasad c iyer <[EMAIL PROTECTED]> wrote:
>
> >
> >
> > Hi,
> > I am creating the client for an existing web service. My problem is the
> schemaLocation is points to the relative path. Is there a way to resolve
> this. So that my client can download the schema.
>
>
> Are you using wsdl2java with  Axis2?  it can  handle the relative
> schemaLocations. I think any tool would do this.
>
> thanks,
> Amila.
>
> >
> >
> >
> >
> > 
> >  targetNamespace="http://localhost:8080/my-app/services/BankServices "
> xmlns="http://schemas.xmlsoap.org/wsdl/";
> xmlns:tns="http://localhost:8080/my-app/services/BankServices";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:bank="http://localhost:8080/my-app/services/BankServices/types";
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";>
> >   
> > 
> > namespace="http://localhost:8080/my-app/services/BankServices/types";
> schemaLocation="BankServices?xsd=xsd0.xsd"/>
> >   
> >   
> >
> >
> >
> > regards
> >
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.



-- 
Keith Chapman
Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://www.keith-chapman.org

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL import and schemaLocation

[prasad c iyer]

I did used WSDL2Java tool. 
What I'm trying to do is consume the service using PHP. But when I query the 
WSDL file it returns me the following schema location.

I don't think it takes care of this.
regards




  - Original Message - 
  From: Amila Suriarachchi 
  To: axis-user@ws.apache.org 
  Sent: Monday, January 14, 2008 8:04 PM
  Subject: Re: WSDL import and schemaLocation





  On Jan 15, 2008 9:08 AM, prasad c iyer <[EMAIL PROTECTED]> wrote:

Hi,
I am creating the client for an existing web service. My problem is the 
schemaLocation is points to the relative path. Is there a way to resolve this. 
So that my client can download the schema.

  Are you using wsdl2java with  Axis2?  it can  handle the relative 
schemaLocations. I think any tool would do this.

  thanks,
  Amila. 



http://localhost:8080/my-app/services/BankServices " 
xmlns="http://schemas.xmlsoap.org/wsdl/"; 
xmlns:tns="http://localhost:8080/my-app/services/BankServices"; 
xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
xmlns:bank="http://localhost:8080/my-app/services/BankServices/types"; 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";>
  

   http://localhost:8080/my-app/services/BankServices/types"; 
schemaLocation="BankServices?xsd=xsd0.xsd"/>
  
  



regards




  -- 
  Amila Suriarachchi,
  WSO2 Inc. 

Re: WSDL import and schemaLocation

[Amila Suriarachchi]

On Jan 15, 2008 9:08 AM, prasad c iyer <[EMAIL PROTECTED]> wrote:

>  Hi,
> I am creating the client for an existing web service. My problem is the
> schemaLocation is points to the relative path. Is there a way to resolve
> this. So that my client can download the schema.
>

Are you using wsdl2java with  Axis2?  it can  handle the relative
schemaLocations. I think any tool would do this.

thanks,
Amila.

>
> 
> http://localhost:8080/my-app/services/BankServices"; xmlns="
> http://schemas.xmlsoap.org/wsdl/"; xmlns:tns="
> http://localhost:8080/my-app/services/BankServices"; xmlns:xsd="
> http://www.w3.org/2001/XMLSchema"; xmlns:bank="
> http://localhost:8080/my-app/services/BankServices/types"; xmlns:soap="
> http://schemas.xmlsoap.org/wsdl/soap/";>
>   
> 
>http://localhost:8080/my-app/services/BankServices/types";
> schemaLocation="BankServices?xsd=xsd0.xsd"/>
>   
>   
>
>
> regards
>
>



-- 
Amila Suriarachchi,
WSO2 Inc.

Re: WSDL XSD Schema Importing...

[Norman Barker]

Hi,

are you trying to create an ebRIM CSW server, that is interesting -
sorry I missed your earlier emails - I have already run wsdl2java on
the ebrim wsdl files, I also tried doing this with Apache Tuscany -
works with Axis, not with Tuscany.

I don't think this is right forum for a discussion so perhaps we can
take this offline, but if your server solution is public domain then
that is interesting and I would like to know more

Just f.y.i. (again apologies since this is the wrong forum) omar is
spatial enabled -
http://ebxmlrr.sourceforge.net/wiki/index.php/Community/ogc.

Norman

On Jan 10, 2008 2:53 PM, silver17 <[EMAIL PROTECTED]> wrote:
>
> Hi Amila,
>
> Your solution was correct;  I replaced the Axis2 v1.3 libs with the nightly
> build (snapshot) libs and everything works fine.  The Eclipse plugins don't
> work, but if I use the WSDL2Java in the nightly build it works as I expected
> it to.
>
>
> Amila Suriarachchi wrote:
> >
> > can you please try with a nightly build? If you still getting the problem
> > please send your wsdl.
> >
> > thanks,
> > Amila.
> >
> > On Jan 10, 2008 3:33 AM, silver17 <[EMAIL PROTECTED]> wrote:
> >
> >>
> >> Hi Guys,
> >>
> >> I've searched a lot of these forum posts and haven't been able to find a
> >> resolution to my problem.  Currently I am using Axis 2.1.3 and Eclipse
> >> Europa with the Apache Codegen wizard plugins.
> >>
> >> I created a WSDL that imports a couple of schemas and I'm having
> >> problems.
> >> When I attempt to use the wizards to generate the client stubs using a
> >> URL
> >> like:  http://localhost:8080/app/services/RegistryPublish?wsdl I get the
> >> following error:
> >>
> >> An error occured while completing process -
> >> java.lang.InterruptedException
> >> :
> >> WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema):
> >> faultCode=OTHER_ERROR: An error occurred while trying to resolve schema
> >> referenced at 'RegistryPublish?xsd=csw-Publication.xsd", relative to
> >> "http://localhost:8080/app/services'.:
>
> >>  java.io.FileNotFoundException:  This
> >> file was not found:
> >> http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd
> >>
> >> And I don't know why it's doing that.  Here's a sample of that wsdl:
> >>
> >>  >> targetNamespace="http://services.registry.company.com/publish/";>
> >>
> >>WSDL Description for the Registry Publishing Service.
> >> 
> >>
> >>
> >>   
> >>  http://www.opengis.net/cat/csw/2.0.2";
> >> schemaLocation="RegistryPublish?xsd=csw-Publication.xsd"/>
> >>
> >>  http://www.opengis.net/ows/1.1";
> >> schemaLocation="RegistryPublish?xsd=owsExceptionReport.xsd"/>
> >>   
> >>
> >> ...
> >>
> >> My web app directory structure is:
> >>
> >> app->web-inf->services->RegistryPublish->META-INF
> >> ...
> >> csw-Publication.xsd
> >> owsExceptionReport.xsd
> >> RegistryPublish.wsdl
> >> services.xml
> >>
> >> I tried using a program called SOAPUI to run a test request to that same
> >> url
> >> as above and it returned a successful result.
> >>
> >> Any thoughts?  I've attached the files.
> >> http://www.nabble.com/file/p14722764/RegistryPublish.wsdl
> >> RegistryPublish.wsdl
> >> http://www.nabble.com/file/p14722764/services.xml services.xml
> >> http://www.nabble.com/file/p14722764/owsExceptionReport.xsd
> >> owsExceptionReport.xsd
> >> http://www.nabble.com/file/p14722764/csw-Publication.xsd
> >> csw-Publication.xsd
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14722764.html
> >> Sent from the Axis - User mailing list archive at Nabble.com.
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> > --
> > Amila Suriarachchi,
> > WSO2 Inc.
> >
> >
>
> --
> View this message in context: 
> http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14744671.html
>
> Sent from the Axis - User mailing list archive at Nabble.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]

Re: WSDL XSD Schema Importing...

[silver17]

Hi Amila,

Your solution was correct;  I replaced the Axis2 v1.3 libs with the nightly
build (snapshot) libs and everything works fine.  The Eclipse plugins don't
work, but if I use the WSDL2Java in the nightly build it works as I expected
it to.


Amila Suriarachchi wrote:
> 
> can you please try with a nightly build? If you still getting the problem
> please send your wsdl.
> 
> thanks,
> Amila.
> 
> On Jan 10, 2008 3:33 AM, silver17 <[EMAIL PROTECTED]> wrote:
> 
>>
>> Hi Guys,
>>
>> I've searched a lot of these forum posts and haven't been able to find a
>> resolution to my problem.  Currently I am using Axis 2.1.3 and Eclipse
>> Europa with the Apache Codegen wizard plugins.
>>
>> I created a WSDL that imports a couple of schemas and I'm having
>> problems.
>> When I attempt to use the wizards to generate the client stubs using a
>> URL
>> like:  http://localhost:8080/app/services/RegistryPublish?wsdl I get the
>> following error:
>>
>> An error occured while completing process -
>> java.lang.InterruptedException
>> :
>> WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema):
>> faultCode=OTHER_ERROR: An error occurred while trying to resolve schema
>> referenced at 'RegistryPublish?xsd=csw-Publication.xsd", relative to
>> "http://localhost:8080/app/services'.:
>>  java.io.FileNotFoundException:  This
>> file was not found:
>> http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd
>>
>> And I don't know why it's doing that.  Here's a sample of that wsdl:
>>
>> > targetNamespace="http://services.registry.company.com/publish/";>
>>
>>WSDL Description for the Registry Publishing Service.
>> 
>>
>>
>>   
>>  http://www.opengis.net/cat/csw/2.0.2";
>> schemaLocation="RegistryPublish?xsd=csw-Publication.xsd"/>
>>
>>  http://www.opengis.net/ows/1.1";
>> schemaLocation="RegistryPublish?xsd=owsExceptionReport.xsd"/>
>>   
>>
>> ...
>>
>> My web app directory structure is:
>>
>> app->web-inf->services->RegistryPublish->META-INF
>> ...
>> csw-Publication.xsd
>> owsExceptionReport.xsd
>> RegistryPublish.wsdl
>> services.xml
>>
>> I tried using a program called SOAPUI to run a test request to that same
>> url
>> as above and it returned a successful result.
>>
>> Any thoughts?  I've attached the files.
>> http://www.nabble.com/file/p14722764/RegistryPublish.wsdl
>> RegistryPublish.wsdl
>> http://www.nabble.com/file/p14722764/services.xml services.xml
>> http://www.nabble.com/file/p14722764/owsExceptionReport.xsd
>> owsExceptionReport.xsd
>> http://www.nabble.com/file/p14722764/csw-Publication.xsd
>> csw-Publication.xsd
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14722764.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> -- 
> Amila Suriarachchi,
> WSO2 Inc.
> 
> 

-- 
View this message in context: 
http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14744671.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: WSDL location

[Kandalam, Anjana]

Hi ,

The client Im using is Axis 1.4 in java.  The wsdl defines both SOAPAction
and wsaw:action settings. In the client if I add the line
call.setSOAPActionURI(" operation name") then I am able to hit the service.
Is there a way to avoid making this change??

Anjana 

-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 10, 2008 12:19 PM
To: axis-user@ws.apache.org
Subject: Re: WSDL location

Anjana

I'm not clear changing the WSDL file is the right solution here, but
you can do it. You save the WSDL, add it into the service archive, and
then set a flag called useOriginalWSDL.

However

Does the WSDL define SOAPAction or wsa:action settings? And what
client are you using.

Basically the client should automatically pick those actions up from
the WSDL and Axis2 sets actions into the WSDL.
If Axis2 isn't setting actions into the WSDL then its probably easier
to get it to do that:
In the services.xml set

   http://foo.org/myAction


If you want more info about the settings in services.xml (including
useOriginalWSDL) see this article by deepal
http://wso2.org/library/2060

Paul

On Jan 10, 2008 5:11 PM, Kandalam, Anjana <[EMAIL PROTECTED]> wrote:
> So is there no way I can change the wsdl file??I am unable to hit the
> service because it complains that WSA action is nullI have not
specified
> the SOAP action in my clientIs there a way out???
>
> Anjana 
>
> -Original Message-
> From: Paul Fremantle [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 10, 2008 11:57 AM
> To: axis-user@ws.apache.org
> Subject: Re: WSDL location
>
> The WSDL is generated on-demand... it isn't stored. If you want to
> store it you can use a browser (Save As...) or wget to grab it.
>
> Paul
>
> On Jan 10, 2008 4:47 PM, Kandalam, Anjana <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> >
> >
> > I have my services in Axis2 and I am using RawXMLINOutMessageReceiver as
> the
> > message receiver class. Axis2 is auto generating the wsdl. Can I know
> where
> > I can find the physical  location of the file on my file system??
>
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.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]
>
>



-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.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]

Re: WSDL location

[Paul Fremantle]

Anjana

I'm not clear changing the WSDL file is the right solution here, but
you can do it. You save the WSDL, add it into the service archive, and
then set a flag called useOriginalWSDL.

However

Does the WSDL define SOAPAction or wsa:action settings? And what
client are you using.

Basically the client should automatically pick those actions up from
the WSDL and Axis2 sets actions into the WSDL.
If Axis2 isn't setting actions into the WSDL then its probably easier
to get it to do that:
In the services.xml set

   http://foo.org/myAction


If you want more info about the settings in services.xml (including
useOriginalWSDL) see this article by deepal
http://wso2.org/library/2060

Paul

On Jan 10, 2008 5:11 PM, Kandalam, Anjana <[EMAIL PROTECTED]> wrote:
> So is there no way I can change the wsdl file??I am unable to hit the
> service because it complains that WSA action is nullI have not specified
> the SOAP action in my clientIs there a way out???
>
> Anjana Kandalam
> Private Client Group - AIG
> Work: 908-679-2608
> Cell: 908-596-0424
>
> -Original Message-
> From: Paul Fremantle [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 10, 2008 11:57 AM
> To: axis-user@ws.apache.org
> Subject: Re: WSDL location
>
> The WSDL is generated on-demand... it isn't stored. If you want to
> store it you can use a browser (Save As...) or wget to grab it.
>
> Paul
>
> On Jan 10, 2008 4:47 PM, Kandalam, Anjana <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> >
> >
> > I have my services in Axis2 and I am using RawXMLINOutMessageReceiver as
> the
> > message receiver class. Axis2 is auto generating the wsdl. Can I know
> where
> > I can find the physical  location of the file on my file system??
>
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.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]
>
>



-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: WSDL location

[Kandalam, Anjana]

So is there no way I can change the wsdl file??I am unable to hit the
service because it complains that WSA action is nullI have not specified
the SOAP action in my clientIs there a way out???

Anjana Kandalam
Private Client Group - AIG
Work: 908-679-2608
Cell: 908-596-0424
-Original Message-
From: Paul Fremantle [mailto:[EMAIL PROTECTED] 
Sent: Thursday, January 10, 2008 11:57 AM
To: axis-user@ws.apache.org
Subject: Re: WSDL location

The WSDL is generated on-demand... it isn't stored. If you want to
store it you can use a browser (Save As...) or wget to grab it.

Paul

On Jan 10, 2008 4:47 PM, Kandalam, Anjana <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
> I have my services in Axis2 and I am using RawXMLINOutMessageReceiver as
the
> message receiver class. Axis2 is auto generating the wsdl. Can I know
where
> I can find the physical  location of the file on my file system??



-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.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]

Re: WSDL location

[Paul Fremantle]

The WSDL is generated on-demand... it isn't stored. If you want to
store it you can use a browser (Save As...) or wget to grab it.

Paul

On Jan 10, 2008 4:47 PM, Kandalam, Anjana <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
>
> I have my services in Axis2 and I am using RawXMLINOutMessageReceiver as the
> message receiver class. Axis2 is auto generating the wsdl. Can I know where
> I can find the physical  location of the file on my file system??



-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL XSD Schema Importing...

[silver17]

As an addition to this discussion, if instead of trying to reference the
http://localhost/app/services/RegistryPublish.wsdl i get the following
error:

http://www.nabble.com/file/p14736457/serviceError.jpg 

silver17 wrote:
> 
> Hi Guys,
> 
> I've searched a lot of these forum posts and haven't been able to find a
> resolution to my problem.  Currently I am using Axis 2.1.3 and Eclipse
> Europa with the Apache Codegen wizard plugins.
> 
> I created a WSDL that imports a couple of schemas and I'm having problems. 
> When I attempt to use the wizards to generate the client stubs using a URL
> like:  http://localhost:8080/app/services/RegistryPublish?wsdl I get the
> following error:
> 
> An error occured while completing process -
> java.lang.InterruptedException: WSDLException (at
> /wsdl:definitions/wsdl:types/xsd:schema):  faultCode=OTHER_ERROR: An error
> occurred while trying to resolve schema referenced at
> 'RegistryPublish?xsd=csw-Publication.xsd", relative to
> "http://localhost:8080/app/services'.:  java.io.FileNotFoundException: 
> This file was not found: 
> http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd
> 
> And I don't know why it's doing that.  Here's a sample of that wsdl:
> 
>  targetNamespace="http://services.registry.company.com/publish/";>
>   
>   WSDL Description for the Registry Publishing Service.
>  
> 
>   
>  
>   http://www.opengis.net/cat/csw/2.0.2"; 
> schemaLocation="RegistryPublish?xsd=csw-Publication.xsd"/>
> 
>   http://www.opengis.net/ows/1.1";
> schemaLocation="RegistryPublish?xsd=owsExceptionReport.xsd"/>
>
> 
> ...
> 
> My web app directory structure is:
> 
> app->web-inf->services->RegistryPublish->META-INF
> ...
> csw-Publication.xsd
> owsExceptionReport.xsd
> RegistryPublish.wsdl
> services.xml
> 
> I tried using a program called SOAPUI to run a test request to that same
> url as above and it returned a successful result.
> 
> Any thoughts?  I've attached the files.
>  http://www.nabble.com/file/p14722764/RegistryPublish.wsdl
> RegistryPublish.wsdl 
>  http://www.nabble.com/file/p14722764/services.xml services.xml 
>  http://www.nabble.com/file/p14722764/owsExceptionReport.xsd
> owsExceptionReport.xsd 
>  http://www.nabble.com/file/p14722764/csw-Publication.xsd
> csw-Publication.xsd 
> 
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14736457.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL XSD Schema Importing...

[silver17]

To answer your first question, yes it was a typo.

I can also validate the wsdl and xsd's fine in eclipse, and when i set up
the web service I can hit it and return a response using SOAPUI.




Mauro Molinari wrote:
> 
> silver17 ha scritto:
>> "http://localhost:8080/app/services'.:  java.io.FileNotFoundException: 
>> This
>> file was not found: 
>> http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd
> 
>>   > namespace="http://www.opengis.net/cat/csw/2.0.2"; 
>> schemaLocation="RegistryPublish?xsd=csw-Publication.xsd"/>
> 
>> http://www.nabble.com/file/p14722764/csw-Publication.xsd
>> csw-Publication.xsd 
> 
> Is the first a copy 'n' paste problem or does Axis2 really says it can't 
> find http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd? 
> Because your file name seems to start with "csw-", not "cs-"...
> 
> Anyway, I can make Axis2 1.3 work with schema imports, except when 
> trying to do some more complex things like sharing a schema between 
> multiple services (please see 
> https://issues.apache.org/jira/browse/AXIS2-3354).
> 
> Does Eclipse give you any validation error on your WSDL and/or XSDs? 
> (try right-click => Validate)?
> 
> -- 
> Mauro Molinari
> Software Developer
> [EMAIL PROTECTED]
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14734904.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL XSD Schema Importing...

[Mauro Molinari]

silver17 ha scritto:

"http://localhost:8080/app/services'.:  java.io.FileNotFoundException:  This
file was not found: 
http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd


  http://www.opengis.net/cat/csw/2.0.2"; 
schemaLocation="RegistryPublish?xsd=csw-Publication.xsd"/>


http://www.nabble.com/file/p14722764/csw-Publication.xsd csw-Publication.xsd 


Is the first a copy 'n' paste problem or does Axis2 really says it can't 
find http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd? 
Because your file name seems to start with "csw-", not "cs-"...


Anyway, I can make Axis2 1.3 work with schema imports, except when 
trying to do some more complex things like sharing a schema between 
multiple services (please see 
https://issues.apache.org/jira/browse/AXIS2-3354).


Does Eclipse give you any validation error on your WSDL and/or XSDs? 
(try right-click => Validate)?


--
Mauro Molinari
Software Developer
[EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: WSDL XSD Schema Importing...

[silver17]

At the moment all I can find for the nightly builds is the Axis2/C version. 
Also I included the RegistryPublish.wsdl file in the previous message.  

What I think it's doing is replacing when I want to use
http://url/path/service?wsdl instead of service.wsdl.  But when I try to
link directly to http://url/path/service.wsdl it gives me a similar error as
well.


http://www.opengis.net/ows/1.1";
schemaLocation="owsExceptionReport.xsd"/>

with:

http://www.opengis.net/ows/1.1";
 schemaLocation="RegistryPublish?xsd=owsExceptionReport.xsd"/>


Amila Suriarachchi wrote:
> 
> can you please try with a nightly build? If you still getting the problem
> please send your wsdl.
> 
> thanks,
> Amila.
> 
> On Jan 10, 2008 3:33 AM, silver17 <[EMAIL PROTECTED]> wrote:
> 
>>
>> Hi Guys,
>>
>> I've searched a lot of these forum posts and haven't been able to find a
>> resolution to my problem.  Currently I am using Axis 2.1.3 and Eclipse
>> Europa with the Apache Codegen wizard plugins.
>>
>> I created a WSDL that imports a couple of schemas and I'm having
>> problems.
>> When I attempt to use the wizards to generate the client stubs using a
>> URL
>> like:  http://localhost:8080/app/services/RegistryPublish?wsdl I get the
>> following error:
>>
>> An error occured while completing process -
>> java.lang.InterruptedException
>> :
>> WSDLException (at /wsdl:definitions/wsdl:types/xsd:schema):
>> faultCode=OTHER_ERROR: An error occurred while trying to resolve schema
>> referenced at 'RegistryPublish?xsd=csw-Publication.xsd", relative to
>> "http://localhost:8080/app/services'.:
>>  java.io.FileNotFoundException:  This
>> file was not found:
>> http://localhost:8080/app/RegistryPublish?xsd=cs-Publication.xsd
>>
>> And I don't know why it's doing that.  Here's a sample of that wsdl:
>>
>> > targetNamespace="http://services.registry.company.com/publish/";>
>>
>>WSDL Description for the Registry Publishing Service.
>> 
>>
>>
>>   
>>  http://www.opengis.net/cat/csw/2.0.2";
>> schemaLocation="RegistryPublish?xsd=csw-Publication.xsd"/>
>>
>>  http://www.opengis.net/ows/1.1";
>> schemaLocation="RegistryPublish?xsd=owsExceptionReport.xsd"/>
>>   
>>
>> ...
>>
>> My web app directory structure is:
>>
>> app->web-inf->services->RegistryPublish->META-INF
>> ...
>> csw-Publication.xsd
>> owsExceptionReport.xsd
>> RegistryPublish.wsdl
>> services.xml
>>
>> I tried using a program called SOAPUI to run a test request to that same
>> url
>> as above and it returned a successful result.
>>
>> Any thoughts?  I've attached the files.
>> http://www.nabble.com/file/p14722764/RegistryPublish.wsdl
>> RegistryPublish.wsdl
>> http://www.nabble.com/file/p14722764/services.xml services.xml
>> http://www.nabble.com/file/p14722764/owsExceptionReport.xsd
>> owsExceptionReport.xsd
>> http://www.nabble.com/file/p14722764/csw-Publication.xsd
>> csw-Publication.xsd
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14722764.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> -- 
> Amila Suriarachchi,
> WSO2 Inc.
> 
> 

-- 
View this message in context: 
http://www.nabble.com/WSDL-XSD-Schema-Importing...-tp14722764p14727914.html
Sent from the Axis - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]