[jira] Resolved: (AXIS2-3059) Date gets changed for xs:date types

[Amila Chinthaka Suriarachchi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS2-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Amila Chinthaka Suriarachchi resolved AXIS2-3059.
-

Resolution: Fixed

instead of converting the date to the GMT now it adds the local time which is 
the recovarable timezone. Now converToString(date) method looks like this,
SimpleDateFormat simpleDateFormat = new SimpleDateFormat("-MM-ddZ");
return simpleDateFormat.format(value);

> Date gets changed for xs:date types
> ---
>
> Key: AXIS2-3059
> URL: https://issues.apache.org/jira/browse/AXIS2-3059
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: adb
>Affects Versions: 1.3
> Environment: Java 5.0 Windows XP
>Reporter: Michael Medric
>Assignee: Amila Chinthaka Suriarachchi
>
> I have an attribute of type xs:date in my WSDL and have generated ADBBean 
> objects via wsdl2java.  This xs:date attribute maps to a DateTime field in 
> our database.  However, our system only cares about the date part (month, 
> day, year), not the time.  As a result, the dates are stored with time 
> 00:00:00 in the database.  When querying for this object using axis2, it 
> moves the day back one day because of the UTC conversion that is done in 
> ConvertUtil.convertToDate(String).  
> For instance, the say the date is '2000-01-01 00:00:00' in the database.  The 
> client is in GMT-5:00 time zone.  What is returned to the client is 
> '1999-12-31 19:00:00'.  Essentially, it seems the day will always get shifted 
> as per the client time zone by way of the ConvertUtil.convertToString(Date) 
> method that always assumes GMT (which appends 'Z' to  the serialized date).  
> It seems to me that the use of xsd:date is undermined here because the day 
> will get always get shifted back for any client timezones behind GMT.  I'm 
> not sure if this is a bug or by design but it seems worth mentioning.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (AXIS2-3273) http://ws.apache.org/axis2/0_94/OMTutorial.html Examples are incorrect

[Martin Gainty (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS2-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Martin Gainty updated AXIS2-3273:
-


documentation changed so the inconsistencies between listing 6 and listing 11 
are no longer present..

Martin--


> http://ws.apache.org/axis2/0_94/OMTutorial.html Examples are incorrect
> --
>
> Key: AXIS2-3273
> URL: https://issues.apache.org/jira/browse/AXIS2-3273
> Project: Axis 2.0 (Axis2)
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.3
> Environment: documentation
>Reporter: Martin Gainty
>
> http://ws.apache.org/axis2/0_94/OMTutorial.html
> There is an example for Code Listing 6:
> OMFactory factory = OMAbstractFactory.getOMFactory();
> OMNamespace ns1 = factory.createOMNamespace("bar","x");
> OMElement root = factory.createOMElement("root",ns1);
> OMNamespace ns2 = root.declareNamespace("bar1","y");
> OMElement elt1 = factory.createOMElement("foo",ns1);
> OMElement elt2 = factory.createOMElement("yuck",ns2);
> OMText txt1 = factory.createText(elt2,"blah");
> elt2.addChild(txt1);
> elt1.addChild(elt2);
> root.addChild(elt1);
> Serilization of the root element produces the following XML
> 
>   
> blah
>   
> 
> //CORRECT!
> then later on 
> Take the following case where a similar Code Listing to Code Listing 6 is 
> used, but with two elements having the same namespace. (NOTE: they are 
> differenent namespaces!)
> Note that the newly added items are in bold. (Not in IE 6)
> Code Listing 11
> OMFactory factory = OMAbstractFactory.getOMFactory();
> OMNamespace ns1 = factory.createOMNamespace("bar","x");
> OMElement root = factory.createOMElement("root",ns1);
> OMNamespace ns2 = root.declareNamespace("bar1","y");
> OMElement elt1 = factory.createOMElement("foo",ns1);
> OMElement elt2 = factory.createOMElement("yuck",ns2);
> OMText txt1 = factory.createText(elt2,"blah");
> elt2.addChild(txt1);
> elt1.addChild(elt2);
> root.addChild(elt1);
> Serialization of the root element provides the following XML
> 
> 
>  blahblah//WRONG!
>  blah
> 
> 
> //INCORRECT.. blahblah is never produced!
> Ie6.0.28 SP1
> Martin--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS-1306) soapFault.setFaultString() etc do not create children...

[Bjorn Townsend (JIRA)]

[ 
https://issues.apache.org/jira/browse/AXIS-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534974
 ] 

Bjorn Townsend commented on AXIS-1306:
--

Never been fixed -- might be worth considering for 1.5.

> soapFault.setFaultString() etc do not create children...
> 
>
> Key: AXIS-1306
> URL: https://issues.apache.org/jira/browse/AXIS-1306
> Project: Axis
>  Issue Type: Bug
>  Components: SAAJ
>Affects Versions: current (nightly)
>Reporter: Brian Ewins
>Priority: Minor
> Attachments: diff.txt
>
>
> If you create a fault using the saaj apis (MessageFactory.createMessage(),... 
> etc) you'd expect that (saaj) SOAPFault.getChildElements() would get all the 
> children of the fault, including the faultcode, faultstring and faultactor, 
> once they have been set. In the Axis implementation, this is not the case - 
> only SOAPFaultDetail objects can be returned.
> One way of fixing this (I guess) would be to create and retain a reference to 
> the faultxxx SOAPElement after it has been set (in 
> org.apache.axis.message.SOAPFault), but I can see there being issues with the 
> element getting out of sync with the internal AxisFault.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (AXIS2-3090) Make SOAP 1.2 bindings optional, as they break older Axis 1 clients

[nadir amra (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS2-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

nadir amra resolved AXIS2-3090.
---

Resolution: Fixed

I hope I am not stepping on any toes, but I have resolved this issue.  Deepal, 
please accept my apologies if I am not doing this according to some process due 
to my handling the issue that is not assigned to me.

Basically added following in axis2.xml:



false

If set to true, not SOAP 1.2 bindings will be generated, for both wsdl and 
wsdl2.  

Of course this issue supplements issue AXIS2-3114.  That is,  AXIS2-3114 still 
needs to be implemented to give more flexibility.

> Make SOAP 1.2 bindings optional, as they break older Axis 1 clients
> ---
>
> Key: AXIS2-3090
> URL: https://issues.apache.org/jira/browse/AXIS2-3090
> Project: Axis 2.0 (Axis2)
>  Issue Type: Improvement
>  Components: kernel
>Affects Versions: 1.2
>Reporter: Thomas Leonard
>Assignee: Deepal Jayasinghe
> Fix For: nightly
>
> Attachments: disable-soap-1.1.patch
>
>
> We're trying to create some Axis 2 services which are usable by other clients 
> (including .NET and Axis 1). At first, we had problems due to AXIS2-2294, but 
> upgrading to Axis 2 1.3-RC2 fixed that. However, the WSDL is still unreadable 
> to the Axis 1 client because of the SOAP 1.2 bindings which are also present 
> in the file:
> java.io.IOException: ERROR: Missing  element inFault 
> "XMLStreamException" in operation "XMLStreamException", in binding sayHello
> The attached patch (disable-soap-1.1.patch) adds a configuration option to 
> disable generation of these bindings.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [Axis2] Secured Axis2-1.3 Client "Masks" Returned Fault Messages

[Tim Munro (myDIALS)]

No, I have not yet resolved this issue & am eagerly awaiting guidance from
this list regarding how I can fault-find it further.

Best,
Tim. 

-Original Message-
From: balaji hari [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, 16 October 2007 4:12 AM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Secured Axis2-1.3 Client "Masks" Returned Fault
Messages


I am facing the same problem too..Did u have a chance to get any information
regarding this issue?

Balaji

Tim Munro (myDIALS) wrote:
> 
> Hi All,
>  
> I have developed an Axis2-1.3 client (with Rampart 1.3, using an 
> xmlbeans
> proxy) that calls methods on a secured .NET web service service. I can 
> successfully communicate with the .NET service, however when the .NET 
> server returns a valid fault message the xmlbeans proxy client never 
> receives the returned fault string; instead all the client receives is 
> the following
> message:
> Must Understand check failed for header 
>
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.
> 0.xsd : Security
> 
> Note that in Axis2-1.2 this was not a problem; my xmlbeans proxy 
> received the correct/expected error string.
> 
> So, for example, if I call a method on the .NET web service with an 
> invalid parameter in the request document, the .NET web service 
> returns an informative message containing details of the problem. 
> Below is an example of the xml response message received from the .NET 
> server, and to me it appears to be a valid response:
>   xmlns:s="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
> urity-
> utility-1.0.xsd">
>   
>xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssec
> urity-
> secext-1.0.xsd" s:mustUnderstand="1">
>   
>   
> 2007-10-12T01:02:16.796Z
>   
> 2007-10-12T01:07:16.796Z
>   
>   
>   
>   
>   
>   s:UnexpectedFault
>   An unexpected error
has occurred in 
> the service.
> System.ServiceModel.FaultException`1[MyDials.Common.ServiceFaults.Inva
> lidReq
> uestFault]: The dimension member 'Midlands' was included in a 
> dimension reference for the 'Products' dimension, but is not valid. 
> (Fault Detail is equal to
MyDials.Common.ServiceFaults.InvalidRequestFault).
>   
>   
> 
> 
> When I interact with this returned message (through the xmlbeans 
> proxy), the error message I see is the "Must Understand check failed 
> for header ..."
> rather than the value contained in the faultstring elemrnt of the 
> returned document.
> 
> The issue appears to be that the received message header contains a
> (valid)
> timestamp, as indicated above, however the Axis2 response handler 
> never seems to to process this timestamp in the header, meaning that 
> when the
> AxisEngine.checkMustUnderstand() performs the 
> headerBlock.isProcessed() test, the result is false and so the "Must
understand check failed ..."
> exception is thrown and my xmlbeans proxy never sees the real 
> faultstring message.
> 
> I am struggling to understand what is going wrong here ... any 
> guidance on what to fault-find next would be greatly appreciated as 
> after a few days looking at this I am unsure if it is a problem in 
> returned document, or my policy.xml.
> 
> Thanks,
> Tim Munro
> ===
> 
> Below is my policy.xml document:
>   xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wss
> ecurit
> y-utility-1.0.xsd"
> xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";>
>   
>   
>xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
>   
>   
>   
>RequireClientCertificate="false"/>
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
>   
>sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/
> Includ
> eToken/AlwaysToRecipient">
>   
>   
> 
>  

Re: [AXIS2] Leverage axis2-metadata to handle JSR181/JAXWS annoations and Java2WSDL mapping?

[Raymond Feng]

Hi, Dustin.

Thank you for the quick response. 

I understand your point to start with the implementation class. But in my case, 
we only have the annotated SEI and we use the interface as the contract to 
drive invocations to the web service without depending on the full JAX-WS 
stack. To be specific, we are dealing with SCA remotable interfaces in Tuscany. 
What's desired is the metadata (or description) of the SEI.

Raymond
Apache Tuscany

- Original Message - 
  From: Dustin Amrhein 
  To: axis-dev@ws.apache.org 
  Sent: Monday, October 15, 2007 11:44 AM
  Subject: Re: [AXIS2] Leverage axis2-metadata to handle JSR181/JAXWS 
annoations and Java2WSDL mapping?


  Raymond,
  As for the DescriptionFactory.createServiceDescription(Class), you are right 
that it assumes you are supplying the implementation class, but it will also 
take into account an SEI class if the implementation class specifies one via 
annotations. The resulting description hierarchy should have information that 
reflects metadata from the SEI. If you find different please post your findings.

  Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,

I'm looking for some capabilities in Axis2 to support JSR181/JAXWS as 
follows:

1) Introspect a service implementation class and/or service endpoint 
interface (SEI) to handle JSR181/JAXWS annotations. Provide the default 
values if customization is not present.

2) A utility method to generate a WSDL4J Defintion following the rules 
defined by JAX-WS 2.0 Chapter 3 Java to WSDL 1.1 mapping rules.

I had a brief look of the axis2-metadata module. The closest method I can 
find is:

org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescription(Class)

But it only accepts service implementation class and is not happy with SEI. 
I cannot construct the EndpointInterfaceDescription directly as all the 
XXXDescriptionImpl classes are not public.

Would it be possible to have some methods on 
org.apache.axis2.jaxws.description.DescriptionFactory?

// Create the endpoint interface description from the SEI
public static EndpointInterfaceDescription 
createEndpointInterfaceDescription(Class sei);

// Generate WSDL defintion from the endpoint interface description
public static Defintion 
createWSDLDefinition(EndpointInterfaceDescription description);

// Generate WSDL defintion from the service description
public static Defintion createWSDLDefinition(ServiceDescription 
description);

Any help will be greatly appreciated.

Thanks,
Raymond




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--
  Looking for a deal? Find great prices on flights and hotels with Yahoo! 
FareChase.

[jira] Closed: (AXIS-1427) sibling method do not work

[Bjorn Townsend (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AXIS-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bjorn Townsend closed AXIS-1427.


   Resolution: Fixed
Fix Version/s: 1.3
 Assignee: Bjorn Townsend

This issue is fixed in versions 1.3 and later -- see AXIS-1537.

> sibling method do not work
> --
>
> Key: AXIS-1427
> URL: https://issues.apache.org/jira/browse/AXIS-1427
> Project: Axis
>  Issue Type: Bug
>  Components: SAAJ
>Affects Versions: 1.2 Beta
>Reporter: nishant kumar
>Assignee: Bjorn Townsend
> Fix For: 1.3
>
> Attachments: diff
>
>
> getNextSibling and getPreviousSibling do not work
> in the test case that i will attach getPreviousSibling is shown not to work 
> but in a cmoplex scenario i have debugged and seen getNextSibling not working.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [AXIS2] Leverage axis2-metadata to handle JSR181/JAXWS annoations and Java2WSDL mapping?

[Dustin Amrhein]

Raymond,
As for the DescriptionFactory.createServiceDescription(Class), you are right 
that it assumes you are supplying the implementation class, but it will also 
take into account an SEI class if the implementation class specifies one via 
annotations. The resulting description hierarchy should have information that 
reflects metadata from the SEI. If you find different please post your findings.

Raymond Feng <[EMAIL PROTECTED]> wrote: Hi,

I'm looking for some capabilities in Axis2 to support JSR181/JAXWS as 
follows:

1) Introspect a service implementation class and/or service endpoint 
interface (SEI) to handle JSR181/JAXWS annotations. Provide the default 
values if customization is not present.

2) A utility method to generate a WSDL4J Defintion following the rules 
defined by JAX-WS 2.0 Chapter 3 Java to WSDL 1.1 mapping rules.

I had a brief look of the axis2-metadata module. The closest method I can 
find is:
org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescription(Class)

But it only accepts service implementation class and is not happy with SEI. 
I cannot construct the EndpointInterfaceDescription directly as all the 
XXXDescriptionImpl classes are not public.

Would it be possible to have some methods on 
org.apache.axis2.jaxws.description.DescriptionFactory?

// Create the endpoint interface description from the SEI
public static EndpointInterfaceDescription 
createEndpointInterfaceDescription(Class sei);

// Generate WSDL defintion from the endpoint interface description
public static Defintion 
createWSDLDefinition(EndpointInterfaceDescription description);

// Generate WSDL defintion from the service description
public static Defintion createWSDLDefinition(ServiceDescription 
description);

Any help will be greatly appreciated.

Thanks,
Raymond




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



   
-
Looking for a deal? Find great prices on flights and hotels with Yahoo! 
FareChase.

[AXIS2] Leverage axis2-metadata to handle JSR181/JAXWS annoations and Java2WSDL mapping?

[Raymond Feng]

Hi,

I'm looking for some capabilities in Axis2 to support JSR181/JAXWS as 
follows:


1) Introspect a service implementation class and/or service endpoint 
interface (SEI) to handle JSR181/JAXWS annotations. Provide the default 
values if customization is not present.


2) A utility method to generate a WSDL4J Defintion following the rules 
defined by JAX-WS 2.0 Chapter 3 Java to WSDL 1.1 mapping rules.


I had a brief look of the axis2-metadata module. The closest method I can 
find is:

org.apache.axis2.jaxws.description.DescriptionFactory.createServiceDescription(Class)

But it only accepts service implementation class and is not happy with SEI. 
I cannot construct the EndpointInterfaceDescription directly as all the 
XXXDescriptionImpl classes are not public.


Would it be possible to have some methods on 
org.apache.axis2.jaxws.description.DescriptionFactory?


   // Create the endpoint interface description from the SEI
   public static EndpointInterfaceDescription 
createEndpointInterfaceDescription(Class sei);


   // Generate WSDL defintion from the endpoint interface description
   public static Defintion 
createWSDLDefinition(EndpointInterfaceDescription description);


   // Generate WSDL defintion from the service description
   public static Defintion createWSDLDefinition(ServiceDescription 
description);


Any help will be greatly appreciated.

Thanks,
Raymond




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Axis2] Secured Axis2-1.3 Client "Masks" Returned Fault Messages

[balaji hari]

I am facing the same problem too..Did u have a chance to get any information
regarding this issue?

Balaji

Tim Munro (myDIALS) wrote:
> 
> Hi All,
>  
> I have developed an Axis2-1.3 client (with Rampart 1.3, using an xmlbeans
> proxy) that calls methods on a secured .NET web service service. I can
> successfully communicate with the .NET service, however when the .NET
> server
> returns a valid fault message the xmlbeans proxy client never receives the
> returned fault string; instead all the client receives is the following
> message:
> Must Understand check failed for header
> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.
> 0.xsd : Security
> 
> Note that in Axis2-1.2 this was not a problem; my xmlbeans proxy received
> the correct/expected error string.
> 
> So, for example, if I call a method on the .NET web service with an
> invalid
> parameter in the request document, the .NET web service returns an
> informative message containing details of the problem. Below is an example
> of the xml response message received from the .NET server, and to me it
> appears to be a valid response:
> 
> http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-
> utility-1.0.xsd">
>   
>xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-
> secext-1.0.xsd" s:mustUnderstand="1">
>   
>   
> 2007-10-12T01:02:16.796Z
>   
> 2007-10-12T01:07:16.796Z
>   
>   
>   
>   
>   
>   s:UnexpectedFault
>   An unexpected error
> has occurred in the service.
> System.ServiceModel.FaultException`1[MyDials.Common.ServiceFaults.InvalidReq
> uestFault]: The dimension member 'Midlands' was included in a dimension
> reference for the 'Products' dimension, but is not valid. (Fault Detail is
> equal to MyDials.Common.ServiceFaults.InvalidRequestFault).
>   
>   
> 
> 
> When I interact with this returned message (through the xmlbeans proxy),
> the
> error message I see is the "Must Understand check failed for header ..."
> rather than the value contained in the faultstring elemrnt of the returned
> document.
> 
> The issue appears to be that the received message header contains a
> (valid)
> timestamp, as indicated above, however the Axis2 response handler never
> seems to to process this timestamp in the header, meaning that when the
> AxisEngine.checkMustUnderstand() performs the headerBlock.isProcessed()
> test, the result is false and so the "Must understand check failed ..."
> exception is thrown and my xmlbeans proxy never sees the real faultstring
> message.
> 
> I am struggling to understand what is going wrong here ... any guidance on
> what to fault-find next would be greatly appreciated as after a few days
> looking at this I am unsure if it is a problem in returned document, or my
> policy.xml.
> 
> Thanks,
> Tim Munro
> ===
> 
> Below is my policy.xml document:
> 
>  xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit
> y-utility-1.0.xsd"
> xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy";>
>   
>   
>xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
>   
>   
>   
>RequireClientCertificate="false"/>
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
>   
>sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/Includ
> eToken/AlwaysToRecipient">
>   
>   
> 
>   
>   
>   
>   
>xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>
>   
>   
>   
>   
>   
>

[jira] Created: (AXIS2-3276) Null pointer exception while doing wsdl get using useOriginalWsdl option. Reason : underlying definitiion is not threadsafe

[Haneef Ali (JIRA)]

Null pointer exception while doing wsdl get using useOriginalWsdl option. 
Reason : underlying definitiion is not threadsafe
---

 Key: AXIS2-3276
 URL: https://issues.apache.org/jira/browse/AXIS2-3276
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.2
 Environment: HP UX
Reporter: Haneef Ali
Priority: Critical


I'm seeing Nullpointer exception during wsdl fetch.   My webservice is created 
using "useOriginalWSDL=true" option.
This happens only during concurrent access. It can be easily  reproduced by  
creating a JMeter test for  http get with 5 thread. BTW I'm using Axis 1.2

 From google search the reason for this seems to be  

" This is because the WSDL handling system reuses javax.wsdl.Definition objects 
across threads, which are not thread safe, because they internally use DOM 
elements."

References
 
http://jira.jboss.com/jira/browse/JBWS-419;jsessionid=AA4270C1E4896751CF
2440D7C6696706
 http://www.mail-archive.com/[EMAIL PROTECTED]/msg01292.html


java.lang.NullPointerException
at org.apache.xerces.dom.ParentNode.nodeListItem(Unknown Source)
at org.apache.xerces.dom.ParentNode.item(Unknown Source)
at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
at com.ibm.wsdl.util.xml.DOM2Writer.print(Unknown Source)
at com.ibm.wsdl.util.xml.DOM2Writer.serializeAsXML(Unknown
Source)
at
com.ibm.wsdl.extensions.schema.SchemaSerializer.marshall(Unknown Source)
at
com.ibm.wsdl.xml.WSDLWriterImpl.printExtensibilityElements(Unknown
Source)
at com.ibm.wsdl.xml.WSDLWriterImpl.printTypes(Unknown Source)
at com.ibm.wsdl.xml.WSDLWriterImpl.printDefinition(Unknown
Source)
at com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(Unknown Source)
at com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(Unknown Source)
at
org.apache.axis2.description.AxisService.printWSDL(AxisService.java:848)
at
org.apache.axis2.transport.http.ListingAgent.processListService(ListingA
gent.java:221)
at
org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:225)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at
weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(St
ubSecurityHelper.java:223)
at
weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityH
elper.java:125)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:2
83)
at
weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:1
75)
at
weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.r
un(WebAppServletContext.java:3245)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSu
bject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121
)
at
weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServ
letContext.java:2003)
at
weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletCont
ext.java:1909) 

 



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (AXIS2-3275) Add option to enable a wsa:MessageId in repsonse message

