[jira] Closed: (AXIS2-954) Simplify the handling of the relationship type by returning a default value if it has not been set explicitly in a RelatesTo object.

[ http://issues.apache.org/jira/browse/AXIS2-954?page=all ] David Illsley closed AXIS2-954. --- Resolution: Fixed Patch from Brian committed. > Simplify the handling of the relationship type by returning a default value > if it has not been set explicitly i

[jira] Created: (AXIS2-967) Allow Constants.Configuration.SEND_STACKTRACE_DETAILS_WITH_FAULTS to be set on Message or OperationContext

Allow Constants.Configuration.SEND_STACKTRACE_DETAILS_WITH_FAULTS to be set on Message or OperationContext -- Key: AXIS2-967 URL: http://issues.apache.org/jira

RE: Customization of SOAP Envelop using Axis2 1.0

Thanks Eran it worked and now I have one more problem... :) In my SOAP request header under tag, there is tag as below: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit y-utility-1.0.xsd" wsu:Id="Timestamp-2086370"> 2006-08-02T11:39:58.015Z 2006-08-02T11:44:58.0

Need info

Hi All, I am basically Java, j2ee guy, But I am very much new to Webservices. My present task is , I need to create one search engine , but our client having that search engine which is already developed in .NET . So now I want to use that component by using webservices , for that I searche

RE: Need info

Hi Sudhakar, I would suggest you to download axis2 latest release (i.e. 1.0) instead of axis 1.x. To learn in detail about axis2, follow the link http://ws.apache.org/axis2/1_0/index.html As I understood your problem is that you want to call a web service which is written in .NET from your java

Re: [jira] Updated: (AXIS2-963) Problems with complex xml schemas in wsdl2java

Carsten, The schema location URL in your WSDL does not point to a document. Perhaps that's already the problem: the code generator just can't load the schema. Also, try checking the WSDL for compliance with Basic Profile using WS-I's analyzer tool. Cheers, Thilo Carsten Ziegeler (JIRA) wrot

Re: [jira] Updated: (AXIS2-963) Problems with complex xml schemas in wsdl2java

Thilo Frotscher schrieb: > Carsten, > > The schema location URL in your WSDL does not point to a document. > Perhaps that's already the problem: the code generator just can't > load the schema. > Hi Thilo, the schema location points to "http://schemas.xmlsoap.org/ws/2005/02/trust/ws-trust.xsd";

[jira] Commented: (AXIS2-758) Generated xmlbeans code is not handling elementFormDefault correctly

