Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility

2009-03-25 Thread Pradeep Fernando
Hi leon,

I'm bit bussy with my GSOC  hopefully i would be able to fix this within
this week itself. I have gathered required info to
work on this issue  looks good. Sagara gave me some valuable info on woden
parser.

thanks ,
pradeep fernando.


Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility

2009-03-25 Thread Leon Searl
Hi Pradeep,

That time frame is fantastic and works great for us! I look forward to
hearing from you or seeing the JIRA status change.

Thank you very much.

leon

- Original Message -
From: Pradeep Fernando pradee...@gmail.com
To: axis-user@ws.apache.org
Sent: Wednesday, March 25, 2009 8:46:21 AM GMT -06:00 US/Canada Central
Subject: Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java  
utility

Hi leon, 

I'm bit bussy with my GSOC  hopefully i would be able to fix this within this 
week itself. I have gathered required info to 
work on this issue  looks good. Sagara gave me some valuable info on woden 
parser. 

thanks , 
pradeep fernando. 

-- 
Leon S. Searl, Software/Hardware Research Engineer
Information and Telecommunication Technology Center, University of Kansas
Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612
Ph: 785-864-7820 Fax: 785-864-0387
http://www.ittc.ku.edu



RE: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility

2009-03-25 Thread Martin Gainty

this discussion was initiated by WS-Policy embedded in WSDL from Dennis S
If memory serves he mentioned something about various transports not being 
handled?
Is this still the case?

Martin 
__ 
Disclaimer and confidentiality note 
This message is confidential and may be privileged. If you are not the intended 
recipient, we kindly ask you to  please inform the sender. Any unauthorised 
dissemination or copying hereof is prohibited. This message serves for 
information purposes only and shall not have any legally binding effect. Given 
that e-mails can easily be subject to manipulation, we can not accept any 
liability for the content provided.






 Date: Wed, 25 Mar 2009 16:01:18 -0500
 From: se...@ittc.ku.edu
 To: axis-user@ws.apache.org
 CC: k...@ittc.ku.edu
 Subject: Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java  
 utility
 
 Hi Pradeep,
 
 That time frame is fantastic and works great for us! I look forward to
 hearing from you or seeing the JIRA status change.
 
 Thank you very much.
 
 leon
 
 - Original Message -
 From: Pradeep Fernando pradee...@gmail.com
 To: axis-user@ws.apache.org
 Sent: Wednesday, March 25, 2009 8:46:21 AM GMT -06:00 US/Canada Central
 Subject: Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java  
 utility
 
 Hi leon, 
 
 I'm bit bussy with my GSOC  hopefully i would be able to fix this within 
 this week itself. I have gathered required info to 
 work on this issue  looks good. Sagara gave me some valuable info on woden 
 parser. 
 
 thanks , 
 pradeep fernando. 
 
 -- 
 Leon S. Searl, Software/Hardware Research Engineer
 Information and Telecommunication Technology Center, University of Kansas
 Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612
 Ph: 785-864-7820 Fax: 785-864-0387
 http://www.ittc.ku.edu
 

_
HotmailĀ® is up to 70% faster. Now good news travels really fast.
http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009

Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility

2009-03-24 Thread Leon Searl
Hi Pradeep,

We've gotten to the point now where we are going
to have to have the WSDL2.0 version of wsdl2java
write policy information from the WSDL2.0 file
into the services.xml file and the client stub.

We've been doing it by hand on a trial basis so 
that we can do some testing and understand
what is needed in the way of policy. But now
we need to do this for all of our
clients and services and doing it by hand
is not practical.

We talked about ways to get by until JIRA
issue AXIS2-4272 is resolved but none seem
to be reasonable for various reasons.
One possibility is to go ahead and try
to resolve AXIS2-4272 ourselves. We don't
want to duplicate any effort that is already going
on though.

So before we start I want to check to 
see if anyone was already working on this
and if so what the expected time frame would
be? If no one is working on this yet and if there
is no one ready to take it on then we'll take a crack
at it. We are hoping that someone else has already
started on it though.