[Erwin Reinhoud (JIRA)]

Add option to enable a wsa:MessageId in repsonse message


 Key: AXIS2-3275
 URL: https://issues.apache.org/jira/browse/AXIS2-3275
 Project: Axis 2.0 (Axis2)
  Issue Type: New Feature
  Components: Addressing
Affects Versions: 1.3
 Environment: axis2 1.3tomcat 5.5java 1.5
Reporter: Erwin Reinhoud


At the moment, the wsa:MessageID on the response message is omitted as a
performance optimisation. It's not really possible to force
Axis2 to include it at the moment. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [AXIS2] Test failures on trunk

[David Illsley]

Looks like the build has been broken for a few days[1]. I'm not sure
why the notifications to the list stopped working...

[1] 
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuilds.vm/view/ProjectBuilds/id/61
David

On 15/10/2007, Amila Suriarachchi <[EMAIL PROTECTED]> wrote:
> Anne did all the integration tests pass when you commit the
> Axis2-2968 patch?
>
> I am getting lot of exceptions in wsdl processing (with imports I guess)
> now.
> did you check all those senarios before you commit?
>
> Amila.
>
>
> On 10/15/07, keith chapman <[EMAIL PROTECTED]> wrote:
> > Forwarding with the Axis2 prefix...
> >
> >
> > -- Forwarded message --
> > From: keith chapman < [EMAIL PROTECTED] >
> > Date: Oct 15, 2007 2:01 PM
> > Subject: Test failures on trunk
> > To: axis-dev@ws.apache.org
> >
> > Hi,
> >
> > Looks like there are test failures on trunk. The specific test that fails
> is
> >
> >
> org.apache.axis2.metadata.registry.MetadataFactoryRegistryTests
> >
> > Can somebody familiar with metadata module fix it.
> >
> > Thanks,
> > Keith.
> >
> > --
> > Keith Chapman
> > WSO2 Inc.
> > Oxygen for Web Services Developers.
> > http://wso2.org/
> >
> > --
> > Keith Chapman
> > WSO2 Inc.
> > Oxygen for Web Services Developers.
> > http://wso2.org/
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.


