Re: Axis 1.8.0

As the package name implies, StAXOMBuilder is an internal implementation class. Use the OMXMLBuilderFactory API to create the builder. Andreas On Thu, May 12, 2022 at 8:31 PM Amir Razi wrote: > > We are migrating from axis 1.7.2 to 1.8.0 and we get class not found error > for below: > >

Re: [axis2-jaxws] Errors occurred while build effective model

On Wed, Feb 2, 2022 at 3:34 PM robertlazarski wrote: > I see the problem, I just compiled the axiom from the latest in git: > > [DEBUG] org.codehaus.mojo:aspectj-maven-plugin:jar:1.14.0 > [DEBUG]org.aspectj:aspectjrt:jar:1.9.7:runtime > [DEBUG]org.aspectj:aspectjtools:jar:1.9.7:runtime >

Re: [Axis2] 1.8.0 not encoding CDATA xml string inputs

On Wed, Apr 20, 2022 at 3:58 PM Tom B. Lake [42-Q] wrote: > Hi Axis2 team, > > We are upgrading from Axis2 1.6.2 to 1.8.0 war. In 1.8.0 testing, if a web > service operation has a string input wrapped in a CDATA tag (because its > xml), the string isn't being xml encoded for < and > characters.

Re: Blank data when customers send CDATA in 1.8.0

you Andreas, > > Any suggestion on how to deal with this while we wait for the next release? > > On Sat, Nov 20, 2021, 8:38 AM Andreas Veithen-Knowles < > andreas.veit...@gmail.com> wrote: > >> It's not a problem with the parser configuration, but a bug in the >> impl

Re: Blank data when customers send CDATA in 1.8.0

It's not a problem with the parser configuration, but a bug in the implementation of the getElementText method of the XMLStreamReader returned by getXMLStreamReaderWithoutCaching. This is fixed by https://github.com/apache/ws-axiom/commit/f8eb657ee0c9ee0fd4754ccdc6c96da20dc6de4d . Andreas On

Re: Re[2]: Namespace prefix in Axis 2 - 1.7.3

what server will accept: > http://www.w3.org/2003/05/soap-envelope; > *xmlns:urn*="urn:wsdltypes.nmvs.eu:v2.0" *xmlns:urn1*="urn:types.nmvs.eu: > v2.0"> > > > <*urn*:G110Request> > <*urn1*:Body> > <*urn1*:Pack *urn1*:sn="P

Re: Namespace prefix in Axis 2 - 1.7.3

In which way are those namespace prefix not correct? Andreas On Mon, Sep 10, 2018 at 5:36 PM Sterpu Victor wrote: > > Hello > > I use Axis 2, version 1.7.3. > I generated a SOAP client java source file with wsdl2java but I have problems > using this service because the namespace prefix is not

Re: Security vulnerabilities in Axis2 dependencies? "tribes" & "juli" JAR files

gered just by having the code on the classpath (i.e. > deserialization etc.). > > Br, Martin > > BR, Martin > > On Mon, Aug 6, 2018 at 2:11 PM, Andreas Veithen > wrote: >> >> These libraries are dependencies of axis2-clustering. Are you using >> the clustering

Re: Security vulnerabilities in Axis2 dependencies? "tribes" & "juli" JAR files

These libraries are dependencies of axis2-clustering. Are you using the clustering support? Andreas On Mon, Aug 6, 2018 at 11:13 AM axis2user82 wrote: > > Hi > > Sorry if you are getting this mail twice, but I sent it before having > finished subscribing, so I was unsure if it reached the

Re: Axis2 Upgrade to latest version

Dec 6, 2017 at 9:00 AM, akash prasad <akash@gmail.com> >>>> wrote: >>>>> >>>>> Yes one of the jsp file have not updated. But still i am not able to >>>>> see my services. Is there any configuration changes or need to add any >&g

Re: Axis2 1.6.2 - generating Java Stub File but not with expected namespace

"Supported" implies that a bug in that release could be fixed by a new patch release (assuming it hasn't already been addressed in an existing release). That is not the case because the last release from the 1.6 branch was 1.6.4 and after that the branch became unmaintained and eventually got

Re: Axis2 1.7.4 external dependencies

On Tue, Jun 27, 2017 at 2:24 PM, Sample, David D wrote: > org.apache.http.impl.auth.BasicScheme.authenticate(Credentials, HttpRequest, > HttpContext) uses the constructor org.apache.commons.codec.binary.Base64(int). > > Axis2 1.7.4 includes commons-codec-1.3.jar which

Re: Can Axis2 1.6.2 work in IPv6 env?

On Wed, Jun 21, 2017 at 8:46 AM, Xiong, Wei wrote: > Hello, > > I am using Axis2(Version:1.6.2) and want to know if it works with IPv6. > > I have a windows 7 and it has dual stack. I have my webservices server > running on Tomcat. I am able to see the WSDL from my

Re: [AXIS2] Version 1.2

You can get them here: http://archive.apache.org/dist/ws/axis2/1_2/ Andreas On Mon, Apr 24, 2017 at 7:20 PM, Ringheisen, Don wrote: > All, > Can you tell me where I can locate the Axix2 1.2 distributions? > > > Don Ringheisen > >

Re: Re[6]: HTTP :unsupported content-encoding of '' found

172.30.8.82 > Expect: 100-Continue > Authorization: Basic > > issuer: C=RO, O=certSIGN, OU=certSIGN Qualified CA Class 3 G2, CN=certSIGN > Qualified CA Class 3 G2 > $WSSN: *** > $WSSP: 80 > Content-Type: te

Re: Axis2 - can I obtain the HTTP client?

On Sat, Nov 19, 2016 at 8:22 PM, Sterpu Victor wrote: > I use a Axis client on a non Axis server. > I need to overide(on clietnside) the Content-Encoding received in the HTTP > header from the server because the server sends an invalid Content-Encoding. > Can I obtain the HTTP

Re: Re[4]: HTTP :unsupported content-encoding of '' found

sending one? > > Thank you. > > -- Original Message -- > From: "Andreas Veithen" <andreas.veit...@gmail.com> > To: "Sterpu Victor" <vic...@caido.ro> > Cc: "java-user" <java-user@axis.apache.org> > Sent: 19/11/

Re: Re[2]: HTTP :unsupported content-encoding of '' found

** > $WSRH: 172.30.8.81 > Expect: 100-Continue > Authorization: Basic *** > issuer: C=RO, O=certSIGN, OU=certSIGN Qualified CA Class 3 G2, CN=certSIGN > Qualified CA Class 3 G2 > $WSSN: ws.des-cnas.ro > $WSSP: 80 > Content-Type: text/xm

Re: HTTP :unsupported content-encoding of '' found

Can you show us the HTTP headers of the response? Andreas On Nov 19, 2016 3:45 PM, "Sterpu Victor" wrote: > I' receiving the error: *Caused by: org.apache.axis2.AxisFault: HTTP > :unsupported content-encoding of '' found* > The SOAP call runs fine on the server, but on the

Re: Re[6]: Raw SOAP XML response

Stop talking nonsense, Martin. He's having an issue on the client side, and it doesn't matter what is running on the server side. As I pointed out earlier, once the response has been consumed, you can no longer serialize it, and that explains the error. Andreas On Wed, Nov 16, 2016 at 2:31 PM,

Re: Raw SOAP XML response

This is by design. To avoid the overhead of building a complete DOM like representation of the message, Axis2 actually consumes the message (more specifically the content of the SOAP Body element) when converting it to a Java object. Once that is done, the original message can no longer be

Re: Exception after upgrading to Axis2 1.7.3

Looking at the stack trace, this is likely an interoperability issue with Crimson. That is an old DOM implementation and should no longer be used. Andreas On Mon, Oct 17, 2016 at 9:58 PM, Bill Phillips wrote: > I was tasked out with upgrading our legacy Axis2

Re: E:\Users\C770817\.m2\repository\org\opensaml\openws\1.2.2\openws-1.2.2.pom

Which Rampart version are you using? Andreas On Wed, Sep 14, 2016 at 3:25 PM, Stadelmann Josef wrote: > If I try to build my web service many thing gets downloaded. > > But the biggest sh. . .t comes from as a dependency in Rampart > > > > Downloading: >

Re: Revised: A teething issue with Axis 2

il.com> wrote: > WSDL attached. > > On Tue, Aug 2, 2016 at 2:54 AM, Andreas Veithen <andreas.veit...@gmail.com> > wrote: >> >> Can you post the WSDL that is generated for this service >> (http://localhost:8080/axis2/services/HelloWorld?wsdl)? >> >&g

Re: Revised: A teething issue with Axis 2

Can you post the WSDL that is generated for this service (http://localhost:8080/axis2/services/HelloWorld?wsdl)? Andreas On Sun, Jul 24, 2016 at 6:00 AM, Rupinder Singh wrote: > Hello > > I have just recently started with Web Services. I started by exposing POJO > in Axis2

Re: Axis2 embeded https server

SimpleHTTPServer doesn't support SSL. To get HTTPS support on the server side, you need to deploy AxisServlet into a servlet container. Andreas On Mon, Jun 27, 2016 at 10:09 AM, Sterpu Victor wrote: > Hello > > I'm trying to make a 2 way authentication https server with axis2

Re: Can't use JAX-WS + SOAP 1.2 ?

Martin, AFAIK you are neither a committer nor a member of the ASF, so please stop using a signature misrepresenting your relationship with the ASF. Andreas On Sun, Jun 19, 2016 at 6:12 PM, Martin Gainty wrote: > Its folks like yourself that make Axis the most reliable WS

Re: Building with mvn install -Dmaven.test.skip=true failes

On Tue, Mar 29, 2016 at 9:37 PM, Martin Gainty wrote: > MG>package phase running testcases errors out on EchoService3 > > axis2-1.8/modules/kernel>maven package > > WARNING: Service [ EchoService3] is trying to expose in a transport : > https and which is not available in

Re: Building with mvn install -Dmaven.test.skip=true failes

That is a problem on your end because the ProviderOMContextListener class no longer exists on the trunk. Andreas On Tue, Mar 29, 2016 at 8:43 AM, Stadelmann Josef < josef.stadelm...@axa-winterthur.ch> wrote: > I’ve read that JIRA [axis2-5752] was fixed. So I did an SVN UPDATE to the > trunk. >

Re: Building with mvn install -Dmaven.test.skip=true

Josef, Please create a JIRA ticket for this issue. Andreas On Mon, Mar 21, 2016 at 9:13 AM, Stadelmann Josef < josef.stadelm...@axa-winterthur.ch> wrote: > Hi > > > > Just wanted to build one more time axis2 from the trunk, with > -Dmaven.test.skip=true > > That worked well for me in the past

Re: [Axis2] Fixed value causes Exception for non fixed values in ADB generated code

Could you create a JIRA issue and attach a patch? Andreas On Thu, Mar 17, 2016 at 1:30 PM, Frederik Hansen wrote: > Hi > > I'm using Axis 1.7.1 and found an issue using fixed values in WDSL and the > ADB Codegenerator. > > Basically when one fixed value/attribute exists,

Re: WSsecurity: SignatureMethod error

You should probably ignore Martin, he's just a troll. What I would do is to build Rampart 1.7.0 (or 1.7.1-SNAPSHOT) from the sources with r1087600 removed, to check whether that change is responsible for the problem. Andreas On Sat, Mar 12, 2016 at 9:15 AM, Enrique Soriano

Re: WSsecurity: SignatureMethod error

I looked at the version history and the following commit seems to be related: http://svn.apache.org/viewvc?rev=1087600=rev Maybe that's the change between 1.6.4 and 1.7.0 that explains your issue. Andreas On Fri, Mar 11, 2016 at 3:55 PM, Enrique Soriano wrote: > Hi

Re: Axis 1.7.0 & WS-ReliableMessaging

On Fri, Feb 12, 2016 at 9:40 AM, Jörg Schaible wrote: > Hello, > > it seems the support of WS-ReliableMessaging is finally gone with Axis > 1.7.0, the Sandesha2 module no longer starts due to missing classes/methods. > None of the release notes since 1.6.2 for

Re: Problem with Axis2 1.7.0

runtime: Axis2. Service > generation level: start service. Client generation level: none > - Click 'finish' to start the web service generation > - get the error > > When I use the steps above on Axis2 1.6.4, it works fine. > > > Regards, > Arif > > > > > O

Re: Problem with Axis2 1.7.0

What tool exactly do you use to perform code generation? Alternatively, do you have a full stacktrace? Andreas On Feb 2, 2016 9:13 AM, "M. Arif Wicaksana" wrote: > Dear all, > > we used to develop web service using predefined WSDL (attached) on > Eclipse. Our

Re: [Axis2] Java Upgrade - 7

That is a question you will not get a definitive answer for. First of all, Axis2 1.5 isn't supported on any platform, in the sense that there will be no maintenance releases for the 1.5 branch. Second, if you look at the release dates for 1.5.x, you will see that with the exception of 1.5.6, all

Re: apache-commons-fileupload symlink vulnerability CVE-2013-0248

For this vulnerability to be exploitable, the following conditions must be met: 1) The attacker must have shell access to the machine on which Axis2 runs with any account. Obviously the vulnerability is interesting only if that account is unprivileged and different from the account Axis2 runs as.

[Announce] Release of Apache Axis2 1.6.3

The Apache Axis2 team is pleased to announce the general availability of the Axis2 1.6.3 release. Axis2 1.6.3 is a maintenance release that fixes over 50 issues [1]. It is also the first release to package all the transport implementations from the formerly separate Axis2 Transports project. This

Re: Formatting BigDecimal element in response

I doubt that there is any Web service framework that supports this use case. The reason is that the XML schema spec clearly specifies that enumeration constrains the value space to a specified set of values. [1] What you are asking for is to restrict the lexical space instead, and there is no good

Re: Error building Rampart from trunk

What version of Maven do you use? Andreas On Mon, Oct 6, 2014 at 7:52 PM, David R. Robison david.robi...@openroadsconsulting.com wrote: I am getting the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-plugin:2.3.1:install (default-install) on project

Re: Weird client webservice behavior after redirect

I am using the default implementation of JAX-WS provided by Websphere 7, that is Axis2. That statement is not correct. WebSphere's JAX-WS implementation is based on Axis2, but it is not Axis2. In particular, the HTTP transport used in WebSphere is proprietary. You should submit that issue to IBM.

Re: [Axis2] Web Services Rest using https support‏‏

See the last section of the following document: http://axis.apache.org/axis2/java/core/docs/servlet-transport.html Andreas On Sat, Jun 14, 2014 at 8:17 PM, Marcos Morales marcos.mora...@outlook.com wrote: Hi! I was trying to develop a web service rest using https (the same web service works

Re: Accessing faultstring in Axis2 client

IIRC, the stub has a method to access the (last) message context. From there you should be able to get to the response message and extract the SOAP fault. Andreas On Thu, Jun 5, 2014 at 2:43 PM, Jack Sprat rexclaim...@yahoo.com.invalid wrote: There is a method in the Exception class named

Re: Accessing faultstring in Axis2 client

context. There are many toOM methods that convert an object to an OMElement object. I am using XMLBeans binding. Thanks, J On Friday, June 6, 2014 8:10 AM, Andreas Veithen andreas.veit...@gmail.com wrote: IIRC, the stub has a method to access the (last) message context. From there you

Re: Accessing faultstring in Axis2 client

, it does extend the org.apache.axis2.client.Stub class. On Friday, June 6, 2014 10:36 AM, Andreas Veithen andreas.veit...@gmail.com wrote: Does it have a _getServiceClient() method (i.e. does it extend org.apache.axis2.client.Stub)? Andreas On Fri, Jun 6, 2014 at 3:29 PM, Jack Sprat

Re: WebSocket support for Axis2

://www.engineyard.com/articles/websocket Regards, Gihan On Tue, Mar 18, 2014 at 11:30 PM, Andreas Veithen andreas.veit...@gmail.com wrote: I think we should start with the basics, namely the question what would be the use case for such a transport? Regards, Andreas On Mon, Mar 17, 2014 at 4:59 PM

Re: WebSocket support for Axis2

I think we should start with the basics, namely the question what would be the use case for such a transport? Regards, Andreas On Mon, Mar 17, 2014 at 4:59 PM, Gihan Madushanka gihang...@gmail.com wrote: Hi All, I'm Gihan Madushanka an undergraduate and also a participant of the GSoC 2013

Re: Dependency conflicts when adding Axis2 to large project.

The difference between the two is the version. For some reason, the servlet API 3.x was imported into Maven central with a different artifact ID. That is not something we control. The version of the servlet API used by Axis2 is specified by a dependencyManagement entry in the parent POM (it is 2

Re: Axis2 Print empty/black soap header

Hi Andy, The problem is actually in Axiom: if the SOAP envelope in the object model has an empty SOAP header, Axiom will skip the serialization of the SOAP header element. This causes a consistency problem, as described in AXIOM-430. I'm happy that you bring this issue up because it gives me an

Re: Using Axis2 with Maven

It's the other way round: the release note for **1.5.3** states that Axis2 now relies exclusively on dependencies available from the Maven central repository, and no other Maven repositories are required. This in particular fixes a build problem that appeared after the **1.5.2** release. Andreas

Re: Rampart Policy Assertions not binding correctly

That is because rampart-policy and rampart-core both contain a META-INF/services/org.apache.neethi.builders.AssertionBuilder resource. If you want to produce a single JAR file including the Rampart classes, then you need to merge the contents of these files into a single file. Andreas On Fri,

Re: Need Assisatance : Http-500(Internal Server Error)

That behavior is required by the SOAP specs [1]: In case of a SOAP error while processing the request, the SOAP HTTP server MUST issue an HTTP 500 Internal Server Error response and include a SOAP message in the response containing a SOAP Fault element (see section 4.4) indicating the SOAP

Re: [AXIS2]: axiom jars not found when moving from axis2-1.6.1 to axis2-1.6.2

The code that triggers this error looks for resources called META-INF/axiom.xml in the classpath. The message indicates that for some reason, it can't find the one included in axiom-impl-x.y.z.jar. You need to check why in your particular case, the class loader wouldn't find that resource.

Re: WSImport w JDK 1.6.0_25 and Axis2 1.6.2: Generated stub fails compilation - Update: Actually issue occurring in WSDL2Code

That's simply because the code in JaxbRIDatabindingTemplate.xsl is incorrect. position() != last() checks if the current node is the last node, but the expression appears in an xsl:if block. So, if the last node doesn't satisfy the condition of the xsl:if block, then an extra comma is generated

Re: [Axis2]: org.apache.axiom.om.OMException: Unable to locate the SOAP Part

Could be related to AXIOM-389. Andreas On Thu, Mar 21, 2013 at 12:25 PM, Stefan Traud stefan_tr...@yahoo.com wrote: We use an Axis2 (1.6.1) webservice and client (top-down design using ADB) to collect medical images (using MTOM). While this works smoothly all over the world, a customer in

Re: java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to org.apache.axiom.soap.SOAPFaultDetail

; //The ClassCastException is a result of this call if (soapFault.getDetail() != null) { MapString, Object jaxbContextProperties = null; //other logic removed for brevity. } Thanks Sumit -Original Message- From: Andreas Veithen [mailto:andreas.veit...@gmail.com

Re: java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to org.apache.axiom.soap.SOAPFaultDetail

How is the SOAPFault created? Andreas On Wed, Mar 13, 2013 at 3:19 PM, Shah, Sumit (CGI Federal) sumit.s...@cgifederal.com wrote: Thanks Yashwanth. It seems like this is an issue in Axiom 1.2.14, because both the SOAPFault11Impl and OMElementImpl are classes in Axiom 1.2.14. Does this mean

Re: org.apache.axiom.om.OMException with Axis2 Client

In what kind of environment is this code running? A J2EE application server? Andreas On Fri, Dec 21, 2012 at 12:50 PM, Oscar Rugama oscas...@hotmail.com wrote: Sorry i didn´t change subject Hi all: I´ve created an Axis2 client to retrieve info from an Axis2 Web Service, when i test it

Re: org.apache.axiom.om.OMException with Axis2 Client

On Fri, Dec 21, 2012 at 4:24 PM, Martin Gainty mgai...@hotmail.com wrote: you're right ..this should be handled by a profile inside pom.ml which triggers on feature property value being 'default' or 'dom' if (feature.equals(FEATURE_DEFAULT)) { jarHint = axiom-impl.jar;

Re: Axis SSL authentication help!

I think that the socket factory is cached. Therefore changing the properties after the first request will have no effect. What I would do is to write my own socket factory that implements the necessary logic to distinguish between the two cases. Andreas On Wed, Nov 14, 2012 at 9:42 PM, am am

Re: Errnn238 after boot calling web services

connection Thanks Oscar El 12/11/2012, a las 19:19, Andreas Veithen andreas.veit...@gmail.com escribió: Are these connections expected to go through an HTTP proxy or are they direct connections? Andreas On Mon, Nov 12, 2012 at 8:18 AM, Oscar Rugama oscas

Re: Errnn238 after boot calling web services

Are these connections expected to go through an HTTP proxy or are they direct connections? Andreas On Mon, Nov 12, 2012 at 8:18 AM, Oscar Rugama oscas...@hotmail.com wrote: Hi Andreas, Please find attached stack trace of the ConnectException? Thanks in advance Kind regards,

Re: Errnn238 after boot calling web services

? Andreas On Mon, Nov 12, 2012 at 7:24 PM, Oscar Rugama oscas...@hotmail.com wrote: It goles through a Http Proxy, no direct connection Thanks Oscar El 12/11/2012, a las 19:19, Andreas Veithen andreas.veit...@gmail.com escribió: Are these connections expected to go through an HTTP proxy

Re: Errnn238 after boot calling web services

Do you have the complete stack trace of the ConnectException? Andreas On Sun, Nov 11, 2012 at 9:28 AM, Oscar Rugama oscas...@hotmail.com wrote: Hi I have been looking for a solution for the following during last two weeks and i´am becoming almost crazy, so any help will be welcomed I have

Re: wsdl2java in axis-1_4 does not generate simpleType

This is actually the behavior required by the JAX-RPC 1.1 specification (see section 4.2.5): A simple type derived by restriction from another simple type, referred to as its base type, is mapped to the same Java type that its base type is mapped to. If its base type does not have a standard

Re: AXIS 1.4 SOCKET CLOSED

Can you please post the complete stacktrace? Andreas On Wed, Oct 24, 2012 at 12:44 PM, VSRI sriram.varadhara...@citi.com wrote: Hi, We are getting socket closed error intermittently when we make a out going WS call using Axis client from the AppServer runtime. The same connection has been

Re: [AXIS2][AXIOM] org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR with OMElement created from XML file. HELP ME PLEASE, IMPORTANT!

Can you please create a bug report for this here: https://issues.apache.org/jira/browse/AXIOM Make sure that you mention the exact Axiom version you are using, provide the necessary code to reproduce the issue and add the complete stack trace. Andreas On Mon, Oct 1, 2012 at 12:02 PM, FILIPPO

Re: Problems using Tomcat 7 connection pool to PostgreSQL with Axis2

This might give you some light. http://www.developer.com/db/article.php/3735771/Exposing-a-Database-as-a-Web-Service.htm Deepal Darren said that he is using a connection pool, not the DriverManager API. In that case, you manage connections differently than the pattern shown in your article.

Re: Questions: 1.7.0

You didn't come across 1.7.0, but 1.7.0-SNAPSHOT, which is a snapshot build of the current trunk (i.e. the branch where active development happens). The site you have seen is generated automatically by our continuous integration tool. The download page uses a CGI script, but since the snapshot

Re: Element is outputted with its namespace uri as element name

Normally, when you package a StAX implementation into a J2EE application, it is expected that the application will get that StAX implementation, and not the implementation provided by the JRE or the application server (it's the same as for DOM and XSLT processor implementations). If that's not the

Re: Element is outputted with its namespace uri as element name

No. Axiom is not a StAX implementation. It is a dependency of Axis2 that requires a StAX implementation. If Woodstox is already on your classpath, then it means that there are multiple StAX implementations present and that an implementation other than Woodstox is selected. Can you add some test

Re: Element is outputted with its namespace uri as element name

That is a known issue in Axiom: https://issues.apache.org/jira/browse/AXIOM-421 A workaround is to use Woodstox as StAX implementation (which is recommended anyway). Andreas On Fri, Aug 24, 2012 at 1:39 PM, Jan Swaelens jan.swael...@sofico.be wrote: Hello, I am having an issue on a stub

Re: Bugs with [RAMPART] and [AXIS2] 1.6.2

Yes, you should create a bug report for that. Andreas On Fri, Jul 27, 2012 at 3:02 PM, James Annesley james.annes...@infoshare-is.com wrote: Hi, I upgraded to 1.6.2 today. I encountered a couple of problems. Shall I raise a bug in Jira? Bug: 1) Missing dependency: I had to add

Re: Servlet failed with IOException

What are the steps to reproduce this issue? Andreas On Thu, Jul 26, 2012 at 5:29 PM, chema gomez josemgom...@gmail.com wrote: I'm calling a Web Service build with Java and Axis2 and throws me the following error: org.apache.axis2.AxisFault: The current node has been removed using a method

Re: Servlet failed with IOException

, Jul 26, 2012 at 8:10 PM, chema gomez josemgom...@gmail.com wrote: Well, I'm working on an interface made in jsp and it receives the input parameters of the service, then they are modified to serve as input to the service. But this error only occurs once every few requests 2012/7/26 Andreas

Re: [axis2-1.6.1] ERRORS during undeployment

That's basically a false positive reported by the Tomcat class loader leak prevention system. See https://issues.apache.org/jira/browse/AXIOM-390. If you want to avoid that message, file a bug report to Apache Tomcat. Andreas On Wed, Jul 25, 2012 at 3:05 PM, Stadelmann Josef

Re: JAX-WS client and service with Rampart module for signing messages

You should also read the following document: http://axis.apache.org/axis2/java/core/docs/app_server.html Andreas On Sat, Jun 30, 2012 at 8:05 PM, Megadeth calisto.s...@gmail.com wrote: Hi Amila, At first I think I need to study this:

Re: Help

Either compile the code with Java source level set to 1.4 or replace org.apache.axis.enum with org.apache.axis.constants (if the Axis version is recent enough). Andreas On Sat, Jul 7, 2012 at 3:04 PM, Maria Din maria...@hotmail.fr wrote: Hello, Please, I have this error , import

Re: axistools-maven-plugin - getServiceClient()

The axistools Maven plugin generates stubs for Axis 1.x, but ServiceClient is an Axis2 API. Andreas On Sat, Jul 14, 2012 at 1:17 AM, tamahmed tameem.ah...@gmail.com wrote: I am using axistools version 1.4 maven plugin to generate stubs for my wsdl. I am not able set http headers to my soap

Re: How to get a formatted OMElement content

The StackOverflow question was for DOM. You can use the same approach for Axiom, but instead of a DOMSource, use the SAXSource returned by the following method: http://ws.apache.org/axiom/apidocs/org/apache/axiom/om/OMContainer.html#getSAXSource(boolean) Andreas On Wed, Jul 11, 2012 at 3:53 PM,

Re: [rampart/opensaml] bad artifacts returned causing mvn builds to fail

much Andreas, Are you saying that only the trunks of Rampart or Axis2 will profit from your change? What SVN versions are you recommending to use for a stable Axis2 Rampart build? Josef -Ursprüngliche Nachricht- Von: Andreas Veithen [mailto:andreas.veit...@gmail.com] Gesendet

Re: [axis2-1.6.2] failed to build

Can you please post the content of the following file? modules/transport/http/target/surefire-reports/org.apache.axis2.transport.http.CommonsHTTPTransportSenderTest.txt Andreas On Wed, Jun 27, 2012 at 2:38 PM, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: At work the test below

Re: doc/literal/wrapped soap response with jaxb binding

This is a bug: AXIS2-5147. I fixed that one just yesterday :-) Andreas On Tue, Jun 26, 2012 at 7:20 PM, Chang, Ruey-Juin ruey-juin.ch...@saic.com wrote: Hi, I am using Axis2 1.6.2 with jaxb data binding.  I noticed that the soap response message always returning the request element instead

Re: axis2 mtom attach document to response - help please

to add an attachment to a response in this way. You need to provide a bit more information about exactly what you are attempting to do. On Tue, May 22, 2012 at 3:21 AM, Andreas Veithen andreas.veit...@gmail.com wrote: The answer depends on the elementFormDefault declared on the schema. Andreas

Re: axis2 - file cache for attachments - file name?

The DataSource stored in the DataHandler that represents the attachment is actually a FileDataSource instance and you can get the name of the file from there. However, the fact that Axiom leaks the file name is actually a design flaw and this will no longer be supported in future Axis2/Axiom

Re: Axis2 - JSON mapped - namespace (mismatch)

On Tue, May 1, 2012 at 5:35 PM, Andreas Veithen andreas.veit...@gmail.com wrote: On Mon, Apr 30, 2012 at 20:54, Shameera Rathnayaka shameerai...@gmail.com wrote: Hi Matthias, org.apache.axis2.json.AbstractJSONOMBuilder line 111         /*         Now we have to read the localname and prefix

Re: Axis2 - JSON mapped - namespace (mismatch)

On Mon, Apr 30, 2012 at 20:54, Shameera Rathnayaka shameerai...@gmail.com wrote: Hi Matthias, org.apache.axis2.json.AbstractJSONOMBuilder line 111         /*         Now we have to read the localname and prefix from the input stream         if there is not prefix, message starts like {foo:  

Re: Axis2 - JSON mapped - namespace (mismatch)

On Tue, May 1, 2012 at 5:35 PM, Andreas Veithen andreas.veit...@gmail.com wrote: On Mon, Apr 30, 2012 at 20:54, Shameera Rathnayaka shameerai...@gmail.com wrote: Hi Matthias, org.apache.axis2.json.AbstractJSONOMBuilder line 111         /*         Now we have to read the localname and prefix

Re: Axis2 - JSON mapped - namespace (mismatch)

On Mon, Apr 30, 2012 at 19:53, ger...@slf.ch wrote: Or is it just a resource issue, and someone (may be I) could add some stuff to support namespaces and maybe databinding. Both. As Shameera explained, there is an architectural issue (for mapped JSON). There are also not many people working on

Re: Policy not supported: is it a bug ?

There are actually two things: 1. Neethi 2 (which is used in Axis2 1.5.x and 1.6.0) is much more lenient and parses certain invalid policies without throwing an exception. Neethi 3 (which is used starting with Axis2 1.6.1) no longer accepts those policies and triggers the exception that you are

Re: [axis2-1.6.1] RequestWrapper.partName() not supported on JDK 1.6.0 but used by JAX-WS

That is because the Maven build is set up so that the relevant JARs are endorsed automatically when running the unit tests. Andreas On Tue, Apr 10, 2012 at 10:06, Stadelmann Josef josef.stadelm...@axa-winterthur.ch wrote: Thanks Sagara, I am very happy about your response. Thanks What I do

Re: Handling MTOM attachments in a message receiver

Can you please elaborate on what you mean by this can't be done at message receiver level as MTOM attachments are handled at axiom level.? Andreas On Tue, Mar 27, 2012 at 14:38, Denis Weerasiri ddweeras...@gmail.com wrote: I'm trying to implement a generic message receiver which can

Re: Can't access SOAP header

AxisMessage doesn't represent the current message. Instead it represents a wsdl:message element, i.e. it is part of the service description. To get the SOAP headers from the current message, get the SOAPEnvelope from the MessageContext. Andreas On Mon, Mar 26, 2012 at 16:49,

Re: AW: [Axis2] Axis2 client generated from WSDL ignoring encoding

On Tue, Mar 20, 2012 at 15:25, Francisco Serrano francisco.serr...@multicom.co.uk wrote: Hello Josef, Thanks a lot for your reply. The exact version I'm using is 1.0 and I can confirm that the stub is generated by WSDL2JAVA. The problem is that from my client I'm using the stub to call an

Re: Changing Default Time Zone in CalendarDeserializer?

Assuming that you are using Axis 1.x, you should be able to achieve that by writing your own Serializer/Deserializer and register them using a typeMapping in the WSDD. That should override the default type mapping. Andreas On Wed, Mar 7, 2012 at 23:20, Advitiya Garg a.ga...@gmail.com wrote:

Re: axis2 xml parser issue

Your application contains 3 different XSLT processor implementations: saxon8.jar xalan-2.7.0.jar xalan.jar In that situation, JAXP doesn't select the implementation in a deterministic way. My guess is that the error occurs when JAXP selects Saxon and that your application works on other systems

Re: Axis 1.4 Java:Problem with missing namespace prefix in SOAP Body

Can you post some self-contained sample code that reproduces the issue? Andreas On Thu, Feb 16, 2012 at 05:56, santhosh kotte santhoshko...@yahoo.com wrote: Sorry for the confusion it is Axis 1.4. --- On Wed, 15/2/12, Andreas Veithen andreas.veit...@gmail.com wrote: From: Andreas Veithen

Re: Axis 1.1(Java): Problem with missing namespace prefix in SOAP Body

On Sat, Feb 18, 2012 at 13:04, santhosh kotte santhoshko...@yahoo.com wrote: Hello I am using Axis 1.1 to call a web service. You just said that you are using Axis 1.4. Can you clarify this please? While converting a  org.w3c.dom.Element into a org.apache.axis.message.SOAPBodyElement the

Re: Axis 1.4 Java:Problem with missing namespace prefix in SOAP Body

Are you using Axis 1.4 (as you wrote in the subject) or 1.1 (as you wrote in the body of the mail)? Andreas On Wed, Feb 15, 2012 at 18:39, santhosh kotte santhoshko...@yahoo.com wrote: Hello I am using Axis 1.1 to call a web service. While converting a  org.w3c.dom.Element into a

  1   2   3   >