Thanks

Leon

- Original Message -
From: Pradeep Fernando pradee...@gmail.com
To: axis-user@ws.apache.org
Sent: Monday, March 16, 2009 12:38:35 AM GMT -06:00 US/Canada Central
Subject: Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java  
utility

Hi leon,

I raised a JIRA issue on behalf of you. you can track it here[1].

thanks,
Pradeep Fernando.

[1] https://issues.apache.org/jira/browse/AXIS2-4272

-- 
Leon S. Searl, Software/Hardware Research Engineer
Information and Telecommunication Technology Center, University of Kansas
Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612
Ph: 785-864-7820 Fax: 785-864-0387
http://www.ittc.ku.edu



Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility

2009-03-24 Thread Pradeep Fernando
Hi leaon,

if anyone was already working on this


yes leon I ve been working on this.

 so what the expected time frame would be?


had a problem with policy element retrieving  had discussion with the
woden-dev list. Sagara came up with a answer  I'm yet to try it out. later
in the day I would be able to update on you about this and with a estimated
time frame.

cheers,
Pradeep Fernando


Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility

2009-03-16 Thread Leon Searl
Hi Pradeep,

Thanks you very much!

leon

- Original Message -
From: Pradeep Fernando pradee...@gmail.com
To: axis-user@ws.apache.org
Sent: Monday, March 16, 2009 12:38:35 AM GMT -06:00 US/Canada Central
Subject: Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java  
utility

Hi leon,

I raised a JIRA issue on behalf of you. you can track it here[1].

thanks,
Pradeep Fernando.

[1] https://issues.apache.org/jira/browse/AXIS2-4272

-- 
Leon S. Searl, Software/Hardware Research Engineer
Information and Telecommunication Technology Center, University of Kansas
Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612
Ph: 785-864-7820 Fax: 785-864-0387
http://www.ittc.ku.edu



Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility

2009-03-15 Thread Pradeep Fernando
Hi leon,

I raised a JIRA issue on behalf of you. you can track it here[1].

thanks,
Pradeep Fernando.

[1] https://issues.apache.org/jira/browse/AXIS2-4272


Re: [Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility

2009-03-13 Thread Pradeep Fernando
Hi Leon,


 However, when I tried to do the same with a service that I had
 written, the generated
 service stub did not include the ws-policy information.

no surprises. currently it is under the TODO list. but I would like to
fix this. can you please raise a JIRA issue
regarding this.

cheers,
Pradeep Fernando.


[Axis2 1.4] WS-Policy in WSDL 1.1 vs WSDL2.0 using wsdl2java utility

2009-03-10 Thread Leon Searl
Hi,

The developers at WS02 OxygenTank provided a very good example of  
implementing
Web Services Security with Rampart (http://wso2.org/library/3190).

In this example, they incorporated the WS-Policy information into the  
service WSDL definition,
and then used the tool, wsdl2java to generate the service stub.
This generated stub incorporated the ws-policy, and so no changes or  
extensions were required
in the client (except to set username/password options).

However, when I tried to do the same with a service that I had  
written, the generated
service stub did not include the ws-policy information.
The key difference between the original example and my code was that  
the example
described the service using WSDL 1.1, and I had a WSDL 2.0 definition  
for my service.

Why doesn't wsdl2java incorporate the ws-policy information in the  
stub when given WSDL 2.0 input?
Have I overlooked some command line option?
Or is it dependent upon where in the WSDL the policy information is  
included
(I have placed the policy element inside the wsdl2:binding element)?

The alternative of attaching the policy to the service stub in the  
client code using,
options.setProperty(RampartMessageData.KEY_RAMPART_POLICY,  policy-
string);
as in the Rampart samples, is much less desirable for our environment.
thanks for your help !

leon

-- 
Leon S. Searl, Software/Hardware Research Engineer
Information and Telecommunication Technology Center, University of Kansas
Nichols Hall, 2335 Irving Hill Road, Lawrence, KS 66045-7612
Ph: 785-864-7820 Fax: 785-864-0387
http://www.ittc.ku.edu