-- 
David Illsley - IBM Web Services Development

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [AXIS2] Test failures on trunk

[Amila Suriarachchi]

Anne did all the integration tests pass when you commit the
Axis2-2968 patch?

I am getting lot of exceptions in wsdl processing (with imports I guess)
now.
did you check all those senarios before you commit?

Amila.

On 10/15/07, keith chapman <[EMAIL PROTECTED]> wrote:
>
> Forwarding with the Axis2 prefix...
>
> -- Forwarded message --
> From: keith chapman <[EMAIL PROTECTED] >
> Date: Oct 15, 2007 2:01 PM
> Subject: Test failures on trunk
> To: axis-dev@ws.apache.org
>
> Hi,
>
> Looks like there are test failures on trunk. The specific test that fails
> is
>
> org.apache.axis2.metadata.registry.MetadataFactoryRegistryTests
>
> Can somebody familiar with metadata module fix it.
>
> Thanks,
> Keith.
>
> --
> Keith Chapman
> WSO2 Inc.
> Oxygen for Web Services Developers.
> http://wso2.org/
>
> --
> Keith Chapman
> WSO2 Inc.
> Oxygen for Web Services Developers.
> http://wso2.org/
>



-- 
Amila Suriarachchi,
WSO2 Inc.

[jira] Created: (AXIS2-3274) Axis2 kernel logging on WAS 6.1