[ http://issues.apache.org/jira/browse/AXIS2-758?page=comments#action_12425507 ] Kent Tong commented on AXIS2-758: - Yes. Just confirmed with the latest nightly build. The request message is: http://foo.com/FileService/schema";> f01 R0lGOD...

Re: [Axis] Load Web Service on Startup

Hi Dims; Sorry for my previous mail :'( , I double checked and realized that there is no any cyclic dependencies between context and configurations and you only keep reference to configurationContext in DeploymentEngine. That is ok with me :) Thanks Deepal Deepal Jayasinghe wrote: >Hi Di

RE: Need info

Hi shyam, Thank you very much , what you understood is correct, I am already read these documents , but the problem is I am not able to configure with tomcat. Actually I copied all the jars which are in axis/web-inf/lib to tomcat /common/lib. But I am not able to run sample exercise. For con

[jira] Commented: (AXIS2-935) Connections are not properly released causing them to stick in the "CLOSE_WAIT" state and cause "Too many files open"

[ http://issues.apache.org/jira/browse/AXIS2-935?page=comments#action_12425509 ] Oleg Kalnichevski commented on AXIS2-935: - > When clean() is called in CommonsHttpTransportSender, I fetch the client, get > the connection manager, and cal

test

sorry pleas ignore

[Axis2] Missing xsi:type in SOAP-Message

Hello, I am trying to create an working inheritance example with Axis2. In the attached example case OAMIFASCapabilitiesType is derived from OAMIServiceSpecificCapabilities. To recognize the inheritance the client needs the xsi:type in the SOAP message, but it is missing as you can see trying the

problem in OC4J

Hello everybody, I have a problem with axis2 in a OC4J container, the wsdl is not generated like in a Tomcat container,does someone know about it?Thank you.

[jira] Created: (AXIS2-968) If a module's init() method throws an AxisFault, the initialization of the complete Axis2 web app fails

If a module's init() method throws an AxisFault, the initialization of the complete Axis2 web app fails Key: AXIS2-968 URL: http://issues.apache.org/jira/bro

[Axis2] problem in OC4J

Hello everybody, I have a problem with axis2 in a OC4J container, the wsdl is not generated like in a Tomcat container, does someone know about it?Thank you.

[jira] Commented: (AXIS2-747) Missing namespace on subelement

[ http://issues.apache.org/jira/browse/AXIS2-747?page=comments#action_12425514 ] Vinh Tran commented on AXIS2-747: - I found a resolution to this issue without having to hack the source. It appears shared namespaces with imported schemas will cau

Re: Need info

Expose the search engine API's call to a webservice.Then call the webservice by making SOAP calls .Does that makes sense!. - Badri On 8/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hi All, I am basically Java, j2ee guy, But I am very much new to Webservices. My present task is , I n

Re: [Axis2] Missing xsi:type in SOAP-Message

This should work in latest nightly. If not, please log a bug. thanks, dims On 8/3/06, Desiree Hilbring <[EMAIL PROTECTED]> wrote: Hello, I am trying to create an working inheritance example with Axis2. In the attached example case OAMIFASCapabilitiesType is derived from OAMIServiceSpecificCapa

[jira] Commented: (AXIS2-953) Wsdl2Java throws a code generation exception if the input message has 2 parts. (Document-Literal Wrapped Dispatching)

[ http://issues.apache.org/jira/browse/AXIS2-953?page=comments#action_12425520 ] Nitesh kant commented on AXIS2-953: --- Okie, i found that if in the input/output messages, i use "type" instead of "element" i.e. if the input message in the specif

Re: Customization of SOAP Envelop using Axis2 1.0

Shyam Shukla wrote: > Thanks Eran it worked and now I have one more problem... :) > In my SOAP request header under tag, there is > tag as below: > > xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit > y-utility-1.0.xsd" wsu:Id="Timestamp-2086370"> > > 2006-08-

[jira] Created: (AXIS2-969) Missing xsi:type in SOAP-Message

Missing xsi:type in SOAP-Message Key: AXIS2-969 URL: http://issues.apache.org/jira/browse/AXIS2-969 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Affects Versions: 1.0 Environment: Windows XP

[jira] Updated: (AXIS2-969) Missing xsi:type in SOAP-Message

[ http://issues.apache.org/jira/browse/AXIS2-969?page=all ] Desiree Hilbring updated AXIS2-969: --- Attachment: GMLSFE060803.wsdl WSDL-File > Missing xsi:type in SOAP-Message > > > Key: AXIS2-969 >

[jira] Updated: (AXIS2-969) Missing xsi:type in SOAP-Message

[ http://issues.apache.org/jira/browse/AXIS2-969?page=all ] Desiree Hilbring updated AXIS2-969: --- Attachment: delivery060803-2.xsd GMLSFESkeleton.java GMLSFClient.java Types used in WSDL, Skeleton and Client example. > M

AW: [Axis2] Missing xsi:type in SOAP-Message

Hello, thanks, I tried the latest nightly, but there I get false code created by WSDL2Java (I created a bug). [javac] Compiling 225 source files to C:\hilbring\EclipseWTP\GMLSFE\classes [javac] C:\hilbring\EclipseWTP\GMLSFE\output\src\org\example\types\GMLSFEStub.java:142: toEnvelope(or

Axis2.0 Data Binding errors !

Hi there ! Currently , We are using Axis 1.4 version as a Client. Today , I downloaded Axis2.0 version and started using it with my existing WSDL file . I was able to generate Client Stubs and other respective java files based on the WSDL by using "xmlbeans" as a option. When i am trying to exe

Re: [Axis2] JSR 181 support

Nick, Could you please help by starting a wiki to capture the discussion / outcome(s)? my head is spinning :) thanks, dims On 8/3/06, Nicholas L Gallardo <[EMAIL PROTECTED]> wrote: Eddie, Thanks for your weighing in here... I'll respond to your notes and Rajith's at the same time. I've i

[jira] Created: (AXIS2-970) Problem when performing AXIOM to SAAJ conversion

Problem when performing AXIOM to SAAJ conversion Key: AXIS2-970 URL: http://issues.apache.org/jira/browse/AXIS2-970 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws

[jira] Created: (AXIS2-971) SAAJConverterImpl.toSAAJ(OMElement, SOAPElement) requires the SOAPElement to be a SOAPEnvelope.

SAAJConverterImpl.toSAAJ(OMElement, SOAPElement) requires the SOAPElement to be a SOAPEnvelope. --- Key: AXIS2-971 URL: http://issues.apache.org/jira/browse/AXIS2-971

[jira] Commented: (AXIS2-970) Problem when performing AXIOM to SAAJ conversion

[ http://issues.apache.org/jira/browse/AXIS2-970?page=comments#action_12425578 ] Rich Scheuerle commented on AXIS2-970: -- Thanks Brian, Can you supply a small test the demonstrates the problem. This will make it easier for me to validate.

[jira] Commented: (AXIS2-971) SAAJConverterImpl.toSAAJ(OMElement, SOAPElement) requires the SOAPElement to be a SOAPEnvelope.

[ http://issues.apache.org/jira/browse/AXIS2-971?page=comments#action_12425581 ] Rich Scheuerle commented on AXIS2-971: -- Brian, Did you try using the SAAJConverterImpl.toSAAJ(OMElement om, SOAPElement parent) method. This will create a SO

[jira] Assigned: (AXIS2-971) SAAJConverterImpl.toSAAJ(OMElement, SOAPElement) requires the SOAPElement to be a SOAPEnvelope.

[ http://issues.apache.org/jira/browse/AXIS2-971?page=all ] Rich Scheuerle reassigned AXIS2-971: Assignee: Rich Scheuerle > SAAJConverterImpl.toSAAJ(OMElement, SOAPElement) requires the SOAPElement to > be a SOAPEnvelope. > -

[jira] Assigned: (AXIS2-970) Problem when performing AXIOM to SAAJ conversion

[ http://issues.apache.org/jira/browse/AXIS2-970?page=all ] Rich Scheuerle reassigned AXIS2-970: Assignee: Rich Scheuerle > Problem when performing AXIOM to SAAJ conversion > > > Key: A

Re: FW: [axis2] questions...

Hi Tony, The article on client api parameters is finally published here (http://www.wso2.net/articles/axis2/java/2006/08/01/client-api-parameters). -- Chinthaka Eran Chinthaka wrote: > Tony Dean wrote: >> Does anyone have any insights on the questions listed below. >> >> For instance setting som

[jira] Updated: (AXIS2-970) Problem when performing AXIOM to SAAJ conversion

[ http://issues.apache.org/jira/browse/AXIS2-970?page=all ] Brian DePradine updated AXIS2-970: -- Attachment: Sample.java Hi Rich, I am attaching the test that you requested. You can run it with Junit. > Problem when performing AXIOM to SAAJ conversion

[jira] Created: (AXIS2-972) Initial annotation processing in metadata abstraction layer and associated refactoring JAXWS Proxy

Initial annotation processing in metadata abstraction layer and associated refactoring JAXWS Proxy --- Key: AXIS2-972 URL: http://issues.apache.org/jira/browse/AXIS2-

[jira] Updated: (AXIS2-972) Initial annotation processing in metadata abstraction layer and associated refactoring JAXWS Proxy

[ http://issues.apache.org/jira/browse/AXIS2-972?page=all ] Jeff Barrett updated AXIS2-972: --- Attachment: patch.txt This patch contains the inital work for annotation processing in the description package as used by dynamic Proxy built from an annotated SE

[jira] Assigned: (AXIS2-951) JAXWS: Need to remove the calls that are being made to the AxisController

[ http://issues.apache.org/jira/browse/AXIS2-951?page=all ] Nick Gallardo reassigned AXIS2-951: --- Assignee: Nick Gallardo > JAXWS: Need to remove the calls that are being made to the AxisController > -

[jira] Assigned: (AXIS2-972) Initial annotation processing in metadata abstraction layer and associated refactoring JAXWS Proxy

[ http://issues.apache.org/jira/browse/AXIS2-972?page=all ] Nick Gallardo reassigned AXIS2-972: --- Assignee: Nick Gallardo > Initial annotation processing in metadata abstraction layer and associated > refactoring JAXWS Proxy > -

[jira] Created: (AXIS2-973) Java2WSDLTask allows only one jar in the classPathURI attribute

Java2WSDLTask allows only one jar in the classPathURI attribute --- Key: AXIS2-973 URL: http://issues.apache.org/jira/browse/AXIS2-973 Project: Apache Axis 2.0 (Axis2) Issue Type: B

Re: problem in OC4J

Hi Carlos; Are you getting any exception ? Or you get nothing ? Please explain the problem a bit. Carlos Prendes Espinosa wrote: > Hello everybody, I have a problem with axis2 in a OC4J container, the > wsdl is not generated like in a Tomcat container, > does someone know about it? > > Thank you

AW: Customization of SOAP Envelop using Axis2 1.0

Well, the format and content of the WSSE timestamp shall (must?) not incluence the content or format of ofther timestamp contained in a SOAP request. The timestamps have different semantic and are relevant only for their environment. The timestamps for WSS are defined in the OASIS WSS specificatio

Re: AW: [Axis2] Missing xsi:type in SOAP-Message

Abandon all hope ye who enter here ;-) ... Even when you get xsi:type working, deserialisation is also completely broken. I have opened a number of Jira's on these issues, but never had much luck. Tried to debug it myself too, but failed miserably. If you have any better luck, please let me