Add some tolerance to BuilderUtil.validateCharSetEncoding()
---
Key: AXIS2-4386
URL: https://issues.apache.org/jira/browse/AXIS2-4386
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/AXIS2-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720535#action_12720535
]
Andreas Veithen commented on AXIS2-4386:
I think it's wrong to say that
[
https://issues.apache.org/jira/browse/AXIS2-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720546#action_12720546
]
Christian Gosch commented on AXIS2-4386:
Custom SOAPBilder sounds fine.
How is
[
https://issues.apache.org/jira/browse/AXIS2-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720575#action_12720575
]
Andreas Veithen commented on AXIS2-4386:
For the moment this is very poorly
Underlying Stax Reader left in a faulty state when sending MTOM attachments
---
Key: AXIS2-4387
URL: https://issues.apache.org/jira/browse/AXIS2-4387
Project: Axis 2.0 (Axis2)
[
https://issues.apache.org/jira/browse/AXIS2-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hans Peter updated AXIS2-4387:
--
Attachment: schema_snippet.xml
There's descriptions on which scenarios that actually do work in the
[
https://issues.apache.org/jira/browse/AXIS2-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720654#action_12720654
]
Christian Gosch commented on AXIS2-4386:
That does not provide very much guidance,
[
https://issues.apache.org/jira/browse/AXIS2-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720657#action_12720657
]
Andreas Veithen commented on AXIS2-4386:
That is correct, except that you can only
[
https://issues.apache.org/jira/browse/AXIS2-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720663#action_12720663
]
Christian Gosch commented on AXIS2-4386:
Fortunately the web service in question is
[
https://issues.apache.org/jira/browse/AXIS2-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720672#action_12720672
]
Andreas Veithen commented on AXIS2-4386:
text/xml is the content type for SOAP 1.1.
JAX-WS: ClassNotFoundException for JAX-WS parameter
---
Key: AXIS2-4388
URL: https://issues.apache.org/jira/browse/AXIS2-4388
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/AXIS2-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4264.
---
Resolution: Fixed
Committed revision 785637
Empty action not applied in
[
https://issues.apache.org/jira/browse/AXIS2-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4388.
---
Resolution: Fixed
Committed Revision: 785647
JAX-WS: ClassNotFoundException for JAX-WS
[
https://issues.apache.org/jira/browse/AXIS2-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-4388:
---
Fix Version/s: 1.6
JAX-WS: ClassNotFoundException for JAX-WS parameter
[
https://issues.apache.org/jira/browse/AXIS2-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-4264:
---
Fix Version/s: 1.6
Empty action not applied in CommonsHTTPTransportSender
[
https://issues.apache.org/jira/browse/AXIS2-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720705#action_12720705
]
Christian Gosch commented on AXIS2-4386:
(I have to admit: This one is only
Axis2 1.5 + EclipseLink + Tomcat 6 = Exceptions, but only sometimes
---
Key: AXIS2-4389
URL: https://issues.apache.org/jira/browse/AXIS2-4389
Project: Axis 2.0 (Axis2)
Issue
[
https://issues.apache.org/jira/browse/AXIS2-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Logan updated AXIS2-4389:
--
Attachment: catalina.out
The stack trace.
Axis2 1.5 + EclipseLink + Tomcat 6 = Exceptions, but only
[
https://issues.apache.org/jira/browse/AXIS2-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-4386.
Resolution: Won't Fix
Marking this issue as resolved. If there are any further questions,
[
https://issues.apache.org/jira/browse/AXIS2-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720717#action_12720717
]
Andreas Veithen commented on AXIS2-4386:
While double quotes are used most of the
[
https://issues.apache.org/jira/browse/AXIS2-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720734#action_12720734
]
Andreas Veithen commented on AXIS2-4389:
The interesting part of the stacktrace is
JAXWS: Java2Security Violation Fixes
Key: AXIS2-4390
URL: https://issues.apache.org/jira/browse/AXIS2-4390
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Rich Scheuerle
[
https://issues.apache.org/jira/browse/AXIS2-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720755#action_12720755
]
Greg Logan commented on AXIS2-4389:
---
I've added a line in my local copy of Axis that
[
https://issues.apache.org/jira/browse/AXIS2-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4390.
---
Resolution: Fixed
Committed revision 785720
JAXWS: Java2Security Violation Fixes
JAX-WS: Two Services Cannot Have the Same Name Error
Key: AXIS2-4391
URL: https://issues.apache.org/jira/browse/AXIS2-4391
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/AXIS2-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4391.
---
Resolution: Fixed
Committed 785748
JAX-WS: Two Services Cannot Have the Same Name Error
JAXWS: DispatchSOAPMessage and ProviderSOAPMessage don't honor SOAPAction
MIMEHeader
Key: AXIS2-4392
URL: https://issues.apache.org/jira/browse/AXIS2-4392
[
https://issues.apache.org/jira/browse/AXIS2-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4392.
---
Resolution: Fixed
Committed 785750
JAXWS: DispatchSOAPMessage and ProviderSOAPMessage
JAXWS: If JAXB classes are not packaged with the JAXWS Application, the service
may fail
Key: AXIS2-4393
URL: https://issues.apache.org/jira/browse/AXIS2-4393
[
https://issues.apache.org/jira/browse/AXIS2-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-4393.
---
Resolution: Fixed
Committed 785755
JAXWS: If JAXB classes are not packaged with the JAXWS
[
https://issues.apache.org/jira/browse/AXIS2-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720834#action_12720834
]
Maite Clay commented on AXIS2-4099:
---
Looks like fixing this issue created a secondary
[
https://issues.apache.org/jira/browse/AXIS2-4391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-4391:
---
Fix Version/s: 1.6
JAX-WS: Two Services Cannot Have the Same Name Error
[
https://issues.apache.org/jira/browse/AXIS2-4392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-4392:
---
Fix Version/s: 1.6
JAXWS: DispatchSOAPMessage and ProviderSOAPMessage don't honor
[
https://issues.apache.org/jira/browse/AXIS2-4393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-4393:
---
Fix Version/s: 1.6
JAXWS: If JAXB classes are not packaged with the JAXWS Application, the
[
https://issues.apache.org/jira/browse/AXIS2-4390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated AXIS2-4390:
---
Fix Version/s: 1.6
JAXWS: Java2Security Violation Fixes
[
https://issues.apache.org/jira/browse/AXIS2-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720848#action_12720848
]
Andreas Veithen commented on AXIS2-4099:
What does the exception say?
I believe that I added a change to the Axis 1.x trunk to stop WSDL2Java from
emitting a multi-argument constructor when the number of arguments reaches the
Java limit of 255.
Not sure what version of Axis 1.x you are using, but you should be able to
check the JavaBeanWriter class for the
[
https://issues.apache.org/jira/browse/AXIS2-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12720862#action_12720862
]
Greg Logan commented on AXIS2-4389:
---
Ok, progress. I did have a missing getter for a
[
https://issues.apache.org/jira/browse/AXIS2-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen reassigned AXIS2-4389:
--
Assignee: Andreas Veithen
Axis2 1.5 + EclipseLink + Tomcat 6 = Exceptions, but only
[
https://issues.apache.org/jira/browse/AXIS2-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen resolved AXIS2-4389.
Resolution: Fixed
Fix Version/s: 1.6
Modified BeanUtil#getPropertyQnameList to
[
https://issues.apache.org/jira/browse/AXIS2-4099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12721020#action_12721020
]
Maite Clay commented on AXIS2-4099:
---
Test code. (2 time zones tested in case the first
Hi Deepal,
is there any other way to engage module without writting
serviceClient.engageModule(); function in the client class to engage the
module when we invoke a service.
Deepal Jayasinghe-2 wrote:
Senthil Sona wrote:
Hi Deepal,
Thanks for your reply. If any module is engage in
42 matches
Mail list logo