[Pierre Casenove (JIRA)]

Axis2 kernel logging on WAS 6.1
---

 Key: AXIS2-3274
 URL: https://issues.apache.org/jira/browse/AXIS2-3274
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.3
 Environment: Axis2 1.3 under Websphere 6.1
Reporter: Pierre Casenove
Priority: Minor


 When deploying Axis2 based application, websphere tries to instantiates 
AxisServlet and throws following exception:
 Caused by: org.apache.commons.logging.LogConfigurationException:
 java.lang.ClassNotFoundException:
 org.apache.commons.logging.impl.Log4jFactory
 at 
org.apache.commons.logging.LogFactory$2.run(LogFactory.java:609)
 at 
java.security.AccessController.doPrivileged(AccessController.java:193)
 at 
org.apache.commons.logging.LogFactory.newFactory(LogFactory.java:561)
 at 
org.apache.commons.logging.LogFactory.getFactory(LogFactory.java:352)
 at 
org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
 at
 org.apache.axis2.transport.http.AxisServlet.(AxisServlet.java:79)

 The root cause is explained here :
 
http://wiki.apache.org/jakarta-commons/Logging/FrequentlyAskedQuestions?highlight=%28websphere%29

 In order to get everything works, I had to modify axis2-kernel.jar to add a 
