How can a namespace prefix conflict with a URI scheme? That sounds
like a quick and dirty workaround for a more fundamental issue.
Andreas
On Wed, Sep 1, 2010 at 07:47, wrote:
> Author: isurues
> Date: Wed Sep 1 05:47:27 2010
> New Revision: 991441
>
> URL: http://svn.apache.org/viewvc?rev=991
On Wed, Sep 1, 2010 at 03:00, Glen Daniels wrote:
> On 8/30/2010 5:43 PM, Andreas Veithen wrote:
>> I also fixed (r965136) another issue on the trunk that (I believe)
>> affected the same test cases. Maybe you are seeing that issue?
>
> OK, update follows... sorry for the long note!
>
> The summa
[
https://issues.apache.org/jira/browse/AXIS2-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joy Kenneth Harry updated AXIS2-4807:
-
Affects Version/s: (was: 1.3)
(was: 1.4)
NullPointerException in internalSerializeAndConsume
---
Key: AXIS2-4809
URL: https://issues.apache.org/jira/browse/AXIS2-4809
Project: Axis2
Issue Type: Bug
Components: om
Affects
On Thu, Sep 2, 2010 at 1:47 AM, Andreas Veithen
wrote:
> How can a namespace prefix conflict with a URI scheme? That sounds
> like a quick and dirty workaround for a more fundamental issue.
>
Let me explain it further.. I came up with a WSDL generated by our
AxisService2WSDL11 class which has the
[
https://issues.apache.org/jira/browse/AXIS2-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srijith Kochunni updated AXIS2-4809:
Environment: A centralized server hosting the web -service, with multiple
clients consuming
