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.
: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
: 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
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
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
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
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,