commons-logging.properties containing:
 priority=1
 
org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl
 org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

I tried to first put this file in my web app classpath but it didn't work.
The only solution was to put it in Axis2 Kernel jar.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[ANN] Apache Savan/C 0.90 Released

[Damitha Kumarage]

Hi List,
Apache Savan/C Team is pleased to announce the release of Apache Savan/C
version 0.90
You can download this release from
http://ws.apache.org/savan/c/download.cgi
This release is supposed to be used with the Axis2C 1.1.0 distribution which
is released recently.

Key Features:

1 Support for WS-Eventing Specification August 2004.
2 Support for Subscribe, Unsubscribe, Renew and GetStatus operations.
3 Support for subscription management endpoint which could be the
Event Source itself or separate subscription management endpoint.
4 Persistent storage for subscribers.
5 Support for both SOAP 1.1 and 1.2.
6 Samples to test scenarios.
7 Documentation

We welcome your early feedback on this implementation.
Thanks for your interest in Savan/C

-- Apache Savan/C Team --

Re: [Axis2] Understanding Axis2 dependencies

[Sanka Samaranayke]

Hi,




Sanjiva Weerawarana wrote:

Thanks Ajith.

I think we should document this somewhere- we often get this question 
and there's obviously reasons for why we have all these dependencies. 
We need to clearly indicate which things are optional and indicate 
under what conditions they come into use.


