[jira] Closed: (AXIS2-1310) Deserialization of XMLBeans fails

[ https://issues.apache.org/jira/browse/AXIS2-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Murygin closed AXIS2-1310. - > Deserialization of XMLBeans fails > - > > Key: AXIS

[jira] Closed: (AXIS-2616) download of a big soap-attachment hangs always at the second time on a WSDL2Java generated client

[ https://issues.apache.org/jira/browse/AXIS-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oilid Adsi closed AXIS-2616. Resolution: Won't Fix No one of the apache-team seems to solve this problem! > download of a big soap-attac

Re: Compiling examples using VC2005 and ANT?

Rajika, I've tried to subscribe to that list and it appears to be down. Maybe I'm the only one that cares.. :-/ Thank you, Andrew J. Leer I'm quite sure that On Fri, Apr 9, 2010 at 10:10 PM, Rajika Kumarasiri wrote: > Andrew, > This list is for axis2/java related discusstions. You'll need

Axis2 and POJO from Axis1

Hi all, I am testing legacy WS modules that were running well on Axis 1.4. In essense with minimal changes I have been able to deploy these services on Axis2 1.5 in Tomcat. I can retrieve their WSDL docs the same way I did with Axis 1.4. However, I am noticing that simple clients that generated

Re: Axis2 in Tomcat

And in a similar token, can someone point towards any information on logging - I am assuming it is feasible to be able to track the execution flow of an Axis2 service as it is executing in the (Tomcat) container. Thanks again Demetris wrote: Hi all, if an Axis2 web service deployed in

Re: Axis2 in Tomcat

Hi all, if an Axis2 web service deployed in Tomcat (or any other container) required an external input file (let's say a text file that it needs to read) where should that file reside? webapps/axis2/WEB-INF/services? I have been deploying Axis2 in other containers so far (OSGi) and that re

[jira] Resolved: (AXIS2-4676) mvn eclipse:eclipse StringIndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/AXIS2-4676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Katherine Sanders resolved AXIS2-4676. -- Resolution: Fixed Thanks for the documentation Andreas, the eclipse generation works wi

[jira] Updated: (AXIS2-4678) AxisFault: The service could not be found for the end point refrence.

[ https://issues.apache.org/jira/browse/AXIS2-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sriram Srinivasan updated AXIS2-4678: - Description: log4j:WARN No appenders could be found for logger (org.apache.axis2.descrip

[jira] Commented: (AXIS2-4678) AxisFault: The service could not be found for the end point refrence.

[ https://issues.apache.org/jira/browse/AXIS2-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856351#action_12856351 ] Sriram Srinivasan commented on AXIS2-4678: -- Let me know how to set the SoapAction

[jira] Created: (AXIS2-4678) AxisFault: The service could not be found for the end point refrence.

AxisFault: The service could not be found for the end point refrence. - Key: AXIS2-4678 URL: https://issues.apache.org/jira/browse/AXIS2-4678 Project: Axis2 Issue Type: Bug

RE: [Axis2-Spring] Let's get started: servlet + axis2.xml + JSR-181

Thanks for the support. The project looks good to me and I will look into the scratch code this week to see if we can create some consistency between the two ways of deployment. Stephan van Hugten Van: Andreas Veithen [mailto:[email protected]] Verzond