Hi Azeez,
What is the verdict on this?
On 31 July 2014 17:14, Sagara Gunathunga sag...@wso2.com wrote:
This issue has been fixed in Apache Woden trunk but Woden trunk use
XMLSchema2 not XMLSchema1 hence we need to do a release from old branch
that is not up to date so can't commit for any
I prefer not forking, but we can treat this as an exception, but create a
Jira item so that we remember to switch to the main code in Apache in the
future.
On Tue, Aug 12, 2014 at 4:32 PM, Uvindra Dias Jayasinha uvin...@wso2.com
wrote:
Hi Azeez,
What is the verdict on this?
On 31 July
JIRA created as requested,
https://wso2.org/jira/browse/APIMANAGER-2730
Sagara will assign it back to AM team once Woden M9 has been released so
that we can do the switch in the future.
On 12 August 2014 17:09, Afkham Azeez az...@wso2.com wrote:
I prefer not forking, but we can treat this
This issue has been fixed in Apache Woden trunk but Woden trunk use
XMLSchema2 not XMLSchema1 hence we need to do a release from old branch
that is not up to date so can't commit for any specific timeline. Since
above changed is already accepted by Woden community IMO it's ok to fork
Woden into
Hi Azeez,
Need approval to fork Apache Woden M9 in order to fix
https://wso2.org/jira/browse/APIMANAGER-2528
in the upcoming APIM 1.7.1 release on chunk 13. Sagara is not in a position
to do an official release of Woden with the fix we require at the moment so
we will need to add this as a
On Wed, Jul 30, 2014 at 6:24 PM, Afkham Azeez az...@wso2.com wrote:
have
Hi Azeez,
This was included as per a bug reported by a client for AM 1.6. We thought
of adding same to 1.7.1 to avoid future issues.
Thanks and Regards,
Ruwan Yatawara
Senior Software Engineer,
WSO2 Inc.
email :
WSDL2 is dead AFAIK. No real deployment we know of uses WSDL2. So, why do
we have to fix this?
On Wed, Jul 30, 2014 at 5:18 PM, Uvindra Dias Jayasinha uvin...@wso2.com
wrote:
Hi Azeez,
Need approval to fork Apache Woden M9 in order to fix
https://wso2.org/jira/browse/APIMANAGER-2528
in