I am not a fan of going back to the seven different distributions 
model as that was confusing to users. Knowing the dependency reasons 
will help embedders decide what they really need to pull in and what's 
optional.


One jar I didn't understand is the mex jar. Why is that around; that 
should only be in the mex mar I believe.


You need that jar if you use MexClient in your client code.

Thanks,
Sanka




Sanjiva.

Ajith Ranabahu wrote:

Hi Lawrence,
Let me see whether I can make sense of some of the stuff. Others will
chip in as needed and will surely holler if I make a mistake.


Axis2 Third Party Dependencies
--
activation-1.1.jarMIME support
annogen-0.1.0.jar Annotation support
axiom-api-1.2.5.jar   XML pull parsing
axiom-dom-1.2.5.jar   XML pull parsing
axiom-impl-1.2.5.jar  XML pull parsing
backport-util-concurrent-2.2.jar  ?


Thread pooling support. This feature is built in for Java 1.5 and this
particular jar has a backport of that code to Java 1.4


commons-codec-1.3.jar URL encoding?
commons-fileupload-1.1.1.jar  Used for uploading new service
  files in the admin client?


Yes - needed only when using the webapp


commons-httpclient-3.0.1.jar  Used by the Axis2 kernel?


Yes - but primarily on the client side. I believe it is needed in the
server side if asynchronous calls are to be supported.


commons-io-1.2.jar?
commons-logging-1.1.jar   Is this related to Log4J?


Well kind of. Commons logging is a common API on multiple logging
frameworks (log4j/java.util.logging) but allows the switching of the
logging engine easily. All the logging code inside the Axis2 source
are made using commons logging classes.


geronimo-annotation_1.0_spec-1.1.jar  More annotation support?
geronimo-jms_1.1_spec-1.1.jar JMS bindings?


JMS transport really.


httpcore-4.0-alpha5.jar   Used by the Axis2 kernel?
httpcore-nio-4.0-alpha5.jar   Used by the Axis2 kernel?
httpcore-niossl-4.0-alpha5.jarUsed by the Axis2 kernel?


The nio (non-blocking io) transport dependancies. Its an improved
version of the HTTP transport. My understanding is that this is used
optionally (the default Axis2.xml does not point to this transport
AFAIK) but needs confirmation


jaxb-api-2.0.jar  Used by the Axis2 kernel?
jaxb-impl-2.0.5.jar   Used by the Axis2 kernel?
jaxb-xjc-2.0.5.jarUsed by the Axis2 kernel?


These were primarily for the Jaxb based code generation but now  the
JAX-WS module uses these as dependencies. In any case these are needed
 1. if the user needs to generate code with Jaxb data binding
 2. If he needs the JAX-WS module running (which is only on a jdk 1.5
environment)

