[jira] Resolved: (AXIS2-829) WSDL service builder fails to see service definition when it comes from an import
[ http://issues.apache.org/jira/browse/AXIS2-829?page=all ] Deepal Jayasinghe resolved AXIS2-829: - Resolution: Fixed fixed in current SVN WSDL service builder fails to see service definition when it comes from an import - Key: AXIS2-829 URL: http://issues.apache.org/jira/browse/AXIS2-829 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: core Versions: 1.0 Reporter: Marc Gagnon Assignee: Deepal Jayasinghe Attachments: WSDL11ToAxisServiceBuilder.patch, wsdl.zip When the service element of a WSDL is not in the first level file, there is an exception like this: [java] Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:94) [java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) [java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) [java] Caused by: org.apache.axis2.AxisFault: No service element found in the WSDL; nested exception is: [java] org.apache.axis2.AxisFault: No service element found in the WSDL [java] at org.apache.axis2.description.WSDL2AxisServiceBuilder.populateService(WSDL2AxisServiceBuilder.java:243) [java] at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:87) I am pretty sure the spec allows services definitions to be imported. The book from which I am learning web services has a specific example using this way of organizing WSDL (J2EE Web Services by Richard Monson-Haefel, page 136 : 5.2.4). So, assuming service definitions of imported WSDL should be visible, here is my patch: The reason for this problem is that the code in WSDL2AxisServiceBuilder method processImports does not recursively include the services in the current level's hash map: ... //add messages Map messagesMap = importedDef.getMessages(); wsdl4JDefinition.getMessages().putAll(messagesMap); //add portypes Map porttypeMap = importedDef.getPortTypes(); wsdl4JDefinition.getPortTypes().putAll(porttypeMap); //add bindings Map bindingMap = importedDef.getBindings(); wsdl4JDefinition.getBindings().putAll(bindingMap); // // Must add services of imported definitions into current wsdl definitions. //- } ... I simply added: //add services Map serviceMap = importedDef.getServices(); wsdl4JDefinition.getServices().putAll(serviceMap); And it worked. I tested this using on the refactored version: WSDL11ToAxisServiceBuilder Here is the patch: Index: WSDL11ToAxisServiceBuilder.java === --- WSDL11ToAxisServiceBuilder.java (revision 415081) +++ WSDL11ToAxisServiceBuilder.java (working copy) @@ -916,6 +916,9 @@ Map bindingMap = importedDef.getBindings(); wsdl4JDefinition.getBindings().putAll(bindingMap); + //add services + Map serviceMap = importedDef.getServices(); + wsdl4JDefinition.getServices().putAll(serviceMap); } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-837) Java2WSDL should generate a WSDL interface that accepts an empty SOAP Body
[ http://issues.apache.org/jira/browse/AXIS2-837?page=all ]
Deepal Jayasinghe resolved AXIS2-837:
-
Resolution: Fixed
applied the patch
Java2WSDL should generate a WSDL interface that accepts an empty SOAP Body
--
Key: AXIS2-837
URL: http://issues.apache.org/jira/browse/AXIS2-837
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Reporter: Davanum Srinivas
Assignee: Deepal Jayasinghe
Attachments: Axis2-Java2WSDL-Patch-30-Jun.diff
Java code:
public class TestAxis {
public String getDate(){
return new java.util.Date().toString();
}
}
Quote from Anne at
http://marc.theaimsgroup.com/?l=axis-userm=115089935000189w=2:
Java2WSDL should generate a WSDL interface that accepts an empty SOAP Body.
e.g.,
wsdl:message name=getDateMessage/
But based on a bunch of recent messages I've seen, Axis2 barfs on an empty
SOAP Body. This is a bug that needs to be fixed. I don't know if anyone has
created a JIRA for it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-756) elementFormDefault=unqualified is default
[ http://issues.apache.org/jira/browse/AXIS2-756?page=comments#action_12418913 ] Venkatakrishnan commented on AXIS2-756: --- This has been addressed as part of the patch submitted for http://issues.apache.org/jira/browse/AXIS2-837. Now there are two more options 'efd' and 'afd' for setting the elementFormDefault and attributeFormDefault values to the xmlschemas. These will default to 'qualified' when none of these options are specified. elementFormDefault=unqualified is default --- Key: AXIS2-756 URL: http://issues.apache.org/jira/browse/AXIS2-756 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: wsdl Versions: 1.0 Reporter: Kinichiro Inoguchi Assignee: Ajith Harshana Ranabahu This issue is talking about elementFormDefault for schema of WSDL. elementFormDefault=qualified is right. With 1.0 elementFormDefault=unqualified seems default. It seems elementFormDefault=qualified was default generated WSDL settings at 0.95. You can check this issu by WSDL of version service. http://localhost:8080/axis2/services/version?wsdl Maybe, this issue affects some parts; - auto generation WSDL function for deployed service - Java2WSDL function - WSDL generating eclipse plug-in BTW, which is better about attributeFormDefault=unqualified or attributeFormDefault=qualified ? I also hope that I could override 'elementFormDefault' value by services.xml, as I could override namespace. pls refer to: http://marc.theaimsgroup.com/?l=axis-userm=114804169309670w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] ReplyTo is not working
On Mon, 2006-07-03 at 01:45 -0400, Davanum Srinivas wrote: Sanjiva, Can you please chime in on the problem itself [1]? Maybe if we concentrate on the problem in question rather than dissect the specific solution we will be better off? Interesting use-case. Is this the scenario that motivated David's proposal? David? Does the WS-Addr spec have anything to say about whether its legit to do this kinda stuff? The scenario is that the response message (containing a RelatesTo with @relationshipType=wsa:Response) is being used as an invocation message for someone else. Didn't the test suite have some stuff that checked proper handling of RelatesTo? Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] ReplyTo is not working
Sanjiva, Quoting from [1]. There is no guarantee that whoever sent the original message may not be the recipient of the reply. /wsa:RelatesTo - This OPTIONAL (repeating) element information item contributes one abstract [relationship] property value, in the form of an (IRI, IRI) pair. The content of this element (of type xs:anyURI) conveys the [message id] of the related message. /wsa:RelatesTo/@RelationshipType - This OPTIONAL attribute (of type xs:anyURI) conveys the relationship type as an IRI. When absent, the implied value of this attribute is http://www.w3.org/2005/08/addressing/reply;. The test suite had only 2 nodes. Here we have 3. Which is not prohibited by the spec. The only reference in the SOAP binding [2] is how the fault messages are correlated to the original message. I racked my brain, but cannot see the spec prohibiting any of the examples / use cases that david mentions in [3]. Could you please do a quick review as well. Thanks, dims [1] http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/ [2] http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/ [3] http://marc.theaimsgroup.com/?l=axis-devm=114915549611516w=2 On 7/3/06, Sanjiva Weerawarana [EMAIL PROTECTED] wrote: On Mon, 2006-07-03 at 01:45 -0400, Davanum Srinivas wrote: Sanjiva, Can you please chime in on the problem itself [1]? Maybe if we concentrate on the problem in question rather than dissect the specific solution we will be better off? Interesting use-case. Is this the scenario that motivated David's proposal? David? Does the WS-Addr spec have anything to say about whether its legit to do this kinda stuff? The scenario is that the response message (containing a RelatesTo with @relationshipType=wsa:Response) is being used as an invocation message for someone else. Didn't the test suite have some stuff that checked proper handling of RelatesTo? Sanjiva. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://people.apache.org/~dims/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] ReplyTo is not working
Sanjiva Weerawarana [EMAIL PROTECTED] wrote on 07/03/2006 08:51:51 AM: On Mon, 2006-07-03 at 01:45 -0400, Davanum Srinivas wrote: Sanjiva, Can you please chime in on the problem itself [1]? Maybe if we concentrate on the problem in question rather than dissect the specific solution we will be better off? Interesting use-case. Is this the scenario that motivated David's proposal? David? Yes, this is the scenario I'd like to support. Does the WS-Addr spec have anything to say about whether its legit to do this kinda stuff? The scenario is that the response message (containing a RelatesTo with @relationshipType=wsa:Response) is being used as an invocation message for someone else. Didn't the test suite have some stuff that checked proper handling of RelatesTo? The spec doesn't say anything about this specific scenario though quite what the point of separate ReplyTo and FaultTo EPRs is if this isn't supported escapes me. The other thing to note is that the reply relationship type is defined very broadly, just defining the semantic and not tieing it to a particular MEP. Because it isn't explicitly mentioned in the spec it didn't appear in the test suite. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-861) cache setting is not working in Nightly build Jun 22,06
cache setting is not working in Nightly build Jun 22,06 --- Key: AXIS2-861 URL: http://issues.apache.org/jira/browse/AXIS2-861 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: core Versions: 1.0 Environment: Axis2 1.0, nightly build version 22 Jun 06 Jetty 6.0.0 beta 16 linux environment java language Reporter: Wan Kaveevivitchai There is the problem of file caching, it doesn't working in nightly build version released on June 22, 06. Eventhough, the cache properties in axis2.xml already been set. Is there any solution for this? Is it a bug? I was writing some email earlier about problem in sending large file ~ 10 MB and got broken pipe exception. And there was the suggestion to use the new nightly release which is the 22 Jun 06 release and the broken pipe problem was solve. So i moved on to test with 100 MB size attachment, and i got java.lang.OutOfMemory error, so i did some setting about cache on axis2.xml as following parameter name=cacheAttachments locked=falsetrue/parameter parameter name=attachmentDIR locked=false/users/alice3/home//parameter parameter name=sizeThreshold locked=false4000/parameter but it seems like it still cache into the memory, also when i check at the home directory, there is no cached file at all. So we tried extend the memory size and the attachment is received fine but it isn't the good way to do it, i supposed. So i think the problem is about cache is not working. The same setting is working fine with the other nightly build version released on 4 Jun 06 but that one has the problem about broken pipe in sending large file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (AXIS2-862) cannot deploy rampart successfully
cannot deploy rampart successfully -- Key: AXIS2-862 URL: http://issues.apache.org/jira/browse/AXIS2-862 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: samples, build,site docs Versions: 1.0 Environment: Axis2 1.0 nightly build released on 22 Jun 06 Jetty 6.0.0 beta 16 linux environment Reporter: Wan Kaveevivitchai I have tested another issue related to the ws-security. I had downloaded the rampart module and then try to deploy it by add the module into axis2.xml and put .aar file into modules directory under web-inf in axis2 , when i started the server, the problem occur it said that : Trying to engage a module which is not available but i did test it with the other version release on Jun 4th, and everything work file for that version as well as the cache..but in Jun 4th version, it had the problem of broken pipe while sending large attachment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-756) elementFormDefault=unqualified is default
[ http://issues.apache.org/jira/browse/AXIS2-756?page=all ] Deepal Jayasinghe resolved AXIS2-756: - Resolution: Fixed vankat is fixed the issue elementFormDefault=unqualified is default --- Key: AXIS2-756 URL: http://issues.apache.org/jira/browse/AXIS2-756 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: wsdl Versions: 1.0 Reporter: Kinichiro Inoguchi Assignee: Ajith Harshana Ranabahu This issue is talking about elementFormDefault for schema of WSDL. elementFormDefault=qualified is right. With 1.0 elementFormDefault=unqualified seems default. It seems elementFormDefault=qualified was default generated WSDL settings at 0.95. You can check this issu by WSDL of version service. http://localhost:8080/axis2/services/version?wsdl Maybe, this issue affects some parts; - auto generation WSDL function for deployed service - Java2WSDL function - WSDL generating eclipse plug-in BTW, which is better about attributeFormDefault=unqualified or attributeFormDefault=qualified ? I also hope that I could override 'elementFormDefault' value by services.xml, as I could override namespace. pls refer to: http://marc.theaimsgroup.com/?l=axis-userm=114804169309670w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS-1529) Bad namespaces in serialized beans in doc/literal
[ http://issues.apache.org/jira/browse/AXIS-1529?page=all ]
Per Salomonsson updated AXIS-1529:
--
Attachment: axis-patch.txt
I have attached a patch (and a patched lib) compatible with 1.4.0
release/branch.
The problem we had was when using document/literal wrapped complex types were
not serialized correctly (missing namespaces). I have also included a fix for
using arrays. them item tag is now used (to match the xml schema in the WSDL
file), and with the correct namespace. The array-fix is taken more or less from
another bugreport that was reported here at JIRA.
Please let me know if it works for you to.
Here is how we have used it:
1. Write the java classes that should represent the web service interface -
including your java beans.
2. generate deploy/undeploy wsdd's using ant task axis-wsdl2java
(DOCUMENT/LITERAL WRAPPED)
3. startup the server and publish the services.
The patch has only been used/tested with axis on the serverside, on the client
side we have used 2 other client implementations to test/verify.
Bad namespaces in serialized beans in doc/literal
-
Key: AXIS-1529
URL: http://issues.apache.org/jira/browse/AXIS-1529
Project: Apache Axis
Type: Bug
Components: Serialization/Deserialization
Versions: current (nightly)
Environment: win xp, jdk 1.4.2, jboss 3.2.5
Reporter: Tudor Teusan
Attachments: axis-patch.txt
It seems that AXIS (latest CVS) doesn't serialize properly complex
objects (beans) when in doc/literal.
More precisely it doesn't handle as it should a SOAP body with multiple
namespaces, as shown in the following exemple :
(I've come upon this problem trying to return a tree structure from a
web service)
The service is a TreeProvider defined as
---
class TreeProvider {
private Node root;
...
public Node getTree(){ return root; }
...
}
---
Node being a very simple bean with two attributes : id and name.
---
class Node {
private String id, name;
public string getName(){ return name; }
...
}
---
Node and TreeProvider are in 2 different packages
com.knowesis.ws.TreeProvider and com.knowesis.tree.Node ( left out for
brevity).
In the constructor of TreeProvider the root node is initilized as
id=root, name=root.
The deploy.wsdd is :
---
...
service name=TreeProvider style=document use=literal
namespaceurn:AthanorWS:ws/namespace
parameter name=className value=com.knowesis.ws.TreeProvider/
parameter name=allowedMethods value=getTree/
beanMapping xmlns:data=urn:AthanorWS:data qname=data:Node
languageSpecificType=java:com.knowesis.tree.Node/
/service
...
---
the service gets deployed ok and the types section in the auto-generated wsdl
looks like this :
---
...
wsdl:types
schema elementFormDefault=qualified
targetNamespace=urn:AthanorWS:data
xmlns=http://www.w3.org/2001/XMLSchema;
complexType name=Node
sequence
element name=id nillable=true type=xsd:string /
element name=name nillable=true type=xsd:string
/
/sequence
/complexType
/schema
schema elementFormDefault=qualified
targetNamespace=urn:AthanorWS:ws
xmlns=http://www.w3.org/2001/XMLSchema;
import namespace=urn:AthanorWS:data /
element name=getTreeReturn type=tns1:Node /
/schema
/wsdl:types
...
---
notice the the two namespaces (and this is how it should be) and the
elementFormDefault=qualified for the two schemas.
A getTree() invocation results in :
---
...
soapenv:Body
getTreeReturn xmlns=urn:AthanorWS:ws
idroot/id
nameroot/name
/getTreeReturn
/soapenv:Body
...
---
The contents of the generated body is not valid with respect to the wsdl
specified schemas.
id and root elements are in the same namespace as getTreeReturn
(urn:AthanorWS:ws) instead of being in their own urn:AthanorWS:data
namespace :
getTreeReturn xmlns=urn:AthanorWS:ws
id xmlns=urn:AthanorWS:dataroot/id
name xmlns=urn:AthanorWS:dataroot/name
/getTreeReturn
As a direct consequence a generated .Net client simply refuses to
deserialize the response and always returns an empty answer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS-1529) Bad namespaces in serialized beans in doc/literal
[ http://issues.apache.org/jira/browse/AXIS-1529?page=all ]
Per Salomonsson updated AXIS-1529:
--
Attachment: axis-patched.jar
And the patched jar.
Bad namespaces in serialized beans in doc/literal
-
Key: AXIS-1529
URL: http://issues.apache.org/jira/browse/AXIS-1529
Project: Apache Axis
Type: Bug
Components: Serialization/Deserialization
Versions: current (nightly)
Environment: win xp, jdk 1.4.2, jboss 3.2.5
Reporter: Tudor Teusan
Attachments: axis-patch.txt, axis-patched.jar
It seems that AXIS (latest CVS) doesn't serialize properly complex
objects (beans) when in doc/literal.
More precisely it doesn't handle as it should a SOAP body with multiple
namespaces, as shown in the following exemple :
(I've come upon this problem trying to return a tree structure from a
web service)
The service is a TreeProvider defined as
---
class TreeProvider {
private Node root;
...
public Node getTree(){ return root; }
...
}
---
Node being a very simple bean with two attributes : id and name.
---
class Node {
private String id, name;
public string getName(){ return name; }
...
}
---
Node and TreeProvider are in 2 different packages
com.knowesis.ws.TreeProvider and com.knowesis.tree.Node ( left out for
brevity).
In the constructor of TreeProvider the root node is initilized as
id=root, name=root.
The deploy.wsdd is :
---
...
service name=TreeProvider style=document use=literal
namespaceurn:AthanorWS:ws/namespace
parameter name=className value=com.knowesis.ws.TreeProvider/
parameter name=allowedMethods value=getTree/
beanMapping xmlns:data=urn:AthanorWS:data qname=data:Node
languageSpecificType=java:com.knowesis.tree.Node/
/service
...
---
the service gets deployed ok and the types section in the auto-generated wsdl
looks like this :
---
...
wsdl:types
schema elementFormDefault=qualified
targetNamespace=urn:AthanorWS:data
xmlns=http://www.w3.org/2001/XMLSchema;
complexType name=Node
sequence
element name=id nillable=true type=xsd:string /
element name=name nillable=true type=xsd:string
/
/sequence
/complexType
/schema
schema elementFormDefault=qualified
targetNamespace=urn:AthanorWS:ws
xmlns=http://www.w3.org/2001/XMLSchema;
import namespace=urn:AthanorWS:data /
element name=getTreeReturn type=tns1:Node /
/schema
/wsdl:types
...
---
notice the the two namespaces (and this is how it should be) and the
elementFormDefault=qualified for the two schemas.
A getTree() invocation results in :
---
...
soapenv:Body
getTreeReturn xmlns=urn:AthanorWS:ws
idroot/id
nameroot/name
/getTreeReturn
/soapenv:Body
...
---
The contents of the generated body is not valid with respect to the wsdl
specified schemas.
id and root elements are in the same namespace as getTreeReturn
(urn:AthanorWS:ws) instead of being in their own urn:AthanorWS:data
namespace :
getTreeReturn xmlns=urn:AthanorWS:ws
id xmlns=urn:AthanorWS:dataroot/id
name xmlns=urn:AthanorWS:dataroot/name
/getTreeReturn
As a direct consequence a generated .Net client simply refuses to
deserialize the response and always returns an empty answer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-862) cannot deploy rampart successfully
[ http://issues.apache.org/jira/browse/AXIS2-862?page=comments#action_12418925 ] Deepal Jayasinghe commented on AXIS2-862: - You have to put .mar file into module directory not .aar file. cannot deploy rampart successfully -- Key: AXIS2-862 URL: http://issues.apache.org/jira/browse/AXIS2-862 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: samples, build,site docs Versions: 1.0 Environment: Axis2 1.0 nightly build released on 22 Jun 06 Jetty 6.0.0 beta 16 linux environment Reporter: Wan Kaveevivitchai I have tested another issue related to the ws-security. I had downloaded the rampart module and then try to deploy it by add the module into axis2.xml and put .aar file into modules directory under web-inf in axis2 , when i started the server, the problem occur it said that : Trying to engage a module which is not available but i did test it with the other version release on Jun 4th, and everything work file for that version as well as the cache..but in Jun 4th version, it had the problem of broken pipe while sending large attachment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (AXIS-2473) Server reponse does not match WSDL
[ http://issues.apache.org/jira/browse/AXIS-2473?page=all ]
Per Salomonsson updated AXIS-2473:
--
Attachment: axis-patched.jar
And a patched lib if you want to try it directly (replace the axis.jar in 1.4
release).
Server reponse does not match WSDL
--
Key: AXIS-2473
URL: http://issues.apache.org/jira/browse/AXIS-2473
Project: Apache Axis
Type: Bug
Components: WSDL processing
Versions: 1.2.1, 1.3
Environment: Win2K, Axis running under Tomcat 4.31
Reporter: John Busfield
Attachments: axis-patch.txt, axis-patched.jar, deploy.wsdd,
server-config.wsdd
Below I have included the WSDL for a simple test service, followed by the
Axis response to a request for this service. As ou can see, the WSDL claims
the paramInt paramStr elements
are in the http://util.services.mycompany.com namespace, but in the
generated response, they're in the http://services.mycompany.com namespace. I
am using Axis 1.2.1 but have also also confirmed this behavior in 1.3.
The class structure behind the service looks like this
/^*** Info.java ***/
package com.mycompany.services.util;
public class Info
{
private String paramStr;
private int paramInt;
public int getParamInt() {
return paramInt;
}
public void setParamInt(int paramInt) {
this.paramInt = paramInt;
}
public String getParamStr() {
return paramStr;
}
public void setParamStr(String paramStr) {
this.paramStr = paramStr;
}
}
/^*** MyService.java ***/
package com.mycompany.services;
import com.mycompany.services.util.Info;
public class MyService
{
public Info getInfo()
{
Info i = new Info();
i.setParamInt(14);
i.setParamStr(hello);
return i;
}
}
WSDL
?xml version=1.0 encoding=UTF-8?
wsdl:definitions targetNamespace=http://services.mycompany.com;
xmlns:apachesoap=http://xml.apache.org/xml-soap;
xmlns:impl=http://services.mycompany.com;
xmlns:intf=http://services.mycompany.com;
xmlns:tns1=http://util.services.mycompany.com;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
!--WSDL created by Apache Axis version: 1.2.1
Built on Jun 14, 2005 (09:15:57 EDT)--
wsdl:types
schema elementFormDefault=qualified
targetNamespace=http://services.mycompany.com;
xmlns=http://www.w3.org/2001/XMLSchema;
import namespace=http://util.services.mycompany.com/
element name=getInfo
complexType/
/element
element name=getInfoResponse
complexType
sequence
element name=getInfoReturn type=tns1:Info/
/sequence
/complexType
/element
/schema
schema elementFormDefault=qualified
targetNamespace=http://util.services.mycompany.com;
xmlns=http://www.w3.org/2001/XMLSchema;
complexType name=Info
sequence
element name=paramInt type=xsd:int/
element name=paramStr nillable=true type=xsd:string/
/sequence
/complexType
/schema
/wsdl:types
wsdl:message name=getInfoRequest
wsdl:part element=impl:getInfo name=parameters/
/wsdl:message
wsdl:message name=getInfoResponse
wsdl:part element=impl:getInfoResponse name=parameters/
/wsdl:message
wsdl:portType name=MyService
wsdl:operation name=getInfo
wsdl:input message=impl:getInfoRequest
name=getInfoRequest/
wsdl:output message=impl:getInfoResponse
name=getInfoResponse/
/wsdl:operation
/wsdl:portType
wsdl:binding name=MyServiceSoapBinding type=impl:MyService
wsdlsoap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=getInfo
wsdlsoap:operation soapAction=/
wsdl:input name=getInfoRequest
wsdlsoap:body use=literal/
/wsdl:input
wsdl:output name=getInfoResponse
wsdlsoap:body use=literal/
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:service name=MyServiceService
wsdl:port binding=impl:MyServiceSoapBinding name=MyService
wsdlsoap:address
location=http://localhost/test/services/MyService/
/wsdl:port
/wsdl:service
/wsdl:definitions
HTTP/1.1 200 OK
Content-Type: text/xml;charset=utf-8
Transfer-Encoding: chunked
Date: Mon, 01 May 2006 16:03:16 GMT
Server: Apache-Coyote/1.1
19e
?xml version=1.0 encoding=UTF-8?soapenv:Envelope
xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-
instancesoapenv:BodygetInfoResponse
[jira] Updated: (AXIS-2473) Server reponse does not match WSDL
[ http://issues.apache.org/jira/browse/AXIS-2473?page=all ]
Per Salomonsson updated AXIS-2473:
--
Attachment: axis-patch.txt
I have attached a patch (and a patched lib) compatible with Axis 1.4.0
release/branch.
The problem we had was when using document/literal wrapped complex types were
not serialized correctly (missing namespaces). I have also included a fix for
using arrays. them item tag is now used (to match the xml schema in the WSDL
file), and with the correct namespace. The array-fix is taken more or less from
another bugreport that was reported here at JIRA.
Please let me know if it works for you to.
Here is how we have used it:
1. Write the java classes that should represent the web service interface -
including your java beans.
2. generate deploy/undeploy wsdd's using ant task axis-wsdl2java
(DOCUMENT/LITERAL WRAPPED)
3. startup the server and publish the services.
The patch has only been used/tested with axis on the serverside, on the client
side we have used 2 other client implementations to test/verify.
Server reponse does not match WSDL
--
Key: AXIS-2473
URL: http://issues.apache.org/jira/browse/AXIS-2473
Project: Apache Axis
Type: Bug
Components: WSDL processing
Versions: 1.2.1, 1.3
Environment: Win2K, Axis running under Tomcat 4.31
Reporter: John Busfield
Attachments: axis-patch.txt, axis-patched.jar, deploy.wsdd,
server-config.wsdd
Below I have included the WSDL for a simple test service, followed by the
Axis response to a request for this service. As ou can see, the WSDL claims
the paramInt paramStr elements
are in the http://util.services.mycompany.com namespace, but in the
generated response, they're in the http://services.mycompany.com namespace. I
am using Axis 1.2.1 but have also also confirmed this behavior in 1.3.
The class structure behind the service looks like this
/^*** Info.java ***/
package com.mycompany.services.util;
public class Info
{
private String paramStr;
private int paramInt;
public int getParamInt() {
return paramInt;
}
public void setParamInt(int paramInt) {
this.paramInt = paramInt;
}
public String getParamStr() {
return paramStr;
}
public void setParamStr(String paramStr) {
this.paramStr = paramStr;
}
}
/^*** MyService.java ***/
package com.mycompany.services;
import com.mycompany.services.util.Info;
public class MyService
{
public Info getInfo()
{
Info i = new Info();
i.setParamInt(14);
i.setParamStr(hello);
return i;
}
}
WSDL
?xml version=1.0 encoding=UTF-8?
wsdl:definitions targetNamespace=http://services.mycompany.com;
xmlns:apachesoap=http://xml.apache.org/xml-soap;
xmlns:impl=http://services.mycompany.com;
xmlns:intf=http://services.mycompany.com;
xmlns:tns1=http://util.services.mycompany.com;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:wsdlsoap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
!--WSDL created by Apache Axis version: 1.2.1
Built on Jun 14, 2005 (09:15:57 EDT)--
wsdl:types
schema elementFormDefault=qualified
targetNamespace=http://services.mycompany.com;
xmlns=http://www.w3.org/2001/XMLSchema;
import namespace=http://util.services.mycompany.com/
element name=getInfo
complexType/
/element
element name=getInfoResponse
complexType
sequence
element name=getInfoReturn type=tns1:Info/
/sequence
/complexType
/element
/schema
schema elementFormDefault=qualified
targetNamespace=http://util.services.mycompany.com;
xmlns=http://www.w3.org/2001/XMLSchema;
complexType name=Info
sequence
element name=paramInt type=xsd:int/
element name=paramStr nillable=true type=xsd:string/
/sequence
/complexType
/schema
/wsdl:types
wsdl:message name=getInfoRequest
wsdl:part element=impl:getInfo name=parameters/
/wsdl:message
wsdl:message name=getInfoResponse
wsdl:part element=impl:getInfoResponse name=parameters/
/wsdl:message
wsdl:portType name=MyService
wsdl:operation name=getInfo
wsdl:input message=impl:getInfoRequest
name=getInfoRequest/
wsdl:output message=impl:getInfoResponse
name=getInfoResponse/
/wsdl:operation
/wsdl:portType
wsdl:binding name=MyServiceSoapBinding type=impl:MyService
wsdlsoap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=getInfo
wsdlsoap:operation soapAction=/
wsdl:input name=getInfoRequest
generating wsdl from java source
Ladies and Gentlemen, I tried to generate the WSDL file from a java class with the code generation Eclipse Plug in (AXIS2 1,0). But the Wizard does not react with selection of this option. The next - button does not have a function. Is there a new version or work around? Thank you for the assistance. Yours sincerely Lutz Schoder SoftConcept GmbH Borriesstraße 35 D-32257 Bünde http://www.softconcept.net http://www.softcontract.de
Re: [Axis2] build failed due to security test failure
Hi Chuck, Thank you very much for your reply. I have already solved the problem by reinstall the JDK. In the previous JDK, due to some policy reason, I was forced to modify the default jre lib. The javax.crypto.Cipher class in the jce.jar is overwritten by another version. The whole jce.jar is disabled. Sun provider is not the first provider, and SunJSSE is disabled. Can i confirm with the team dealing with security, whether the security package assumes that Sun provider is the first provider in the list? and whether the SunJSSE will be used? If the answers are yes, could the security team modify update the code to insert the Sun provider as the first provider at runtime? Regards, Xinjun On 7/3/06, Chuck Williams [EMAIL PROTECTED] wrote: Xinjun, I'm not sure why you are getting these failures, but you can find the details in the test reports, which are in modules/integration/target/test-reports/ (substitute 'integration' for a different module name if you get failures in any other modules). Chuck Xinjun Chen wrote on 07/02/2006 04:38 PM: Hi, I am trying to build the Axis2 from SVN. I get build failure due to the security test failures. The error messages are at the end of this post. As can be seen, most of the security test scenarios get failures. I am using JDK1.4.2_11 on Windows XP. Maven version 1.0.2. I use the command line maven under axis2 base directory in DOS prompt. Could anyone suggest the reason of this build failure? By the way, in my machine, I installed some self-signed digital certs for SSL use, and also imported them into the CACerts keystore. Will that be the cause of the security test failure? How can I view more detailed error messages? The error messages: [junit] Running org.apache.axis2.security.AddressingMTOMSecurityTest [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 14.828 sec [junit] [ERROR] TEST org.apache.axis2.security.AddressingMTOMSecurityTest FAILED [junit] Running org.apache.axis2.security.MTOMOptimizedSecurityTest [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 15.906 sec [junit] [ERROR] TEST org.apache.axis2.security.MTOMOptimizedSecurityTest FAILED [junit] Running org.apache.axis2.security.sc.ConversationScenario1Test [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 15.828 sec [junit] [ERROR] TEST org.apache.axis2.security.sc.ConversationScenario1Test FAILED [junit] Running org.apache.axis2.security.sc.ConversationScenario2Test [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 14.203 sec [junit] [ERROR] TEST org.apache.axis2.security.sc.ConversationScenario2Test FAILED [junit] Running org.apache.axis2.security.sc.ConversationScenario3Test [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 6.578 sec [junit] [ERROR] TEST org.apache.axis2.security.sc.ConversationScenario3Test FAILED [junit] Running org.apache.axis2.security.sc.ConversationScenario4Test [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 9.593 sec [junit] [ERROR] TEST org.apache.axis2.security.sc.ConversationScenario4Test FAILED [junit] Running org.apache.axis2.security.Scenario1Test [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 13.968 sec [junit] Running org.apache.axis2.security.Scenario2aTest [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 12.609 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario2aTest FAILED [junit] Running org.apache.axis2.security.Scenario2Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 12.219 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario2Test FAILED [junit] Running org.apache.axis2.security.Scenario3Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 12.484 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario3Test FAILED [junit] Running org.apache.axis2.security.Scenario4Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 12.375 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario4Test FAILED [junit] Running org.apache.axis2.security.Scenario5Test [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 14.078 sec [junit] Running org.apache.axis2.security.Scenario6Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 12.625 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario6Test FAILED [junit] Running org.apache.axis2.security.Scenario7Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 12.75 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario7Test FAILED [junit] Running org.apache.axis2.swa.EchoRawSwATest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.859 sec [junit] Running org.apache.axis2.tcp.TCPEchoRawXMLTest [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 7.265 sec [junit] Running org.apache.axis2.tcp.TCPTwoChannelEchoRawXMLTest
Re: Services
Hi Robert, Thanks for your quick reply. What you answered to my first problem seems to be what I'm looking for, so you udnerstood me correctly :) Since in JMX the MBean server does the instancing of classes for you ServiceObjectSupplier will work great. The problem is, as you say, that you have to define the ServiceObject in the services.xml file. What I would like to do is to deploy using code. So when our middleware discovers a a new component in its deploy folder it will load it as a MBean and then create a soap service pointing to that mbean. Creating a new service in the way axis deployes its services will be problematic. Creating a way to dynamically deploy soap services is what's needed for us. Since I'm not to familiar with the codebase of axis 2 I would appreicate it greately if anyone could tell me how to deploy services from code or could point me to the correct files so I could found out for myself. Dan On Fri, 30 Jun 2006 20:05:50 +0200, robert lazarski [EMAIL PROTECTED] wrote: Hi Dan, I'm interested in what you're doing with JMX, as I do a lot of axis2 programming with JBoss / EJB which as you may know is a very heavily user of JMX. See my comments inline: On 6/30/06, Dan Peder Eriksen [EMAIL PROTECTED] wrote: Hello, I'm a master degree student from the university of Tromsø working on a middlware platform for context sensitive services. The middlware is built by using MBeans (JMX http://java.sun.com/products/JavaManagement) and Axis 2 has been installed on an embedded installation of Jetty 5.1.11RC0. We want to make it possible for components deployed in the middleware to expose certain methods as web services using axis 2. When trying to use the API some problems have arisen. The two problems I encounter when trying to do this is: 1. A way to register already created objects as a service, so I supply the instance of the object (the component) instead of axis 2 creating the instance for me. You happen to be lucky and this issue was just implemented in recent days - if I understand you correctly ;-) . In my case I did the Spring support that does its own loading of objects, but ran into the same issue. The Spring classes haven't been updated yet, but hope to do that in the next few days. In the latest svn take a look at modules/core/src/org/apache/axis2/receivers/AbstractMessageReceiver.java You can now define ServiceObjectSupplier as you would ServiceClass in your services.xml, and return your object as you see fit. 2. A way to programmatically register services. This most also be possible at runtime as the middleware supports hot deployment. So what I'm looking at creating (if it doesnt already exists) for our middleware is something like this, pseudocode: //My component I want to register Component comp = Middleware.getComponent(Component Name); //Methods the service should expose, everything Method[] methods = comp.getClass().getMethods(); //Singelton pattern Axis axis = Axis.getInstance(); //Deploy Service axis.deployService(Service Name, comp, methods); If does not exist already it's something I would like to create. I'm sure it would be usefull for others aswell. Where would one start to create something like this? This is not the area I typically work on, though I'll take an educated guess. Others may be able to give better advice. You either need an axis2.xml or you can create one programatically via AxisConfiguration . From there you can go with the exploded dir options as this tutorial explains: http://www.wso2.net/kb/90 AFAIK, however, the exploded dir option is not hot deploy. To do that, my possibly completely wrong thoughts, based on entirely too much world cup fever, would be: 1) First get the axisConfiguration as descibed above. 2) Then get the AxisService corresponding to the service to create from axisConfiguration. 3) AxisService createService(String implClass, AxisConfiguration axisConfig) throws org.apache.axis2.AxisFault; 4) To invoke: new ServiceClient(ConfigurationContext configContext, AxisService axisService); serviceClient.sendReceive(OMElement); HTH, Robert http://www.braziloutsource.com/ HTH, Robert http://www.braziloutsource.com/ Sincerely Dan Peder Eriksen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-854) documentation elements in custom wsdl are lost during ?wsdl
[ http://issues.apache.org/jira/browse/AXIS2-854?page=all ] Deepal Jayasinghe resolved AXIS2-854: - Resolution: Fixed fixed in current SVN documentation elements in custom wsdl are lost during ?wsdl - Key: AXIS2-854 URL: http://issues.apache.org/jira/browse/AXIS2-854 Project: Apache Axis 2.0 (Axis2) Type: Bug Reporter: Davanum Srinivas documentation elements in a custom wsdl are lost when someone tries to look at the wsdl using ?wsdl -- dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-849) NullPointerException in OutInAxisOperationClient
[
http://issues.apache.org/jira/browse/AXIS2-849?page=comments#action_12418938 ]
Michele Mazzucco commented on AXIS2-849:
Deepal, no, it is not fixed. I'm running the snapshot of July 3 and I'm still
getting:
ERROR QueueSizeServiceHandler:client - java.lang.NullPointerException
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:260)
at
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:361)
at
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:341)
at
ncl.qosp.controller.scheduler.queue.QueueSizeServiceHandler.client(QueueSizeServiceHandler.java:577)
at
ncl.qosp.controller.scheduler.queue.QueueSizeServiceHandler.send(QueueSizeServiceHandler.java:541)
at
ncl.qosp.controller.scheduler.queue.QueueSizeServiceHandler.addResource(QueueSizeServiceHandler.java:318)
at
ncl.qosp.controller.scheduler.queue.QueueSizeTimeScheduler.requireResources(QueueSizeTimeScheduler.java:291)
at
ncl.qosp.controller.scheduler.queue.QueueSizeServiceHandler.setOptimalValue(QueueSizeServiceHandler.java:269)
at
ncl.qosp.controller.scheduler.queue.QueueSizeTimeScheduler$ReminderTask.reallocateResources(QueueSizeTimeScheduler.java:531)
at
ncl.qosp.controller.scheduler.queue.QueueSizeTimeScheduler$ReminderTask.run(QueueSizeTimeScheduler.java:501)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
NullPointerException in OutInAxisOperationClient
-
Key: AXIS2-849
URL: http://issues.apache.org/jira/browse/AXIS2-849
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: client-api
Versions: 1.0
Environment: Windows XP SP2, Java J2SE 1.5.0_03, Axis 2 SNAPSHOT Jun 08, 2006
Reporter: Michele Mazzucco
Assignee: Deepal Jayasinghe
I'm trying to send a message from a web service A to a web service B, but I
get this exception:
ERROR
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler
- java.lang.NullPointerException
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:260)
at
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:350)
at
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:330)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.client(WeightedAvgRespTimeServiceHandler.java:609)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.send(WeightedAvgRespTimeServiceHandler.java:560)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.addResource(WeightedAvgRespTimeServiceHandler.java:333)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeScheduler.requireResources(WeightedAvgRespTimeScheduler.java:296)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.setOptimalValue(WeightedAvgRespTimeServiceHandler.java:284)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeScheduler$ReminderTask.reallocateResources(WeightedAvgRespTimeScheduler.java:549)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeScheduler$ReminderTask.run(WeightedAvgRespTimeScheduler.java:519)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
The chunk of code generating the above exception is:
EndpointReference targetEPR = new EndpointReference(target);
Options options = new Options();
options.setTo(targetEPR);
options.setAction(urn:echo);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setUseSeparateListener(true);
ServiceClient sender = new ServiceClient();
sender.engageModule(new QName(Constants.MODULE_ADDRESSING));
sender.setOptions(options);
try {
sender.sendRobust(r.request);
} catch (Exception e) {
StringWriter sw = new StringWriter();
PrintWriter pw = new PrintWriter(sw);
e.printStackTrace(pw);
log.error(sw.getBuffer().toString());
pw.close();
}
Please note that this code works if a sendReceiveNonBlocking() call is
used instead of sendRobust().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-859) Improve checks for required WS-Addressing headers in inbound handlers
[ http://issues.apache.org/jira/browse/AXIS2-859?page=comments#action_12418946 ] Davanum Srinivas commented on AXIS2-859: looks good to me as all are tests. Improve checks for required WS-Addressing headers in inbound handlers - Key: AXIS2-859 URL: http://issues.apache.org/jira/browse/AXIS2-859 Project: Apache Axis 2.0 (Axis2) Type: Improvement Components: core Reporter: Brian DePradine Attachments: myPatch.txt Perform more rigorous checks on WS-Addressing headers to validate that all required headers have been included on inbound messages. Patch to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-859) Improve checks for required WS-Addressing headers in inbound handlers
[ http://issues.apache.org/jira/browse/AXIS2-859?page=comments#action_12418948 ] Davanum Srinivas commented on AXIS2-859: for spec compliance. Improve checks for required WS-Addressing headers in inbound handlers - Key: AXIS2-859 URL: http://issues.apache.org/jira/browse/AXIS2-859 Project: Apache Axis 2.0 (Axis2) Type: Improvement Components: core Reporter: Brian DePradine Attachments: myPatch.txt Perform more rigorous checks on WS-Addressing headers to validate that all required headers have been included on inbound messages. Patch to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jira] Commented: (AXIS2-849) NullPointerException in OutInAxisOperationClient
can you please help me to regenerate the issue
Michele Mazzucco (JIRA) wrote:
[
http://issues.apache.org/jira/browse/AXIS2-849?page=comments#action_12418938
]
Michele Mazzucco commented on AXIS2-849:
Deepal, no, it is not fixed. I'm running the snapshot of July 3 and I'm still
getting:
ERROR QueueSizeServiceHandler:client - java.lang.NullPointerException
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:260)
at
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:361)
at
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:341)
at
ncl.qosp.controller.scheduler.queue.QueueSizeServiceHandler.client(QueueSizeServiceHandler.java:577)
at
ncl.qosp.controller.scheduler.queue.QueueSizeServiceHandler.send(QueueSizeServiceHandler.java:541)
at
ncl.qosp.controller.scheduler.queue.QueueSizeServiceHandler.addResource(QueueSizeServiceHandler.java:318)
at
ncl.qosp.controller.scheduler.queue.QueueSizeTimeScheduler.requireResources(QueueSizeTimeScheduler.java:291)
at
ncl.qosp.controller.scheduler.queue.QueueSizeServiceHandler.setOptimalValue(QueueSizeServiceHandler.java:269)
at
ncl.qosp.controller.scheduler.queue.QueueSizeTimeScheduler$ReminderTask.reallocateResources(QueueSizeTimeScheduler.java:531)
at
ncl.qosp.controller.scheduler.queue.QueueSizeTimeScheduler$ReminderTask.run(QueueSizeTimeScheduler.java:501)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
NullPointerException in OutInAxisOperationClient
-
Key: AXIS2-849
URL: http://issues.apache.org/jira/browse/AXIS2-849
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: client-api
Versions: 1.0
Environment: Windows XP SP2, Java J2SE 1.5.0_03, Axis 2 SNAPSHOT Jun 08, 2006
Reporter: Michele Mazzucco
Assignee: Deepal Jayasinghe
I'm trying to send a message from a web service A to a web service B, but I
get this exception:
ERROR
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler
- java.lang.NullPointerException
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:260)
at
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:350)
at
org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:330)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.client(WeightedAvgRespTimeServiceHandler.java:609)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.send(WeightedAvgRespTimeServiceHandler.java:560)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.addResource(WeightedAvgRespTimeServiceHandler.java:333)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeScheduler.requireResources(WeightedAvgRespTimeScheduler.java:296)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeServiceHandler.setOptimalValue(WeightedAvgRespTimeServiceHandler.java:284)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeScheduler$ReminderTask.reallocateResources(WeightedAvgRespTimeScheduler.java:549)
at
ncl.qosp.controller.scheduler.weighted.WeightedAvgRespTimeScheduler$ReminderTask.run(WeightedAvgRespTimeScheduler.java:519)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
The chunk of code generating the above exception is:
EndpointReference targetEPR = new EndpointReference(target);
Options options = new Options();
options.setTo(targetEPR);
options.setAction(urn:echo);
options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
options.setUseSeparateListener(true);
ServiceClient sender = new ServiceClient();
sender.engageModule(new QName(Constants.MODULE_ADDRESSING));
sender.setOptions(options);
try {
sender.sendRobust(r.request);
} catch (Exception e) {
StringWriter sw = new StringWriter();
PrintWriter pw = new PrintWriter(sw);
e.printStackTrace(pw);
log.error(sw.getBuffer().toString());
pw.close();
}
Please note that this code works if a sendReceiveNonBlocking() call is
used instead of sendRobust().
--
Thanks,
Deepal
~Future is Open~
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-859) Improve checks for required WS-Addressing headers in inbound handlers
[ http://issues.apache.org/jira/browse/AXIS2-859?page=all ] David Illsley resolved AXIS2-859: - Resolution: Fixed Assign To: David Illsley Patch applied and committed to SVN. Improve checks for required WS-Addressing headers in inbound handlers - Key: AXIS2-859 URL: http://issues.apache.org/jira/browse/AXIS2-859 Project: Apache Axis 2.0 (Axis2) Type: Improvement Components: core Reporter: Brian DePradine Assignee: David Illsley Attachments: myPatch.txt Perform more rigorous checks on WS-Addressing headers to validate that all required headers have been included on inbound messages. Patch to follow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] build failed due to security test failure
Hi, WSS4J leaves position 1 is for the JCE implementation of the JRE. I think this is because of the following [1], since we have to load the signed BC provider. Werner, please correct me if I'm mistaken :-) See the log message here [2] And as for inserting the Sun provider in position 1 all the time, I'm not sure whether we can assume that the Sun provider will be available all the time, for example how would it work in the case of the IBM JRE? Thanks, Ruchith [1] http://java.sun.com/products/jce/jce122_knownbugs.html [2] http://svn.apache.org/viewvc?view=revrevision=386294 On 7/3/06, Xinjun Chen [EMAIL PROTECTED] wrote: Hi Chuck, Thank you very much for your reply. I have already solved the problem by reinstall the JDK. In the previous JDK, due to some policy reason, I was forced to modify the default jre lib. The javax.crypto.Cipher class in the jce.jar is overwritten by another version. The whole jce.jar is disabled. Sun provider is not the first provider, and SunJSSE is disabled. Can i confirm with the team dealing with security, whether the security package assumes that Sun provider is the first provider in the list? and whether the SunJSSE will be used? If the answers are yes, could the security team modify update the code to insert the Sun provider as the first provider at runtime? Regards, Xinjun On 7/3/06, Chuck Williams [EMAIL PROTECTED] wrote: Xinjun, I'm not sure why you are getting these failures, but you can find the details in the test reports, which are in modules/integration/target/test-reports/ (substitute 'integration' for a different module name if you get failures in any other modules). Chuck Xinjun Chen wrote on 07/02/2006 04:38 PM: Hi, I am trying to build the Axis2 from SVN. I get build failure due to the security test failures. The error messages are at the end of this post. As can be seen, most of the security test scenarios get failures. I am using JDK1.4.2_11 on Windows XP. Maven version 1.0.2. I use the command line maven under axis2 base directory in DOS prompt. Could anyone suggest the reason of this build failure? By the way, in my machine, I installed some self-signed digital certs for SSL use, and also imported them into the CACerts keystore. Will that be the cause of the security test failure? How can I view more detailed error messages? The error messages: [junit] Running org.apache.axis2.security.AddressingMTOMSecurityTest [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 14.828 sec [junit] [ERROR] TEST org.apache.axis2.security.AddressingMTOMSecurityTest FAILED [junit] Running org.apache.axis2.security.MTOMOptimizedSecurityTest [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 15.906 sec [junit] [ERROR] TEST org.apache.axis2.security.MTOMOptimizedSecurityTest FAILED [junit] Running org.apache.axis2.security.sc.ConversationScenario1Test [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 15.828 sec [junit] [ERROR] TEST org.apache.axis2.security.sc.ConversationScenario1Test FAILED [junit] Running org.apache.axis2.security.sc.ConversationScenario2Test [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 14.203 sec [junit] [ERROR] TEST org.apache.axis2.security.sc.ConversationScenario2Test FAILED [junit] Running org.apache.axis2.security.sc.ConversationScenario3Test [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 6.578 sec [junit] [ERROR] TEST org.apache.axis2.security.sc.ConversationScenario3Test FAILED [junit] Running org.apache.axis2.security.sc.ConversationScenario4Test [junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 9.593 sec [junit] [ERROR] TEST org.apache.axis2.security.sc.ConversationScenario4Test FAILED [junit] Running org.apache.axis2.security.Scenario1Test [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 13.968 sec [junit] Running org.apache.axis2.security.Scenario2aTest [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 12.609 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario2aTest FAILED [junit] Running org.apache.axis2.security.Scenario2Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 12.219 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario2Test FAILED [junit] Running org.apache.axis2.security.Scenario3Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 12.484 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario3Test FAILED [junit] Running org.apache.axis2.security.Scenario4Test [junit] Tests run: 2, Failures: 2, Errors: 0, Time elapsed: 12.375 sec [junit] [ERROR] TEST org.apache.axis2.security.Scenario4Test FAILED [junit] Running org.apache.axis2.security.Scenario5Test [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 14.078 sec [junit] Running
[axis2] XML Schema repository unavailable
The XMLSchema source repository mentioned on XML Schema web site ( http://svn.apache.org/repos/asf/webservices/commons/modules/XmlSchema/tags/XmlSchema-1.0.1) is not accessible. What is the good repository url? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] XML Schema repository unavailable
were you looking for this: http://svn.apache.org/repos/asf/webservices/commons/tags/XmlSchema/1.0.1/ On 7/3/06, Sébastien Arod [EMAIL PROTECTED] wrote: The XMLSchema source repository mentioned on XML Schema web site ( http://svn.apache.org/repos/asf/webservices/commons/modules/XmlSchema/tags/XmlSchema-1.0.1) is not accessible. What is the good repository url? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] XML Schema repository unavailable
That's it thanks The XMLSchema web site (http://ws.apache.org/commons/XmlSchema/) doesn't seems up to date Jeremy Hughes a écrit : were you looking for this: http://svn.apache.org/repos/asf/webservices/commons/tags/XmlSchema/1.0.1/ On 7/3/06, Sébastien Arod [EMAIL PROTECTED] wrote: The XMLSchema source repository mentioned on XML Schema web site ( http://svn.apache.org/repos/asf/webservices/commons/modules/XmlSchema/tags/XmlSchema-1.0.1) is not accessible. What is the good repository url? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-857) Administrator create server error
[ http://issues.apache.org/jira/browse/AXIS2-857?page=comments#action_12419000 ] Tom Debevoise commented on AXIS2-857: - Deepal I downloaded the nightly build and installed it, All seems to be OK now. You can close this issue, however, I did not try to replicate the issues with the old WAR. Tom Administrator create server error - Key: AXIS2-857 URL: http://issues.apache.org/jira/browse/AXIS2-857 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: deployment Versions: 1.0 Environment: JRE 1.5.0_6-b05, Tomcat 5.0.27 XP Reporter: Tom Debevoise When I run the Axis2 Administrator I get an Internal Server Error The Tomcat log says: - Error dispatching request /axis2/axis2-admin/login java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.transport.http.AbstractAgent.handle(AbstractAgent.java:77) at org.apache.axis2.transport.http.AdminAgent.handle(AdminAgent.java:93) at org.apache.axis2.transport.http.AxisAdminServlet.doGet(AxisAdminServlet.java:41) at org.apache.axis2.transport.http.AxisAdminServlet.doPost(AxisAdminServlet.java:35) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException at org.apache.axis2.transport.http.AdminAgent.processLogin(AdminAgent.java:167) ... 34 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Axis2] JMS support improvements
Hi, In last few weeks, I'm playing with two JMS implementations of Axis2 over SonicMQ and would like to share my thoughts. Many of them already posted to the user list. New JMS Implementation - [New Feature] Handling connections to security enabled brokers [1] - There is no support for authenticated connections. But in real life; - Each connection may require username and password - Each binding/broker(transport.jms.ConnectionFactoryJNDIName) may require a different username password - There is a need for a place to store connection username password (probably within axis2.xml [2]) - [New Feature] ConnectionFactory cache [3] - In SonicMQ, if ConnectionFactory is retrieved from the JNDI for each connection, very high memory usage which prevents access to admin console occurs during high message traffic. And sometimes the server crashes. - AFAIK, old JMS implementation uses connectors to achive this. - [New Feature] Connection pool [3] - I'm not 100% sure here. Caching ConnectionFactory would be suffient if vendor specific ConnectionFactory internally supports connection pool. Or, perhaps, a ConnectionPool which internally holds connections and uses ConnectionFactory cache may be written. The Current JMS Implementation - - [Improvement] Some of the missing points I've figured out [4] - Modules are loaded three times - jndiName is lost - username and password are lost - Ambiguity and incompleteness in the code - Configuration file is loaded many times - There are lots of static definitions for the repository and conf/axis2.xml - These are found under integration module and not part of the core. - Unclearness of the differences between connectorMap and cfMap - Many TODO comments that indicate incomplete features Common for both Implementation - - [Bug?] fireAndForget () waits for response when it comes to JMS[5] - In JMSSender.invoke(), there is waitForResponse variable that is set according to the separate channel use. Because of this, I need to pass true to options.setUseSeparateListener() before calling fireAndForget (). Does it logically correct? I mean, don't we expect fireAndForget() to be used for one-way messaging? I think fireAndForget() should be irrelevant to the response message and so the listener. - [New Feature] Message driven beans as service endpoints - That would be a great feature. JBossWS supports MDBs[6]. - [Improvement] JMS URL concept/proposal/tutorial should be clarified/updated[7] - There is one proposal for Axis1[8] and none for Axis2. It seems, some of the parameters are not used in Axis2. Regards, Ali Sadik Kumlali [1] http://www.mail-archive.com/axis-user@ws.apache.org/msg15817.html [2] http://www.mail-archive.com/axis-user@ws.apache.org/msg15404.html [3] http://www.mail-archive.com/axis-user%40ws.apache.org/msg15854.html [4] http://www.mail-archive.com/axis-user@ws.apache.org/msg15132.html [5] http://www.mail-archive.com/axis-user@ws.apache.org/msg15406.html [6] http://labs.jboss.com/portal/jbossws/user-guide/en/html/jms-transport.html [7] http://www.mail-archive.com/axis-user@ws.apache.org/msg15257.html [8] http://marc.theaimsgroup.com/?l=axis-devm=103617964921940q=p3) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (AXIS2-857) Administrator create server error
[ http://issues.apache.org/jira/browse/AXIS2-857?page=all ] Davanum Srinivas resolved AXIS2-857: Resolution: Fixed looks like it's working in latest nightly/svn. thanks, dims Administrator create server error - Key: AXIS2-857 URL: http://issues.apache.org/jira/browse/AXIS2-857 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: deployment Versions: 1.0 Environment: JRE 1.5.0_6-b05, Tomcat 5.0.27 XP Reporter: Tom Debevoise When I run the Axis2 Administrator I get an Internal Server Error The Tomcat log says: - Error dispatching request /axis2/axis2-admin/login java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.axis2.transport.http.AbstractAgent.handle(AbstractAgent.java:77) at org.apache.axis2.transport.http.AdminAgent.handle(AdminAgent.java:93) at org.apache.axis2.transport.http.AxisAdminServlet.doGet(AxisAdminServlet.java:41) at org.apache.axis2.transport.http.AxisAdminServlet.doPost(AxisAdminServlet.java:35) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException at org.apache.axis2.transport.http.AdminAgent.processLogin(AdminAgent.java:167) ... 34 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (AXIS2-861) cache setting is not working in Nightly build Jun 22,06
[ http://issues.apache.org/jira/browse/AXIS2-861?page=all ] Thilina Gunarathne reassigned AXIS2-861: Assign To: Thilina Gunarathne cache setting is not working in Nightly build Jun 22,06 --- Key: AXIS2-861 URL: http://issues.apache.org/jira/browse/AXIS2-861 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: core Versions: 1.0 Environment: Axis2 1.0, nightly build version 22 Jun 06 Jetty 6.0.0 beta 16 linux environment java language Reporter: Wan Kaveevivitchai Assignee: Thilina Gunarathne There is the problem of file caching, it doesn't working in nightly build version released on June 22, 06. Eventhough, the cache properties in axis2.xml already been set. Is there any solution for this? Is it a bug? I was writing some email earlier about problem in sending large file ~ 10 MB and got broken pipe exception. And there was the suggestion to use the new nightly release which is the 22 Jun 06 release and the broken pipe problem was solve. So i moved on to test with 100 MB size attachment, and i got java.lang.OutOfMemory error, so i did some setting about cache on axis2.xml as following parameter name=cacheAttachments locked=falsetrue/parameter parameter name=attachmentDIR locked=false/users/alice3/home//parameter parameter name=sizeThreshold locked=false4000/parameter but it seems like it still cache into the memory, also when i check at the home directory, there is no cached file at all. So we tried extend the memory size and the attachment is received fine but it isn't the good way to do it, i supposed. So i think the problem is about cache is not working. The same setting is working fine with the other nightly build version released on 4 Jun 06 but that one has the problem about broken pipe in sending large file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (AXIS2-756) elementFormDefault=unqualified is default
[ http://issues.apache.org/jira/browse/AXIS2-756?page=comments#action_12419036 ] Kinichiro Inoguchi commented on AXIS2-756: -- Vankat, Deepal, Thanks. I could see elementFormDefault is set to qualified in version service. I used Nightly builds war distribution. BTW, I found another error. Is this refer to this fixing ? At Validate page, I saw this error. Examining Version Service There was a problem of examine Version service , may be the service not available or some thing has gone wrong. But this does not mean system does not working ! Try to upload a some other service and check to see whether it is working. And tomcat startup log was like this, 2006/07/04 10:31:24 org.apache.axis2.rpc.receivers.RPCMessageReceiver invokeBusinessLogic fatal: Exception occurred while trying to invoke service method getVersion org.apache.axis2.AxisFault: namespace mismatch. Axis Oepration expects non-namespace qualified element. But received a namespace qualified element at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:99) at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:37) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:504) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:284) at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:144) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683) at java.lang.Thread.run(Thread.java:534) null elementFormDefault=unqualified is default --- Key: AXIS2-756 URL: http://issues.apache.org/jira/browse/AXIS2-756 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: wsdl Versions: 1.0 Reporter: Kinichiro Inoguchi Assignee: Ajith Harshana Ranabahu This issue is talking about elementFormDefault for schema of WSDL. elementFormDefault=qualified is right. With 1.0 elementFormDefault=unqualified seems default. It seems elementFormDefault=qualified was default generated WSDL settings at 0.95. You can check this issu by WSDL of version service. http://localhost:8080/axis2/services/version?wsdl Maybe, this issue affects some parts; - auto generation WSDL function for deployed service - Java2WSDL function - WSDL generating eclipse plug-in BTW, which is better about attributeFormDefault=unqualified or attributeFormDefault=qualified ? I also hope that I could override 'elementFormDefault' value by services.xml, as I could override namespace. pls
[jira] Resolved: (AXIS2-827) aar file is locked if it fails to deploy
[ http://issues.apache.org/jira/browse/AXIS2-827?page=all ] Deepal Jayasinghe resolved AXIS2-827: - Resolution: Fixed fixed in current SVN aar file is locked if it fails to deploy Key: AXIS2-827 URL: http://issues.apache.org/jira/browse/AXIS2-827 Project: Apache Axis 2.0 (Axis2) Type: Bug Components: deployment Versions: 1.0 Environment: Axis2 1.0 nightly snapshot dated June 17, 2006. Tomcat. WinXP. Reporter: Kent Tong Assignee: Deepal Jayasinghe Priority: Minor Similar to AXIS2-673 (which has been resolved). The difference is that if the aar file fails to deploy, then the aar file is locked and can't be deleted. In my case, my service fails to deploy because it is using a module which has not been deployed yet: serviceGroup service name=FooService module ref=someUnknownModule/ ... /service /serviceGroup -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] JMS support improvements
Hi Ali I wrote the new JMS implementation, but please note that it has not been made the default Axis2 JMS implementation yet.. As I come from the Synapse background, my main concerns were to be able to listen on multiple JMS destinations (probably using different JMS servers) by different services. I really appreciate your feedback and apologize for the delay in replying to this email thread as I was at ApacheCon last week. So.. as I guess you are not alone anymore in the JMS space.. can we take things one by one and get them resolved? Nothing would make me happier than to also see you get involved in fixing some of these issues you have discovered with your suggested resolutions :-) I will answer the following questions from the new JMS implementation perspective as I do not have much experience with the current implementation. New JMS Implementation - [New Feature] Handling connections to security enabled brokers [1] - There is no support for authenticated connections. But in real life; - Each connection may require username and password - Each binding/broker(transport.jms.ConnectionFactoryJNDIName) may require a different username password - There is a need for a place to store connection username password (probably within axis2.xml [2]) The new JMS implementation allows you to define one or more connection factories that you could listen on. You can provide the user name and password to be used to get the context through the java.naming.security.principal and java.naming.security.credentials properties set on the connection factory. I believe that the javax.jms.ConnectionFactory.createConnection() now uses the above, as the default user identity. transportReceiver name="jms" class="org.apache.axis2.transport.njms.JMSListener" parameter name="myQueueConnectionFactory" locked="false" parameter name="java.naming.factory.initial" locked="false"org.apache.activemq.jndi.ActiveMQInitialContextFactory/parameter parameter name="java.naming.provider.url" locked="false"tcp://localhost:61616/parameter parameter name="java.naming.security.principal" locked="false"myuser/parameter parameter name="java.naming.security.credentials" locked="false"mypassword/parameter parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false"QueueConnectionFactory/parameter /parameter /transportReceiver - [New Feature] ConnectionFactory cache [3] - In SonicMQ, if ConnectionFactory is retrieved from the JNDI for each connection, very high memory usage which prevents access to admin console occurs during high message traffic. And sometimes the server crashes. - AFAIK, old JMS implementation uses connectors to achive this. The JMS listener focuses on listening for JMS messages - and I believe that the optimization that one could perform on outgoing JMS is limited - as different messages may be destined for different JMS destinations. However, I also think that we could use the "default" connection factory (if one is defined) for outgoing messages with a minor patch.. Will this be ok? - [New Feature] Connection pool [3] - I'm not 100% sure here. Caching ConnectionFactory would be suffient if vendor specific ConnectionFactory internally supports connection pool. Or, perhaps, a ConnectionPool which internally holds connections and uses ConnectionFactory cache may be written. The new code does not go into vendor specifics.. hence if a vendor does have optimizations, they will be used through the standard JMS code we are using. Common for both Implementation - - [Bug?] fireAndForget () waits for response when it comes to JMS[5] - In JMSSender.invoke(), there is waitForResponse variable that is set according to the separate channel use. Because of this, I need to pass true to options.setUseSeparateListener() before calling fireAndForget (). Does it logically correct? I mean, don't we expect fireAndForget() to be used for one-way messaging? I think fireAndForget() should be irrelevant to the response message and so the listener. I think the fireAndForget() should set the appropriate settings. Do you think so too? - [New Feature] Message driven beans as service endpoints - That would be a great feature. JBossWS supports MDBs[6]. I'm sure any help on such features would be very welcome by the community :-) - [Improvement] JMS URL concept/proposal/tutorial should be clarified/updated[7] - There is one proposal for Axis1[8] and none for Axis2. It seems, some of the parameters are not used in Axis2. Agreed.. will need some time though as I'm working more on Synapse right now.. again any help is most welcome asankha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL
