Re: Axis 1.8.0

[Andreas Veithen-Knowles]

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:
>
> StAXOMBuilder:org.apache.axiom.om.impl.builder.StAXOMBuilder
> Which JAR from the binary download for axis2 1.8.0 include the
> StAXOMBuilder?
>
> When we say "Classes to be moved from axiom-api to om-aspects", where
> om-aspects class are packages? What is the JAR name? Is this related to the
> class not found error for StAXOMBuilder above?
>
> Regards, Amir Razi
>

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

[Andreas Veithen-Knowles]

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
> [DEBUG]com.sun:tools:jar:11.0.2:system
>
> Yet it seems part of the axiom dom-testsuite so not sure why it's a
> dependency in the distributed axiom.
>

In Axiom 1.3.0, axiom-impl and axiom-dom were actually
using aspectj-maven-plugin. In 1.4.0 only dom-testsuite continues to use
AspectJ.

Note that I think this is actually a bug in Gradle. axiom-impl and
axiom-dom are used as dependencies here, and Gradle should not care about
plugins configured in the POMs for those artifacts since they are only used
when building them. I think Maven does this right.


>
>
> I suppose add the equivalent to your gradle config?
>
> 
> com.sun
> tools
> ${java.version}
> system
> ${project.basedir}/pom.xml
> 
>
>
> On Wed, Feb 2, 2022 at 2:22 AM Henrik Strand 
> wrote:
>
>> Hi,
>>
>>
>>
>> Including *axis2-jaxws* as a dependency in the *build.gradle* file
>>
>>
>>
>> *dependencies {*
>>
>> *  implementation 'org.apache.axis2:axis2-jaxws:1.8.0'*
>>
>> *  ...*
>>
>> *}*
>>
>>
>>
>> gives me the following error:
>>
>>
>>
>> *Errors occurred while build effective model from
>> C:\Users\sehenst\.gradle\caches\modules-2\files-2.1\org.apache.ws.commons.axiom\axiom-impl\1.3.0\2f553468b717352b6042a134e28eaf2c4c4d28cf\axiom-impl-1.3.0.pom:*
>>
>> *
>> 'build.plugins.plugin[org.codehaus.mojo:aspectj-maven-plugin].dependencies.dependency.systemPath'
>> for com.sun:tools:jar must specify an absolute path but is
>> ${project.basedir}/pom.xml in org.apache.ws.commons.axiom:axiom-impl:1.3.0*
>>
>> *Errors occurred while build effective model from
>> C:\Users\sehenst\.gradle\caches\modules-2\files-2.1\org.apache.ws.commons.axiom\axiom-dom\1.3.0\ff7124954484b7d4bbc396cfb5eda78dee67ef3f\axiom-dom-1.3.0.pom:*
>>
>> *
>> 'build.plugins.plugin[org.codehaus.mojo:aspectj-maven-plugin].dependencies.dependency.systemPath'
>> for com.sun:tools:jar must specify an absolute path but is
>> ${project.basedir}/pom.xml in org.apache.ws.commons.axiom:axiom-dom:1.3.0*
>>
>>
>>
>> I'm building with Java 11 and it looks like the com.sun:tools:jar file
>> was removed in Java 9.
>>
>>
>>
>> What can I do in order to solve this error?
>>
>>
>>
>> Thanks in advance.
>>
>>
>>
>> /Henrik
>>
>>
>>
>

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

[Andreas Veithen-Knowles]

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. We log the
> soap message at the start of MessageReceiverInOut. With axis2 1.6.2 the
> input string is encoded at that point but with 1.8.0 it's still wrapped in
> a CDATA tag. The web service op ends up with an empty string for the input
> because it's still wrapped in a CDATA tag?
>

That shouldn't be the case. How is the Web service implemented?


> Is there a config to have CDATA tags converted in 1.8.0?
>
> 1.8.0 log:
> 2022-04-20T12:59:10,283 INFO http-nio-8081-exec-5
> org.apache.axis2.receivers.AbstractMessageReceiver - Request:
> http://schemas.xmlsoap.org/soap/envelope/;
> xmlns:urn="urn:intranet:MDS:hcommsf">
>
>
>   
>  
> 
>   
>
> 
>
> 1.6.2 log:
> 2022-04-20 13:01:29,138 INFO  [AbstractMessageReceiver] (41) - Request:
> http://schemas.xmlsoap.org/soap/envelope/;
> xmlns:urn="urn:intranet:MDS:hcommsf">
>   
>  
> ACKNOWLEDGEMENTS>
>   ROUTING_URL>
> http://localhost:8081/axis2/services/hcommsfService?wsdl/ROUTING_URL>
>   MESSAGE_ID>AF880DCF68605199E050D8CCC4203C18/MESSAGE_ID>
>   TRANSACTION_ID>1938378/TRANSACTION_ID>
>   ACK_TYPE>WIPMOVE ACK/ACK_TYPE>
>   ORG_ID>TEST1/ORG_ID>
>   PROJECT_CODE>ABCD|TEST1/PROJECT_CODE>
> ACKNOWLEDGEMENT>
> ORIGINAL_TRANSACTION_ID>1113/ORIGINAL_TRANSACTION_ID>
> DATA>TEST-LM022/DATA>
> STATUS_CODE>4/STATUS_CODE>
> STATUS_DESCRIPTION>PROCESSED OKAY/STATUS_DESCRIPTION>
>   /ACKNOWLEDGEMENT>
> /ACKNOWLEDGEMENTS>
> 
>   
>
>
> Regards
>
> CONFIDENTIALITY
> This e-mail message and any attachments thereto, is intended only for use
> by the addressee(s) named herein and may contain legally privileged and/or
> confidential information. If you are not the intended recipient of this
> e-mail message, you are hereby notified that any dissemination,
> distribution or copying of this e-mail message, and any attachments
> thereto, is strictly prohibited. If you have received this e-mail message
> in error, please immediately notify the sender and permanently delete the
> original and any copies of this email and any prints thereof.
> ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS E-MAIL IS
> NOT INTENDED AS A SUBSTITUTE FOR A WRITING. Notwithstanding the Uniform
> Electronic Transactions Act or the applicability of any other law of
> similar substance and effect, absent an express statement to the contrary
> hereinabove, this e-mail message its contents, and any attachments hereto
> are not intended to represent an offer or acceptance to enter into a
> contract and are not otherwise intended to bind the sender, 42Q (or any of
> its subsidiaries), or any other person or entity.
>

Re: Blank data when customers send CDATA in 1.8.0

[Andreas Veithen-Knowles]

Unfortunately there is no workaround. Could you try running your code with
Axiom 1.3.1-SNAPSHOT to see if there are any other issues? The Maven
repository for those snapshots is https://repository.apache.org/snapshots/.

Andreas

On Sat, Nov 20, 2021 at 2:47 PM joey fedor  wrote:

> Thank 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
>> 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 Fri, Nov 19, 2021 at 5:06 PM joey fedor  wrote:
>>
>>> Hi,
>>>
>>> Ignore this if it is a duplicate, It seemed to be undeliverable on my
>>> other email.
>>>
>>> Recently we updated AXIS2 from version 1.7.9 to version 1.8.0. After
>>> running our server we quickly found some adverse behavior from the update.
>>> Our clients will send a soap envelope to the server with several fields. If
>>> one of these fields is wrapped in a CDATA tag it gets parsed as an empty
>>> string.
>>>
>>>
>>> *For example:*
>>> >> http://schemas.xmlsoap.org/soap/envelope/
>>>   xmlns:web=http://testsite.partner.inbound>
>>> 
>>> 
>>> 
>>>
>>> 
>>> username
>>>
>>> 
>>> password
>>>
>>> 
>>> 
>>>
>>> 
>>> 
>>> 
>>>
>>>
>>> *Code generated using wsdl2java:*
>>> XMLStreamReader parser =
>>> root.getBody().getFirstElement().getXMLStreamReaderWithoutCaching();
>>>
>>> Upload u = Upload.Factory.parse(parser);
>>>
>>> String username = u.getUsername());
>>> String password = u.getPassword());
>>> String data = u.getData());
>>>
>>>
>>>
>>> *our expected results for each variable is:*username =  “username”
>>> password = “password”
>>> data = “TestCdata”
>>>
>>>
>>> *but we are getting the following:*username =  “username”
>>> password = “password”
>>> data = “”
>>>
>>> After some digging this appears to be due to a change in the way that
>>> the newer version of axiom handles preserving Cdata as well as its change
>>> in default coalescing. I have been reading through the axiom userguide with
>>> the recommendation of changing javax.xml.stream.isCoalescing=true (ive
>>> tried false as well), but its seems to have no effect.
>>>
>>> Am I missing something here or is CDATA not something that Axis2 is able
>>> to handle as of 1.8.0 ?
>>>
>>> Thank you,
>>> Joey
>>>
>>

Re: Blank data when customers send CDATA in 1.8.0

[Andreas Veithen-Knowles]

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 Fri, Nov 19, 2021 at 5:06 PM joey fedor  wrote:

> Hi,
>
> Ignore this if it is a duplicate, It seemed to be undeliverable on my
> other email.
>
> Recently we updated AXIS2 from version 1.7.9 to version 1.8.0. After
> running our server we quickly found some adverse behavior from the update.
> Our clients will send a soap envelope to the server with several fields. If
> one of these fields is wrapped in a CDATA tag it gets parsed as an empty
> string.
>
>
> *For example:*
> http://schemas.xmlsoap.org/soap/envelope/
>   xmlns:web=http://testsite.partner.inbound>
> 
> 
> 
>
> 
> username
>
> 
> password
>
> 
> 
>
> 
> 
> 
>
>
> *Code generated using wsdl2java:*
> XMLStreamReader parser =
> root.getBody().getFirstElement().getXMLStreamReaderWithoutCaching();
>
> Upload u = Upload.Factory.parse(parser);
>
> String username = u.getUsername());
> String password = u.getPassword());
> String data = u.getData());
>
>
>
> *our expected results for each variable is:*username =  “username”
> password = “password”
> data = “TestCdata”
>
>
> *but we are getting the following:*username =  “username”
> password = “password”
> data = “”
>
> After some digging this appears to be due to a change in the way that the
> newer version of axiom handles preserving Cdata as well as its change in
> default coalescing. I have been reading through the axiom userguide with
> the recommendation of changing javax.xml.stream.isCoalescing=true (ive
> tried false as well), but its seems to have no effect.
>
> Am I missing something here or is CDATA not something that Axis2 is able
> to handle as of 1.8.0 ?
>
> Thank you,
> Joey
>

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

[Andreas Veithen]

So basically the namespace of the sn attribute is not correct. There had
been a couple of regressions with respect to namespace handling in Axis2
1.7 which were subsequently fixed in patch releases. Can you test this with
1.7.9 (Don't forget to regenerate the code) and if the issue still exists,
create a JIRA ticket with the WSDL and the wsdl2java command line?

Andreas

On Mon, 10 Sep 2018, 17:59 Sterpu Victor,  wrote:

> This is what Axis2 client generates:
> 
> http://www.w3.org/2003/05/soap-envelope;>
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> And this is 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="PK0019AD10873229648"/>
> 
> 
> 
> 
>
> -- Original Message --
> From: "Andreas Veithen" 
> To: "java-user" ; "Sterpu Victor" <
> vic...@caido.ro>
> Sent: 10/9/2018 7:49:29 PM
> Subject: 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 correct in
> the XML send from the client.
>  How can I set the namespace in Axis client?
>
>  Thank you,
>  Victor Sterpu
>
>

Re: Namespace prefix in Axis 2 - 1.7.3

[Andreas Veithen]

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 correct in the XML 
> send from the client.
> How can I set the namespace in Axis client?
>
> Thank you,
> Victor Sterpu

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

On Mon, Aug 6, 2018 at 1:21 PM Martin H  wrote:
>
> Hi Andreas
>
> I don't think so - we have a load balancer (Netscaler) in front of the 
> solution that handles the distribution to the nodes running the application 
> which uses Axis2. But no clustering/load-balancing that Axis2 is aware of. Is 
> there a way to determine for sure if it is enabled/disabled?

I think the way to check that is to look for a  element in axis2.xml.

>
> Assuming we don't use clustering support:
>
> 1) Is it safe to remove those JAR files from the classpath if we don't use 
> clustering support?

Yes.

> 2) Will the files pose a threat if on the classpath even with clustering 
> support disabled?

Unlikely, but better to remove them.

>
> I guess with respect #2 the safest thing to omit the JAR's altogether because 
> some vulns can be triggered 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 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 list.
>> >
>> > We have recently integrated the OWASP Dependency Checker into our 
>> > CI-setup, and it has flagged two libraries as potentially problematic 
>> > (i.e. affected by serious CVE's), namely tribes-6.0.16.jar & 
>> > juli-6.0.16.jar. It turns out those are actually dependencies for Axis2. 
>> > Both JAR files seem to be part of Tomcat 6. Question is, how should we 
>> > react to this finding? Are the CVE's for those libraries not relevant when 
>> > used in the context of Axis2, since they haven't been updated(the latest 
>> > version of Axis2 still ships those versions)?
>> >
>> > Thanks!
>> >
>> > BR, Martin
>> >
>> > ---
>> >
>> > Dependency CPE Coordinates Highest Severity CVE Count↓ CPE Confidence 
>> > Evidence Count
>> >
>> > tribes-6.0.16.jar cpe:/a:apache:tomcat:6.0.16
>> > cpe:/a:apache_software_foundation:tomcat:6.0.16
>> > cpe:/a:apache_tomcat:apache_tomcat:6.0.16 org.apache.tomcat:tribes:6.0.16 
>> > ✓ High 66 Highest 18
>> >
>> >
>> > juli-6.0.16.jar cpe:/a:apache:tomcat:6.0.16
>> > cpe:/a:apache_software_foundation:tomcat:6.0.16
>> > cpe:/a:apache_tomcat:apache_tomcat:6.0.16 org.apache.tomcat:juli:6.0.16 ✓ 
>> > High 66 Highest 16
>> >
>>
>> -
>> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
>> For additional commands, e-mail: java-user-h...@axis.apache.org
>>
>

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 list.
>
> We have recently integrated the OWASP Dependency Checker into our CI-setup, 
> and it has flagged two libraries as potentially problematic (i.e. affected by 
> serious CVE's), namely tribes-6.0.16.jar & juli-6.0.16.jar. It turns out 
> those are actually dependencies for Axis2. Both JAR files seem to be part of 
> Tomcat 6. Question is, how should we react to this finding? Are the CVE's for 
> those libraries not relevant when used in the context of Axis2, since they 
> haven't been updated(the latest version of Axis2 still ships those versions)?
>
> Thanks!
>
> BR, Martin
>
> ---
>
> Dependency CPE Coordinates Highest Severity CVE Count↓ CPE Confidence 
> Evidence Count
>
> tribes-6.0.16.jar cpe:/a:apache:tomcat:6.0.16
> cpe:/a:apache_software_foundation:tomcat:6.0.16
> cpe:/a:apache_tomcat:apache_tomcat:6.0.16 org.apache.tomcat:tribes:6.0.16 ✓ 
> High 66 Highest 18
>
>
> juli-6.0.16.jar cpe:/a:apache:tomcat:6.0.16
> cpe:/a:apache_software_foundation:tomcat:6.0.16
> cpe:/a:apache_tomcat:apache_tomcat:6.0.16 org.apache.tomcat:juli:6.0.16 ✓ 
> High 66 Highest 16
>

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Axis2 Upgrade to latest version

[Andreas Veithen]

On Fri, Dec 8, 2017 at 6:32 AM, akash prasad <akash@gmail.com> wrote:
> Hi,
>
> By debugging i figured out the problem as in latest version there has been
> some new configuration added and those was missing in my component. After
> doing that i am getting the below exception
>
> Caused by: java.lang.ClassCastException:
> org.apache.axis2.saaj.SOAPElementImpl cannot be cast to
> org.apache.axiom.om.impl.dom.NodeImpl
> at org.apache.axiom.om.impl.dom.ParentNode.checkNewChild(ParentNode.java:51)
> ~[axiom-dom-1.2.19.jar:?]
> at org.apache.axiom.om.impl.dom.ParentNode.appendChild(ParentNode.java:39)
> ~[axiom-dom-1.2.19.jar:?]
>
> I can see there has been one ticket raised for this
> (https://issues.apache.org/jira/browse/AXIS2-5770).

AXIS2-5770 will be fixed in the next release. However, that's not the
same error.

>
> Is this really a bug or any change is required to work this.
>
> Thanks in advance.
>
> Regards,
> Akash Prasad.
>
>
> On Thu, Dec 7, 2017 at 12:15 AM, robertlazarski . <robertlazar...@gmail.com>
> wrote:
>>
>>
>>
>> On Wed, Dec 6, 2017 at 11:14 AM, robertlazarski .
>> <robertlazar...@gmail.com> wrote:
>>>
>>>
>>>
>>> On Wed, Dec 6, 2017 at 10:35 AM, robertlazarski .
>>> <robertlazar...@gmail.com> wrote:
>>>>
>>>>
>>>>
>>>> On Wed, 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 
>>>>> other
>>>>> node or so in services.xml file.
>>>>> I have compared with the samples as well. I couldn't find any
>>>>> difference but not sure though.
>>>>>
>>>>> On Wed, Dec 6, 2017 at 7:14 PM, Andreas Veithen
>>>>> <andreas.veit...@gmail.com> wrote:
>>>>>>
>>>>>> My guess is that your Web app still has the JSP files from the old
>>>>>> Axis2 version. That won't work.
>>>>>>
>>>>>> Andreas
>>>>>>
>>>>>> On Wed, Dec 6, 2017 at 12:17 PM, akash prasad <akash@gmail.com>
>>>>>> wrote:
>>>>>> > Hi Team,
>>>>>> >
>>>>>> > Initially my Axis2 server was developed in 1.5.6 and now upgrading
>>>>>> > to the
>>>>>> > latest version. By looking into the release notes upgraded all the
>>>>>> > dependent
>>>>>> > libraries. Now i am facing the error as "Session creation forbidden"
>>>>>> > when i
>>>>>> > try to browse the list of services and also i am getting 500 error
>>>>>> > for the
>>>>>> > other requests, after looking into the source code found that
>>>>>> > "ForbidSessionCreationWrapper " has been included in 1.7.4 version.
>>>>>> > Is there
>>>>>> > any configuration change required to make it compatible my
>>>>>> > application with
>>>>>> > Axis2 latest version.
>>>>>> >
>>>>>> > Even i have made changes to my application as per the changes did
>>>>>> > for
>>>>>> > "Session Fixation"
>>>>>> >
>>>>>> > https://github.com/apache/axis2-java/commit/0959a27a51e844c7381ec1ad8a411861bba09b98
>>>>>> >
>>>>>> > Can you please provide some help with this.
>>>>>> >
>>>>>> > Thanks in advance.
>>>>>> >
>>>>>> > Regards,
>>>>>> > Akash Prasad.
>>>>>>
>>>>>> -
>>>>>> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
>>>>>> For additional commands, e-mail: java-user-h...@axis.apache.org
>>>>>>
>>>>>
>>>>
>>>> You should be able to hit localhost:8080/axis2-web/ or whatever your url
>>>> is, and see the "happy axis2" page.
>>>>
>>>> One quick thing to verify is your axis2.war/axis2-web and
>>>> axis2.war/WEB-INF/include dirs match the supplied dirs in the axis2 distro.
>>>>
>>>> Kind regar

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

[Andreas Veithen]

"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 deleted. Any fix would go into a 1.7.x release or
into 1.8.0, i.e. you would have to upgrade.

Andreas

On Wed, Jul 19, 2017 at 3:42 PM, Robert Seletsky  wrote:
> I have a legacy application that uses Axis2 1.6.2 and wondering if this
> version is still supported?
>
> In any event, I assume best to migrate code to use Axis2 1.7.5?
>
>
> Robert

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Axis2 1.7.4 external dependencies

[Andreas Veithen]

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 does not have this 
> constructor.
>
> Exception in thread "main" java.lang.NoSuchMethodError: 
> org.apache.commons.codec.binary.Base64.(I)V
>at 
> org.apache.http.impl.auth.BasicScheme.authenticate(BasicScheme.java:168)
>at Main.main(Main.java:249)
>
> I can upgrade commons-codec to a later version to eliminate the error. Are 
> there other jars included in Axis2 1.7.4 that must be upgraded for it to be 
> used?

I'm not aware of any other reports about such dependencies.

>
> David
>
>
> Please consider the environment before printing this email and any 
> attachments.
>
>
>
> This e-mail and any attachments are intended only for the individual or 
> company to which it is addressed and may contain information which is 
> privileged, confidential and prohibited from disclosure or unauthorized use 
> under applicable law. If you are not the intended recipient of this e-mail, 
> you are hereby notified that any use, dissemination, or copying of this 
> e-mail or the information contained in this e-mail is strictly prohibited by 
> the sender. If you have received this transmission in error, please return 
> the material received to the sender and delete all copies from your system.
>
> -
> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-user-h...@axis.apache.org
>

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Can Axis2 1.6.2 work in IPv6 env?

[Andreas Veithen]

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 browser.
> But is error when I access the method of webservice on IPv6.
> Error Message：
> javax.xml.ws.WebServiceException: Unsupported endpoint address:
> at 
> com.sun.xml.ws.api.pipe.TransportTubeFactory.createDefault(TransportTubeFactory.java:167)
> at 
> com.sun.xml.ws.api.pipe.TransportTubeFactory.create(TransportTubeFactory.java:157)
> at 
> com.sun.xml.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:135)
> ...

That's not an Axis2 error.

>
> Thanks in advance
>
>

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: [AXIS2] Version 1.2

[Andreas Veithen]

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
>
> -
> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-user-h...@axis.apache.org
>

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

On Thu, Nov 24, 2016 at 8:43 PM, Sterpu Victor <vic...@caido.ro> wrote:
> I followed the answers from the server fo a few days and found that
> sometimes the server sends no Content-Encoding and I still get this error -
> "HTTP :unsupported content-encoding of ''".

I doubt that. If that was the case, then Axis2 would fail in the vast
majority of standard use cases.

> Down there is a header received from the server with this error and without
> Content-Encoding. Why is Axis assuming an empty Content-Encoding when the
> headers contain no Content-Encoding?
> The answer contains a Authorization field that should not be present in the
> server response.
> I don't know why but everytime when I receive "unsupported content-encoding"
> the response header contains a Authorization field,  a OSCP_RESPONSE and a
> lot of other fields that are not in a usual SOAP response.
>
> HTTP/1.1 200 OK
> X-Backside-Transport: OK OK
> Connection: Keep-Alive
> Date: Sun, 20 Nov 2016 13:23:53 GMT
> X-Powered-By: Servlet/3.0
> SOAPAction:
> "core.des.uti.ro/StoreClinicalDocument/storeClinicalDocumentSRequest"
> $WSPR: HTTP/1.1
> User-Agent: Axis2
> x509:
> ***
> Host: ws.des-cnas.ro
> _WS_HAPRT_WLMVERSION: -1
> $WSIS: false
> Surrogate-Capability: WS-ESI="ESI/1.0+"
> Via: 1.1 BwAAAKxf0QA-
> $WSRA: 172.30.8.82
> OSCP_RESPONSE:
> *
> $WSSC: http
> X-Client-IP: 89.43.152.14,89.43.152.14
> serial: *
> $WSRH: 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: text/xml
> Content-Language: en-US
> X-Archived-Client-IP: ***
> Content-Length: 14813
>
> -- 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/2016 7:58:50 PM
> Subject: Re: Re[4]: HTTP :unsupported content-encoding of '' found
>
>> You could submit a patch to Axis2 to ignore empty Content-Encoding
>> headers.
>>
>> Andreas
>>
>> On Sat, Nov 19, 2016 at 5:15 PM, Sterpu Victor <vic...@caido.ro> wrote:
>>>
>>>  I don't control the server, so I need a client side solution.
>>>  Could I set a default content encoding if the server is not 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/2016 7:04:16 PM
>>>  Subject: Re: Re[2]: HTTP :unsupported content-encoding of '' found
>>>
>>>
>>>  According to the HTTP/1.1 specification the Content-Encoding header must
>>>  have the following form:
>>>
>>>  Content-Encoding = "Content-Encoding" ":" 1#content-coding
>>>
>>>  I.e. an empty value is not allowed, so this is a server side problem.
>>>
>>>  Andreas
>>>
>>>
>>>  On Nov 19, 2016 4:30 PM, "Sterpu Victor" <vic...@caido.ro> wrote:
>>>>
>>>>
>>>>  Yes, I traced everything with fiddler.
>>>>  I can now see that "Content-Encoding: " is not defined. If this is the
>>>>  reason can I safely ignore this error?
>>>>  This is the raw header:
>>>>
>>>>  HTTP/1.1 200 OK
>>>>  X-Backside-Transport: OK OK
>>>>  Connection: Keep-Alive
>>>>  Transfer-Encoding: chunked
>>>>  Date: Sat, 19 Nov 2016 16:08:44 GMT
>>>>  X-Powered-By: Servlet/3.0
>>>>  SOAPAction:
>>>>  "core.des.uti.ro/StoreClinicalDocument/storeClinicalDocumentSRequest"
>>>>  $WSPR: HTTP/1.1
>>>>  User-Agent: Axis2
>>>>  x509: 
>>>>  Host: ws.des-cnas.ro
>>>>  _WS_HAPRT_WLMVERSION: -1
>>>>  $WSIS: false
>>>>  Surrogate-Capability: WS-ESI="ESI/1.0+"
>>>>  Via: 1.1 AQAAAEZVhAE-
>>>>  $WSRA: 172.30.8.81
>>>>  OSCP_RES

Re: Axis2 - can I obtain the HTTP client?

[Andreas Veithen]

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 client from the stub class? I want to try to rewrite
> the header before it gets processed as described here:
> https://adamscheller.com/java/httpexception-unsupported-content-coding-none-solution/

Note that this is for httpclient4, but the stacktrace you posted
earlier shows that you are using the httpclient3 based transport
(which is the default in Axis2 1.7.x). You will first need to switch
to the httpclient4 based transport.

I think you can inject an HTTPClient instance into the message
context. Probably the best is to look at the source code of the
httpclient4 transport.

>
> Thank you.

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

You could submit a patch to Axis2 to ignore empty Content-Encoding headers.

Andreas

On Sat, Nov 19, 2016 at 5:15 PM, Sterpu Victor <vic...@caido.ro> wrote:
> I don't control the server, so I need a client side solution.
> Could I set a default content encoding if the server is not 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/2016 7:04:16 PM
> Subject: Re: Re[2]: HTTP :unsupported content-encoding of '' found
>
>
> According to the HTTP/1.1 specification the Content-Encoding header must
> have the following form:
>
> Content-Encoding = "Content-Encoding" ":" 1#content-coding
>
> I.e. an empty value is not allowed, so this is a server side problem.
>
> Andreas
>
>
> On Nov 19, 2016 4:30 PM, "Sterpu Victor" <vic...@caido.ro> wrote:
>>
>> Yes, I traced everything with fiddler.
>> I can now see that "Content-Encoding: " is not defined. If this is the
>> reason can I safely ignore this error?
>> This is the raw header:
>>
>> HTTP/1.1 200 OK
>> X-Backside-Transport: OK OK
>> Connection: Keep-Alive
>> Transfer-Encoding: chunked
>> Date: Sat, 19 Nov 2016 16:08:44 GMT
>> X-Powered-By: Servlet/3.0
>> SOAPAction:
>> "core.des.uti.ro/StoreClinicalDocument/storeClinicalDocumentSRequest"
>> $WSPR: HTTP/1.1
>> User-Agent: Axis2
>> x509: 
>> Host: ws.des-cnas.ro
>> _WS_HAPRT_WLMVERSION: -1
>> $WSIS: false
>> Surrogate-Capability: WS-ESI="ESI/1.0+"
>> Via: 1.1 AQAAAEZVhAE-
>> $WSRA: 172.30.8.81
>> OSCP_RESPONSE: *
>> $WSSC: http
>> X-Client-IP: 
>> serial: **
>> $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/xml
>> Content-Encoding:
>> Content-Language: en-US
>> X-Archived-Client-IP: 
>>
>>
>> -- Original Message --
>> From: "Andreas Veithen" <andreas.veit...@gmail.com>
>> To: "Sterpu Victor" <vic...@caido.ro>; "java-user"
>> <java-user@axis.apache.org>
>> Sent: 19/11/2016 6:04:04 PM
>> Subject: 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" <vic...@caido.ro> 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 client side this error
>>> appears.
>>> How can I fix this? I could catch this exception and consider that the
>>> call is fine, but can I fix it in another way?
>>>
>>> This is the whole stack trace:
>>> Caused by: org.apache.axis2.AxisFault: HTTP :unsupported content-encoding
>>> of '' found
>>>  at
>>> org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl.processResponse(HTTPSenderImpl.java:476)
>>>  at
>>> org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl.handleResponse(HTTPSenderImpl.java:311)
>>>  at
>>> org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl.sendViaPost(HTTPSenderImpl.java:213)
>>>  at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:121)
>>>  at
>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:403)
>>>  at
>>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:234)
>>>  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:431)
>>>  at
>>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:399)
>>>  at
>>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
>>>  at
>>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:150)
>>>  at
>>> stubs.StoreClinicalDocument.client.StoreClinicalDocumentStub.storeClinicalDocumentS(StoreClinicalDocumentStub.java:377)
>>>
>>> In StoreClinicalDocumentStub.java, at the line 377 I have:
>>> "_operationClient.execute(true);"
>>>
>>> Thank you.
>>>
>>>

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

According to the HTTP/1.1 specification the Content-Encoding header must
have the following form:

Content-Encoding = "Content-Encoding" ":" 1#content-coding

I.e. an empty value is not allowed, so this is a server side problem.

Andreas

On Nov 19, 2016 4:30 PM, "Sterpu Victor" <vic...@caido.ro> wrote:

> Yes, I traced everything with fiddler.
> I can now see that "Content-Encoding: " is not defined. If this is the
> reason can I safely ignore this error?
> This is the raw header:
>
> HTTP/1.1 200 OK
> X-Backside-Transport: OK OK
> Connection: Keep-Alive
> Transfer-Encoding: chunked
> Date: Sat, 19 Nov 2016 16:08:44 GMT
> X-Powered-By: Servlet/3.0
> SOAPAction: "core.des.uti.ro/StoreClinicalDocument/
> storeClinicalDocumentSRequest"
> $WSPR: HTTP/1.1
> User-Agent: Axis2
> x509: 
> Host: ws.des-cnas.ro
> _WS_HAPRT_WLMVERSION: -1
> $WSIS: false
> Surrogate-Capability: WS-ESI="ESI/1.0+"
> Via: 1.1 AQAAAEZVhAE-
> $WSRA: 172.30.8.81
> OSCP_RESPONSE: *
> $WSSC: http
> X-Client-IP: 
> serial: **
> $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/xml
> *Content-Encoding:*
> Content-Language: en-US
> X-Archived-Client-IP: 
>
>
> -- Original Message --
> From: "Andreas Veithen" <andreas.veit...@gmail.com>
> To: "Sterpu Victor" <vic...@caido.ro>; "java-user" <
> java-user@axis.apache.org>
> Sent: 19/11/2016 6:04:04 PM
> Subject: 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" <vic...@caido.ro> 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 client side this error
>> appears.
>> How can I fix this? I could catch this exception and consider that the
>> call is fine, but can I fix it in another way?
>>
>> This is the whole stack trace:
>> Caused by: org.apache.axis2.AxisFault: HTTP :unsupported content-encoding
>> of '' found
>>  at org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderI
>> mpl.processResponse(HTTPSenderImpl.java:476)
>>  at org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderI
>> mpl.handleResponse(HTTPSenderImpl.java:311)
>>  at org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderI
>> mpl.sendViaPost(HTTPSenderImpl.java:213)
>>  at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:121)
>>  at org.apache.axis2.transport.http.CommonsHTTPTransportSender.w
>> riteMessageWithCommons(CommonsHTTPTransportSender.java:403)
>>  at org.apache.axis2.transport.http.CommonsHTTPTransportSender.i
>> nvoke(CommonsHTTPTransportSender.java:234)
>>  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:431)
>>  at org.apache.axis2.description.OutInAxisOperationClient.send(O
>> utInAxisOperation.java:399)
>>  at org.apache.axis2.description.OutInAxisOperationClient.execut
>> eImpl(OutInAxisOperation.java:225)
>>  at org.apache.axis2.client.OperationClient.execute(OperationCli
>> ent.java:150)
>>  at stubs.StoreClinicalDocument.client.StoreClinicalDocumentStub
>> .storeClinicalDocumentS(StoreClinicalDocumentStub.java:377)
>>
>> In StoreClinicalDocumentStub.java, at the line 377 I have: "
>> *_operationClient.execute(true);*"
>>
>> Thank you.
>>
>>
>>
>

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

[Andreas Veithen]

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 client side this error
> appears.
> How can I fix this? I could catch this exception and consider that the
> call is fine, but can I fix it in another way?
>
> This is the whole stack trace:
> Caused by: org.apache.axis2.AxisFault: HTTP :unsupported content-encoding
> of '' found
>  at org.apache.axis2.transport.http.impl.httpclient3.HTTPSenderImpl.
> processResponse(HTTPSenderImpl.java:476)
>  at org.apache.axis2.transport.http.impl.httpclient3.
> HTTPSenderImpl.handleResponse(HTTPSenderImpl.java:311)
>  at org.apache.axis2.transport.http.impl.httpclient3.
> HTTPSenderImpl.sendViaPost(HTTPSenderImpl.java:213)
>  at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:121)
>  at org.apache.axis2.transport.http.CommonsHTTPTransportSender.
> writeMessageWithCommons(CommonsHTTPTransportSender.java:403)
>  at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(
> CommonsHTTPTransportSender.java:234)
>  at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:431)
>  at org.apache.axis2.description.OutInAxisOperationClient.send(
> OutInAxisOperation.java:399)
>  at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(
> OutInAxisOperation.java:225)
>  at org.apache.axis2.client.OperationClient.execute(
> OperationClient.java:150)
>  at stubs.StoreClinicalDocument.client.StoreClinicalDocumentStub.
> storeClinicalDocumentS(StoreClinicalDocumentStub.java:377)
>
> In StoreClinicalDocumentStub.java, at the line 377 I have: "
> *_operationClient.execute(true);*"
>
> Thank you.
>
>
>

Re: Re[6]: Raw SOAP XML response

[Andreas Veithen]

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, Martin Gainty  wrote:

> nothing we can do to mitigate if we dont know the status of the Axis2
> Server
>
>
> feel free to pass this information to Axis2 ServerAdmin and have them
> contact us for assistance
>
>
> mulţumesc
>
>
> Martin
> __
>
>
>
>
> --
> *From:* Sterpu Victor 
> *Sent:* Wednesday, November 16, 2016 6:50 AM
> *To:* java-user@axis.apache.org; java-user@axis.apache.org
> *Subject:* Re[6]: Raw SOAP XML response
>
> I don't have a Axis2 server at all, the server is not implemented by me, I
> just want to use a Axis2 client.
> This is why I don't have axis2.xml. :)
>
>
> -- Original Message --
> From: "Martin Gainty" 
> To: "java-user@axis.apache.org" 
> Sent: 16/11/2016 3:07:55 AM
> Subject: Re: Re[4]: Raw SOAP XML response
>
>
>
>
> Martin Gainty
> __
>
>  _ _  _ _  _ ___ _
> _   _ _   _  |_   _| |_ ___   |  _  |___ 
> ___ ___| |_ ___   |   __|___|  _| |_ _ _ _ ___ ___ ___   |   __|___ _ _ ___ 
> _| |___| |_|_|___ ___| | |   | -_|  | | . | .'|  _|   | -_|  |__   | 
> . |  _|  _| | | | .'|  _| -_|  |   __| . | | |   | . | .'|  _| | . |   |   
> |_| |_|_|___|  |__|__|  _|__,|___|_|_|___|  |_|___|_| |_| |_|__,|_| 
> |___|  |__|  |___|___|_|_|___|__,|_| |_|___|_|_||_|
>
>
>
>
> --
> *From:* Martin Gainty 
> *Sent:* Tuesday, November 15, 2016 6:46 AM
> *To:* java-user@axis.apache.org; Sterpu Victor
> *Subject:* Re: Re[4]: Raw SOAP XML response
>
>
> if you dont have axis2.xml in server config do you have annotations
> defined in server code?
>
> http://www.ibm.com/developerworks/library/j-jws8/
> Java Web services: JAXB and JAX-WS in Axis2
> 
> www.ibm.com
> Apache Axis2 supports a range of data-binding technologies, including the
> official Java standard, JAXB 2.x. Axis2 also supports the Java standard for
> Web service configuration, JAX-WS 2.x, as an alternative to its own custom
> configuration technique. Dennis Sosnoski continues his Java Web services
> column series by demonstrating how you can use each of these Java standards
> with Axis2 and discussing some of the limitations of Axis2's current
> support for them.
>
>
>
> do you have a Axis2 Server fully operational.. what does Axis Happiness
> page say?
>
>
> http://localhost:8080/axis2-web/HappyAxis.jsp
>
>
> MG>http://ServerHostName:ServerPortNumber/axis2/axis2-web/HappyAxis.jsp
>
>
> Martin
> __
>
>
>
>
> --
> *From:* Sterpu Victor 
> *Sent:* Monday, November 14, 2016 4:58 PM
> *To:* Martin Gainty; java-user@axis.apache.org
> *Subject:* Re[4]: Raw SOAP XML response
>
> I tired your code but I got a problem. This is what I wrote(I don't have a
> axis2.xml file, I just create the stub with wsdl2java and used the class):
> ConfigurationContext configContext = ConfigurationContextFactory.
> createDefaultConfigurationContext();
> ServiceClient sender = new ServiceClient(configContext, null);
> OperationClient mepClient = sender.createClient(ServiceClient.ANON_OUT_IN_OP);
>
> MessageContext response=mepClient.getMessageContext(
> WSDLConstants.MESSAGE_LABEL_IN_VALUE);
> String response_xml = response.getEnvelope().toString();
>
> These lines are executed immediatly after the succesful SOAP call and I
> receive a java.lang.NullPointerException at the line "String response_xml
> = response.getEnvelope().toString();".
> I traced the SOAP response with Fiddler and the answer is " version="1.0" encoding="UTF-8"?>http://schemas.xmlsoap.org/soap/envelope/;> xmlns:dlwmin="core.des.uti.ro" xmlns:xsi="http://www.w3.org/
> 2001/XMLSchema-instance"> storeClinicalDocumentSResponse>"
>
> Thank you.
>
> -- Original Message --
> From: "Martin Gainty" 
> To: "java-user@axis.apache.org" ; "Sterpu
> Victor" 
> Sent: 2/11/2016 9:28:48 PM
> Subject: Re: Re[2]: Raw SOAP XML response
>
>
>
> --
> *From:* Sterpu Victor 
> *Sent:* Wednesday, November 2, 2016 11:57 AM
> *To:* Martin Gainty; java-user@axis.apache.org
> *Subject:* Re[2]: Raw SOAP XML response
>
> It didn't work.
> This is what I did: I deleted from the directory of Axis2\lib 4 files:
> axiom-jaxb-1.2.19.jar, axiom-api-1.2.19.jar, axiom-dom-1.2.19.jar,
> 

Re: Raw SOAP XML response

[Andreas Veithen]

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 serialized. In the fault case the situation
is different because Axis2 doesn't get to the point where it would
consume (part of) the message.

Andreas

On Wed, Nov 2, 2016 at 1:37 PM, Sterpu Victor  wrote:
> Hello
>
> I need to save the raw SOAP XML response from Axis2(I use axis 2 1.7.3).
> When Axis2 call retusrns an error this code works: String response =
> sc.getLastOperationContext().getMessageContext("In").getEnvelope().toString();
> But when I run a succesful Axis2 call the same code gives the following
> error: "java.lang.IllegalStateException: Can't process next node because
> caching is disabled"
>
> I tryed to enable cache like this, but it didn't work:
>
> ServiceClient sc =
> (ServiceClient)method_getServiceClient.invoke(objectReflect);
> ServiceContext srv_context =
> sc.getServiceContext();
>
> srv_context.setCachingOperationContext(true);
> OperationContext oc= new OperationContext();
> oc.setComplete(true);
> srv_context.setLastOperationContext(oc);
>
> Thank you
>
>

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Exception after upgrading to Axis2 1.7.3

[Andreas Veithen]

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 implemtation from 1.5.6  to
> 1.7.3.
>
> I have worked through all the various library and compilation changes and it
> seems to be compiling and packaging as expected.
>
> However, when I attempt to start the app, I receive the following:
>
>
>> 2016-10-17 20:38:49.688 [localhost-startStop-1] ERROR
>> org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/axis2] null
>> - StandardWrapper.Throwable
>> java.lang.ExceptionInInitializerError
>> at
>> org.apache.axis2.description.AxisDescription.(AxisDescription.java:72)
>> ~[axis2-kernel-1.7.3.jar:1.7.3]
>> at
>> org.apache.axis2.engine.AxisConfiguration.(AxisConfiguration.java:175)
>> ~[axis2-kernel-1.7.3.jar:1.7.3]
>> at
>> org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:627)
>> ~[axis2-kernel-1.7.3.jar:1.7.3]
>> at
>> org.apache.axis2.deployment.WarBasedAxisConfigurator.(WarBasedAxisConfigurator.java:157)
>> ~[axis2-kernel-1.7.3.jar:1.7.3]
>> at
>> org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:620)
>> ~[axis2-transport-http-1.7.3.jar:1.7.3]
>> at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:471)
>> ~[axis2-transport-http-1.7.3.jar:1.7.3]
>> at
>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1183)
>> [catalina.jar:8.5.5]
>> at
>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1099)
>> [catalina.jar:8.5.5]
>> at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:989)
>> [catalina.jar:8.5.5]
>> at
>> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4913)
>> [catalina.jar:8.5.5]
>> at
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5223)
>> [catalina.jar:8.5.5]
>> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
>> [catalina.jar:8.5.5]
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:724)
>> [catalina.jar:8.5.5]
>> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:700)
>> [catalina.jar:8.5.5]
>> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
>> [catalina.jar:8.5.5]
>> at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:952)
>> [catalina.jar:8.5.5]
>> at
>> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1823)
>> [catalina.jar:8.5.5]
>> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
>> [?:1.8.0_102]
>> at java.util.concurrent.FutureTask.run(Unknown Source) [?:1.8.0_102]
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>> [?:1.8.0_102]
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>> [?:1.8.0_102]
>> at java.lang.Thread.run(Unknown Source) [?:1.8.0_102]
>> Caused by: java.lang.NullPointerException
>> at
>> org.apache.crimson.tree.ElementNode.getAttributeNodeNS(ElementNode.java:415)
>> ~[crimson.jar:1.1]
>> at
>> org.apache.crimson.tree.ElementNode.getAttributeNS(ElementNode.java:392)
>> ~[crimson.jar:1.1]
>> at
>> org.apache.axiom.locator.ImplementationFactory.parseImplementation(ImplementationFactory.java:131)
>> ~[axiom-api-1.2.19.jar:1.2.19]
>> at
>> org.apache.axiom.locator.ImplementationFactory.parseDescriptor(ImplementationFactory.java:98)
>> ~[axiom-api-1.2.19.jar:1.2.19]
>> at
>> org.apache.axiom.locator.DefaultOMMetaFactoryLocator.(DefaultOMMetaFactoryLocator.java:87)
>> ~[axiom-api-1.2.19.jar:1.2.19]
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>> ~[?:1.8.0_102]
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
>> ~[?:1.8.0_102]
>> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
>> Source) ~[?:1.8.0_102]
>> at java.lang.reflect.Constructor.newInstance(Unknown Source)
>> ~[?:1.8.0_102]
>> at java.lang.Class.newInstance(Unknown Source) ~[?:1.8.0_102]
>> at
>> org.apache.axiom.om.OMAbstractFactory.(OMAbstractFactory.java:104)
>> ~[axiom-api-1.2.19.jar:1.2.19]
>> ... 22 more
>
>
>
> I'm at a loss at to what is causing this problem.
>
> Can anyone point me to a likely cause of this error?
>
>
> Thanks,
>
>
> Bill

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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:
> http://shibboleth.internet2.edu/downloads/maven2/org/opensaml/openws/1.2.2/openws-1.2.2.pom
>
> Checksum validation failed, expected  374ce7abae3a0f0dc91c5d6370ab40f4a12fadf0 for
> http://shibboleth.internet2.edu/downloads/maven2/org/opensaml/openws/1.2.2/openws-1.2.2.pom
>
> Checksum validation failed, expected  374ce7abae3a0f0dc91c5d6370ab40f4a12fadf0 for
> http://shibboleth.internet2.edu/downloads/maven2/org/opensaml/openws/1.2.2/openws-1.2.2.pom
>
>
>
> What is immediately visible is that this so said pom is in fact a web page.
>
>
>
> I just opened that page in internet explorer and yeas, it is a nice web page
> but certainly not a pom.
>
>
>
> FULLSTOP
>
>
>
> Does someone have the openws-1.2.2.pom file as a pom?
>
>
>
> And I also have the same problems with xalan.jar and jargs.jar (the current
> referenced download points are unusable)
>
> While I could fix, I hope so this two, what can I do with openws-1.2.2.jar
> and pom.
>
>
>
> I fix the jar. At least I believe it. I used RAR to unpack and then repacked
> the directory tree into a RAR file and renamed it to a JAR.
>
> So far it looks promising. Because some of the bugs went away.
>
>
>
> But I can only say that for sure when I have seen the openws-1.2.2.pom
> content.
>
>
>
> You can look into the repository using NetBeans. If you see jar files
> without a + that means something is wrong with them.
>
>
>
> So it should not go like that, but what gets downloaded from this
> shibboleth.internet2.edu is for the foxes
>
>
>
> Downloading:
> http://shibboleth.internet2.edu/downloads/maven2/org/opensaml/openws/1.2.2/openws-1.2.2.pom
>
> Checksum validation failed, expected  374ce7abae3a0f0dc91c5d6370ab40f4a12fadf0 for
> http://shibboleth.internet2.edu/downloads/maven2/org/opensaml/openws/1.2.2/openws-1.2.2.pom
>
> Checksum validation failed, expected  374ce7abae3a0f0dc91c5d6370ab40f4a12fadf0 for
> http://shibboleth.internet2.edu/downloads/maven2/org/opensaml/openws/1.2.2/openws-1.2.2.pom
>
>
>
> Downloaded:
> http://shibboleth.internet2.edu/downloads/maven2/org/opensaml/openws/1.2.2/openws-1.2.2.pom
> (140 KB at 16.2 KB/sec)
>
> The POM for org.opensaml:openws:jar:1.2.2 is invalid, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
>
> The POM for org.apache.xerces:xml-apis:jar:2.9.1 is invalid, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
>
> The POM for org.apache.xerces:xercesImpl:jar:2.9.1 is invalid, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
>
> The POM for org.apache.xerces:resolver:jar:2.9.1 is invalid, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
>
> The POM for org.apache.xerces:serializer:jar:2.9.1 is invalid, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
>
>
>
> --- maven-enforcer-plugin:1.1:enforce (default) @ SpezplaService ---
>
>
>
> --- maven-enforcer-plugin:1.1:display-info (default) @ SpezplaService ---
>
> Maven Version: 3.1-SNAPSHOT
>
> JDK Version: 1.7.0_51 normalized as: 1.7.0-51
>
> OS Info: Arch: amd64 Family: windows Name: windows 7 Version: 6.1
>
>
>
> --- maven-remote-resources-plugin:1.2.1:process (default) @ SpezplaService
> ---
>
> Invalid POM for org.opensaml:openws:jar:1.2.2, transitive dependencies (if
> any) will not be available, enable debug logging for more details
>
> Invalid POM for org.apache.xerces:xml-apis:jar:2.9.1, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
>
> Invalid POM for org.apache.xerces:xercesImpl:jar:2.9.1, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
>
> Invalid POM for org.apache.xerces:resolver:jar:2.9.1, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
>
> Invalid POM for org.apache.xerces:serializer:jar:2.9.1, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
>
>
>
> --- maven-resources-plugin:2.4.3:resources (default-resources) @
> SpezplaService ---
>
> Using 'ISO-8859-1' encoding to copy filtered resources.
>
> Copying 2 resources
>
> Copying 3 resources
>
>
>
> --- maven-compiler-plugin:2.3.2:compile (default-compile) @ SpezplaService
> ---
>
> Compiling 13 source files to
> E:\Users\C770817\SW-PROJEKTE\SpezplaService\target\classes
>
> -
>
> COMPILATION ERROR :
>
> -
>
> error: error reading
> 

Re: Revised: A teething issue with Axis 2

[Andreas Veithen]

According to the WSDL, the parameter name is "args0". That probably
means that you compiled the class without debugging information, in
which case Axis2 doesn't have a way to determine the correct parameter
name.

Andreas

On Tue, Aug 2, 2016 at 4:11 PM, Rupinder Singh <rupi@gmail.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)?
>>
>> Andreas
>>
>> On Sun, Jul 24, 2016 at 6:00 AM, Rupinder Singh <rupi@gmail.com>
>> wrote:
>> > Hello
>> >
>> > I have just recently started with Web Services. I started by exposing
>> > POJO
>> > in Axis2 deployed in Tomcat. When I run
>> > http://localhost:8080/axis2/services/HelloWorld/sayHello?name="Axis2; in
>> > browser.
>> >
>> >
>> > Hello null
>> >
>> > NOT Hello Axis2 !
>> >
>> > could you help?
>> >
>> >
>> > regards
>> > Rupinder Pal Singh
>>
>> -
>> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
>> For additional commands, e-mail: java-user-h...@axis.apache.org
>>
>
>
>
> -
> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-user-h...@axis.apache.org

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Revised: A teething issue with Axis 2

[Andreas Veithen]

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 deployed in Tomcat. When I run
> http://localhost:8080/axis2/services/HelloWorld/sayHello?name="Axis2; in
> browser.
>
>
> Hello null
>
> NOT Hello Axis2 !
>
> could you help?
>
>
> regards
> Rupinder Pal Singh

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Axis2 embeded https server

[Andreas Veithen]

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 and I
> don't know how to activate https from code.
> Server starts from code on http and works fine.
> This is my code:
>
> public static void test() {
> try {
> ConfigurationContext configContext =
> ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
> null);
>
> SimpleHTTPServer server = new SimpleHTTPServer(configContext,
> 8080);
> server.start();
>
> File serviceArchiveFile = new
> File("C:\\Users\\victor\\Documents\\NetBeansProjects\\sr010\\jar\\axis2-1.7.3\\repository\\services\\StockQuoteService.aar");
> AxisServiceGroup serviceGroup =
> DeploymentEngine.loadServiceGroup(serviceArchiveFile, configContext);
>
> AxisConfiguration axiConfiguration =
> configContext.getAxisConfiguration();
> axiConfiguration.addServiceGroup(serviceGroup);
> } catch(Exception ex) {
>
> Logger.getLogger(Axis2ServerTest.class.getName()).log(Level.SEVERE, null,
> ex);
> }
> }
>
> I read the documentation here:
>
> "Please note that by default HTTPS works only when the server does not
> expect to authenticate the clients (1-way SSL only) and where the server has
> the clients' public keys in its trust store. If you want to perform SSL
> client authentication (2-way SSL), you may use the Protocol.registerProtocol
> feature of HttpClient. You can overwrite the "https" protocol, or use a
> different protocol for your SSL client authentication communications if you
> don't want to mess with regular https. Find more information at
> http://jakarta.apache.org/commons/httpclient/sslguide.html;
>
>
>
>
> But I don't know how how to set 1 way HTTPS yet.
>
> Thank you.

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 project hosted
> by Apache
>
> Glad I could help
>
> Thanks Ianabe!
>
> Martin Gainty
> __
> Member
>
>  _ _  _ _  _ ___ _
> _   _ _   _
> |_   _| |_ ___   |  _  |___ ___ ___| |_ ___   |   __|___|  _| |_ _ _ _ ___
> ___ ___   |   __|___ _ _ ___ _| |___| |_|_|___ ___
>   | | |   | -_|  | | . | .'|  _|   | -_|  |__   | . |  _|  _| | | | .'|
> _| -_|  |   __| . | | |   | . | .'|  _| | . |   |
>   |_| |_|_|___|  |__|__|  _|__,|___|_|_|___|  |_|___|_| |_|
> |_|__,|_| |___|  |__|  |___|___|_|_|___|__,|_| |_|___|_|_|
>|_|
>
>
>
>
> 
> From: lanabe.lan...@gmail.com
> Date: Sun, 19 Jun 2016 08:43:23 +
>
> Subject: Re: Can't use JAX-WS + SOAP 1.2 ?
> To: java-user@axis.apache.org
>
> Martin, Thank you for your confirmation.
>
>> file a jira bug to replace hardcoded SOAP11HTTP_BINDING in the Providers
>> and with parameterised Binding
> Done!
> https://issues.apache.org/jira/browse/AXIS2-5790
>
> On Fri, Jun 17, 2016 at 10:44 PM Martin Gainty  wrote:
>
> MG2>quick comments
>
> 
> From: lanabe.lan...@gmail.com
> Date: Fri, 17 Jun 2016 05:45:21 +
>
> Subject: Re: Can't use JAX-WS + SOAP 1.2 ?
> To: java-user@axis.apache.org
>
> Martin, thanks a lot!
>
> You mean I must use pojo + services.xml for Web seivices like a
> quickstart[1]?
> MG2>for reliable HTTPBinding to SOAP1.2 use the programmatic approach below
> to bind HTTP to SOAP1.2
>
> In my example[2], my service classes use only JAX-WS annotations like
> java_first_jaxws example[3].
>
> And in my understanding, it seems this issue is caused from hard-corded with
> SOAP 1.1 binding.
> MG2>with some of the providers unfortunately yes
>
> In my example case, you should get a wsdl generated by axis2 runtime if you
> access
> 'http://localhost:8080/axis2-jaxws-soap12-demo-server/services/HelloWorldSoap12?wsdl'.
>
> Axis2 uses wsgen(included JDK) to generate the requested wsdl.
> https://github.com/apache/axis2-java/blob/v1.7.3/modules/metadata/src/org/apache/axis2/jaxws/description/builder/JAXWSRIWSDLGenerator.java#L183-L184
>
> and, however, initialize() set binding as SOAP 1.1 regardless of the service
> classess binding annotation.
> https://github.com/apache/axis2-java/blob/v1.7.3/modules/metadata/src/org/apache/axis2/jaxws/description/builder/JAXWSRIWSDLGenerator.java#L389
>
> so, wsgen arguments will set for SOAP 1.1.
> https://github.com/apache/axis2-java/blob/v1.7.3/modules/metadata/src/org/apache/axis2/jaxws/description/builder/JAXWSRIWSDLGenerator.java#L208-L215
>
> You must set extra arguments like extension, wsdl:Xsoap1.2 If you want to
> use wsgen for SOAP 1.2. so, wsgen will complain about it.
> https://github.com/emag/axis2-jaxws-soap12-demo#error-log
>
> MG2>annotations can tweak targetNamespace,serviceName,wsdlLocation and
> PortName from SOAP12EchoImpl.java:
>
> @javax.xml.ws.WebServiceProvider(targetNamespace="http://jaxws.axis2.apache.org/proxy/soap12;,
> serviceName="SOAP12EchoService",
> wsdlLocation="META-INF/SOAP12Echo.wsdl",
> portName="EchoPort")
> @javax.xml.ws.BindingType(SOAPBinding.SOAP12HTTP_BINDING)
> @javax.xml.ws.ServiceMode(Mode.MESSAGE)
> public class SOAP12EchoImpl implements javax.xml.ws.Provider {
>
> MG2>Note: you must implement javax.xml.ws.Provider
>
> Can I change this behavior? Thanks.
>
> MG2>all Axis2 functionality routes to axis2  Impl class that *must*
> implement Provider
> MG2>*some* of the providers do have hardcoded SOAP11HTTP_BINDING e.g.
>
>>grep -S "HTTP11_BINDING" *Provider.java
> .\addressing\AddressingProvider.java:@BindingType(SOAPBinding.SOAP11HTTP_BINDING)
>
> .\jaxb\JAXBProvider.java:@BindingType(SOAPBinding.SOAP11HTTP_BINDING)
>
> .\soapmsg\SoapMessageProvider.java:@BindingType(SOAPBinding.SOAP11HTTP_BINDING)
>
> .\soapmsgcheckmtom\SoapMessageCheckMTOMProvider.java:@BindingType(SOAPBinding.SOAP11HTTP_BINDING)
>
> .\soapmsgmu\SoapMessageMUProvider.java:@BindingType(SOAPBinding.SOAP11HTTP_BINDING)
>
> .\soapmsgreturnnull\SoapMessageNullProvider.java:@BindingType(SOAPBinding.SOAP11HTTP_BINDING)
>
> .\sourcemsg\SourceMessageProvider.java:@BindingType(SOAPBinding.SOAP11HTTP_BINDING)
>
> .\string\StringProvider.java:@BindingType(SOAPBinding.SOAP11HTTP_BINDING)
>
> .\stringmsg\StringMessageProvider.java:@BindingType(SOAPBinding.SOAP11HTTP_BINDING)
>
> MG2>file a jira bug to replace hardcoded SOAP11HTTP_BINDING in the Providers
> and with parameterised Binding
>
> 

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

[Andreas Veithen]

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 Axis2
> org.apache.axis2.deployment.DeploymentException: Service [EchoService3] is
> trying expose in tranpsorts: 
> https
>  and which is/are not available in Axis2
>
> ?
>

That's not a build failure but the expected outcome of the test.


> MG> if I disable tests a clean jar is produced ..ready for deploy and
> install
>
> axis2-1.8/modules/kernel>mvn -e -X -DskipTests=true package
>
> ./target/axis2-1.8-SNAPSHOT.jar is produced
>
> MG>attaching pom.xml
> Martin
> __
>
>
>
> --
> From: andreas.veit...@gmail.com
> Date: Tue, 29 Mar 2016 18:59:56 +0100
> Subject: Re: Building with mvn install -Dmaven.test.skip=true failes
> To: java-user@axis.apache.org
>
>
> 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.
>
>
>
> I tried to rebuild to see the fix working and, indeed, as I expected it
> from the axis developers
>
> that JAVA WSDL builds now perfect.  Thanks,
>
>
>
> However, now I get another build abort a few modules down, which I report
> here, ready to file
>
> a JIRA if needed. I just did a  mvn install –Dmaven.test.skip=true
>
> to the trunk and it fails
>
>
>
> Josef
>
>
>
> [INFO]
>
> [INFO]
> 
>
> [INFO] Building Apache Axis2 - JAXWS 1.8.0-SNAPSHOT
>
> [INFO]
> 
>
> [INFO]
>
> [INFO] --- maven-enforcer-plugin:1.1:enforce (default) @ axis2-jaxws ---
>
> [INFO]
>
> [INFO] --- alta-maven-plugin:0.4:generate-properties (default) @
> axis2-jaxws ---
>
> [INFO]
>
> [INFO] --- maven-remote-resources-plugin:1.5:process (default) @
> axis2-jaxws ---
>
> [INFO]
>
> [INFO] --- maven-resources-plugin:2.4.2:resources (default-resources) @
> axis2-jaxws ---
>
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>
> [INFO] skip non existing resourceDirectory
> E:\asf\axis\axis2\java\core\trunk\modules\jaxws\conf
>
> [INFO] Copying 0 resource
>
> [INFO] Copying 1 resource
>
> [INFO] Copying 2 resources
>
> [INFO]
>
> [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @
> axis2-jaxws ---
>
> [INFO] Nothing to compile - all classes are up to date
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-echo) @ axis2-jaxws ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-stock1) @ axis2-jaxws ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-stock2) @ axis2-jaxws ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-samplemtom) @ axis2-jaxws
> ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-ProxyDocLitWrapped) @
> axis2-jaxws ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-AddNumbers) @ axis2-jaxws
> ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- axis2-repo-maven-plugin:1.8.0-SNAPSHOT:create-test-repository
> (default) @ axis2-jaxws ---
>
> [INFO] Tests 

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

[Andreas Veithen]

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.
>
>
>
> I tried to rebuild to see the fix working and, indeed, as I expected it
> from the axis developers
>
> that JAVA WSDL builds now perfect.  Thanks,
>
>
>
> However, now I get another build abort a few modules down, which I report
> here, ready to file
>
> a JIRA if needed. I just did a  mvn install –Dmaven.test.skip=true
>
> to the trunk and it fails
>
>
>
> Josef
>
>
>
> [INFO]
>
> [INFO]
> 
>
> [INFO] Building Apache Axis2 - JAXWS 1.8.0-SNAPSHOT
>
> [INFO]
> 
>
> [INFO]
>
> [INFO] --- maven-enforcer-plugin:1.1:enforce (default) @ axis2-jaxws ---
>
> [INFO]
>
> [INFO] --- alta-maven-plugin:0.4:generate-properties (default) @
> axis2-jaxws ---
>
> [INFO]
>
> [INFO] --- maven-remote-resources-plugin:1.5:process (default) @
> axis2-jaxws ---
>
> [INFO]
>
> [INFO] --- maven-resources-plugin:2.4.2:resources (default-resources) @
> axis2-jaxws ---
>
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>
> [INFO] skip non existing resourceDirectory
> E:\asf\axis\axis2\java\core\trunk\modules\jaxws\conf
>
> [INFO] Copying 0 resource
>
> [INFO] Copying 1 resource
>
> [INFO] Copying 2 resources
>
> [INFO]
>
> [INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @
> axis2-jaxws ---
>
> [INFO] Nothing to compile - all classes are up to date
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-echo) @ axis2-jaxws ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-stock1) @ axis2-jaxws ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-stock2) @ axis2-jaxws ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-samplemtom) @ axis2-jaxws
> ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-ProxyDocLitWrapped) @
> axis2-jaxws ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- jaxb2-maven-plugin:2.2:testXjc (xjc-AddNumbers) @ axis2-jaxws
> ---
>
> [INFO] Ignored given or default testXjbSources
> [E:\asf\axis\axis2\java\core\trunk\modules\jaxws\src\test\xjb], since it is
> not an existent file or directory.
>
> [INFO] No changes detected in schema or binding files - skipping JAXB
> generation.
>
> [INFO]
>
> [INFO] --- axis2-repo-maven-plugin:1.8.0-SNAPSHOT:create-test-repository
> (default) @ axis2-jaxws ---
>
> [INFO] Tests are skipped
>
> [INFO]
>
> [INFO] --- maven-resources-plugin:2.4.2:testResources
> (default-testResources) @ axis2-jaxws ---
>
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
>
> [INFO] Copying 7 resources
>
> [INFO] Copying 61 resources
>
> [INFO] Copying 2 resources
>
> [INFO]
>
> [INFO] --- maven-compiler-plugin:2.3.1:testCompile (default-testCompile) @
> axis2-jaxws ---
>
> [INFO] Not compiling test sources
>
> [INFO]
>
> [INFO] --- maven-antrun-plugin:1.2:run (build-repo) @ axis2-jaxws ---
>
> [INFO] Executing tasks
>
> [INFO] Executed tasks
>
> [INFO]
>
> [INFO] --- maven-surefire-plugin:2.13:test (default-test) @ axis2-jaxws ---
>
> [INFO] Tests are skipped.
>
> [INFO]
>
> [INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ axis2-jaxws ---
>
> [INFO] Building jar:
> E:\asf\axis\axis2\java\core\trunk\modules\jaxws\target\axis2-jaxws-1.8.0-SNAPSHOT.jar
>
> [INFO]
>
> [INFO] --- maven-source-plugin:2.4:jar-no-fork (source-jars) @ axis2-jaxws
> ---
>
> [INFO] Building jar:
> 

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

[Andreas Veithen]

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 as I started to not run all the tests
> as they seldom where running and where too often the cause for a abort of
> the build.
>
> Now even with –Dmaven.test.skip=true it failed. The reason is a missing
> file which is not generated if tests are skipped.
>
>
>
> 
>
> maven-antrun-plugin
>
> 
>
> 
>
> 
>
> run
>
> 
>
> test
>
> 
>
> 
>
> 
>
>
>
>  classname="org.apache.ws.java2wsdl.Java2WSDL"
> classpathref="maven.test.classpath" fork="true" failonerror="true">
>
> 
>
>  value="${project.build.directory}/java2wsdl" />
>
> 
>
> 
>
> 
>
>  value="org.apache.axis2.description.CalculatorService" />
>
> 
>
>  value="[org.apache.axis2.description,http://www.example.org/calculator];
> />
>
> 
>
> http://www.example.org/calculator-service; />
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
>
>
> The file p2n.wsdl is missing as it will be not generated if
> -Dmaven.test.skip=true is selected.
>
> Why is that file not generated when I just intend to not have tests?
>
>
>
> Josef
>
>
>
>
>
> [INFO] BUILD FAILURE
>
> [INFO]
> 
>
> [INFO] Total time: 6.552s
>
> [INFO] Finished at: Mon Mar 21 10:00:45 CET 2016
>
> [INFO] Final Memory: 46M/911M
>
> [INFO]
> 
>
> [ERROR] Failed to execute goal
> org.codehaus.gmavenplus:gmavenplus-plugin:1.5:execute (default) on project
> axis2-java2wsdl: Error occurred while calling a method on a Groovy class
> from classp
>
> ath. InvocationTargetException:
> E:\asf\axis\axis2\java\core\trunk\modules\java2wsdl\target\java2wsdl\p2n.wsdl
> (The system cannot find the path specified) -> [Help 1]
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.codehaus.gmavenplus:gmavenplus-plugin:1.5:execute (default) on
> project axis2-java2wsdl: Error occurred whil
>
> e calling a method on a Groovy class from classpath.
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:310)
>
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:146)
>
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:534)
>
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:211)
>
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:156)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:606)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error occurred
> while calling a method on a Groovy class from classpath.
>
> at
> 

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

[Andreas Veithen]

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, all attributes are
> treated as fixed attributes. This means, when setting the value on a
> non-fixed attribute, it set be seen as null (but set) and causing an
> exception.
>
> I've attached a simplified WSDL, the generate java files, one with the
> fixed value in place, and one without, and also a diff showing the issue
> (the missing line with "this.localPersonId = param;").
>
> I've looked in the ADB Codegen code, and IMHO the issue seems to be in
> SchemaCompiler where the code says:
>
> // register the fixed value if present
> if (xsElt.getFixedValue() != null) {
> metainf.registerDefaultValue(xsElt.getQName(),
> xsElt.getFixedValue());
> metainf.setFixed(true);
> }
>
> The setFixed seems to be too broad, and maybe it can be changed into
> something following the registerNillableQName-flow, e.g.
> registerFixedQName(xsElt.getQName()).
>
> Just to test, I've also tried version 1.7.0 and 1.6.4, there the same
> issue exists.
>
> Hope this make sense.
>
> Regards,
> Frederik Hansen
>
>
> -
> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-user-h...@axis.apache.org
>

Re: WSsecurity: SignatureMethod error

[Andreas Veithen]

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 
wrote:

> Martin, read the thread again. Did you read the first mail?
>
> I specified the problem in the first mail (including the versions). I was
> asking for help, I was not posting a bug (I didn't know it could be a bug).
>
> Your answers were confusing. I had to tell you that I wanted to use
> rsa-sha1 signatures for *three times*.
>
> Denigrating tone? You said my question is no-op. I've been quite polite so
> far.
>
> Just a suggestion: if you want to help, please try to read and understand
> the questions. Otherwise, it's just empty bragging.
>
> Thanks for your time (again).
> Regards.
>
>
>
>
>
> On Sat, Mar 12, 2016 at 2:16 AM, Martin Gainty 
> wrote:
>
>>
>>
>> On Fri, Mar 11, 2016 at 3:55 PM, Enrique Soriano <
>> enrique.sori...@gmail.com> wrote:
>>
>> Hi Martin, I really appreciate your efforts to help me, but I think you
>> didn’t understand the problem.
>>
>> The client stubs generated by Axis2 1.7.1 were sending rsa-sha256
>> signatures, this is a fact.
>>
>> MG>faux pas as you should be posting version specific bugs at
>> https://issues.apache.org/jira/browse/AXIS2
>> MG>for your edification dont use this email list for one off version
>> specific possible bugs
>> MG>this is for versions that have already been released not for issues on
>> new (unreleased) versions are addressed here
>> MG>nobody could track the version you were implementing as you were
>> always assuming we knew
>> MG>In the future watch your denigrating tone, dont assume we know what
>> version you are using
>> MF>obey the rules and you should be ok if not you be will ignored
>> MG>adios
>>
>> The server I need to use requires rsa-sha1 signatures, this is a fact.
>>
>> The client stubs generated by Axis2 1.6.4 are sending rsa-sha1
>> signatures, this is a fact.
>>
>> The client and the server can *now* verify the request/responses, this is
>> a fact.
>>
>> My question was not a no-op.
>>
>>
>> Thanks again.
>> Regards.
>>
>> On Fri, Mar 11, 2016 at 1:56 PM, Martin Gainty 
>> wrote:
>>
>> for my understanding and to be clear
>>
>> 1)you are not implementing rsa-sha256 on Initiator or recipient so the
>> rsa-sha256 question is a no-op
>>
>> 2)you are not implementing EncryptedKeySHA1  which is for
>> encryption/decryption only
>>
>> 3)if the web-service is implementing rsa-sha1
>> Martin Gainty
>> __
>>
>>  _ _  _ _  _ ___ _   
>>  _   _ _   _
>> |_   _| |_ ___   |  _  |___ ___ ___| |_ ___   |   __|___|  _| |_ _ _ _ ___ 
>> ___ ___   |   __|___ _ _ ___ _| |___| |_|_|___ ___
>>   | | |   | -_|  | | . | .'|  _|   | -_|  |__   | . |  _|  _| | | | .'|  
>> _| -_|  |   __| . | | |   | . | .'|  _| | . |   |
>>   |_| |_|_|___|  |__|__|  _|__,|___|_|_|___|  |_|___|_| |_| 
>> |_|__,|_| |___|  |__|  |___|___|_|_|___|__,|_| |_|___|_|_|
>>|_|
>>
>>
>>
>>
>> > Date: Thu, 10 Mar 2016 15:57:11 +0100
>> > Subject: Re: WSsecurity: SignatureMethod error
>> > From: enrique.sori...@gmail.com
>> > To: java-user@axis.apache.org
>> >
>> > Hi Martin, thanks for your response (again).
>> >
>> > I've solved the problem by downgrading to axis2-1.6.4. Now the client
>> > stubs generated by wsdl2java work ok.
>> >
>> > Maybe it's just a bug in Axis2 2-1.7.1 (??).
>> >
>> > >> how would client signing with rsa-sha1 algorithm be able to
>> communicate with any webservice expecting rsa-sha256 signature?
>> >
>> > This web service expects a rsa-sha1, as I said in previous messages.
>> >
>> > According to [1] and [2], WS SecurityPolicy specifies that rsa-sha1
>> > must be the signature algorithm. I'm not familiar with WS Security
>> > anyway.
>> >
>> > Regards.
>> > Enrique
>> >
>> > Refs:
>> >
>> > [1]
>> https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.0/html/Web_Services_Security_Guide/files/MsgProtect-SOAP-SpecifyAlgorithmSuite.html
>> MG>this is what Fuse supports..one work around is to implement with
>> Apache ESB which supports OASIS spec
>> MG>speaking of which ..lets reference the OASIS spec on Asymmetric
>> Binding to make sure we are on the same page
>> MG>if for no other reason than 99% of Financial Institutions only
>> implement X509 tokens..so if your implementation
>> MG>does not support X509 you wont be able to implement in majority of
>> financial institutions
>> MG>below is a verbatim parroting of OASIS spec:
>>
>> C.3.1 Policy
>>
>> The following example shows a policy indicating an Asymmetric Binding,
>> an X509 token as the [Initiator Token],
>> an X509 token as the [Recipient Token],
>> an algorithm suite, a 

Re: WSsecurity: SignatureMethod error

[Andreas Veithen]

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 Martin, I really appreciate your efforts to help me, but I think you
> didn’t understand the problem.
>
> The client stubs generated by Axis2 1.7.1 were sending rsa-sha256
> signatures, this is a fact.
>
> The server I need to use requires rsa-sha1 signatures, this is a fact.
>
> The client stubs generated by Axis2 1.6.4 are sending rsa-sha1 signatures,
> this is a fact.
>
> The client and the server can *now* verify the request/responses, this is
> a fact.
>
> My question was not a no-op.
>
>
> Thanks again.
> Regards.
>
> On Fri, Mar 11, 2016 at 1:56 PM, Martin Gainty 
> wrote:
>
>> for my understanding and to be clear
>>
>> 1)you are not implementing rsa-sha256 on Initiator or recipient so the
>> rsa-sha256 question is a no-op
>>
>> 2)you are not implementing EncryptedKeySHA1  which is for
>> encryption/decryption only
>>
>> 3)if the web-service is implementing rsa-sha1
>> Martin Gainty
>> __
>>
>>  _ _  _ _  _ ___ _   
>>  _   _ _   _
>> |_   _| |_ ___   |  _  |___ ___ ___| |_ ___   |   __|___|  _| |_ _ _ _ ___ 
>> ___ ___   |   __|___ _ _ ___ _| |___| |_|_|___ ___
>>   | | |   | -_|  | | . | .'|  _|   | -_|  |__   | . |  _|  _| | | | .'|  
>> _| -_|  |   __| . | | |   | . | .'|  _| | . |   |
>>   |_| |_|_|___|  |__|__|  _|__,|___|_|_|___|  |_|___|_| |_| 
>> |_|__,|_| |___|  |__|  |___|___|_|_|___|__,|_| |_|___|_|_|
>>|_|
>>
>>
>>
>>
>> > Date: Thu, 10 Mar 2016 15:57:11 +0100
>> > Subject: Re: WSsecurity: SignatureMethod error
>> > From: enrique.sori...@gmail.com
>> > To: java-user@axis.apache.org
>> >
>> > Hi Martin, thanks for your response (again).
>> >
>> > I've solved the problem by downgrading to axis2-1.6.4. Now the client
>> > stubs generated by wsdl2java work ok.
>> >
>> > Maybe it's just a bug in Axis2 2-1.7.1 (??).
>> >
>> > >> how would client signing with rsa-sha1 algorithm be able to
>> communicate with any webservice expecting rsa-sha256 signature?
>> >
>> > This web service expects a rsa-sha1, as I said in previous messages.
>> >
>> > According to [1] and [2], WS SecurityPolicy specifies that rsa-sha1
>> > must be the signature algorithm. I'm not familiar with WS Security
>> > anyway.
>> >
>> > Regards.
>> > Enrique
>> >
>> > Refs:
>> >
>> > [1]
>> https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.0/html/Web_Services_Security_Guide/files/MsgProtect-SOAP-SpecifyAlgorithmSuite.html
>> MG>this is what Fuse supports..one work around is to implement with
>> Apache ESB which supports OASIS spec
>> MG>speaking of which ..lets reference the OASIS spec on Asymmetric
>> Binding to make sure we are on the same page
>> MG>if for no other reason than 99% of Financial Institutions only
>> implement X509 tokens..so if your implementation
>> MG>does not support X509 you wont be able to implement in majority of
>> financial institutions
>> MG>below is a verbatim parroting of OASIS spec:
>>
>> C.3.1 Policy
>>
>> The following example shows a policy indicating an Asymmetric Binding,
>> an X509 token as the [Initiator Token],
>> an X509 token as the [Recipient Token],
>> an algorithm suite, a requirement to encrypt the message parts before
>> signing,
>> a requirement to encrypt the message signature,
>> a requirement to include tokens in the message signature and the
>> supporting signatures,
>> a requirement to include wsse11:SignatureConfirmation elements,
>> a username token attached to the message, and finally an X509 token
>> attached to the message and endorsing the message signature.
>> Minimum message protection requirements are described as well.
>>
>> 
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>>  
>>  
>>
>>  
>>
>>  
>>  
>>
>>  
>>
>>  
>>  
>> 
>>   
>> 
>>  
>>  
>>  
>>  
>>  
>>
>>   
>>   
>> 
>>   
>> 
>>   
>>   
>> 
>>   
>>
>> 
>>
>>   
>>
>> 
>>
>>   
>> 
>>   
>>   
>> 
>>   
>> 
>>   
>> 
>>
>>
>>
>> 
>> 
>>   
>> 
>> 
>> 
>>   
>>   
>> 
>> 
>>   
>> 
>>
>>
>> MG>by Jboss Fuse doc the Algorithm Suite sp:Basic256 for signature
>> encryption is wrong?
>>  
>>
>>  
>>
>>  
>> MG>Jboss Fuse requirements states there is no algorithm other than
>> dsa-rsa1 supported?
>> MG>but OASIS standards DO support encryption of SIGNATURES with
>> sp:Basic256
>> MG>is OASIS incorrect?
>>
>> > [2] http://cxf.apache.org/docs/ws-securitypolicy.html
>> 

Re: Axis 1.7.0 & WS-ReliableMessaging

[Andreas Veithen]

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 Axis2 even mention Sandesha2 and
> its current state regarding the Axis2 release.
>
> Nevertheless the Axis homepage still claims that such a module is under
> development (along with a invalid link for Kandula2 module) and Sandesha2 is
> listed as available in extension modules (and also mentioned in the list of
> add-ons).

These pages will be updated when Axis2 1.7.1 is released.

> So, does Axis2 officially no longer support RM at all or is there an
> alternative available in the Axis2 ecosystem?
>
> Cheers,
> Jörg
>
>
> -
> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-user-h...@axis.apache.org
>

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Problem with Axis2 1.7.0

[Andreas Veithen]

That wizard is maintained by the Eclipse project. I suspect that they
construct the class loader that they use to load the Axis2 tooling in
a way that makes it incompatible across different major Axis2
releases. You should probably file a bug with them.

That being said, the wizard is fine to experiment and play around, but
it should not be part of your development process. Instead, all
generated code should be produced during your build process, i.e. you
should use the Maven plugins or the Ant task.

Andreas

On Tue, Feb 2, 2016 at 12:37 PM, M. Arif Wicaksana
<a...@belalangtempur.com> wrote:
> Hi Andreas,
>
> I attach the trace together with this email.
>
> I am not sure what tool is used by Eclipse for code generation. But I think
> it might be Ant.
>
> My steps:
> I use Eclipse (Luna R2), Tomcat 8, and Axis2 1.7.0
> I create new dynamic web project.
> I put my WSDL in the project (attached in my previous email).
> I use 'new > web services > web service' wizard:
> - 'Top down Java bean web service' is selected
> - my WSDL file is referred as the service definition
> - Server runtime: Tomcat 8.0 server, Web service 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
>
>
>
>
> On Tue, Feb 2, 2016 at 1:23 PM, Andreas Veithen <andreas.veit...@gmail.com>
> wrote:
>>
>> 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" <a...@belalangtempur.com>
>> wrote:
>>>
>>> Dear all,
>>>
>>> we used to develop web service using predefined WSDL (attached) on
>>> Eclipse. Our development tools were Eclipse (Luna R2), Tomcat 1.8.0, and
>>> Axis2 1.6.x. and it worked fine.
>>>
>>> Now, I want to create web service based on the same WSDL file, but using
>>> Axis2 1.7.0 instead of 1.6.4.
>>>
>>> I got the following error during WSDL-to-code generation:
>>> Exception occurred during code generation for the WSDL  :
>>> java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/XmlSchema
>>>
>>> I understand from the release note that Axis2 1.7.0 has upgraded its
>>> XMLSchema hence it is backward incompatible with Axis2 1.6.x. But I am not
>>> sure how can I relate this to my problem. From what I understand, Axis2
>>> complains that XMLSchema is not present. So, I import XMLSchema jar into my
>>> project build path. But the same error still occurs.
>>>
>>> Would you mind to point out how to solve this problem?
>>>
>>> Thanks!
>>>
>>> Regards,
>>> Arif
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
>>> For additional commands, e-mail: java-user-h...@axis.apache.org
>
>
>
>
> -
> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-user-h...@axis.apache.org

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Problem with Axis2 1.7.0

[Andreas Veithen]

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 development tools were Eclipse (Luna R2), Tomcat 1.8.0, and
> Axis2 1.6.x. and it worked fine.
>
> Now, I want to create web service based on the same WSDL file, but using
> Axis2 1.7.0 instead of 1.6.4.
>
> I got the following error during WSDL-to-code generation:
> Exception occurred during code generation for the WSDL  :
> java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/XmlSchema
>
> I understand from the release note that Axis2 1.7.0 has upgraded its
> XMLSchema hence it is backward incompatible with Axis2 1.6.x. But I am not
> sure how can I relate this to my problem. From what I understand, Axis2
> complains that XMLSchema is not present. So, I import XMLSchema jar into my
> project build path. But the same error still occurs.
>
> Would you mind to point out how to solve this problem?
>
> Thanks!
>
> Regards,
> Arif
>
>
> -
> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-user-h...@axis.apache.org
>

Re: [Axis2] Java Upgrade - 7

[Andreas Veithen]

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 releases happened before Java 7 became
available. 1.5.6 was releases a few weeks after that, but as far as I
know it hadn't been extensively tested on Java 7. That being said,
chances are high that it will just work. The problem is that a typical
project that depends on Axis2 will only actually use a small fraction
of the code, and even if we had an exhaustive list of known issues
with Java 7, it would be virtually impossible to predict if your
project would actually encounter any of these issues.

Anyway, software projects are expected to have sufficient test
coverage and it should therefore just be a matter of executing your
test suite with Java 7...

Andreas


On Mon, Nov 23, 2015 at 7:43 AM, Ashish Mantri  wrote:
> Hi,
>
> I am planning to upgrade JDK version from 6 to 7 for my project.
> I am using axis2 - 1.5 to generate client code for WS call.
>
> Can you please let me know if axis2 - 1.5 will be supported on JDK 7 or i
> will need to upgrade axis 2 for latest version.
>
> Thanks and Regards,
> Ashish Mantri

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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.
2) Axis2 must be configured to use the servlet based HTTP transport
(because commons-fileupload depends on the servlet API).
3) The temporary directory as configured by the java.io.tmpdir system
property must be writable to the attacker. In practice, this means
world writable, as is the case if java.io.tmpdir is set to /tmp.
4) MultipartFormDataBuilder must be enabled. This is the case for the
default axis2.xml config file distributed with Axis2.
5) At least one Web service must be deployed on Axis2. [I'm not 100%
sure here, but this condition is trivially satisfied in most cases
anyway]

For the standalone Axis2 server, condition 3 is satisfied, but 2 is
not. Tomcat sets java.io.tmpdir to a directory that is writable only
to the user the Tomcat instance runs as. Therefore condition 2 is not
satisfied, and Axis2 deployments on Tomcat are not vulnerable. I would
expect that any decent application server behaves similar to Tomcat. A
notable exception is IBM WebSphere Application Server which doesn't
change java.io.tmpdir, so that it points to the default /tmp. This
would mean that Axis2 applications deployed on WAS will likely be
vulnerable. Note that I believe that the Axis2 version that is part of
the JAX-WS implementation in the WAS runtime is not vulnerable because
it doesn't enable MultipartFormDataBuilder.

Also note that the mitigation strategy is trivial: upgrade
commons-fileupload or disable MultipartFormDataBuilder.

Andreas

On Thu, Jul 23, 2015 at 11:41 AM, Charlie Martin
charlie.mar...@uk.ibm.com wrote:
 Hi,

 The current (v1.6.3) and previous releases of Axis2 contain the apache
 commons-fileupload-1.2.jar.

 This jar is flagged as being vulnerable to CVE-2013-0248

 Could anyone confirm if either:

 This vulnerability is not applicable to the use of the jar in Axis2
 If an update is planned


 Details of the vulnerability:
 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0248

 Many thanks,
 Charlie Martin


 WebSphere MQ Development
 IBM Hursley Labs, Hursley Park, Winchester, Hants. SO21 2JN. UK.
 Email: charlie.mar...@uk.ibm.com
 Tel: +44 (0) 1962 815860, Internal: 37245860


 Unless stated otherwise above:
 IBM United Kingdom Limited - Registered in England and Wales with number
 741598.
 Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

 Unless stated otherwise above:
 IBM United Kingdom Limited - Registered in England and Wales with number
 741598.
 Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

[Announce] Release of Apache Axis2 1.6.3

[Andreas Veithen]

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 release uses
Apache Axiom 1.2.14.

The new version can be downloaded here:

http://axis.apache.org/axis2/java/core/download.cgi

It is also available from Maven central.

-- The Apache Axis2 team

[1] 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10611version=12320771

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Formatting BigDecimal element in response

[Andreas Veithen]

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 reason for that.

Andreas

[1] 
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-enumeration

On Wed, Jul 1, 2015 at 2:55 PM, T. Allen b...@verizon.net wrote:
 I have an element defined as:

 xsd:simpleType name=ShipmentType
 xsd:restriction base=decimal
 xsd:enumeration value=50 /
 xsd:enumeration value=60 /
 xsd:enumeration value=77.5 /
 /xsd:restriction
 /xsd:simpleType

 The class generated by the wsdl2java tool expects a BigDecimal parameter:

 public void setShipment(java.math.BigDecimal ship)

 The problem is that passing a value of 50 to the method produces a value of
 50.0 (no quotes) in the response.  How can I get the value formatted as in
 the enumeration?  I want the values to appear as 50, 60 or 77.5.

 Any advice or tips are much appreciated!

 Thanks,
 T


 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Error building Rampart from trunk

[Andreas Veithen]

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 rampart-policy: Failed to install artifact
 org.apache.rampart:rampart-policy:exec:jacoco:1.7.0-SNAPSHOT:
 C:\Workspaces\3rdParty\rampart-trunk\modules\rampart-policy\target\jacoco.exec
 (The system cannot find the file specified) - [Help 1]

 Any ideas what I am doing wrong? David

 --

 David R Robison
 Open Roads Consulting, Inc.
 103 Watson Road, Chesapeake, VA 23320
 phone: +1 757-546-3401
 e-mail: david.robi...@openroadsconsulting.com
 web: http://www.openroadsconsulting.com
 blog: http://therobe.blogspot.com
 book: http://www.xulonpress.com/bookstore/bookdetail.php?PB_ISBN=9781597816526



 This email communication (including any attachments) may contain confidential 
 and/or privileged material intended solely for the individual or entity to 
 which it is addressed.
 If you are not the intended recipient, please delete this email immediately.


 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Weird client webservice behavior after redirect

[Andreas Veithen]

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.

Andreas

On Wed, Jul 2, 2014 at 9:19 AM, Alberto Gori a.g...@siaspa.com wrote:
 I am using the default implementation of JAX-WS provided by Websphere 7,
 that is Axis2.

 My problem arises when a ws client receives a redirect (HTTP code 302)
 because the network team implemented a rule (that I can’t change) that
 redirects to an HTML error page in case of an application error (HTTP code
 500).



 At this point Axis client tries to follow the redirect, obviously failing:
 org.apache.axis2.AxisFault: WSWS7093W: The HTTP response redirected the
 target resource to a new location: http://agori:7070/jmil/BaseServices.



 This is ok for me. The problem  is that every Axis client (at least the ones
 created on that endpoint) from that moment on continues to follow the error
 page.

 At this point I have to restart the whole application if I want that my ws
 client does not point to the error page.



 This is weird because:



 1.   302 is not a permanent redirect

 2.   I could understand if the redirect becomes permanent  for the
 client that performed the failing request, but why this happens also for ws
 client created after the fail?



 I found a solution that is forcing the initial endpoint before every
 request. That is calling this line of code every time I attempt to invoke a
 ws method:



 ((BindingProvider)
 myService).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY,
 startingEndpoint);



 Is there a better solution, maybe passing some setting that disable
 redirect?



 Thank you



 Alberto Gori.

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 using http) but i'm having the following error:

 GRAVE: El Servlet.service() para el servlet [AxisServlet] en el contexto con
 ruta [/axis2] lanzó la excepción [https is forbidden] con causa raíz
 javax.servlet.ServletException: https is forbidden
 at
 org.apache.axis2.transport.http.AxisServlet.preprocessRequest(AxisServlet.java:637)
 at org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:247)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
 at
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
 at
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
 at
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
 at
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
 at
 org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
 at
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
 at
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
 at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
 at
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
 at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
 at
 org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
 at
 org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
 at
 org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)


 My question is: Axis2 support web services rest using https protocol?


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Accessing faultstring in Axis2 client

[Andreas Veithen]

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 #getFaultMessage.  This
 returns blank, which is correct since there is no text in the exception.  It
 would be very easy if this was the answer.

 I need to get the faultstring.  The faultstring is outside the exception.
 See the XML snippet below.

 I'm working on a different way of sending the request and capturing the
 response.  There is a lot more coding involved but appears to be the only
 way to get the faultstring element.

 Thanks,
 J




 On Thursday, June 5, 2014 2:37 AM, satyapriya sahoo
 sahoo.satyapr...@gmail.com wrote:

 Jack,

 Hope bellow points will help you to solve your Problem.

 You can process in 3 ways.

 1) IN your client code you need an catch block for AxisFault and U need to
 retrieve the message from that exception
 try{
   //Client code
 }catch(AxisFault af){
if(af!=null){
  String faultMsg =  af.getMessage();
  System.out.println(FaultString :: +faultMsg  );
   }
 }

 2) If it is coming as a string, then you can do some String operation.

 3) You can also take the help of dom parser or sax parse to retrieve the
 specific value, because it is coming as a xml format.

 Thanks,
 Satya



-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Accessing faultstring in Axis2 client

[Andreas Veithen]

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
rexclaim...@yahoo.com.invalid wrote:
 Andreas,

 Thanks very much for the reply.  I don't see any methods in the stub class to 
 get the message 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 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 #getFaultMessage.  This
 returns blank, which is correct since there is no text in the exception.  It
 would be very easy if this was the answer.

 I need to get the faultstring.  The faultstring is outside the exception.
 See the XML snippet below.

 I'm working on a different way of sending the request and capturing the
 response.  There is a lot more coding involved but appears to be the only
 way to get the faultstring element.

 Thanks,
 J




 On Thursday, June 5, 2014 2:37 AM, satyapriya sahoo
 sahoo.satyapr...@gmail.com wrote:

 Jack,

 Hope bellow points will help you to solve your Problem.

 You can process in 3 ways.

 1) IN your client code you need an catch block for AxisFault and U need to
 retrieve the message from that exception
 try{
   //Client code
 }catch(AxisFault af){
if(af!=null){
  String faultMsg =  af.getMessage();
  System.out.println(FaultString :: +faultMsg  );
   }
 }

 2) If it is coming as a string, then you can do some String operation.

 3) You can also take the help of dom parser or sax parse to retrieve the
 specific value, because it is coming as a xml format.

 Thanks,
 Satya



 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org

 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Accessing faultstring in Axis2 client

[Andreas Veithen]

In that case, you can use the _getServiceClient() method to get the
ServiceClient. From there you will be able to get to the last
OperationContext and from there to the MessageContext with the
response.

Andreas

On Fri, Jun 6, 2014 at 3:55 PM, Jack Sprat
rexclaim...@yahoo.com.invalid wrote:

 Yes, 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
 rexclaim...@yahoo.com.invalid wrote:
 Andreas,

 Thanks very much for the reply.  I don't see any methods in the stub class 
 to get the message 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 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 #getFaultMessage.  This
 returns blank, which is correct since there is no text in the exception.  It
 would be very easy if this was the answer.

 I need to get the faultstring.  The faultstring is outside the exception.
 See the XML snippet below.

 I'm working on a different way of sending the request and capturing the
 response.  There is a lot more coding involved but appears to be the only
 way to get the faultstring element.

 Thanks,
 J




 On Thursday, June 5, 2014 2:37 AM, satyapriya sahoo
 sahoo.satyapr...@gmail.com wrote:

 Jack,

 Hope bellow points will help you to solve your Problem.

 You can process in 3 ways.

 1) IN your client code you need an catch block for AxisFault and U need to
 retrieve the message from that exception
 try{
   //Client code
 }catch(AxisFault af){
if(af!=null){
  String faultMsg =  af.getMessage();
  System.out.println(FaultString :: +faultMsg  );
   }
 }

 2) If it is coming as a string, then you can do some String operation.

 3) You can also take the help of dom parser or sax parse to retrieve the
 specific value, because it is coming as a xml format.

 Thanks,
 Satya



 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org

 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: WebSocket support for Axis2

[Andreas Veithen]

Hi Gihan,

My knowledge of WebSockets is very limited, so this immediately raises
a couple of other questions for me:

* According to the JIRA issue you created, you propose to use SOAP
over WebSockets. SOAP assumes that the transport protocol is message
oriented (in the sense that you can use the transport protocol to send
and/or receive discrete messages). WebSockets being stream-oriented,
you need something between SOAP and WebSocket. Is there an existing
standard for this?
* Obviously, in general your transport would be used on the server
side, while the client is a browser. Are there JavaScript frameworks
that support SOAP over WebSockets?
* WebSockets can indeed be used to push messages from the server to
the client. Any idea how this would be supported by the Axis2
architecture?

Regards,

Andreas

On Thu, Mar 20, 2014 at 12:13 PM, Gihan Madushanka gihang...@gmail.com wrote:

 Hi Andreas,

 Thanks for your comment. I prepared following list of use cases and I will
 try to find more use cases.

 1. As WebSocket protocol is based on full-duplex single connection above
 suggested new transport will reduce unnecessary network traffic and latency.
 Due to above advantages WebSocket transport will be a preferable choice for
 performance centric web service applications.

 2. As far as i know existing Axis2 transports are not designed to support
 use cases like notification from server side. Another use case of this
 suggested new transport  is it can be used to develop a server side
 notification application. As an example after opening a connection client
 can wait to receive notifications from the server.

 3. I don't have much knowledge about Apache Synapse project but it looks
 like suggested new transport can be used with Apache Synapse too. I found
 following page from Apache Camel web site
 (https://camel.apache.org/websocket.html) may be suggested new transport can
 be used to develop similar use cases.

 4.  Additionally following two pages contain number of other advantages of
 WebSocket.

 https://www.websocket.org/quantum.html
 https://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, Gihan Madushanka gihang...@gmail.com
 wrote:
  Hi All,
 
  I'm Gihan Madushanka  an undergraduate and also a participant of the
  GSoC
  2013 programme. This year also I look forward  to participate this
  programme.  Few weeks ago I contacted a mentor and received few possible
  project ideas. Among them I like to implement the idea of WebSocket
  transport support for Axis2 as my project of this year.  I spent last
  few
  days to do the basic research and draft initial project proposal.
 
  According to my research I found that one of the following frameworks
  can be
  used to provide WebSocket transport support for Axis2 and these
  frameworks
  also can be further categorized into two types as annotation based and
  not-annotation based. I'm much thankfull if Axis2 developers can review
  and
  help me to identify best framework for my project.
 
 
  Annotation based frameworks
 
  https://github.com/Atmosphere/atmosphere
 
  https://tyrus.java.net/
 
 
 
  Non-annotation based framework
 
  https://github.com/TooTallNate/Java-WebSocket
 
 
  http://www.eclipse.org/jetty/documentation/current/jetty-websocket-client-api.html
 
 
  Regards,
 
  Gihan

 -
 To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-dev-h...@axis.apache.org



-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: WebSocket support for Axis2

[Andreas Veithen]

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 programme. This year also I look forward  to participate this
 programme.  Few weeks ago I contacted a mentor and received few possible
 project ideas. Among them I like to implement the idea of WebSocket
 transport support for Axis2 as my project of this year.  I spent last few
 days to do the basic research and draft initial project proposal.

 According to my research I found that one of the following frameworks can be
 used to provide WebSocket transport support for Axis2 and these frameworks
 also can be further categorized into two types as annotation based and
 not-annotation based. I'm much thankfull if Axis2 developers can review and
 help me to identify best framework for my project.


 Annotation based frameworks

 https://github.com/Atmosphere/atmosphere

 https://tyrus.java.net/



 Non-annotation based framework

 https://github.com/TooTallNate/Java-WebSocket

 http://www.eclipse.org/jetty/documentation/current/jetty-websocket-client-api.html


 Regards,

 Gihan

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Dependency conflicts when adding Axis2 to large project.

[Andreas Veithen]

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 dot something).

The avoid the conflict, add an exclusion to the Axis2 dependency (or
dependencies).

Andreas

On Thursday, February 6, 2014, Todd Chapman t...@chaka.net wrote:

 Hello,

 We have a multi-module Maven project that we are adding Axis2 to as a
 dependency.

 The axis2-kernel-1.6.2.pom has a dependency:

dependency
 groupIdjavax.servlet/groupId
 artifactIdservlet-api/artifactId
 /dependency

 This seems to conflict with a pre-existing project dependency:

 dependency
 groupIdjavax.servlet/groupId
 artifactIdjavax.servlet-api/artifactId
 version3.0.1/version
 /dependency

 What is the difference between the servlet-api artifact and the
 javax.servlet-api artifact? Also why doesn't the axis2-kernel, servlet-api
 dependency specify a version?

 Thank you for any help!

 -Todd

Re: Axis2 Print empty/black soap header

[Andreas Veithen]

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 excuse
to get rid of that aberration in Axiom. Can you please create a JIRA
issue with the problem description from your previous mail?

Andreas


On Mon, Jan 27, 2014 at 2:23 PM, Andy Schmidt andy.schm...@kisters.de wrote:
 Hi,

 is it possible that the Axis2 1.6.2 framework prints a empty default soap
 header into the soap response envelope? Like:

 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Header/
soapenv:Body
   ns1:Response xmlns:ns1=example
  ns1:valuetrue/ns1:value
   /ns1:Response
/soapenv:Body
 /soapenv:Envelope

 I am implementing a soap web service which must be return a soap envelope
 which contains a empty soap header, because the requesting client does
 expact a empty soap header. Normally the client should ignore black soap
 headers, but its not possible to change the client system at the moment.

 Is there a way to print empty soap header? Maybe set a property?

 I have been taking a look into the SOAP-Standard documents, but I didn't
 found a description of how to manage empty/black soap headers.

 Regards,

 Andy Schmidt
 
 Andy Schmidt - KISTERS AG - Charlottenburger Allee 5 - 52068 Aachen -
 Germany
 Handelsregister Aachen, HRB-Nr. 7838 | Vorstand: Klaus Kisters, Hanns
 Kisters | Aufsichtsratsvorsitzender: Dr. Thomas Klevers
 Tel.: +49 241 9671 -449 | Fax: +49 241 9671 -555 | E-Mail:
 andy.schm...@kisters.de | WWW: http://www.kisters.de
 
 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
 Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
 irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
 vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
 Weitergabe dieser Mail ist nicht gestattet.
 This e-mail may contain confidential and/or privileged information. If you
 are not the intended recipient (or have received this e-mail in error)
 please notify the sender immediately and destroy this e-mail. Any
 unauthorised copying, disclosure or distribution of the material in this
 e-mail is strictly forbidden.

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Using Axis2 with Maven

[Andreas Veithen]

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

On Mon, May 13, 2013 at 12:41 PM, Hendrik Geßner
hgess...@uni-potsdam.de wrote:
 I’m trying to use Axis2 by resolving all dependencies with maven.
 Unfortunately there doesn’t seem to be an official dependency code snippet
 on the project page.



 Trying to copy the snippet that the rampart samples use, I ran into the
 well-known redirect problem
 (http://www.ashlux.com/wordpress/2010/06/15/axis2-maven-and-java.net-woes-and-why-maven-sucks/).
 The release note for 1.5.2 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.3 release.”



 Thanks,

 Hendrik

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Rampart Policy Assertions not binding correctly

[Andreas Veithen]

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, Apr 19, 2013 at 1:14 AM, Rostom A rosto...@yahoo.com wrote:
 I have a strange problem, which I'm hoping someone can help me with...

 I am using axis2 ADB bindings and Rampart to make a call to a web service as
 a client.  Everything works fine when I am in Eclipse (using Maven).
 However, when I expand all the dependent JAR files and build a single JAR
 file of my code (using Maven) and its dependencies, then run the same main
 class/method, it fails with the following error:

 java.lang.RuntimeException: Undefined 'Security policy namespace cannot be
 null.' resource property

 After some analysis, I seem to have found the root cause, but just don't
 know how to fix it.  The problem seems to be that when the Policy object is
 built, it isn't associating the correct Assertion classes within it.  Here
 is the code that I used to discover this:

 StAXOMBuilder builder = new StAXOMBuilder(policyXmlPath);   //policyXmlPath
 is the full path to my policy.xml file
 Policy servicePolicy = PolicyEngine.getPolicy(builder.getDocumentElement());
 List it = (List)servicePolicy.getAlternatives().next();
 for (int i=0; iit.size(); i++) {
 Assertion assertion = (Assertion)it.get(i);
 logger.debug(i: %s   |   type: %s   |   name: %s   |   namespace uri:
 %s, i, assertion.getClass().getName(), assertion.getName(),
 assertion.getName().getNamespaceURI());
 }

 The printout I get from Eclipse is:

 i: 0   |   type: org.apache.ws.secpolicy.model.AsymmetricBinding   |   name:
 {http://schemas.xmlsoap.org/ws/2005/07/securitypolicy}AsymmetricBinding   |
 namespace uri: http://schemas.xmlsoap.org/ws/2005/07/securitypolicy
 i: 1   |   type: org.apache.ws.secpolicy.model.Wss10   |   name:
 {http://schemas.xmlsoap.org/ws/2005/07/securitypolicy}Wss10   |   namespace
 uri: http://schemas.xmlsoap.org/ws/2005/07/securitypolicy
 i: 2   |   type: org.apache.ws.secpolicy.model.SignedEncryptedParts   |
 name: {http://schemas.xmlsoap.org/ws/2005/07/securitypolicy}SignedParts   |
 namespace uri: http://schemas.xmlsoap.org/ws/2005/07/securitypolicy
 i: 3   |   type: org.apache.rampart.policy.model.RampartConfig   |   name:
 {http://ws.apache.org/rampart/policy}RampartConfig   |   namespace uri:
 http://ws.apache.org/rampart/policy

 Whereas the printout I get from running the main class via the JAR file is:

 i: 0   |   type:
 org.apache.neethi.builders.PolicyContainingPrimitiveAssertion   |   name:
 {http://schemas.xmlsoap.org/ws/2005/07/securitypolicy}AsymmetricBinding   |
 namespace uri: http://schemas.xmlsoap.org/ws/2005/07/securitypolicy
 i: 1   |   type:
 org.apache.neethi.builders.PolicyContainingPrimitiveAssertion   |   name:
 {http://schemas.xmlsoap.org/ws/2005/07/securitypolicy}Wss10   |   namespace
 uri: http://schemas.xmlsoap.org/ws/2005/07/securitypolicy
 i: 2   |   type: org.apache.neethi.builders.xml.XmlPrimitiveAssertion   |
 name: {http://schemas.xmlsoap.org/ws/2005/07/securitypolicy}SignedParts   |
 namespace uri: http://schemas.xmlsoap.org/ws/2005/07/securitypolicy
 i: 3   |   type: org.apache.rampart.policy.model.RampartConfig   |   name:
 {http://ws.apache.org/rampart/policy}RampartConfig   |   namespace uri:
 http://ws.apache.org/rampart/policy

 Notice that in the latter case, the first two are the generic
 PolicyContainingPrimitiveAssertion rather than the more specific
 AsymmetricBinding and Wss10 classes, respectively.  I do in fact have all
 the files from rampart-policy and rampart-trust (which originally
 encapsulated these two classes) in my JAR file. So why then is it not
 binding them to what it finds from the policy.xml file?

 Any help would be greatly appreciated.

 --rostom

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 processing error.

Andreas

[1] http://www.w3.org/TR/2000/NOTE-SOAP-2508

On Wed, Apr 10, 2013 at 11:47 AM, santosh kumar 2408.sant...@gmail.com wrote:
 Hi,

 I am facing an issue with Axis2 framework.
 I am using Apache Tomcat version 7.0.25 on which i have deployed my web
 service.
 The issue faced is :

 1. whenever my service throws any exception Axis throws the same exception
 in XML format correctly  but in RAW data we see

 HTTP/1.1 500 Internal Server Error
 Server: Apache-Coyote/1.1
 Content-Type: text/xml;charset=UTF-8
 Transfer-Encoding: chunked
 Date: Wed, 10 Apr 2013 08:48:13 GMT
 Connection: close

 I want to know is it correct behaviour of Axis2 that in case of any
 exception it should throw Error 500 (Internal Server Error).
 Ideally it should throw Http code 200 along with the XML information
 containing the exception raised by web service, because communication is
 proper.

 If its the correct behavior then do we have any option to change this
 behavior of Axis 2.

 Please suggest some valuable tips as i am stuck with it .

 With Regards
 Santosh Kumar


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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.

Andreas

On Thu, Mar 28, 2013 at 11:57 AM, Stefan Traud stefan_tr...@yahoo.com wrote:
 When moving a client application from axis2-1.6.1 to axis2-1.6.2, I get the
 following exception:

 org.apache.axiom.om.OMException: No meta factory found for feature
 'default'; this usually means that axiom-impl.jar is not in the classpath

 All I did for the migration is replacing the axis2 jars with those from
 axis2-1.6.2 and adjusting the classpath.
 axiom-impl-1.2.13.jar, axiom-api-1.2.13.jar and axiom-dom-1.2.13.jar are in
 the classpath.

 When running the client within eclipse-IDE, it works and nothing is being
 missed. When trying to run the client standalone, the above exception is
 thrown.

 I found that others also had similar trouble, but could not find a
 workaround to resolve this. Just renaming the jars is not sufficient.

 Thanks for any help
 --stefan

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 and the generated code won't compile.

Andreas

On Wed, Mar 20, 2013 at 11:20 PM, Shah, Sumit (CGI Federal)
sumit.s...@cgifederal.com wrote:
 I did some research and it’s the code/XSL in JaxbRIDatabindingTemplate.xsl
 that is writing out the portion of the stub that causing the compilation
 issue. Unless a concurrency issue, I wonder why consistently in couple of
 cases the ‘position() != last()’ seems to be ‘true’ when it should be false.
 And hence the additional comma at the end of the last element in the array.
 I would appreciate any pointers.



 ‘

 private static final javax.xml.bind.JAXBContext wsContext;

 static {

 javax.xml.bind.JAXBContext jc;

 jc = null;

 try {

jc = javax.xml.bind.JAXBContext.newInstance(

 xsl:for-each select=param[not(@type =
 preceding-sibling::param/@type)]

 xsl:if test=@type!=''

 xsl:value-of select=@type/.classxsl:if
 test=position() != last(),

 /xsl:if

 /xsl:if

 /xsl:for-each

);

 }

 catch ( javax.xml.bind.JAXBException ex ) {

 System.err.println(Unable to create JAXBContext:  +
 ex.getMessage());

 ex.printStackTrace(System.err);

 Runtime.getRuntime().exit(-1);

 }

 finally {

 wsContext = jc;

  }

 }

 ’

 Thanks

 Sumit



 From: Shah, Sumit (CGI Federal)
 Sent: Wednesday, March 20, 2013 3:27 PM
 To: java-user@axis.apache.org
 Subject: RE: WSImport w JDK 1.6.0_25 and Axis2 1.6.2: Generated stub fails
 compilation - Update: Actually issue occurring in WSDL2Code



 I take the WSImport part back. It is actually happening with WSDL2Code. It
 does not happen if I use the WSDL2Code with Axis2 1.6.0.



 The issue is happening with WSDL2Code in Axis2 1.6.2 and I am using Axiom
 1.2.14. Is anyone aware of the issue with 1.6.2?



 From: Shah, Sumit (CGI Federal)
 Sent: Wednesday, March 20, 2013 11:22 AM
 To: java-user@axis.apache.org
 Subject: WSImport w JDK 1.6.0_25 and Axis2 1.6.2: Generated stub fails
 compilation



 Hi,



 I am using WSImport to generate the client stubs for a bunch of wsdl files.
 After the generation the code fails to compile. I am using this with Axis2
 1.6.2. The following code block fails:



 If you notice: the line:
 'com.sample.test.webservices.impl.participant.Notify.class,' ends with a
 comma that shouldn't be there. Ironically it only happens for 2 of the 10 or
 so wsdl files I have.  Any information would be appreciated.



 private static final javax.xml.bind.JAXBContext wsContext;

 static {

 javax.xml.bind.JAXBContext jc;

 jc = null;

 try {

 jc =
 javax.xml.bind.JAXBContext.newInstance(

 com.sample.test.webservices.impl.participant.Add.class,


 com.sample.test.webservices.impl.participant.AddResponse.class,


 com.sample.test.webservices.exceptions.UnrecoverableFault.class,


 com.sample.test.webservices.exceptions.RecoverableFault.class,


 com.sample.test.webservices.impl.participant.Delete.class,


 com.sample.test.webservices.impl.participant.DeleteResponse.class,


 com.sample.test.webservices.impl.participant.Select.class,


 com.sample.test.webservices.impl.participant.SelectResponse.class,


 com.sample.test.webservices.impl.participant.AddChange.class,


 com.sample.test.webservices.impl.participant.AddChangeResponse.class,


 com.sample.test.webservices.impl.participant.Query.class,


 com.sample.test.webservices.impl.participant.QueryResponse.class,


 com.sample.test.webservices.impl.participant.Update.class,


 com.sample.test.webservices.impl.participant.UpdateResponse.class,


 com.sample.test.webservices.impl.participant.Change.class,


 com.sample.test.webservices.impl.participant.ChangeResponse.class,


 com.sample.test.webservices.impl.participant.Synchronize.class,


 com.sample.test.webservices.impl.participant.SynchronizeResponse.class,


 com.sample.test.webservices.impl.participant.Notify.class,



 );

 }

 catch ( javax.xml.bind.JAXBException ex ) {

 System.err.println(Unable to create JAXBContext:  +
 ex.getMessage());

 ex.printStackTrace(System.err);

 Runtime.getRuntime().exit(-1);

 }

 finally {

 wsContext = jc;

   

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

[Andreas Veithen]

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 Turkey can not
 get rid of the following exception:
 (...)
 Caused by: org.apache.axis2.AxisFault: Unable to locate the SOAP part;
 content ID was 0.0785513db83d55a4a646b6640b9e0d2257813e7713c83...@apache.org
 mailto:0.0785513db83d55a4a646b6640b9e0d2257813e7713c83...@apache.org

  at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
  at
 org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:123)
  at
 org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67)
  at
 org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:354)
  at
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)
  at
 org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
  at
 org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
  at ch.msmri.transfer.client.DicomTransferServiceStub.datasetUpload(Unknown
 Source)
  ... 11 more
 Caused by: org.apache.axiom.om.OMException: Unable to locate the SOAP part;
 content ID was 0.0785513db83d55a4a646b6640b9e0d2257813e7713c83...@apache.org
 mailto:0.0785513db83d55a4a646b6640b9e0d2257813e7713c83...@apache.org
  at org.apache.axiom.attachments.Attachments.getSOAPPartContentType(Unknown
 Source)
  at
 org.apache.axis2.builder.MIMEBuilder.processDocument(MIMEBuilder.java:41)
  at
 org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:179)
  at
 org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:145)
  at
 org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:108)
  ... 17 more

 Not sure if the following info is of any help:
 - all communications run via https
 - Client runs on Windows XP/JRE 1.6.0_29-b11
 - The customer's institute uses no proxy server
 - The customer's institute uses a Trend micro security agent, however
 added an exception for connections to our webserver (to exclude as possible
 source)

 Does anyone have an idea what could cause this exception?
 Any help is highly appreciated
 Thanks in advance
 --stefan

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

Could you insert some code that calls
soapFault.getFirstChildWithName(SOAP11Constants.QNAME_FAULT_DETAIL)
and try to determine where the returned OMElement is coming from? It
obviously can't be the one returned by
axisFault.getFaultDetailElement() because that one must be a
SOAPFaultDetail.

Andreas

On Fri, Mar 15, 2013 at 10:03 PM, Shah, Sumit (CGI Federal)
sumit.s...@cgifederal.com wrote:
 Hi Andreas,

 This is how I create the SOAP Fault. This is using Axiom 1.2.13. I am not 
 sure if this has changed in 1.2.14.

 catch (AxisFault axisFault) {
 if (axisFault.getFaultMessageContext() != null  
 axisFault.getFaultMessageContext().getEnvelope() != null) {
 SOAPFault soapFault = null;

 if 
 (axisFault.getFaultMessageContext().isSOAP11()) {
 soapFault = new 
 SOAP11Factory().createSOAPFault(axisFault.getFaultMessageContext().getEnvelope().getBody());
 }
 else {
 soapFault = new 
 SOAP12Factory().createSOAPFault(axisFault.getFaultMessageContext().getEnvelope().getBody());

 if (axisFault.getFaultNodeElement() != null) {
 
 soapFault.setNode(axisFault.getFaultNodeElement());
 }
 }

 if (axisFault.getFaultCodeElement() != null) {
 
 soapFault.setCode(axisFault.getFaultCodeElement());
 }

 if (axisFault.getFaultDetailElement() != null) {
 
 soapFault.setDetail(axisFault.getFaultDetailElement());
 }

 if (axisFault.getFaultReasonElement() != null) {
 
 soapFault.setReason(axisFault.getFaultReasonElement());
 }

 if (axisFault.getFaultRoleElement() != null) {
 
 soapFault.setRole(axisFault.getFaultRoleElement());
 }

 //This get called
 this.handleSOAPFault(method, soapFault);
 }
 else {
 throw axisFault;
 }
 }


 The CCE happens in the method here:
 protected void handleSOAPFault(Method method, SOAPFault soapFault) throws 
 Exception {
 Exception faultException = null;

   //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]
 Sent: Wednesday, March 13, 2013 12:25 PM
 To: java-user
 Subject: 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 this a bug?



 Sumit



 From: Yashwanth Rajaram -X (yrajaram - ZENSAR TECHNOLOGIES INC at
 Cisco) [mailto:yraja...@cisco.com]
 Sent: Tuesday, March 12, 2013 1:35 PM
 To: java-user@axis.apache.org
 Subject: RE: java.lang.ClassCastException:
 org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to
 org.apache.axiom.soap.SOAPFaultDetail



 Sumit, I think you might have to do something like this:



 SOAPFaultDetail detail =
 OMAbstractFactory.getSOAP11Factory().createSOAPFaultDetail();

 detail.addChild(getFirstChildWithName(SOAP11Constants.QNAME_FAULT_DETA
 IL));



 Sincerely, Yashwanth

 Technical Architect, EBIS



 From: Shah, Sumit (CGI Federal) [mailto:sumit.s...@cgifederal.com]
 Sent: Tuesday, March 12, 2013 8:16 AM
 To: java-user@axis.apache.org
 Subject: java.lang.ClassCastException:
 org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to
 org.apache.axiom.soap.SOAPFaultDetail



 Hi,



 I am running into the following ClassCastException running Axis2 1.6.2
 and Axiom 1.2.14 (I have also included the axiom-compat jar for
 backwards compatibility). I noticed a similar issue reported for
 Synapse/Carbon https://wso2.org/jira/browse/CARBON-13759. I am not
 sure if these are related.





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



 Its occurring here in the SOAP11FaultImpl:



 public SOAPFaultDetail getDetail() {

 return (SOAPFaultDetail

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

[Andreas Veithen]

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 this a bug?



 Sumit



 From: Yashwanth Rajaram -X (yrajaram - ZENSAR TECHNOLOGIES INC at Cisco)
 [mailto:yraja...@cisco.com]
 Sent: Tuesday, March 12, 2013 1:35 PM
 To: java-user@axis.apache.org
 Subject: RE: java.lang.ClassCastException:
 org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to
 org.apache.axiom.soap.SOAPFaultDetail



 Sumit, I think you might have to do something like this:



 SOAPFaultDetail detail =
 OMAbstractFactory.getSOAP11Factory().createSOAPFaultDetail();

 detail.addChild(getFirstChildWithName(SOAP11Constants.QNAME_FAULT_DETAIL));



 Sincerely, Yashwanth

 Technical Architect, EBIS



 From: Shah, Sumit (CGI Federal) [mailto:sumit.s...@cgifederal.com]
 Sent: Tuesday, March 12, 2013 8:16 AM
 To: java-user@axis.apache.org
 Subject: java.lang.ClassCastException:
 org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to
 org.apache.axiom.soap.SOAPFaultDetail



 Hi,



 I am running into the following ClassCastException running Axis2 1.6.2 and
 Axiom 1.2.14 (I have also included the axiom-compat jar for backwards
 compatibility). I noticed a similar issue reported for Synapse/Carbon
 https://wso2.org/jira/browse/CARBON-13759. I am not sure if these are
 related.





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



 Its occurring here in the SOAP11FaultImpl:



 public SOAPFaultDetail getDetail() {

 return (SOAPFaultDetail)
 getFirstChildWithName(SOAP11Constants.QNAME_FAULT_DETAIL);

 }



 I see that getFirstChildWithName() currently returns an OMELement, however
 the cast above fails. I would appreciate any suggestions.



 Thanks

 Sumit

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 at my local Ide Netbeans it all works fine, but when i try it
 at Testing environment (which is a copy of Pro) it says me the following
 error:

 org.apache.axiom.om.OMException: No meta factory found for feature
 'default'; this usually means that axiom-impl.jar is not in the classpath


   I´am pretty sure i have axiom-impl-1.2.13 on my classpath (i have tried
 with all axiom jars which comes with Axis2 distribution and with axiom.jar
 also). None of this tries works, i search on google and only what i found
 it´s to use axiom.jar instead o impl or api one (i have also tried this and
 doesn´t work)

  Could anyone help me with this feature?

  Thanks in advace

  Kind regards and also Merry Christmas!!

  Oscar


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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;
 } else if (feature.equals(FEATURE_DOM)) {
 jarHint = axiom-dom.jar;
 } else {
 jarHint = null;
 }

Nonsense. The purpose of that piece of code is just to produce a more
meaningful error message (instead of just No meta factory found for
feature 'xxx').

 assuming axiom-impl-1.2.13.jar is on classpath

 mv axiom-impl-1.2.13.jar axiom-impl.jar

 org.apache.axiom.om.OMAbstractFactory is not able to pickup version specific 
 axiom-impl-1.2.13.jar

Nonsense. The code (that loads the meta factories, not the one shown
above) looks for resources called META-INF/axiom.xml. The name of the
JAR doesn't matter.


 Feliz Navidad desde EEUU,
 Martin Gainty
 __
 por favor no altere ni interrumpir la transmisión
 por favor no altere ni interrumpir la transmisión..Gracias



 
 From: oscas...@hotmail.com
 To: axis-u...@ws.apache.org
 Subject: org.apache.axiom.om.OMException with Axis2 Client
 Date: Fri, 21 Dec 2012 12:50:40 +0100


 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 at my local Ide Netbeans it all works fine, but when i try it 
 at Testing environment (which is a copy of Pro) it says me the following 
 error:

 org.apache.axiom.om.OMException: No meta factory found for feature 'default'; 
 this usually means that axiom-impl.jar is not in the classpath


   I´am pretty sure i have axiom-impl-1.2.13 on my classpath (i have tried 
 with all axiom jars which comes with Axis2 distribution and with axiom.jar 
 also). None of this tries works, i search on google and only what i found 
 it´s to use axiom.jar instead o impl or api one (i have also tried this and 
 doesn´t work)

  Could anyone help me with this feature?

  Thanks in advace

  Kind regards and also Merry Christmas!!

  Oscar


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Axis SSL authentication help!

[Andreas Veithen]

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 akme...@yahoo.com wrote:
 No. I have a web service client that uses axis1 to consume web services from
 server A and server B. For server A I need to do authentication while for
 server B there is no such need. So the problem is on my client side where I
 need to configure axis to do authentication on some of the requests (based
 on my truststore) and NOT do authentication in other requests using
 SunJSSESocketFactory. The way I understand it (docs are not clear)
 AxisProperties will override each other per request. Right? Is my problem
 clearer now?

 From: Martin Gainty mgai...@hotmail.com
 To: java-user@axis.apache.org
 Sent: Wednesday, November 14, 2012 3:43 PM

 Subject: RE: Axis SSL authentication help!



 You need 2 different webapps
 one which implements SunFakeTrustSocketFactory for implementing unsigned
 server certs ..which would NEVER be used in Production Environment
 this would allow someone's client to hack in with their own self-signed
 certs

 one which implements
 http://ws.apache.org/axis/java/apiDocs/org/apache/axis/components/net/SunJSSESocketFactory.html
 provided requesting client has a valid (public) key of type RSA AND your
 client or B2B requesting entity supports JSSE key exchange
 this would prevent someone's client to hack in with their own self-signed
 certs

 so the question is are you implementing with self-signed certs OR are you
 using CA level certs (such as certs obtained from Verisign or Thawte)

 Martin
 __
 Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

 Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
 Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
 Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
 dient lediglich dem Austausch von Informationen und entfaltet keine
 rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
 E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

 Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
 destinataire prévu, nous te demandons avec bonté que pour satisfaire
 informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
 de ceci est interdite. Ce message sert à l'information seulement et n'aura
 pas n'importe quel effet légalement obligatoire. Étant donné que les email
 peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
 aucune responsabilité pour le contenu fourni.




 Date: Tue, 13 Nov 2012 22:27:37 -0800
 From: akme...@yahoo.com
 Subject: Re: Axis SSL authentication help!
 To: java-user@axis.apache.org

 Also why are you mentioning about the refactoring to different web apps? I
 am asking about client side code

 From: Martin Gainty mgai...@hotmail.com
 To: java-user@axis.apache.org
 Sent: Wednesday, November 14, 2012 4:03 AM
 Subject: RE: Axis SSL authentication help!

 need to skip any server authentication in some requests (e.g. use
 SunFakeTrustSocketFactory).

 MGyou need to retask this to use 2 separate webapps
 MGone which will authenticate your credentials with MySSLSocketFactory
 MGone which not authenticate which will use SunFakeTrustSocketFactory

 MGthis is very clumsy and your options for specifying the security
 algorithm of your choosing as well as custom keysize are quite limited
 MGwhy not use Axis2 and engage the Rampart Security Module?
 MGMartin

 Date: Tue, 13 Nov 2012 13:37:28 -0800
 From: akme...@yahoo.com
 Subject: Axis SSL authentication help!
 To: java-user@axis.apache.org

 Hi,
 I am using Axis 1 and need to do SSL authentication of a web service.
 I found that I need to use:
 AxisProperties.setProperty(axis.socketSecureFactory,
 com.example.MySSLSocketFactory); to set my custom factory and trust
 managers.
 Problem: I also need to skip any server authentication in some requests
 (e.g. use SunFakeTrustSocketFactory).
 I assume that this AxisProperties.setProperty is some central property that
 affects all threads, right? So how could I implement my use case?
 Keep reseting AxisProperties.setProperty before each web service call? Is
 this the proper way? But I found this bug ticket that seems to complaint
 that once the socket factory is set in AxisProperties it is cached and any
 new setting has not
 effect:https://issues.apache.org/jira/browse/AXIS-2751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel#issue-tabs
 Is there a workarround for this?
 If you could help me here it would be great guys!
 Thank you





-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, 

Re: Errnn238 after boot calling web services

[Andreas Veithen]

On Tue, Nov 13, 2012 at 9:46 AM, Oscar Rugama oscas...@hotmail.com wrote:
 Thanks Andreas, but i want to say that it no only fails at first Web Service
 call, after restarting Tomcat it fails forever until i undeploy and deploy
 again application. Also the properties file i know is loaded because it´s
 used to set data pool connection to Oracle and it works (if not loaded i
 can´t connect to Oracle because in this properties you can find url to
 database, user and pass)

As I said, the proxy settings are cached by Axis 1.4. They will only
be read during the first Web service call. If they are not set
correctly at that point, then subsequent calls will also fail, even if
you set the system properties later. If you restart or redeploy the
application, then the cache will be reset, which explains why the
application starts working afterwards.

 When you said 'It's better to set them once and for all in the server
 configuration', it means doing proxy authentication at tomcat server?

No, just setting the relevant system properties on the command line of
the JVM so that they don't change at runtime.

  Thanks again
 Regards
  Oscar


 From: andreas.veit...@gmail.com
 Date: Tue, 13 Nov 2012 09:26:19 +0100

 Subject: Re: Errnn238 after boot calling web services
 To: java-user@axis.apache.org

 The problem is that Axis 1.4 caches the proxy settings. If after a
 restart of tomcat the application no longer works, then this would
 mean that the the system properties are not yet set when the very
 first Web service call is made. It should also be noted that setting
 system properties programmatically in a Web application is not
 recommended. It's better to set them once and for all in the server
 configuration.

 Andreas

 On Tue, Nov 13, 2012 at 8:11 AM, Oscar Rugama oscas...@hotmail.com
 wrote:
  Hi,
 
 
  I configure http connection like that:
 
  http
 
  System.setProperty(http.proxySet, true);
  System.setProperty(http.proxyHost,
  ConfigurationManager.getProperty(ws.proxy.host));
  System.setProperty(http.proxyPort,
  ConfigurationManager.getProperty(ws.proxy.port));
 
 
  System.setProperty(http.proxyType,ConfigurationManager.getProperty(ws.proxy.type));
 
  System.setProperty(http.proxyUser, proxyUser);
  System.setProperty(http.proxyPassword, proxyPassword);
 
  https
 
 
 
 
  System.setProperty(https.proxySet,ConfigurationManager.getProperty(asnef.proxySet));
 
 
  System.setProperty(https.proxyHost,ConfigurationManager.getProperty(ws.proxy.host));
 
 
  System.setProperty(https.proxyPort,ConfigurationManager.getProperty(ws.proxy.port));
 
 
  System.setProperty(https.proxyType,ConfigurationManager.getProperty(ws.proxy.type));
 
  System.setProperty(https.proxyUser, proxyUser);
  System.setProperty(https.proxyPassword, proxyPassword);
 
 
  As i said in one mail before, all this code works until we re-start
  tomcat
  (shutdown and startup) when it stars to fail and get errn238
 
  Thank you very much
  Kind regards,
  Oscar
 
 
 
 
  From: andreas.veit...@gmail.com
  Date: Mon, 12 Nov 2012 19:35:13 +0100
 
  Subject: Re: Errnn238 after boot calling web services
  To: java-user@axis.apache.org
 
  The problem is that the following line in the stack trace is in the
  code path that is executed for direct connections:
 
  at
 
  org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:120)
 
  How do you configure the HTTP proxy to be used by your Web application?
 
  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 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,
   Oscar
  
  
  
   From: andreas.veit...@gmail.com
   Date: Sun, 11 Nov 2012 20:09:56 +0100
  
   Subject: Re: Errnn238 after boot calling web services
   To: java-user@axis.apache.org
  
  
   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 a Web Service with Axis2 that publish several methods. One
   of
   this
   methods call two external (Internet) Web Services so for this web
   services i
   am a client. The client for this Web Services is made with Axis
   1.4.
  
   I can say that all works fine but when we boot the web server
   (tomcat
   and i
   have also test in JBoss) the client for this web services don´t
   work
   it
   raises
  
   AxisFault

Re: Errnn238 after boot calling web services

[Andreas Veithen]

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,
   Oscar



 From: andreas.veit...@gmail.com
 Date: Sun, 11 Nov 2012 20:09:56 +0100

 Subject: Re: Errnn238 after boot calling web services
 To: java-user@axis.apache.org


 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 a Web Service with Axis2 that publish several methods. One of
  this
  methods call two external (Internet) Web Services so for this web
  services i
  am a client. The client for this Web Services is made with Axis 1.4.
 
  I can say that all works fine but when we boot the web server (tomcat
  and i
  have also test in JBoss) the client for this web services don´t work it
  raises
 
  AxisFault
  faultCode:
  {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
  faultSubcode:
  faultString: java.net.ConnectException: Connection timed out (errno:238)
  faultActor:
  faultNode:
  faultDetail:
  {http://xml.apache.org/axis/}stackTrace:java.net.ConnectException:
  Connection timed out (errno:238)
 
  When trying to connect to the external Web Services. The rest of the
  methods
  i publish in Axis2 if they don´t have to call these external web
  services,
  works fine.
 
  Tomcat server 6 and jdk 1.5 (also tested with 1.6)
 
  I´m becoming crazy because this source code works fine until a boot is
  made
  and after that calling external web services don´t work. To make it work
  i
  have to undeploy mi Web Service un Axis2 an redeploy and sometimes i
  also
  have to redeploy Axis2.
 
  Any idea please?
 
  Thanks in advance
  Oscar

 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org



 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Errnn238 after boot calling web services

[Andreas Veithen]

The problem is that the following line in the stack trace is in the
code path that is executed for direct connections:

at 
org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:120)

How do you configure the HTTP proxy to be used by your Web application?

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 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,
  Oscar



 From: andreas.veit...@gmail.com
 Date: Sun, 11 Nov 2012 20:09:56 +0100

 Subject: Re: Errnn238 after boot calling web services
 To: java-user@axis.apache.org


 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 a Web Service with Axis2 that publish several methods. One of
 this
 methods call two external (Internet) Web Services so for this web
 services i
 am a client. The client for this Web Services is made with Axis 1.4.

 I can say that all works fine but when we boot the web server (tomcat
 and i
 have also test in JBoss) the client for this web services don´t work it
 raises

 AxisFault
 faultCode:
 {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.net.ConnectException: Connection timed out (errno:238)
 faultActor:
 faultNode:
 faultDetail:
 {http://xml.apache.org/axis/}stackTrace:java.net.ConnectException:
 Connection timed out (errno:238)

 When trying to connect to the external Web Services. The rest of the
 methods
 i publish in Axis2 if they don´t have to call these external web
 services,
 works fine.

 Tomcat server 6 and jdk 1.5 (also tested with 1.6)

 I´m becoming crazy because this source code works fine until a boot is
 made
 and after that calling external web services don´t work. To make it work
 i
 have to undeploy mi Web Service un Axis2 an redeploy and sometimes i
 also
 have to redeploy Axis2.

 Any idea please?

 Thanks in advance
 Oscar

 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org



 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org

 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Errnn238 after boot calling web services

[Andreas Veithen]

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 a Web Service with Axis2 that publish several methods. One of this
 methods call two external (Internet) Web Services so for this web services i
 am a client. The client for this Web Services is made with Axis 1.4.

 I can say that all works fine but when we boot the web server (tomcat and i
 have also test in JBoss) the client for this web services don´t work it
 raises

 AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode:
 faultString: java.net.ConnectException: Connection timed out (errno:238)
 faultActor:
 faultNode:
 faultDetail:
 {http://xml.apache.org/axis/}stackTrace:java.net.ConnectException:
 Connection timed out (errno:238)

 When trying to connect to the external Web Services. The rest of the methods
 i publish in Axis2 if they don´t have to call these external web services,
 works fine.

 Tomcat server 6 and jdk 1.5 (also tested with 1.6)

 I´m becoming crazy because this source code works fine until a boot is made
 and after that calling external web services don´t work. To make it work i
 have to undeploy mi Web Service un Axis2 an redeploy and sometimes i also
 have to redeploy Axis2.

 Any idea please?

 Thanks in advance
 Oscar

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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
JAX-RPC mapping (i.e. is unsupported), then the derived type itself is
unsupported.

In your case, Int1_15 should therefore be mapped to long.

I think that the rationale for this requirement is that restriction
relationships in XML Schema should be mapped to inheritance
relationships in Java. This is easy for complex types because a
complex type is mapped to a generated class which can be inherited. On
the other hand, simple types are mapped to primitive types, wrapper
types or String, and none of them can be inherited.

Andreas


On Wed, Nov 7, 2012 at 1:19 PM, vera_83 vera...@abv.bg wrote:

 Hello,

 I'm using axis-1_4 and jdk 1.4. I'm trying to generate java classes from
 wsdl file.
 I'm executing: java org.apache.axis.wsdl.WSDL2Java -a -u -s -w
 my_service.wsdl.
 No error appears during the command execution but some java classes are
 missing, for example:

 xsd:simpleType name=Int1_15
 xsd:annotationxsd:documentationInteger
 (1-15)/xsd:documentation/xsd:annotation
 xsd:restriction base=xsd:long
 xsd:minInclusive value=1/
 xsd:maxInclusive value=15/
 /xsd:restriction
 /xsd:simpleType

 No class named Int1_15 is generated.

 Can someone help me with that?

 Thank you.
 --
 View this message in context: 
 http://old.nabble.com/wsdl2java-in-axis-1_4-does-not-generate-simpleType-tp34651517p34651517.html
 Sent from the Axis - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: AXIS 1.4 SOCKET CLOSED

[Andreas Veithen]

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 working fine to this host before this error's
 occurrence, and after a instance restart, this restores and comes back to
 normal. Axis.jar version - 1.4 Sample stack trace java.net.SocketException:
 Socket is closed java.net.SocketException: Socket is closed
 java.net.Socket.getInputStream(Socket.java(Compiled Code)) We need your help
 to debug further on this issue. Thanks, Sriram.V
 
 View this message in context: AXIS 1.4 SOCKET CLOSED
 Sent from the Axis - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 AGAZZI
filippo.aga...@studenti.unipr.it wrote:
 Hi,
 i've got a big problem with this: i wanto to do sth like this.

 FileInputStream policyStream = null;
 try {
 policyStream = new FileInputStream (policy_file);
 } catch (FileNotFoundException e) {
 e.printStackTrace();
 }
 StAXOMBuilder stAXOMBuilder = new
 StAXOMBuilder(policyStream);
 OMElement documentElement =
 stAXOMBuilder.getDocumentElement();

 tnPolicyColl.addChild(documentElement);
 where tnPolicyColl is an OMElement created with a determinate OMFactory.

 But i get an error  WRONG_DOCUMENT_ERR: A node is used in a different
 document than the one that created it. By many searches i understand that
 thw two OMElement must have the same OMFactory. But, the problem is: how can
 i do this, when i need to attach as a child an OMElement created from a
 source, that is a n XML File? I try also this:

 FileReader soapFileReader = new FileReader(policy_file);
 XMLStreamReader parser =
 XMLInputFactory.newInstance().createXMLStreamReader(soapFileReader);
 StAXOMBuilder stAXOMBuilder =  new StAXOMBuilder(omFactory,
 parser);
 OMElement documentElement =
 stAXOMBuilder.getDocumentElement();

 But it didn't work. How can i creat an AXIOM object, with a child created
 from XML File? Please help me, i'm in big trouble!
 Thanks in advance,
 Agazzi

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

 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. If you use that pattern together with a
container managed connection pool, then it becomes an anti-pattern.

Andreas

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Questions: 1.7.0

[Andreas Veithen]

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 site is not deployed to an Apache HTTPD sever, that
doesn't work. Note that this will not be fixed because the goal of
that snapshot site is merely to allow developers to get a preview of
the site and occasionally point users to documentation that has not
yet been published.

Andreas

On Sun, Sep 9, 2012 at 7:31 AM, Ryon Day ryon_...@yahoo.com wrote:
 Hello all, I've been a happy Axis user for a few years now; my company 
 leverages a few commercial SOAP-based web services quite often, and Axis has 
 treated me quite well in my development endeavors; I find it far more 
 straightforward than CXF, and ADB nicer on the eyes than the other 
 databindings, so thanks for everything!

 I recently came across 1.7.0 quite randomly, as it's on the various Maven 
 repos, and I have a few questions around it:
 1: 1.7.0 is not on the main Apache Axis site, and there is in fact no mention 
 of it at all. Has it not been officially released?
 2: The download link is completely broken on the 1.7.0 site; it appears to be 
 some sort of permissions problem on the server
 3: A presentation I found touted 1.7.0 leveraging of Lists, Generics, and 
 real Java Enum objects. However, after downloading a 1.7.0-SNAPSHOT package 
 and running wsdl2java on a few of the WSDLs we deal with, I was sad to see 
 that the ADB client still had the same old arrays and typesafe-enum pattern 
 things, even for types explicitly labeled as enumeration in the WSDLs. 
 XMLBeans seemingly has always had support for 1.5-type stuff. Was I 
 leveraging wsdl2java incorrectly in this case? I did not see an additional 
 command line switch for ADB to use this sweet, sweet syntactic sugar.

 Thanks a lot!

 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 case on WebLogic, then you need to
check the WebLogic documentation to see how to do this.

Andreas

On Tue, Aug 28, 2012 at 11:22 AM, Jan Swaelens jan.swael...@sofico.be wrote:
 Hi,

 It is giving me: weblogic.xml.stax.XMLStreamInputFactory

 This is on a WebLogic server, we also deploy on WebSphere and JBOSS -- some
 approach that would work on all app servers would be great!

 thanks


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 code that calls
XMLInputFactory.newInstance() and that shows the type of the returned
instance?

Andreas

On Mon, Aug 27, 2012 at 8:54 AM, Jan Swaelens jan.swael...@sofico.be wrote:
 Hi,

 I looked a bit further and found the woodstox jar (wstx-asl-3.2.9.jar) on
 the classpath, should I delete the axiom*.jar instances to enable woodstox
 stax implementation?

 thanks

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 generated with axis2 version 1.5.3.

 Somehow the stub generates the XML containing an element badly causing the
 XML to be invalid.

 This is how it comes out (notice bad content inside ExecuteRequest):

 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
 ns1:ExecuteRequest xmlns:ns1=http://services.bkr.nl/servicesv2/;
   ns1:http://services.bkr.nl/servicesv2/
!-- here comes our message --
   /ns1:http://services.bkr.nl/servicesv2/
 /ns1:ExecuteRequest
/soapenv:Body
 /soapenv:Envelope

 This is how it is supposed to come out (notice the xmlMessage element as it
 should be outputted):

 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
   ns1:ExecuteRequest xmlns:ns1=http://services.bkr.nl/servicesv2/;
  xmlMessage
!-- here comes our message --
  /xmlMessage
   /ns1:ExecuteRequest
/soapenv:Body
 /soapenv:Envelope


 We generate the stub with this command:
 wsdl2java.bat -uri ../mywsdl/BKRService2.wsdl -o ../myoutput -s -uw -p
 be.sofico.nl.iface.bkr.verification -or

 We invoke the 'ExecuteRequest' operation

 This is the wsdl:

 ?xml version=1.0 encoding=utf-8?
 wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
 xmlns:tm=http://microsoft.com/wsdl/mime/textMatching/;
 xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/;
 xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
 xmlns:tns=http://services.bkr.nl/servicesv2/;
 xmlns:s=http://www.w3.org/2001/XMLSchema;
 xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
 xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
 targetNamespace=http://services.bkr.nl/servicesv2/;
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
 wsdl:documentation
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;Provides an interface for
 performing CKI, LIS toetsing and registration/wsdl:documentation
 wsdl:types
 s:schema elementFormDefault=qualified
 targetNamespace=http://services.bkr.nl/servicesv2/;
 s:element name=ExecuteRequest
 s:complexType
 s:sequence
 s:element minOccurs=0 maxOccurs=1
 name=xmlMessage
 s:complexType mixed=true
 s:sequence
 s:any /
 /s:sequence
 /s:complexType
 /s:element
 /s:sequence
 /s:complexType
 /s:element
 s:element name=ExecuteRequestResponse
 s:complexType
 s:sequence
 s:element minOccurs=0 maxOccurs=1
 name=ExecuteRequestResult
 s:complexType mixed=true
 s:sequence
 s:any /
 /s:sequence
 /s:complexType
 /s:element
 /s:sequence
 /s:complexType
 /s:element
 s:element name=ExecuteRequestCompressed
 s:complexType
 s:sequence
 s:element minOccurs=0 maxOccurs=1
 name=xmlMessage
 s:complexType mixed=true
 s:sequence
 s:any /
 /s:sequence
 /s:complexType
 /s:element
 /s:sequence
 /s:complexType
 /s:element
 s:element name=ExecuteRequestCompressedResponse
 s:complexType
 s:sequence
 s:element minOccurs=0 maxOccurs=1
 name=ExecuteRequestCompressedResult
 s:complexType mixed=true
 s:sequence
 s:any /
 /s:sequence
 /s:complexType
 /s:element
 /s:sequence
 /s:complexType
 /s:element
 /s:schema
 /wsdl:types
 wsdl:message name=ExecuteRequestSoapIn
 wsdl:part name=parameters element=tns:ExecuteRequest /
 /wsdl:message
 wsdl:message name=ExecuteRequestSoapOut
 wsdl:part name=parameters element=tns:ExecuteRequestResponse /
 /wsdl:message
 wsdl:message name=ExecuteRequestCompressedSoapIn
 wsdl:part name=parameters 

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

[Andreas Veithen]

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 serializer.jar from Xerces. This
 might have something to do with my configuration.

 2)  I got a policy related bug:

 a.   My setup

i.
 Context:
 ConfigurationContextFactory.createConfigurationContextFromURIs(null, null);

  ii.
 Rampart module engaged

 1.   client.engageModule(rampart);

 iii.
 Microsoft WCF SOAP server

 b.  My Solution – see [1] and [2]

i.  I
 replaced the getPolicy function [1]

  ii.
 Performed a find replace on sp:policy and /sp:policy to wsp:policy and
 /wsp:policy respectively [2].





 [1]
 http://stackoverflow.com/questions/8364193/illegalargumentexception-protectiontoken-is-not-a-wsppolicy-element

 [2] http://markmail.org/thread/6hhk72zzgtba5y3v





 What are the benefits of 1.6.2 over 1.5.6 for a client?





 James Annesley

 Lead “User Interface” Developer



 Office: +44 (0) 208 541 0111

 Email: james.annes...@infoshare-is.com



 information is everything



 Infoshare Limited

 Millennium House

 21 Eden Street

 Kingston upon Thames

 Surrey

 KT1 1BL

 United Kingdom



 www.infoshare-is.com/



 
 The content of this e-mail (and any attachment to it) is confidential. Any
 views or opinions do not represent the views or opinions of Infoshare Ltd.
 If you have received this e-mail in error please notify the sender and
 delete it. You may not use, copy or disclose the information in any way.
 Infoshare Ltd monitors incoming and outgoing e-mails. Please consider the
 environment. Do you really need to print this email?

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Servlet failed with IOException

[Andreas Veithen]

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
 other than Iterator#remove()
 at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
 at org.apache.axis2.description.AxisService.getWSDL(AxisService.java:1653)
 at org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1413)
 at
 org.apache.axis2.transport.http.ListingAgent.handleWSDLRequest(ListingAgent.java:327)
 at
 org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:183)
 Truncated. see log file for complete stacktrace
 Caused By: java.util.ConcurrentModificationException: The current node has
 been removed using a method other than Iterator#remove()
 at
 org.apache.axiom.om.impl.traverse.OMAbstractIterator.hasNext(OMAbstractIterator.java:67)
 at
 org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:555)
 at
 org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:874)
 at
 org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:556)
 at
 org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:874)
 Truncated. see log file for complete stacktrace

 Can you help me with this, please?
 Thank you.




-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Servlet failed with IOException

[Andreas Veithen]

The stack trace indicates that the error doesn't occur while invoking
the service, but while fetching the WSDL. There have been thread
safety issues in that part of the code:

https://issues.apache.org/jira/browse/AXIS2-3276

This would explain the sporadic nature of the issue.

Andreas

On Thu, 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 Veithen andreas.veit...@gmail.com

 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
  other than Iterator#remove()
  at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
  at
  org.apache.axis2.description.AxisService.getWSDL(AxisService.java:1653)
  at
  org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1413)
  at
 
  org.apache.axis2.transport.http.ListingAgent.handleWSDLRequest(ListingAgent.java:327)
  at
 
  org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:183)
  Truncated. see log file for complete stacktrace
  Caused By: java.util.ConcurrentModificationException: The current node
  has
  been removed using a method other than Iterator#remove()
  at
 
  org.apache.axiom.om.impl.traverse.OMAbstractIterator.hasNext(OMAbstractIterator.java:67)
  at
 
  org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:555)
  at
 
  org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:874)
  at
 
  org.apache.axiom.om.impl.util.OMSerializerUtil.serializeChildren(OMSerializerUtil.java:556)
  at
 
  org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:874)
  Truncated. see log file for complete stacktrace
 
  Can you help me with this, please?
  Thank you.
 
 
 

 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org




 --
 José Ma. Gómez M.
 Desarrollador
 0412-243-6245


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: [axis2-1.6.1] ERRORS during undeployment

[Andreas Veithen]

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
josef.stadelm...@axa-winterthur.ch wrote:
 I have a axis2 JAXWS Application departing from the MTOM Sample of Axis2. I
 run on Vista and OpenVMS under JDK 6.0 and Axis2-16.1.

 Depolyment is error free, however undeployment or stop causes output from
 Tomcat as shown below.

 How can I prevent that?

 I am not so knowleged about ThreadLocal's? Where's a good ref/wiki about
 that?

 Any references are welcome but mainly:

 How can I avoid this errors from showing up?

 Josef

 INFO: Manager: undeploy: Undeploying web application at '/SpezplaFS'

 25.07.2012 14:58:10 org.apache.catalina.loader.WebappClassLoader
 clearThreadLocalMap

 SCHWERWIEGEND: A web application created a ThreadLocal with key of type
 [null] (value [org.apache.axiom.util.UIDGenerator$1@1727745]) and a value of
 type [long[]] (value [[J@1f480e3]) but failed to remove it when the web
 application was stopped. To prevent a memory leak, the ThreadLocal has been
 forcibly removed.

 25.07.2012 14:58:10 org.apache.catalina.loader.WebappClassLoader
 clearThreadLocalMap

 SCHWERWIEGEND: A web application created a ThreadLocal with key of type
 [java.lang.InheritableThreadLocal] (value
 [java.lang.InheritableThreadLocal@139ed6d]) and a value of type
 [org.apache.axis2.jaxws.addressing.util.EndpointContextMap] (value
 [{Service: {http://ch/axa/spezpla/fs1/}MtomFileService12, Port:
 {http://ch/axa/spezpla/fs1/}MtomFilePort=MtomFileService12, Service:
 {http://ch/axa/spezpla/fs1/}MtomFileService, Port:
 {http://ch/axa/spezpla/fs1/}MtomFilePort=MtomFileService}]) but failed to
 remove it when the web application was stopped. To prevent a memory leak,
 the ThreadLocal has been forcibly removed.

 25.07.2012 14:58:10 org.apache.catalina.loader.WebappClassLoader
 clearThreadLocalMap

 SCHWERWIEGEND: A web application created a ThreadLocal with key of type
 [java.lang.InheritableThreadLocal] (value
 [java.lang.InheritableThreadLocal@139ed6d]) and a value of type
 [org.apache.axis2.jaxws.addressing.util.EndpointContextMap] (value
 [{Service: {http://ch/axa/spezpla/fs1/}MtomFileService12, Port:
 {http://ch/axa/spezpla/fs1/}MtomFilePort=MtomFileService12, Service:
 {http://ch/axa/spezpla/fs1/}MtomFileService, Port:
 {http://ch/axa/spezpla/fs1/}MtomFilePort=MtomFileService}]) but failed to
 remove it when the web application was stopped. To prevent a memory leak,
 the ThreadLocal has been forcibly removed.

 25.07.2012 14:58:10 org.apache.catalina.loader.WebappClassLoader
 clearThreadLocalMap

 SCHWERWIEGEND: A web application created a ThreadLocal with key of type
 [java.lang.InheritableThreadLocal] (value
 [java.lang.InheritableThreadLocal@139ed6d]) and a value of type
 [org.apache.axis2.jaxws.addressing.util.EndpointContextMap] (value
 [{Service: {http://ch/axa/spezpla/fs1/}MtomFileService12, Port:
 {http://ch/axa/spezpla/fs1/}MtomFilePort=MtomFileService12, Service:
 {http://ch/axa/spezpla/fs1/}MtomFileService, Port:
 {http://ch/axa/spezpla/fs1/}MtomFilePort=MtomFileService}]) but failed to
 remove it when the web application was stopped. To prevent a memory leak,
 the ThreadLocal has been forcibly removed.

 25.07.2012 14:58:10 org.apache.catalina.loader.WebappClassLoader
 clearThreadLocalMap

 SCHWERWIEGEND: A web application created a ThreadLocal with key of type
 [java.lang.InheritableThreadLocal] (value
 [java.lang.InheritableThreadLocal@139ed6d]) and a value of type
 [org.apache.axis2.jaxws.addressing.util.EndpointContextMap] (value
 [{Service: {http://ch/axa/spezpla/fs1/}MtomFileService12, Port:
 {http://ch/axa/spezpla/fs1/}MtomFilePort=MtomFileService12, Service:
 {http://ch/axa/spezpla/fs1/}MtomFileService, Port:
 {http://ch/axa/spezpla/fs1/}MtomFilePort=MtomFileService}]) but failed to
 remove it when the web application was stopped. To prevent a memory leak,
 the ThreadLocal has been forcibly removed.

 25.07.2012 14:58:10 org.apache.catalina.loader.WebappClassLoader
 clearThreadLocalMap

 SCHWERWIEGEND: A web application created a ThreadLocal with key of type
 [java.lang.InheritableThreadLocal] (value
 [java.lang.InheritableThreadLocal@139ed6d]) and a value of type
 [org.apache.axis2.jaxws.addressing.util.EndpointContextMap] (value
 [{Service: {http://ch/axa/spezpla/fs1/}MtomFileService12, Port:
 {http://ch/axa/spezpla/fs1/}MtomFilePort=MtomFileService12, Service:
 {http://ch/axa/spezpla/fs1/}MtomFileService, Port:
 {http://ch/axa/spezpla/fs1/}MtomFilePort=MtomFileService}]) but failed to
 remove it when the web application was stopped. To prevent a memory leak,
 the ThreadLocal has been forcibly removed.

 25.07.2012 14:58:10 org.apache.catalina.loader.WebappClassLoader
 clearThreadLocalMap

 SCHWERWIEGEND: A web application created a ThreadLocal with key of type
 

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

[Andreas Veithen]

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:

 http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.nd.doc%2Finfo%2Fae%2Fae%2Ftwbs_thirdparty.html

 I'll be back :)


 --
 View this message in context: 
 http://old.nabble.com/JAX-WS-client-and-service-with-Rampart-module-for-signing-messages-tp34070987p34096102.html
 Sent from the Axis - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Help

[Andreas Veithen]

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 org.apache.axis.enum.Style;
 gives me this Error:
 Syntax error on token enum, Identifier expected

 String nsOp = call.getOperationStyle().equals(Style.RPC) ? u : ;
 gives me this Error:
 The type org.apache.axis.enum.Style cannot be resolved. It is indirectly
 referenced from required .class files


 Please, help me, I am really blocked

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: axistools-maven-plugin - getServiceClient()

[Andreas Veithen]

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 request because there is no method
 in the generated client stubs which gives me serviceClient.  Can anyone
 please tell me how to get serviceClient and set Options using the generated
 sources with this plugin.

 if(options == null){
 options = new Options();
 client._getServiceClient().setOptions(options);  //This doesn't work with
 axistools-maven-plugin
 }
 options.setProperty(HTTPConstants.HTTP_HEADERS,myheaders);

 This is the plugin I am using.

 plugin
 groupIdorg.codehaus.mojo/groupId
 artifactIdaxistools-maven-plugin/artifactId
 version1.4/version
 configuration
 !-- SourceDirectory should only refer to the 
 directory where the wsdl
 resides and not the actual 
 wsdl file itself --
 
 sourceDirectorysrc/main/resources/wsdl//sourceDirectory

 outputDirectory${project.build.directory}/generated-sources//outputDirectory
 
 packageSpacecom.myservice/packageSpace
 serverSidefalse/serverSide
 /configuration
 executions
 execution
 goals
 goalwsdl2java/goal
 /goals
 /execution
 /executions
 /plugin
 --
 View this message in context: 
 http://old.nabble.com/axistools-maven-plugin---getServiceClient%28%29-tp34159284p34159284.html
 Sent from the Axis - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: How to get a formatted OMElement content

[Andreas Veithen]

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, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
 Maybe that one helps

 http://stackoverflow.com/questions/1384802/java-how-to-indent-xml-generated-by-transformer

 Josef –

 there is a lot more in Google,

 also if you feed your stream into a file.xml and

 pass that file.xml to an InternetExplorer

 IE will format itself for display purpose.







 Von: Flavio Palumbo [mailto:flavio.palumb...@gmail.com]
 Gesendet: Mittwoch, 11. Juli 2012 15:01
 An: java-user@axis.apache.org
 Betreff: How to get a formatted OMElement content



 Hi all,

 how can I get a formatted XML from an OMElement ?

 For now I use the toString method but I get XML in one row, while Iwould
 like to have it with line breaks.

 Any hint would be appreciated.


 Flavio

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

We cannot change versions that have already been released. Therefore
the change is currently only available in trunk. Note that only
Rampart has this issue. Axis2 is unaffected.

Andreas

On Mon, Jul 9, 2012 at 1:22 PM, Stadelmann Josef
josef.stadelm...@axa-winterthur.ch wrote:
 Thank you very 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: Donnerstag, 5. Juli 2012 21:35
 An: java-user@axis.apache.org
 Betreff: Re: [rampart/opensaml] bad artifacts returned causing mvn builds to 
 fail

 Yes, a few days ago the Shibboleth project moved its repository and
 they did that in such a way that all builds using this repository are
 badly broken.

 I've banned the repository from Rampart trunk and 1.6:

 http://svn.apache.org/viewvc?rev=1357818view=rev
 http://svn.apache.org/viewvc?rev=1357821view=rev

 Andreas

 On Thu, Jul 5, 2012 at 9:55 AM, Stadelmann Josef
 josef.stadelm...@axa-winterthur.ch wrote:
 I am just  struggling to build my project using maven axis2 and rampart
 after I cleared out the local .m2/repository cache.

 Also the problem explained is discussed as well in us...@maven.apache.org
 subject:[mvn] bad artifacts returned

 The issue is as simple as that:

 shibboleth edu has moved theire artifact repository to another placeand

 asking for a POM you get HTML back and status  OK (200)

 in short you always get htm back what ever you ask for!

 The effect becomes visible if you delet your .m2/repository:

 And even when you work with a MRM that one is only a mirror.

 It might have in a cahe what your asking for.

 But once that cache is invalidated (like my m2/repository)

 you go to your MRM and from there to maven central

 and you will be redirected through transitive dependencies

 to the place called shibbolet

 you can not expect that project builds correctly unless you already have all
 artifacts in your local cache .m2/repository

 which is the case for my PC (so projects build there)= but not for my other
 machine.

 AS LONG AS a repository with a url to shibbolte is defined in one of your
 poms as long you will have problem.

 -   be it a direct dependency or indirect, transitive dependencies

 AFAIK: the following 2 artifacts are afected -lead to problems artifact

 org/apache/rampart/rampart-project/1.6.2/rampart-project-1.6.1.*



 repositories

 repository

 releases

 enabledtrue/enabled

 updatePolicyalways/updatePolicy

 checksumPolicywarn/checksumPolicy

 /releases

 snapshots

 enabledtrue/enabled

 updatePolicynever/updatePolicy

 checksumPolicywarn/checksumPolicy

 /snapshots

 idopen-saml/id

 nameOpenSAML/name

 urlhttp://shibboleth.internet2.edu/downloads/maven2//url

 /repository

 /repositories

 And org/opensaml/opensaml/2.2.3/opensaml-2.2.3.*

 has a reference to this bad behaving server as well

repositories

 repository

 idshibboleth.internet2.edu/id

 nameInternet2/name

 layoutdefault/layout

 urlhttp://shibboleth.internet2.edu/downloads/maven2/url

 snapshots

 enabledfalse/enabled

 /snapshots

 /repository

 /repositories

 true for axis2-1.6.2 as well!

 The server at shibbolet behaves bad

 because if I ask a server for a pom

 I do not want a html back with status code OK!

 Just try the following for an artifac you may need sooner than later;:

 http://shibboleth.internet2.edu/downloads/maven2/org/apache/xalan/xalan/2.7.1/xalan-2.7.1.pom

 and there where many more artifacs at shibboleth

 Josef

 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: [axis2-1.6.2] failed to build

[Andreas Veithen]

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 on a axis2-1.6.2 build for  ./tags/v1.6.2 fail.
 Guess: I sit behind a firewall?

 At home, on my old windows 2000 advanced server the same build runs very
 perfect the first time?

 THANK YOU DOING A GREAT JOB

 Josef

 $ mvn clean install

 . . .

 . . .

 ---

  T E S T S

 ---

 Running org.apache.axis2.transport.http.CommonsHTTPTransportSenderTest

 Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.279 sec
  FAILURE!

 Results :

 Failed tests:


 testConnectionReleaseWith404(org.apache.axis2.transport.http.CommonsHTTPTransportSenderTest)

 Tests run: 1, Failures: 1, Errors: 0, Skipped: 0

 [INFO]
 

 [INFO] Reactor Summary:

 [INFO]

 [INFO] Apache Axis2 - Parent . SUCCESS
 [5.116s]

 [INFO] Apache Axis2 - Resource bundle  SUCCESS
 [4.821s]

 [INFO] Apache Axis2 - Kernel . SUCCESS
 [57.267s]

 [INFO] Apache Axis2 - Data Binding ... SUCCESS
 [14.930s]

 [INFO] Apache Axis2 - Transport - Local .. SUCCESS
 [4.617s]

 [INFO] Apache Axis2 - Transport - HTTP ... FAILURE
 [5.632s]

 [INFO] Apache Axis2 - Code Generation  SKIPPED

 [INFO] Apache Axis2 - ADB Codegen  SKIPPED

 [INFO] Apache Axis2 - Addressing . SKIPPED

 [INFO] Apache Axis2 - Java2WSDL .. SKIPPED

 . . .

 . . .

 E:\asf\axis\axis2\java\core\tags\v1.6.2mvn -version

 Apache Maven 3.0.5-SNAPSHOT (r1297401; 2012-03-06 12:23:19+0100)

 Maven home: E:\Users\C770817\SW-UMGEBUNG\apache-maven-3.0.5

 Java version: 1.6.0_30, vendor: Sun Microsystems Inc.

 Java home: E:\Users\C770817\SW-UMGEBUNG\Java\jdk1.6.0_30\jre

 Default locale: de_CH, platform encoding: Cp1252

 OS name: windows vista, version: 6.0, arch: x86, family: windows

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 of response
 element as expected.  I even tried the wsdl file from the ‘version’ service
 but switched to use jaxb binding, still got getVersion and not
 getVersionResponse.  However, programmatically, both the server and client
 side code work pretty well.  I am just puzzled by the xml message (the
 response part) shown in both SoapMonitor and plain browser.



 Is this a feature, a bug, or something I did not follow?



 Thanks,

 Ruey









-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: axis2 mtom attach document to response - help please

[Andreas Veithen]

On Tue, May 22, 2012 at 6:36 PM, eric johnson ejjohn...@gmail.com wrote:
 Thanks - the elementFormDefault isn't declared and I believe the
 default is unqualified.  I've played around quite a bit with those
 arguments for creating the OMNamespace and am less certain that is the
 cause of my error.

In that case you need to pass null as the OMNamespace when creating
the document element.

 I'm not sure why I am not getting an attachment back from the call.
 Is this even possible when working from the generated code in the
 skeleton?  I have found no complete examples of anyone using mtom 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

 On Mon, May 21, 2012 at 10:10 PM, eric johnson ejjohn...@gmail.com wrote:
 Hi,

 I'm having some trouble adding an attachment to my response after
 attempting to follow the instructions here:
 http://axis.apache.org/axis2/java/core/docs/mtom-guide.html#

 The example from that url I am following is:

         OMElement imageElement = fac.createOMElement(image, omNs);

         // Creating the Data Handler for the file.  Any implementation of
         // javax.activation.DataSource interface can fit here.
         javax.activation.DataHandler dataHandler = new
 javax.activation.DataHandler(new FileDataSource(SomeFile));

         //create an OMText node with the above DataHandler and set
 optimized to true
         OMText textData = fac.createOMText(dataHandler, true);

         imageElement.addChild(textData);


 I suspect I am making a mistake in the creation of OMElement and
 OMNameSpace in my code below.

       OMFactory factory = OMAbstractFactory.getOMFactory();
       OMNamespace omNs = factory.createOMNamespace(I put the
 targetNamespace from the wsdl here, ns);
       OMElement documentElement = factory.createOMElement(document, omNs);
       OMText textData = factory.createOMText(documentDataHandler, true);

       documentElement.addChild(textData);

 So what should I be using for the URI and prefix values?  (I realize
 this is probably web services 101, but this is all new to me and a bit
 overwhelming).

 The document element is really part of a GetDocumentResponse type
 defined in my wsdl as:
       xs:element name=GetDocumentResponse
 type=tns:GetDocumentResponseType /

       xs:complexType name=GetDocumentResponseType
         xs:sequence
           xs:element name=mimeType type=xs:string minOccurs=1
 maxOccurs=1/
           xs:element name=documentName type=xs:string
 minOccurs=1 maxOccurs=1/
           xs:element name=storageTimestamp type=tns:sDateTime
 minOccurs=1 maxOccurs=1/
           xs:element name=document type=xs:base64Binary
 minOccurs=1 maxOccurs=1/
         /xs:sequence
       /xs:complexType

 should I use tns:GetDocumentResponse for the prefix when creating
 the OMNamespace object?

 Should I be using the soap:address from the wsdl:service/wsdl:port as the 
 uri?

 Is there anything besides the code example I need to do to complete
 the addition of the attachment?

 Thanks!

 Eric

 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 versions (but there will then likely
be a well defined API to convert an attachment to a file). For more
information see [1].

Andreas

[1] http://ws.apache.org/axiom/devguide/ch03.html

On Fri, May 18, 2012 at 12:21 AM, eric johnson ejjohn...@gmail.com wrote:
 Hi,

 I've set up file caching for attachments by following these instructions:

 http://axis.apache.org/axis2/java/core/docs/mtom-guide.html#a4

 I need a way to programmatically know what the name of the file that was
 created is so that in my web services skeleton I can process the file. How
 can this be accomplished?

 I have seen the files that are generated have names such as:

 axiomfc4c46332e06dfee16108281aab8ab7c5f1685e8d6ea7ca8.att

 Thanks,

 Eric

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Axis2 - JSON mapped - namespace (mismatch)

[Andreas Veithen]

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 from the input stream
         if there is not prefix, message starts like {foo:
         if there is a prefix, message starts like {prefix:foo:
          */
                                         :
             //if the part we read ends with , there is no prefix,
 otherwise it has a prefix
                                         :
                     prefix = localName.substring(1, localName.length()) +
 :;



                                       :


 What are these prefixes used for (separated by colon) if they have nothing
 to do with namespaces?
 Are they part of some JSON format?


 Yes, This is for handle namespaces in badgerfish convention. where it
 separate prefix and localname by a ':' colon.



 And finally, is there a fundamental reason why:
         “Mapped” formatted JSON with namespaces are not supported in Axis2


 Axis2 uses Axiom as XML info-set representation for SOAP messages. That
 means, to process the request it should have clear XML info-set with it. It
 is not possible to know the namespace mappings used on one side of the
 transport to the other side when we use mapped convention.

 Actually this may be much simpler to implement than we thought. I
 modified the code so that it now uses the new feature introduced by
 AXIOM-399. This means that the OMDataSource is expanded when the name
 of the element is first requested. I would expect that this occurs in
 the code that dispatches to the service operation. At that point the
 service should already be set in the message context. If that is
 correct, then this means that at the time the OMDataSource is
 expanded, the service to which the request is dispatched is already
 known. We could then get the namespace mappings from a service
 parameter that the user must configure in services.xml.

I implemented that design and both Badgerfish and mapped JSON are now
working (although there is still a potential performance issue to
solve). See my last comment in AXIS2-5158 for more information about
how to set up an Axis2 service to work with mapped JSON.

 Thanks
 Shameera.


 Or is it just a resource issue, and someone (may be I) could add some
 stuff to support namespaces and maybe databinding.

 Thanks and regards
 Matthias



 From:        Shameera Rathnayaka shameerai...@gmail.com
 To:        java-user@axis.apache.org,
 Date:        26-04-2012 19:40
 Subject:        Re: Axis2 - JSON mapped - namespace (mismatch)
 



 Hi Matthias,

 According to the documentation [1] it simply says that “Mapped” formatted
 JSON with namespaces are not supported in Axis2, I think you already have
 got this point. Let me explain how current implementation of axis2 expect
 mapped Json strings.

 The best way to demonstrate this is a short example,
 assume you need to send following xml ,

 price xmlns=http://acme.com;10.00/price

 Using the mapped convention this can be turned into:

 { acme.price : { 10.00 } where http://acme.com -- acme

 as axis2 doesn't support namesapce mapping it expect this as

 { price : { 10.00 }
 That is why it checks always ':' colon instaed of '.' to get the
 localname.

 [1] http://wso2.org/library/768

 Thanks,
 Shameera.


 On Thu, Apr 26, 2012 at 6:29 PM, ger...@slf.ch wrote:
 Hi

 I'm trying to get my SOAP web service to run using mapped JSON instead of
 XML.
 Because it is not that obvious when moving to JSON, what works and what
 does not, I had to do some drilling down in to the code.
 I got a sample Service running based in an
 org.apache.axis2.receivers.RawXMLINOutMessageReceiver.
 But that's not the way to implement web services in these days.
 Basically, as AXIS is designed, we should be able to use databinding, as
 soon as we get the JSON stuff properly converted in to XML.
 This seams not to be the case at the moment (namespace mismatch)

 So i though about writing a wrapper around my generated skeleton and
 adding the correct namespaces myself, based on the prefixes used in the
 mapped JSON.

 Now it is where i get confused.
 In the documentation is mentioned to us a full stop . to separate
 namespace-pefix from element name.
         http://axis.apache.org/axis2/java/core/docs/json_support.html
 When i look at the code, I see, that there a colon : is expected to
 separate the prefix from the element name.
         See org.apache.axis2.json.AbstractJSONOMBuilder line 116 to 143

 When I use a full stop . I get an error, that the method is not found
 (Axis is looking for the howl thing, prefix and element name)
 When I use a colon : I get the an error in the data binding (this is ok,
  because of the mismatching namespace issue and when i get the prefixed
 matched to the correct

Re: Axis2 - JSON mapped - namespace (mismatch)

[Andreas Veithen]

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:
         if there is a prefix, message starts like {prefix:foo:
          */
                                         :
             //if the part we read ends with , there is no prefix,
 otherwise it has a prefix
                                         :
                     prefix = localName.substring(1, localName.length()) +
 :;



                                       :


 What are these prefixes used for (separated by colon) if they have nothing
 to do with namespaces?
 Are they part of some JSON format?


 Yes, This is for handle namespaces in badgerfish convention. where it
 separate prefix and localname by a ':' colon.



 And finally, is there a fundamental reason why:
         “Mapped” formatted JSON with namespaces are not supported in Axis2


 Axis2 uses Axiom as XML info-set representation for SOAP messages. That
 means, to process the request it should have clear XML info-set with it. It
 is not possible to know the namespace mappings used on one side of the
 transport to the other side when we use mapped convention.

Actually this may be much simpler to implement than we thought. I
modified the code so that it now uses the new feature introduced by
AXIOM-399. This means that the OMDataSource is expanded when the name
of the element is first requested. I would expect that this occurs in
the code that dispatches to the service operation. At that point the
service should already be set in the message context. If that is
correct, then this means that at the time the OMDataSource is
expanded, the service to which the request is dispatched is already
known. We could then get the namespace mappings from a service
parameter that the user must configure in services.xml.

 Thanks
 Shameera.


 Or is it just a resource issue, and someone (may be I) could add some
 stuff to support namespaces and maybe databinding.

 Thanks and regards
 Matthias



 From:        Shameera Rathnayaka shameerai...@gmail.com
 To:        java-user@axis.apache.org,
 Date:        26-04-2012 19:40
 Subject:        Re: Axis2 - JSON mapped - namespace (mismatch)
 



 Hi Matthias,

 According to the documentation [1] it simply says that “Mapped” formatted
 JSON with namespaces are not supported in Axis2, I think you already have
 got this point. Let me explain how current implementation of axis2 expect
 mapped Json strings.

 The best way to demonstrate this is a short example,
 assume you need to send following xml ,

 price xmlns=http://acme.com;10.00/price

 Using the mapped convention this can be turned into:

 { acme.price : { 10.00 } where http://acme.com -- acme

 as axis2 doesn't support namesapce mapping it expect this as

 { price : { 10.00 }
 That is why it checks always ':' colon instaed of '.' to get the
 localname.

 [1] http://wso2.org/library/768

 Thanks,
 Shameera.


 On Thu, Apr 26, 2012 at 6:29 PM, ger...@slf.ch wrote:
 Hi

 I'm trying to get my SOAP web service to run using mapped JSON instead of
 XML.
 Because it is not that obvious when moving to JSON, what works and what
 does not, I had to do some drilling down in to the code.
 I got a sample Service running based in an
 org.apache.axis2.receivers.RawXMLINOutMessageReceiver.
 But that's not the way to implement web services in these days.
 Basically, as AXIS is designed, we should be able to use databinding, as
 soon as we get the JSON stuff properly converted in to XML.
 This seams not to be the case at the moment (namespace mismatch)

 So i though about writing a wrapper around my generated skeleton and
 adding the correct namespaces myself, based on the prefixes used in the
 mapped JSON.

 Now it is where i get confused.
 In the documentation is mentioned to us a full stop . to separate
 namespace-pefix from element name.
         http://axis.apache.org/axis2/java/core/docs/json_support.html
 When i look at the code, I see, that there a colon : is expected to
 separate the prefix from the element name.
         See org.apache.axis2.json.AbstractJSONOMBuilder line 116 to 143

 When I use a full stop . I get an error, that the method is not found
 (Axis is looking for the howl thing, prefix and element name)
 When I use a colon : I get the an error in the data binding (this is ok,
  because of the mismatching namespace issue and when i get the prefixed
 matched to the correct namespaces this should be solved.)

 Before I try to work around the mismatching namespace issue I really would
 like to know,
 how this is supposed to work with prefix, how prefix and element-name are
 separated, what prefixes are used for and what axis does with them.

 Thanks for your help and best regards
 Matthias



 --
 Shameera Rathnayaka
 

Re: Axis2 - JSON mapped - namespace (mismatch)

[Andreas Veithen]

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 from the input stream
         if there is not prefix, message starts like {foo:
         if there is a prefix, message starts like {prefix:foo:
          */
                                         :
             //if the part we read ends with , there is no prefix,
 otherwise it has a prefix
                                         :
                     prefix = localName.substring(1, localName.length()) +
 :;



                                       :


 What are these prefixes used for (separated by colon) if they have nothing
 to do with namespaces?
 Are they part of some JSON format?


 Yes, This is for handle namespaces in badgerfish convention. where it
 separate prefix and localname by a ':' colon.



 And finally, is there a fundamental reason why:
         “Mapped” formatted JSON with namespaces are not supported in Axis2


 Axis2 uses Axiom as XML info-set representation for SOAP messages. That
 means, to process the request it should have clear XML info-set with it. It
 is not possible to know the namespace mappings used on one side of the
 transport to the other side when we use mapped convention.

 Actually this may be much simpler to implement than we thought. I
 modified the code so that it now uses the new feature introduced by
 AXIOM-399. This means that the OMDataSource is expanded when the name
 of the element is first requested. I would expect that this occurs in
 the code that dispatches to the service operation. At that point the
 service should already be set in the message context. If that is
 correct, then this means that at the time the OMDataSource is
 expanded, the service to which the request is dispatched is already
 known. We could then get the namespace mappings from a service
 parameter that the user must configure in services.xml.

I did a quick test and it appears that there are two locations where
Axis2 attempts to get the name of the element in the SOAP body
(causing expansion of the OMSourcedElement for JSON). The first one is
here:

at 
org.apache.axis2.json.AbstractJSONDataSource.getReader(AbstractJSONDataSource.java:50)
at 
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpand(OMSourcedElementImpl.java:253)
at 
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.ensureLocalNameSet(OMSourcedElementImpl.java:494)
at 
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getLocalName(OMSourcedElementImpl.java:500)
at 
org.apache.axiom.soap.impl.llom.SOAPBodyImpl.getFirstElementLocalName(SOAPBodyImpl.java:224)
at 
org.apache.axiom.soap.impl.llom.SOAPBodyImpl.hasFault(SOAPBodyImpl.java:99)
at 
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.hasFault(SOAPEnvelopeImpl.java:288)
at 
org.apache.axis2.context.MessageContext.isFault(MessageContext.java:4303)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:154)
at 
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:176)
at 
org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:307)
at 
org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281)
at 
org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187)
at 
org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)

This is very early in the processing (when the service has not yet
been determined) and the purpose is to check if the message contains a
SOAP fault. One may wonder why the code the element name instead of
the element type (SOAPFault). This appears to be related to a
particular optimization that is important in another scenario. I think
that this can be improved so that it interacts better with the feature
introduced by AXIOM-399, i.e. so that it doesn't require expansion of
the OMSourcedElement.

The second location is here:

at 
org.apache.axis2.json.AbstractJSONDataSource.getReader(AbstractJSONDataSource.java:50)
at 
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.forceExpand(OMSourcedElementImpl.java:253)
at 
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.ensureLocalNameSet(OMSourcedElementImpl.java:494)
at 
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.getLocalName(OMSourcedElementImpl.java:500)
at 
org.apache.axiom.soap.impl.llom.SOAPBodyImpl.getFirstElementLocalName(SOAPBodyImpl.java

Re: Axis2 - JSON mapped - namespace (mismatch)

[Andreas Veithen]

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 that part of
the code. Note however that I recently implemented a feature in Axiom
(see AXIOM-399) that is important in order to improve the JSON support
and I was going to work on the code anyway to test that new feature in
Axiom. You are of course welcome to help testing and why not
contributing code.

Andreas

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Policy not supported: is it a bug ?

[Andreas Veithen]

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
seeing.

2. When generating client code, Axis2 doesn't simply copy the policy
from the WSDL. It actually re-serializes the model created by Neethi
from the original policy. The problem is that in all released Rampart
versions (i.e. all versions up to and including 1.6.1), the code
responsible for serializing the policy has some issues that cause it
to produce invalid serialized policies in some cases. These invalid
policies are accepted by Neethi 2, but not by Neethi 3. That problem
has been fixed in Rampart 1.6.2-SNAPSHOT and 1.7.0-SNAPSHOT.

Therefore the problem should only exist in Axis2/Rampart 1.6.1. Work
on the 1.6.2 releases will start soon, but there are no plans for
1.7.0. Therefore you should test your code with 1.6.2-SNAPSHOT and
report if there are still issues (so that there is a chance to get
them fixed before the release).

Andreas

On Thu, Apr 12, 2012 at 23:51, Gordon2 gordon_dak...@yahoo.com wrote:
 Jaime,

 I got the latest axis2-1.7.0 and rampart snapshot using maven, and I found
 that my client actually succeeds in adding the UsernameToken security
 policy, which it fails to do in 1.6.1 (for me at least).  I see axis2-1.7.0
 uses neethi 3.0.2, and  axis2-1.6.1 uses 3.0.1. I don't know if that
 accounts for why my error occurs with 1.6.1, but not 1.7.0.

 Using the debugger, I get these 2 parsing behaviors, when the parser reaches
 the SupportingTokens element, which contains the Policy that contains the
 UsernameToken:

 With 1.7.0:

 SupportingTokensBuilder.build receives the SupportingTokens element, and
 UsernameTokenBuilder.build returns a UsernameToken with no problem.

 With 1.6.1:

 SupportingTokensBuilder.build receives the Policy containing the
 UsernameToken (instead of the SupportingTokens itself), and it calls
 PolicyEngine.getPolicy for the Policy's child UsernameToken. That leads to
 PolicyBuilder.processOperationElement calling isInPolicyNS, which complains
 that UsernameToken's namespace is not one of the 3 policy namespace in
 Constants.java.

 With 1.5.1, neethi 2 doesn't check the UsernameToken's namespace, and
 parsing succeeds.

 Is UsernameToken definitely known to work on the client side with 1.6.1?  If
 so, maybe my system isn't configured correctly with 1.6.1.

 BTW, do you know roughly when 1.7.0 will be released?

 Gordon


 Jaime Hablutzel Egoavil wrote

 I had a similar problem to this... but this was happening in axis2 1.4 and
 it got fixed in newer versions... your problem seems to be different..
 altought UsernameToken is well supported... I'm not sure about your
 problem, but I suggest you a couple of things, first try stepping with a
 debugger through

 org.apache.neethi.PolicyBuilder.getPolicyOperator(PolicyBuilder.java:177)

 download the source for that (if using maven that is really easy) and
 check
 around, check well the versions for libraries you are using... specially
 neethi version for your axis2 version.

 Another suggestion would be to download the last development version of
 axis from their subversion trunk and try using that... it is packaged with
 maven so if you know maven you won't have too much problems.

 GOod luck




 --
 View this message in context: 
 http://axis2.867.n6.nabble.com/Policy-not-supported-is-it-a-bug-tp4340911p4865622.html
 Sent from the Axis2-user mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 not understand is: I have built axis2-1.6.1 from sources using 
 maven-2.2.1 and once with maven-3.0.4 always from JDK 1.6.0_22. WITH SUCCESS. 
 There was no claim from maven that a certain feature can not be compiled or 
 from surefire that a certain feature can not be tested when built against JDK 
 1.6.

 Or interpreting your words, that Axis2 uses newer versions of both artifacts. 
 In case of i.e. a @RequestWrapper#partName introduced starting from JAX-WS 
 2.2 [1] will not be available with previous versions[2] of JAX-WS found in 
 JDK1.6.


 Please note: There are axis2-1.6.1/samples/jaxws-samples which under this 
 circumstances do not run on JDK 1.6.0_30 i.e.  
 org.apache.axis2.jaxws.calculator.CalculatorServer.main(CalculatorServer.java:33),
  at least not without a word about moving certain libs into endorsed 
 directories.

 AND because axis2-1.6.1 code at package 
 org.apache.axis2.jaxws.description.builder.converter.JavaMethodsToMDCConverter
  uses a call which dependes on JDK 7.0 and artifacts, or in short, will not 
 run on JDK 6.0 without particular artifacts endorsed. Why does maven not 
 produce a failure or warning that the full functionality of JAX-WS 2.2 is 
 only available when axis2-1.6.1 runs on top of JDK 7.0


    /**
     * This method will drive the attachment of @ResponeWrapper annotation 
 data to the
     * codeMethodDescriptionComposite/code
     *
     * @param mdc    - codeMethodDescriptionComposite/code
     * @param method - codeMethod/code
     */
    private void attachResponseWrapperAnnotation(MethodDescriptionComposite 
 mdc, Method
            method) {
        ResponseWrapper responseWrapper = 
 (ResponseWrapper)ConverterUtils.getAnnotation(
                ResponseWrapper.class, method);
        if (responseWrapper != null) {
            ResponseWrapperAnnot rwAnnot = 
 ResponseWrapperAnnot.createResponseWrapperAnnotImpl();
            rwAnnot.setClassName(responseWrapper.className());
            rwAnnot.setLocalName(responseWrapper.localName());
            rwAnnot.setTargetNamespace(responseWrapper.targetNamespace());
            rwAnnot.setPartName(responseWrapper.partName());
            mdc.setResponseWrapperAnnot(rwAnnot);
        }
    }

 What I do not understand is that axis2-1.6.1 sources can compile against JDK 
 1.6.0 where as .partName is clearly not an artifact delivered with JDK 1.6.0 
 and/or dependent artifacs; I am not a Java Expert and have no explanation for 
 that. Maven regulates so many dependecies; why not such a dependency; at 
 least I would expect one word of caution in the SAMPLE README file for i.e. 
 the Calculator Sample, stating that @Addressing or certain other known 
 @Annotations are not working when used by Axis2 with JDK 1.6.0

 After all: In short and in my mind, please correct if I am wrong 
 @Addressing is only supported with JDK 1.7 when used in a JAX-WS annotaion.

 Josef



 -Ursprüngliche Nachricht-
 Von: Sagara Gunathunga [mailto:sagara.gunathu...@gmail.com]
 Gesendet: Montag, 9. April 2012 06:44
 An: java-user@axis.apache.org
 Betreff: Re: [axis2-1.6.1] RequestWrapper.partName() not supported on JDK 
 1.6.0 but used by JAX-WS

 This is not a Axis2 issue instead JDK 1.6 related JAX-WS issue, JDK 6
 shipped JAXB 2.0 and JAX-WS 2.0 as a part of JDK but Axis2 uses newer
 versions of both artifacts. In your case @RequestWrapper#partName
 introduced starting from JAX-WS 2.2 [1] and not available on previous
 versions[2].

 It is recommended to use one of a endorsed mechanisms mentioned here
 [3] [4] to solve those issues. For Axis2 you can easily find artifacts
 that needed to be endorsed within the /lob/endorsed/ directory of
 binary distribution.

 [1] -  
 http://docs.oracle.com/javase/6/docs/api/javax/xml/ws/RequestWrapper.html
 [2] -  
 http://docs.oracle.com/javase/7/docs/api/javax/xml/ws/RequestWrapper.html#partName%28%29
 [2] -  
 http://weblogs.java.net/blog/ramapulavarthi/archive/2007/01/problems_using.html
 [3] -  
 http://weblogs.java.net/blog/vivekp/archive/2007/01/running_jaxws_2.html

 Thanks !

 On Thu, Apr 5, 2012 at 10:17 PM, Stadelmann Josef
 josef.stadelm...@axa-winterthur.ch wrote:
 [exec:exec]

 Starting Server

 Exception in thread main java.lang.NoSuchMethodError:
 javax.xml.ws.RequestWrapper.partName()Ljava/lang/String;

     at
 org.apache.axis2.jaxws.description.builder.converter.JavaMethodsToMDCConverter.attachRequestWrapperAnnotation(JavaMethodsToMDCConverter.java:203)

     at
 org.apache.axis2.jaxws.description.builder.converter.JavaMethodsToMDCConverter.convertMethods(JavaMethodsToMDCConverter.java:85)

     at
 

Re: Handling MTOM attachments in a message receiver

[Andreas Veithen]

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
 manipulate(extract and store) an MTOM attachment (if exist) from the
 message-context.
 When digged into the problem, it seems, this can't be done at message
 receiver level as MTOM attachments are handled at axiom level.
 Please provide me some insight on possible ways to implement this.


 --
 Thanks,
 Denis
 --
 Denis Weerasiri

 site: https://sites.google.com/site/ddweerasiri/
 blog: http://ddweerasiri.blogspot.com
 twitter: http://twitter.com/ddweerasiri
 linked-in: http://lk.linkedin.com/in/ddweerasiri


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: Can't access SOAP header

[Andreas Veithen]

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,  aaron.stro...@rsa.com wrote:
 Hello all,



 My web service client passes a custom SOAP header to the service. The
 SOAPMonitor shows that it is included soapenv:Header element.

 On the server side I’m attempting to get it using this bit of code:



 MessageContext ctx = MessageContext.getCurrentMessageContext();



 OperationContext opctx = ctx.getOperationContext();

 try {

     MessageContext msgctx =
 opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);

     AxisMessage message = msgctx.getAxisMessage();

  ArrayList headers = message.getSoapHeaders();

 } catch (AxisFault e) {

     log.debug(Failed getting incoming message context, e);

 }



 But the headers list is empty.



 I’m using Axis 1.6.1. According to various document I found on the net, I
 should be able to get the SOAP message from the message context, SOAP
 envelope from the SOAP message and from that get the headers but
 org.apache.axis2.context.MessageContext allows me to get only to
 AxisMessage, which does not provide the means to get the SOAP envelope.
 Please advise what I am doing wrong and what is the correct way. Thanks,



 -a

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 external
 service. The response from this service is using UTF8 to encode the content,
 I've checked with Wireshark the communications and messages and the response
 is specifying UTF8 and the problematic character (a dash) is correctly
 encoded with UTF8. The response specifies text/xml; charset=utf-8 in the
 HTTP header and the xml message within it ?xml version='1.0'
 encoding='utf-8'? and the character in the payload is specified as: e2 80
 93 (UTF-8 (hex) representation for EN DASH:
 http://www.fileformat.info/info/unicode/char/2013/index.htm).

 But when the control comes back to my application, the stub is using
 ISO-8859-15 (which is the charset specified for my JVM) to decode that
 response so the response is showing incorrect characters for the dash,
 debugging the code I'm getting: â

 According to
 http://osdir.com/ml/axis-dev-ws.apache.org/2009-08/msg00132.html looks like
 before version 1.6 the encoding wasn't being taken into account in a
 reliable way...

The scope of AXIS2-4468 is limited to the XmlBeans data binding and
the issue occurs in the serialization of an outgoing message, not in
the deserialization of an incoming message.

 Wouldn't be any other way to solve this rather than generating the client
 with a newer version?

 Thanks,
 Francisco.



 On 20/03/2012 09:12, Stadelmann Josef wrote:

 Francisco



 What is your exact version of AXIS2?



 And just to be sure; are you creating a Java Client calling a stub
 generated by WSDL2JAVA?



 Are you using SOAP-XML over HTTP? THEN XML cannot keep all ISO-8859-1
 characters.

 To transfer you need to escape certain characters before inserting it into
 your ISO-8859-1

 XML string, and it might be better to use UTF-8 for that.



 We had recently a similar issue which we did not have unless we changed to
 AXIS2-1.6.1

 Guess it has to do with Axiom version delivered with this release of
 AXIS2.



 I strongly suggest to use TCP Monitor to look what you get back by the
 sender which is

 in your case the service-response.



 How does the service return payload characters i.e. a ä ö ü è é or   
 %



 and I think that will get you further.

 http://osdir.com/ml/axis-dev-ws.apache.org/2009-08/msg00132.html





 let me know if it helps.



 Josef









 Von: Francisco Serrano [mailto:francisco.serr...@multicom.co.uk]
 Gesendet: Montag, 19. März 2012 15:47
 An: java-user@axis.apache.org
 Betreff: [Axis2] Axis2 client generated from WSDL ignoring encoding



 Any advice on this please?

  Original Message 

 Subject:

 [Axis2] Axis2 client generated from WSDL ignoring encoding

 Date:

 Thu, 23 Feb 2012 17:02:42 +

 From:

 Francisco Serrano francisco.serr...@multicom.co.uk

 To:

 java-user@axis.apache.org



 Hello,



 I have an axis2 client generated from a WSDL, which is working fine but

 I'm having some problems since it's ignoring the charset specified in

 the response it's getting back.



 The response specifies charset=UTF-8 in the Content-Type HTTP header and

 the same in the encoding parameter in the xml message.



 Instead of using UTF-8 to decode the xml content, it's using ISO-8859-1

 which is the one set for the JVM where the client is running. For this

 reason I'm getting some strange characters in the response. I've double

 checked that the characters are encoded correctly using UTF-8.



 It's an old client generated with version 1.0. Does anybody know if

 there's some issue about that version regarding this problem? Are there

 any parameters to specify the charset to use to decode the response?



 Best regards,

 Francisco.



 Multicom Products Limited is a company registered in England and Wales
 (Registered Number 2447353 Wales) with its registered office at 33 Victoria
 Street, Bristol, BS1 6AS.
 This email is confidential to the addressee and may contain privileged
 information. If you have reason to believe that you are not the intended
 recipient of this communication, please delete it from your system and
 contact the sender immediately. You are not permitted to use or copy this
 email or its attachments nor may you disclose the same to any third party.
 Unauthorised use or disclosure of this email is prohibited and may be
 unlawful.
 We reserve the right to intercept and read emails sent or received by our
 employees. This is to ensure compliance with our internal policies and to
 protect our business. If you do not wish for your communications to be
 subjected to such scrutiny, you should not communicate via this email
 system.
 We endeavour to exclude viruses and other malware from our data but it is
 the responsibility of the recipient to scan all emails and attachments for
 

Re: Changing Default Time Zone in CalendarDeserializer?

[Andreas Veithen]

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:

 Hi,

 Is there any one found the solution as given by Brad, I am facing the same
 issue and wanted the system date as default.


 Regards
 Adi

 Brad Lohnes wrote:

 Hello,



 I am new to the list and apologize if this question has already been
 answered - I spent a few hours searching for the issue but did not find
 it.



 Here is the issue:



 When converting XML dateTime types, axis converts to java.util.Calendar,
 which is fine. However, the implementation of CalendarSerializer
 hard-codes the time zone to GMT (and also hard-codes the format, as
 well).



 We have implemented a web service using axis but have received a new
 requirement very late in the project (scheduled to finish testing this
 week). The requirement is that our web service assume not GMT at the
 interface endpoint, but rather another timezone (GMT+12:00). This means
 two things:



 1.    When we receive an XML dateTime element with no time zone
 information, we must assume our local time zone, not GMT.
 2.    When serializing our own output, we are required to not include
 time zone information, and other services within the SOA are to assume
 local timezone information.



 I am not interested in debating the merits of this design - our opinion
 has been made clear. Nevertheless, it is our requirement. :-)



 How can we replace the existing axis functionality?



 1.    Is there a simple configuration option? (I have not found one)
 2.    Is there a simple way to replace (through configuration) the
 CalendarDeserializer implementation with our own?
 3.    Is there another option that has not been considered?
 4.    Is the only option to replace the CalendarDeserializer class and
 compile axis ourselves? (We are currently working from the distribution
 library rather than compiliing from source ourselves).



 Your urgent response in this matter would be greatly appreciated.



 Regards,



 Brad






 --
 View this message in context: 
 http://old.nabble.com/Changing-Default-Time-Zone-in-CalendarDeserializer--tp4722785p33461536.html
 Sent from the Axis - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

Re: axis2 xml parser issue

[Andreas Veithen]

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 because on
these systems JAXP selects one of the Xalan versions. You should start
by resolving that issue.

Andreas

On Thu, Mar 1, 2012 at 08:43, Anthony Seniunas
anthony.seniu...@kirona.com wrote:
 Hi Sagara,
   Thanks for that. I've done some research and think the
 problem is related to running a set of application libraries compatible with
 Java 1.5 on a Java 1.6 Tomcat container.I've found out that Java 1.6
 includes the following

 SAAJ1.3
 JAXB 2.0
 JAXP 1.4

 The last two are Xerces and Xalan

  I think there are two options to resolve this problem:-

 Option 1 - Remove conflicting jars

 This would involve removing jars conflicting with the above. The list of
 .jars in usage is as follows:-

 FastInfoset.jar
 PngEncoder.jar
 XMBMobileGateway.jar
 XmlSchema-1.4.2.jar
 activation-1.1.jar
 annogen-0.1.0.jar
 aopalliance.jar
 aspectjweaver.jar
 axiom-api-1.2.7.jar
 axiom-dom-1.2.7.jar
 axiom-impl-1.2.7.jar
 axis.jar
 axis2-adb-1.4.1.jar
 axis2-adb-codegen-1.4.1.ja
 axis2-ant-plugin-1.4.1.jar
 axis2-clustering-1.4.1.jar
 axis2-codegen-1.4.1.jar
 axis2-corba-1.4.1.jar
 axis2-fastinfoset-1.4.1.ja
 axis2-java2wsdl-1.4.1.jar
 axis2-jaxbri-1.4.1.jar
 axis2-jaxws-1.4.1.jar
 axis2-jaxws-api-1.4.1.jar
 axis2-jibx-1.4.1.jar
 axis2-json-1.4.1.jar
 axis2-jws-api-1.4.1.jar
 axis2-kernel-1.4.1.jar
 axis2-metadata-1.4.1.jar
 axis2-mtompolicy-1.4.1.jar
 axis2-saaj-1.4.1.jar
 axis2-saaj-api-1.4.1.jar
 axis2-spring-1.4.1.jar
 axis2-xmlbeans-1.4.1.jar
 backport-util-concurrent-3
 bicmn.jar
 bipres.jar
 clibwrapper_jiio.jar
 collections.jar
 com.springsource.com.thoug
 com.springsource.org.xmlpu
 commons-codec-1.3.jar
 commons-dbcp.jar
 commons-discovery-0.2.jar
 commons-fileupload-1.2.jar
 commons-httpclient-3.1.jar
 commons-io-1.4.jar
 commons-lang-2.6.jar
 commons-net-1.3.0.jar
 commons-pool.jar
 cos.jar
 geronimo-annotation_1.0_sp
 geronimo-stax-api_1.0_spec
 httpcore-4.0-beta1.jar
 httpcore-nio-4.0-beta1.jar
 i18nAPI_v3.jar
 iText-rtf-2.1.7.jar
 iText.jar
 iTextXML.jar
 jai_codec.jar
 jai_core.jar
 jai_imageio.jar
 jakarta-oro-2.0.8.jar
 jalopy-1.5rc3.jar
 jaxb-api-2.1.jar
 jaxb-impl-2.1.6.jar
 jaxb-xjc-2.1.6.jar
 jaxen-1.1.1.jar
 jaxr-api.jar
  jaxr-impl.jar
 jaxrpc-api.jar
 jaxrpc-impl.jar
 jaxrpc.jar
 jcl-over-slf4j-1.5.6.jar
 jcommon-0.9.5.jar
 jec.jar
 jettison-1.0-RC2.jar
 jewt4.jar
 jfreechart-0.9.20-demo.jar
 jfreechart-0.9.20.jar
 jibx-bind-1.1.5.jar
 jibx-run-1.1.5.jar
 json_simple-1.1.jar
 jsr173_1.0_api.jar
 junit.jar
 log4j-1.2.15.jar
 mail-1.4.jar
 mex-1.4.1.jar
 msbase.jar
 mssqlserver.jar
 msutil.jar
 neethi-2.0.4.jar
 ojdbc14.jar
 orai18n.jar
 quartz-all-1.6.6.jar
 resolver.jar
 rowset.jar
 saaj-api.jar
 saaj-impl.jar
 saxon8.jar
 share.jar
 slf4j-api-1.5.6.jar
 slf4j-log4j12-1.5.6.jar
 soap.jar
 soapmonitor-1.4.1.jar
 spring-aop-2.5.6.jar
 spring-aspects.jar
 spring-batch-infrastructur
 spring-beans-2.5.6.jar
 spring-context-2.5.6.jar
 spring-context-support.jar
 spring-core-2.5.6.jar
 spring-jdbc-2.5.6.jar
 spring-jms-2.5.6.jar
 spring-orm-2.5.6.jar
 spring-test.jar
 spring-tx-2.5.6.jar
 spring-web-2.5.6.jar
 spring-webmvc-2.5.6.jar
 spring-ws-1.5.9-all.jar
 ujac.jar
 versioninfo.jar
 woden-api-1.0M8.jar
 woden-impl-dom-1.0M8.jar
 wsdl4j-1.5.1.jar
 wsdl4j-1.6.2.jar
 wstx-asl-3.2.4.jar
 xalan-2.7.0.jar
 xalan.jar
 xbean.jar
 xdocore.jar
 xdoparser.jar
 xercesImpl-2.8.1.jar
 xercesImpl.jar
 xml-apis-1.3.04.jar
 xml-resolver-1.2.jar
 xmlbeans-2.3.0.jar
 xmlbeans-qname.jar
 xmlparserv2.jar

 As you can see there is potential for conflicts in such a large library
 list. A cursory look at the above library I think I might have to remove the
 following if I wanted to use Java 1.6 inbuilt libraries.

 Remove to avoid JAXB Conflicts

 jaxb-api-2.1.jar
 jaxb-impl-2.1.6.jar
 jaxb-xjc-2.1.6.jar

 Remove to avoid SAAJ conflicts

 axis2-saaj-1.4.1.jar
 axis2-saaj-api-1.4.1.jar

 saaj-api.jar
 saaj-impl.jar

 Remove to avoid JAXB/JAXP Conflicts

 xalan-2.7.0.jar
 xalan.jar

 xercesImpl-2.8.1.jar
 xercesImpl.jar

 The following are not so clear.

 You mentioned axis2 does not have a saxon dependency so can the following
 jar be removed also?

 saxon8.jar

 and not sure whether these can be removed?

 xml-apis-1.3.04.jar
 xmlparserv2.jar

 Option 2 - Set Java properties to run axis2 SOAP factories etc...

 I found the following config in a post to force usage of axis2 SOAP
 factories as opposed to Java 1.6 SOAP factories (I think the switches the
 JAXB/JAXP back to axis2)

 java -Djavax.xml.soap.SOAPFactory=org.apache.axis.soap.SOAPFactoryImpl
 -Djavax.xml.soap.MessageFactory=org.apache.axis.soap.MessageFactoryImpl
 -Djavax.xml.soap.SOAPConnectionFactory=org.apache.axis.soap.SOAPConnectionFactoryImpl
 

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

[Andreas Veithen]

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 andreas.veit...@gmail.com
 Subject: Re: Axis 1.4 Java:Problem with missing namespace prefix in SOAP Body
 To: java-user@axis.apache.org
 Cc: axis1-java-u...@axis.apache.org
 Date: Wednesday, 15 February, 2012, 10:50 AM

 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 
  org.apache.axis.message.SOAPBodyElement the namespace prefix present in the 
  Element is being removed.
  Eg:
  Following is the Element
  ns:Extend xmlns:ns=http://xyz; /ns:Extend
  When it is converted into  SOAPBodyElement it becomes
  Extend/Extend
 
  I am using the following constructor to create SOAPBodyElement from Element 
  type.
  SOAPBodyElement sle=new SOAPBodyElement(bodyElement);
  where bodyElement is the Element type.
 
  Can anyone please help me in resolving this issue?

 -
 To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
 For additional commands, e-mail: java-user-h...@axis.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 namespace prefix present in the 
 Element is being removed.
 Eg:
 Following is the Element
 ns:Extend xmlns:ns=http://xyz; /ns:Extend
 When it is converted into  SOAPBodyElement it becomes
 Extend/Extend

 I am using the following constructor to create SOAPBodyElement from Element 
 type.
 SOAPBodyElement sle=new SOAPBodyElement(bodyElement);
 where bodyElement is the Element type.

 The second issue is that the multiple namespace prefixes are generated for 
 the same namespace URI when the Element type is converted to SOAPBodyElement 
 type.
 Eg:
 xmlns:x=http://xyz;
 xmlns:y=http://xyz;
 xmlns:z=http://xyz;

 Can anyone please help me in resolving this issue?

 Thanks in advance
 santhosh

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org

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

[Andreas Veithen]

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 
 org.apache.axis.message.SOAPBodyElement the namespace prefix present in the 
 Element is being removed.
 Eg:
 Following is the Element
 ns:Extend xmlns:ns=http://xyz; /ns:Extend
 When it is converted into  SOAPBodyElement it becomes
 Extend/Extend

 I am using the following constructor to create SOAPBodyElement from Element 
 type.
 SOAPBodyElement sle=new SOAPBodyElement(bodyElement);
 where bodyElement is the Element type.

 Can anyone please help me in resolving this issue?

-
To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org
For additional commands, e-mail: java-user-h...@axis.apache.org