jaxen-1.1.1.jar   XPath engine - where is this 
used?


AXIOM has a Jaxen based Xpath implementation and this jar has the core
Jaxen classes for it


jettison-1.0-RC1.jar  JSON StAX parser



jibx-bind-1.1.5.jar   Related to JAXB?
jibx-run-1.1.5.jarRelated to JAXB?


Nope. Jibx is an alternate databinding. My guess is one would need
these only to use Jibx generated code (databinding - either on server
side or client side)


juli-6.0.10.jar   ?


Juli is an alternate implementation to Java.util logging from tomcat.
Here is what the tomcat site says
 "A limitation of JDK Logging appears to be the inability to have
per-web application logging, as the configuration is per-VM. As a
result, Tomcat will, in the default configuration, replace the default
LogManager implementation with a container friendly implementation
called JULI, which addresses these shortcomings."

It seems that this one is needed only when the webapp comes to play

log4j-1.2.14.jar  Logging - Is this optional? I 
don't

  always want to use Log4J - for
  example, when working with 
Eclipse.


I suppose the default logging configuration with common-logging is
log4j. I assume we can turn it to java.util logging but most folks are
not in favor of it (it will reduce this jar though)


mail-1.4.jar  MIME support?


Yes


mex-impl-1.3.jar  ?


Metadata exchange implementation (WS-Mex).


neethi-2.0.2.jar  WS Policy - Is this optional?


I don't think so. This would be required both at runtime and codegen
time to process policies


soapmonit

[AXIS2] Test failures on trunk

[keith chapman]

Forwarding with the Axis2 prefix...

-- Forwarded message --
From: keith chapman <[EMAIL PROTECTED]>
Date: Oct 15, 2007 2:01 PM
Subject: Test failures on trunk
To: axis-dev@ws.apache.org

Hi,

Looks like there are test failures on trunk. The specific test that fails is

org.apache.axis2.metadata.registry.MetadataFactoryRegistryTests

Can somebody familiar with metadata module fix it.

Thanks,
Keith.

-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/

AxisFault: unknown exception is getting

[Pradip Sonar]

 

Hi,

I am invoking web service from Client application.

For one specific condition, we are raising AxisFault exception in web
service method on server side.

On client side we are getting following exception,

 

org.apache.axis2.AxisFault: unknown

  at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java
:434)

  at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper
ation.java:373)

  at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO
peration.java:294)

  at
com.erisk.wsabacus.client.WsabacuswsabacusSOAP11PortStub.getDataset(Wsab
acuswsabacusSOAP11PortStub.java:825)

  at
com.erisk.wsabacus.test.TestWebOperations.testGetDataset(TestWebOperatio
ns.java:241)

  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

  at java.lang.reflect.Method.invoke(Unknown Source)

  at junit.framework.TestCase.runTest(TestCase.java:154)

  at junit.framework.TestCase.runBare(TestCase.java:127)

  at junit.framework.TestResult$1.protect(TestResult.java:106)

  at junit.framework.TestResult.runProtected(TestResult.java:124)

  at junit.framework.TestResult.run(TestResult.java:109)

  at junit.framework.TestCase.run(TestCase.java:118)

  at junit.framework.TestSuite.runTest(TestSuite.java:208)

  at junit.framework.TestSuite.run(TestSuite.java:203)

  at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe
stRunner.java:478)

  at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRun
ner.java:344)

  at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRu
nner.java:196)

 

 

Please provide the possible reasons for this

 

Thanks & Regards,

Pradip S. Sonar

Software Engineer * SunGard * BancWare

Meridian Plaza Sr.No.108/8/1+2/1, S.B. Road,

Pune 411053
Tel +91-20-2560 6000  Ext. 6220

Direct  +91-20-2560 6220

Mobile  9833767145, 9860937675

[EMAIL PROTECTED]   *
www.sungard.com   

 

P Think before you print
CONFIDENTIALITY: This e-mail (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited.  If you receive this e-mail in error,
please notify the sender and delete this e-mail from your system. 

 

Test failures on trunk

[keith chapman]

Hi,

Looks like there are test failures on trunk. The specific test that fails is

org.apache.axis2.metadata.registry.MetadataFactoryRegistryTests

Can somebody familiar with metadata module fix it.

Thanks,
Keith.

-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/