[
http://issues.apache.org/jira/browse/AXIS2-1224?page=comments#action_12440288 ]
Derek Foster commented on AXIS2-1224:
-
You could have MessageContext hold all of its data in ThreadLocal variables...
That way, no user code would have to chan
[
http://issues.apache.org/jira/browse/AXIS2-1185?page=comments#action_12438256 ]
Derek Foster commented on AXIS2-1185:
-
I definitely think a clear error message about this case is necessary. A lot of
people on the mailing list (myself inclu
[
http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12438183 ]
Derek Foster commented on AXIS2-917:
Just to clarify: I was not suggesting that any changes be rolled back. I
somehow failed to notice Eran's comment that he ha
[
http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12437927 ]
Derek Foster commented on AXIS2-917:
As far as making the transition smoother: If these issues are not going to be
fixed in the Axis2 1.1 release, then the rele
[
http://issues.apache.org/jira/browse/AXIS2-957?page=comments#action_12437896 ]
Derek Foster commented on AXIS2-957:
I definitely agree on the issue of unbundling the exceptions. The current
implementation as an inner class also makes it im
[
http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12437895 ]
Derek Foster commented on AXIS2-917:
Excellent. Thank you all!
It seems that some new issues have emerged from William's analysis. Probably
these should be log
Automatically warn users who try to use rpc/encoded or document/encoded that it
is unsupported.
---
Key: AXIS2-1194
URL: http://issues.apache.org/jira/browse/AXIS2-1194
[
http://issues.apache.org/jira/browse/AXIS2-663?page=comments#action_12434584 ]
Derek Foster commented on AXIS2-663:
I have run into this problem too. It is really frustrating.
Suppose I have services Service1 and Service2. They both includ
[
http://issues.apache.org/jira/browse/AXIS2-919?page=comments#action_12434546 ]
Derek Foster commented on AXIS2-919:
Thank you!
> Unable to print out entire SOAP message: bug in OMElement.serialize()
> --
[
http://issues.apache.org/jira/browse/AXIS2-1129?page=comments#action_12434542 ]
Derek Foster commented on AXIS2-1129:
-
Hmm. I still think it's a real bug (especially considering your workaround
seems to require changes to the XML schema in
[
http://issues.apache.org/jira/browse/AXIS2-928?page=comments#action_12434525 ]
Derek Foster commented on AXIS2-928:
Thanks to you and everyone who helped fix this!
> Not all added header elements are included in outgoing SOAP header unles
[
http://issues.apache.org/jira/browse/AXIS2-1129?page=comments#action_12434520 ]
Derek Foster commented on AXIS2-1129:
-
Hmm. In reading the above comment, it's not clear to me whether Dims found and
fixed an actual bug in the Axis2 or XMLBe
[
http://issues.apache.org/jira/browse/AXIS2-928?page=comments#action_12434315 ]
Derek Foster commented on AXIS2-928:
Here's F.xsd, although it might be easier to just revise the WSDL to not
reference it, since it's not directly related to t
[
http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12434272 ]
Derek Foster commented on AXIS2-917:
Thanks for the pointer to the code samples, Dims.
Based on my reading of the document, I tend to agree with William's asses
[
http://issues.apache.org/jira/browse/AXIS2-1129?page=comments#action_12434019 ]
Derek Foster commented on AXIS2-1129:
-
In answer to Ajith's question:
As I remember, I was using the nightly build from probably September 1st or so,
and foun
[
http://issues.apache.org/jira/browse/AXIS2-931?page=comments#action_12433957 ]
Derek Foster commented on AXIS2-931:
Thanks for fixing this!
> WSDL2Java generated fault exceptions don't provide a way to specify an
> exception message or ca
[
http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12433952 ]
Derek Foster commented on AXIS2-917:
Eran, I appreciate your desire to get Axis 1.1 working code into the hands of
users. I think that your belief that document
[
http://issues.apache.org/jira/browse/AXIS2-1129?page=comments#action_12433934 ]
Derek Foster commented on AXIS2-1129:
-
Ajith is correct in that there is a typo in the example that I posted, but he
is wrong when he suggests that this bug re
Doubled wrapper elements around XMLBeans-generated XML
--
Key: AXIS2-1129
URL: http://issues.apache.org/jira/browse/AXIS2-1129
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Com
[
http://issues.apache.org/jira/browse/AXIS2-919?page=comments#action_12432945 ]
Derek Foster commented on AXIS2-919:
For closing this bug (and getting Axis 1.1 out the door), I don't care if
Iterator-related interface changes are made. I th
[
http://issues.apache.org/jira/browse/AXIS2-919?page=comments#action_12432700 ]
Derek Foster commented on AXIS2-919:
Hi, Eran.
As for me helping fix the iterator issue: I just got back from vacation, and
have a lot of catching up to do. I
[
http://issues.apache.org/jira/browse/AXIS2-1076?page=comments#action_12430578 ]
Derek Foster commented on AXIS2-1076:
-
First of all, I'd like to mention AXIS2-917 here, which notes that the user
guide needs to describe faults and fault han
[
http://issues.apache.org/jira/browse/AXIS2-1074?page=comments#action_12430373 ]
Derek Foster commented on AXIS2-1074:
-
Mea Culpa. It looks like the old JARS were the cause of this problem. Please
close this bug as "Not a bug".
Thanks.
[
http://issues.apache.org/jira/browse/AXIS2-1074?page=comments#action_12430364 ]
Derek Foster commented on AXIS2-1074:
-
This may be due to some old AXIOM JARs that were in my classpath. I am still
investigating...
> WSDL2Java referring to
WSDL2Java referring to nonexistent method OMNamespace.getNamespaceURI
-
Key: AXIS2-1074
URL: http://issues.apache.org/jira/browse/AXIS2-1074
Project: Apache Axis 2.0 (Axis2)
[
http://issues.apache.org/jira/browse/AXIS2-919?page=comments#action_12429161 ]
Derek Foster commented on AXIS2-919:
One further note on the AXIOM classes: The common use of Iterators rather than
Collections in interfaces (as method return
[
http://issues.apache.org/jira/browse/AXIS2-919?page=comments#action_12429158 ]
Derek Foster commented on AXIS2-919:
Hi, Chinthaka.
Thanks for the reply. I think I understand what you are suggesting about what
the bug is. I'm not sure I co
[
http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12428841 ]
Derek Foster commented on AXIS2-917:
Richard:
All you need to do, I think, is to start another bug report with an appropriate
title and a short several-sentenc
[
http://issues.apache.org/jira/browse/AXIS2-931?page=comments#action_12428766 ]
Derek Foster commented on AXIS2-931:
There is a copy of my WSDL in AXIS2-928. I think that pretty much any WSDL that
uses faults should exhibit this problem, th
[
http://issues.apache.org/jira/browse/AXIS2-928?page=comments#action_12428729 ]
Derek Foster commented on AXIS2-928:
I would like to propose this issue as a blocker for Axis2 1.1.
This issue is making it impossible for me to get a working w
[
http://issues.apache.org/jira/browse/AXIS2-931?page=comments#action_12428728 ]
Derek Foster commented on AXIS2-931:
Note that as a result of this bug, the standard Java methods 'getMessage()' and
'getCause()' are useless for such exception
[
http://issues.apache.org/jira/browse/AXIS2-919?page=comments#action_12428727 ]
Derek Foster commented on AXIS2-919:
I would like to propose this issue as a blocker for Axis2 1.1.
This is a basic, clear bug in the implementation of AXIOM wh
[
http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12428724 ]
Derek Foster commented on AXIS2-917:
It seems that the discussion in this bug report has gotten somewhat far away
from the original problem that the bug report
[
http://issues.apache.org/jira/browse/AXIS2-1037?page=comments#action_12428197 ]
Derek Foster commented on AXIS2-1037:
-
Thanks!
Derek
> Error message needs extra space
> ---
>
> Key: AXIS2-1037
>
Error message needs extra space
---
Key: AXIS2-1037
URL: http://issues.apache.org/jira/browse/AXIS2-1037
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Components: Tools
Affects Versions: 1.0
[
http://issues.apache.org/jira/browse/AXIS2-928?page=comments#action_12423454 ]
Derek Foster commented on AXIS2-928:
The version I was running when I reported this was the nightly build from about
four days ago. I just downloaded and tested
[
http://issues.apache.org/jira/browse/AXIS2-931?page=comments#action_12423432 ]
Derek Foster commented on AXIS2-931:
Actually, on consideration, I'd also like to see some additional constructors:
FailureException(String message, FailureDocu
WSDL2Java generated fault exceptions don't provide a way to specify an
exception message or cause.
--
Key: AXIS2-931
URL: http://issues.apache.org/jira/browse/AXIS2-93
[
http://issues.apache.org/jira/browse/AXIS2-928?page=comments#action_12423206 ]
Derek Foster commented on AXIS2-928:
Here's the SOAP that gets generated:
POST /axis2/services/FEUService HTTP/1.1
SOAPAction: acceptFEUEventAction
User-Agent:
[
http://issues.apache.org/jira/browse/AXIS2-928?page=comments#action_12423204 ]
Derek Foster commented on AXIS2-928:
Here's a more complete WSDL:
http://www.C-corp.com/wsdl/2004-10-01/f";
xmlns:tns="http://www.C-corp.com/wsdl/2004-10-0
Not all added header elements are included in outgoing SOAP header unless run
under debugger - bug in OMElement caching?
Key: AXIS2-928
URL: h
WSDL2Java namespace2package option should be additive
-
Key: AXIS2-925
URL: http://issues.apache.org/jira/browse/AXIS2-925
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
[
http://issues.apache.org/jira/browse/AXIS2-919?page=comments#action_12422805 ]
Derek Foster commented on AXIS2-919:
The title of this one should be "bug in OMElement.serialize()", not "but in..."
Looks like my finger slipped.
> Unable to
Unable to print out entire SOAP message: but in OMElement.serialize()
-
Key: AXIS2-919
URL: http://issues.apache.org/jira/browse/AXIS2-919
Project: Apache Axis 2.0 (Axis2)
I
[
http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12422741 ]
Derek Foster commented on AXIS2-917:
Note also issue AXIS2-918, which affects fault handling.
> User guide should give explanation and examples of fault handlin
WSDL2Java/XMLBeans generated interfaces should not reference inner classes of
their own subclasses
--
Key: AXIS2-918
URL: http://issues.apache.org/jira/browse/AXIS2-91
[
http://issues.apache.org/jira/browse/AXIS2-917?page=comments#action_12422734 ]
Derek Foster commented on AXIS2-917:
In case it matters, I am using XMLBeans data binding. If fault handling differs
between data bindings, an example of each s
User guide should give explanation and examples of fault handling
-
Key: AXIS2-917
URL: http://issues.apache.org/jira/browse/AXIS2-917
Project: Apache Axis 2.0 (Axis2)
Issue Typ
Extra "[#text [#text" around description in generated WSDL
--
Key: AXIS2-911
URL: http://issues.apache.org/jira/browse/AXIS2-911
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
[
http://issues.apache.org/jira/browse/AXIS2-903?page=comments#action_12421978 ]
Derek Foster commented on AXIS2-903:
As per the comment I left on AXIS2-844, this does indeed appear to fix the
problem. Apparently it was indeed a lexical scop
[
http://issues.apache.org/jira/browse/AXIS2-845?page=comments#action_12421975 ]
Derek Foster commented on AXIS2-845:
Thanks for fixing this, Ajith!
> WSDL2Java fails to detect nonexistent element referenced by wsdl:message
> ---
[
http://issues.apache.org/jira/browse/AXIS2-844?page=comments#action_12421974 ]
Derek Foster commented on AXIS2-844:
I revised my WSDL as per your suggestion, and it seems to work OK now. (I
haven't tested running it yet, but at least it co
[
http://issues.apache.org/jira/browse/AXIS2-844?page=comments#action_12421751 ]
Derek Foster commented on AXIS2-844:
Oops. That was supposed to be AXIS2-903.
> WSDL2Java uses XmlObject for skeleton parameter when data in XML schema in
> sa
[
http://issues.apache.org/jira/browse/AXIS2-844?page=comments#action_12421750 ]
Derek Foster commented on AXIS2-844:
Thanks for your efforts, Ajith. Unfortunately, this bug does not appear to be
fixed by the above changes. I am still seeing
[
http://issues.apache.org/jira/browse/AXIS2-903?page=comments#action_12421749 ]
Derek Foster commented on AXIS2-903:
Note that I downloaded the nightly build that was released after the fix for
AXIS2-844 was announced, and verified in the s
WSDL2Java STILL uses XmlObject for skeleton parameter when data in XML schema
in same namespace as WSDL document
Key: AXIS2-903
URL: http://issues.apa
[
http://issues.apache.org/jira/browse/AXIS2-845?page=comments#action_12420968 ]
Derek Foster commented on AXIS2-845:
See also AXIS2-765 and AXIS2-844.
> WSDL2Java fails to detect nonexistent element referenced by wsdl:message
>
[
http://issues.apache.org/jira/browse/AXIS2-844?page=comments#action_12420967 ]
Derek Foster commented on AXIS2-844:
See also AXIS2-765 and AXIS2-845.
> WSDL2Java uses XmlObject for skeleton parameter when data in XML schema in
> same namespace as WSD
[
http://issues.apache.org/jira/browse/AXIS2-765?page=comments#action_12420966 ]
Derek Foster commented on AXIS2-765:
This issue probably has the same root cause as AXIS2-844 and Axis2-845.
> Incorrect parameter type in WSDL2Java generated stub method O
[
http://issues.apache.org/jira/browse/AXIS2-844?page=comments#action_12418075 ]
Derek Foster commented on AXIS2-844:
Yes. I have already tested this. When the namespace of the schema is the same
as the targetNamespace of the WSDL document, the problem
WSDL2Java fails to detect nonexistent element referenced by wsdl:message
Key: AXIS2-845
URL: http://issues.apache.org/jira/browse/AXIS2-845
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Report
WSDL2Java uses XmlObject for skeleton parameter when data in XML schema in same
namespace as WSDL document
--
Key: AXIS2-844
URL: http://issues.apache.org/jira/browse/AXIS2-84
62 matches
Mail list logo
