[
http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12416389 ]
Dave MacLean commented on AXIS2-747:
Something to add...if in the Axis2 source code for the MessageContext class,
you can add a line to setEnvelope that seems to fix this p
[
http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12422260 ]
Vinh Tran commented on AXIS2-747:
-
Here is some more information to help resolve this issue
I ran into the same problem with the missing namespace on instance t
[
http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12422355 ]
Ajith Harshana Ranabahu commented on AXIS2-747:
---
What all this tells me is that this could be a possible bug in Axiom. The
reason why it suceeds after
[
http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12425514 ]
Vinh Tran commented on AXIS2-747:
-
I found a resolution to this issue without having to hack the source. It
appears shared namespaces with imported schemas will cau
[
http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12428107 ]
Royston Shufflebotham commented on AXIS2-747:
-
I've just been tracing this through, and it *seems* to be the Jsr173
XMLStreamReader wrapper that's going
[
http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12433599 ]
Ajith Harshana Ranabahu commented on AXIS2-747:
---
Is this still there - I mean has anyone tried the nightlies ?
> Missing namespace on subelement
> --
[
http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12434312 ]
Dave MacLean commented on AXIS2-747:
I will test one of the nightly builds, but unless someone has checked in a fix,
this would still be broken. It was broken
[
http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12438112 ]
Davanum Srinivas commented on AXIS2-747:
I used the wsdl from vinh here:
http://issues.apache.org/jira/browse/AXIS2-747#action_12422260
With the following c
[
http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12414365 ]
Ajith Harshana Ranabahu commented on AXIS2-747:
---
Hmm... this seems to be an XMLBeans issue to me. We rely on the XMLStreamReader
returned from the XMLBeans object