[jira] Resolved: (AXIS2-4549) Repository "java.net" is corrupted
[
https://issues.apache.org/jira/browse/AXIS2-4549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-4549.
-
Resolution: Fixed
Fix Version/s: nightly
Already fixed. For now with older axis2 versions, Please add a settings.xml
under your .m2 directory with the following content:
java.net.2
java.net Mirror of http://repo1.maven.org/maven2/
http://download.java.net/maven/2/
java.net
> Repository "java.net" is corrupted
> --
>
> Key: AXIS2-4549
> URL: https://issues.apache.org/jira/browse/AXIS2-4549
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
>Reporter: Dušan Križan
>Priority: Blocker
> Fix For: nightly
>
>
> Repository "java.net" is corrupted. Could you please remove this code from
> "axis2-parent-1.5.1.pom"
> {code}
>
> java.net
> https://maven-repository.dev.java.net/nonav/repository/
> legacy
>
> false
>
>
> true
>
>
> {code}
> Regards
> Dušan Križan
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4460) Axis2 Trunk Does Not Build From a Clean Maven Repo
[ https://issues.apache.org/jira/browse/AXIS2-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741268#action_12741268 ] Davanum Srinivas commented on AXIS2-4460: - building mar/aar maven plugins is a known issue for several releases...so yes, you need to build them first on a fresh machine or if you nuke ~/.m2/repository for some reason. Please try using latest JDK1.6 and see if that works or fails. [d...@dims-desktop jaxws-integration]$/usr/lib/jvm/jdk6_14/bin/java -version java version "1.6.0_14" Java(TM) SE Runtime Environment (build 1.6.0_14-b08) Java HotSpot(TM) Server VM (build 14.0-b16, mixed mode) thanks, dims > Axis2 Trunk Does Not Build From a Clean Maven Repo > -- > > Key: AXIS2-4460 > URL: https://issues.apache.org/jira/browse/AXIS2-4460 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: samples, build,site > Environment: OS: Debian GNU/Linux 4.0 > Apache Maven 2.1.0 (r755702; 2009-03-18 12:10:27-0700) > Java version: 1.5.0_08 > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.16.33-xenu" >Reporter: Hiranya Jayathilaka > Attachments: attempt1.log, attempt2.log, attempt3.log, > newRepoError.log, surefire-reports.zip > > > A number of build issues were encountered when trying to build Axis2 from a > clean Maven repo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AXIS2-3736) java.util.List is not known to this context
[
https://issues.apache.org/jira/browse/AXIS2-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas reassigned AXIS2-3736:
---
Assignee: Rich Scheuerle
> java.util.List is not known to this context
> ---
>
> Key: AXIS2-3736
> URL: https://issues.apache.org/jira/browse/AXIS2-3736
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
>Reporter: Davanum Srinivas
>Assignee: Rich Scheuerle
> Attachments: apples.zip
>
>
> == SEI
> @WebService
> @XmlSeeAlso({ Apple.class, Fuji.class })
> public interface AppleFinder {
> List getApple(String appType);
> }
> == Impl
> @WebService(endpointInterface =
> "org.apache.cxf.systest.type_substitution.AppleFinder",
> serviceName = "AppleFinder")
> public class AppleFinderImpl implements AppleFinder {
> public List getApple(String appleType) {
> List apples = new ArrayList();
> apples.add(new Fuji("Red", "mild", "Fuji-1"));
> apples.add(new Fuji("Yellow", "sweet", "Fuji-2"));
> return apples;
> }
> }
> = Stack Trace =
> [javax.xml.bind.JAXBException: java.util.List is not known to this context]
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:331)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:175)
> at
> org.apache.axis2.datasource.jaxb.JAXBDSContext$3.run(JAXBDSContext.java:664)
> at
> org.apache.axis2.java.security.AccessController.doPrivileged(AccessController.java:76)
> at
> org.apache.axis2.datasource.jaxb.JAXBDSContext.marshalByType(JAXBDSContext.java:566)
> at
> org.apache.axis2.datasource.jaxb.JAXBDSContext.marshal(JAXBDSContext.java:294)
> at
> org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl._outputFromBO(JAXBBlockImpl.java:175)
> at
> org.apache.axis2.jaxws.message.impl.BlockImpl.outputTo(BlockImpl.java:342)
> at
> org.apache.axis2.jaxws.message.impl.BlockImpl.serialize(BlockImpl.java:266)
> at
> org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume(OMSourcedElementImpl.java:664)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:918)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:918)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
> at
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:240)
> at
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:228)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
> at
> org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:471)
> at
> org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:68)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:330)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:213)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
> at
> org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:210)
> ... 9 more
> Caused by: javax.xml.bind.JAXBException: java.util.List is not known to this
> context
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:242)
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:257)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(ElementBeanInfoImpl.java:143)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(ElementBeanInfoImpl.java:185)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeBody(ElementBeanInfoImpl.java:305)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(ElementBeanInfoImpl.java:312)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(ElementBeanInfoImpl.java:71)
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:490)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:328)
> ... 31 more
> Caused by: javax.xml.bind.JAXBException: java.util.List is not known to this
> context
> at
> com.sun.xml.bind.v2.runtime.JAX
[jira] Assigned: (AXIS2-4459) JAX-WS implementation throws JAXBException for complextypes
[ https://issues.apache.org/jira/browse/AXIS2-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas reassigned AXIS2-4459: --- Assignee: Rich Scheuerle i believe Rich is working on this one. > JAX-WS implementation throws JAXBException for complextypes > --- > > Key: AXIS2-4459 > URL: https://issues.apache.org/jira/browse/AXIS2-4459 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Affects Versions: 1.5 > Environment: Windows XP Service Pack 3. Java 1.6.0_13 >Reporter: Brandon Richins >Assignee: Rich Scheuerle > Attachments: JaxWsExample.zip > > > When calling an operation on a JAX-WS service that returns an array, Axis2 > throws a JAXBException indicating that XYZ class "is not known to this > context". It seems able to marshall when returning a single element. But > arrays don't seem to work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-4458) JABRI: Multiple JAXBContext creation
[ https://issues.apache.org/jira/browse/AXIS2-4458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-4458. - Resolution: Fixed Fixed in svn revision 801630. > JABRI: Multiple JAXBContext creation > > > Key: AXIS2-4458 > URL: https://issues.apache.org/jira/browse/AXIS2-4458 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: codegen >Affects Versions: 1.5 >Reporter: Sebastian J. >Priority: Blocker > Attachments: JaxbRIDatabindingTemplate.xsl > > > I use the lastest Axis2 1.5 release with JAXB databinding and wsdl2java for > class generation. > The generated classes work, but each operation/class has it's own JAXBContext > object. > According to [1] this isn't nessassary anymore in JAXB2.0. > A single JAXBContext per application is the prefered way. > So I modified the XSLT template in jaxbri-1.5.jar (which als solves > AXIS2-4042). > This new template generates just one JAXBContext per MessageReceiverInOut > class. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-4042) jaxbri binding should report exception in addition to "Unable to create JAXBContext for class"
[ https://issues.apache.org/jira/browse/AXIS2-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-4042. - Resolution: Fixed Fixed in svn revision 801630. > jaxbri binding should report exception in addition to "Unable to create > JAXBContext for class" > -- > > Key: AXIS2-4042 > URL: https://issues.apache.org/jira/browse/AXIS2-4042 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement >Affects Versions: 1.4 >Reporter: Jake Goulding >Priority: Minor > > I have a schema that reported the following error: > Unable to create JAXBContext for class: vivisimo.velocity.test.Dictionary > I had to recompile the entirety of Axis to add one line after it: > ex.printStackTrace(System.err); > Which made debugging a whole lot easier! > This is in the file: > modules/codegen/target/test-classes/org/apache/axis2/jaxbri/template/JaxbRIDatabindingTemplate.xsl -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4264) Empty action not applied in CommonsHTTPTransportSender
[ https://issues.apache.org/jira/browse/AXIS2-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698155#action_12698155 ] Davanum Srinivas commented on AXIS2-4264: - Props to Xin Huang for finding the JIRA defects and Rich Scheuerle for suggesting the fix. thanks, dims > Empty action not applied in CommonsHTTPTransportSender > -- > > Key: AXIS2-4264 > URL: https://issues.apache.org/jira/browse/AXIS2-4264 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: transports >Affects Versions: 1.5, 1.4.1, 1.4, 1.3 >Reporter: Alexis Midon > Attachments: AXIS2-4264.patch.txt > > > Hello there, > I'm invoking a service using a ServiceClient, the wsdl operation declares an > empty soapAction. > However the soapActiuon actually sent is "urn:anonOutInOp" which the server > refuses. This action is the action the anonymous operation "urn:anonOutInOp" > and is set by the ServiceClient. > Later when CommonsHTTPTransportSender#findSOAPAction [1] is invoked, if the > action of the MessageContext is null or empty, the operation action is used. > The empty case seems like a bug, because this is the action set in the wsdl > and it is not applied. > This opinion is strengthened by the fact that other senders do not have this > behavior. > The right behavior would be: > if null ; use the operation action as a default > if empty ; send an empty soapAction > Could you confirm please? > Alexis > [1] http://is.gd/m0Mt -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4264) Empty action not applied in CommonsHTTPTransportSender
[
https://issues.apache.org/jira/browse/AXIS2-4264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12698154#action_12698154
]
Davanum Srinivas commented on AXIS2-4264:
-
Alexis,
we think there may be cases where AxisOperation may be the correct one to use.
Can you please try this patch? You may have to apply the patch by hand as there
are differences between current axis2 version and the one that i am using.
thanks,
dims
Index: src/org/apache/axis2/transport/http/CommonsHTTPTransportSender.java
===
--- src/org/apache/axis2/transport/http/CommonsHTTPTransportSender.java
(revision 6604)
+++ src/org/apache/axis2/transport/http/CommonsHTTPTransportSender.java
(working copy)
@@ -22,6 +22,7 @@
import org.apache.axiom.om.OMOutputFormat;
import org.apache.axis2.AxisFault;
import org.apache.axis2.Constants;
+import org.apache.axis2.client.ServiceClient;
import org.apache.axis2.addressing.EndpointReference;
import org.apache.axis2.context.ConfigurationContext;
import org.apache.axis2.context.MessageContext;
@@ -399,12 +400,25 @@
if ((soapActionString == null) || (soapActionString.length() ==
0)) {
// now let's try to get WSA action
soapActionString = messageContext.getWSAAction();
+if (log.isDebugEnabled()) {
+log.debug("SOAP Action from getWSAAction was : " +
soapActionString);
+}
if (messageContext.getAxisOperation() != null
&& ((soapActionString == null) || (soapActionString
.length() == 0))) {
// last option is to get it from the axis operation
-soapActionString = messageContext.getAxisOperation()
+String axisOpSOAPAction = messageContext.getAxisOperation()
.getSoapAction();
+log.debug("SOAP Action from AxisOperation was : " +
axisOpSOAPAction);
+if (ServiceClient.ANON_OUT_ONLY_OP.equals(axisOpSOAPAction)
+||
(ServiceClient.ANON_OUT_ONLY_OP.equals(axisOpSOAPAction))
+||
(ServiceClient.ANON_OUT_ONLY_OP.equals(axisOpSOAPAction))) {
+if (log.isDebugEnabled()) {
+log.debug("Will not override SOAP Action as " +
axisOpSOAPAction + " in AxisOperation was auto-generated");
+}
+} else {
+soapActionString = axisOpSOAPAction;
+}
}
}
}
> Empty action not applied in CommonsHTTPTransportSender
> --
>
> Key: AXIS2-4264
> URL: https://issues.apache.org/jira/browse/AXIS2-4264
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: transports
>Affects Versions: 1.5, 1.4.1, 1.4, 1.3
>Reporter: Alexis Midon
> Attachments: AXIS2-4264.patch.txt
>
>
> Hello there,
> I'm invoking a service using a ServiceClient, the wsdl operation declares an
> empty soapAction.
> However the soapActiuon actually sent is "urn:anonOutInOp" which the server
> refuses. This action is the action the anonymous operation "urn:anonOutInOp"
> and is set by the ServiceClient.
> Later when CommonsHTTPTransportSender#findSOAPAction [1] is invoked, if the
> action of the MessageContext is null or empty, the operation action is used.
> The empty case seems like a bug, because this is the action set in the wsdl
> and it is not applied.
> This opinion is strengthened by the fact that other senders do not have this
> behavior.
> The right behavior would be:
> if null ; use the operation action as a default
> if empty ; send an empty soapAction
> Could you confirm please?
> Alexis
> [1] http://is.gd/m0Mt
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AXIS2-4282) JarFileClassLoader allows resources to be loaded from locations outside of the directory specified in its classpath
[ https://issues.apache.org/jira/browse/AXIS2-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688201#action_12688201 ] Davanum Srinivas commented on AXIS2-4282: - Jarek, JarFileClassLoader was originally from Geronimo... thanks, dims > JarFileClassLoader allows resources to be loaded from locations outside of > the directory specified in its classpath > --- > > Key: AXIS2-4282 > URL: https://issues.apache.org/jira/browse/AXIS2-4282 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel >Affects Versions: 1.5, nightly >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 1.5, nightly > > > If JarFileClassLoader contains one classpath entry that is a directory, it > will allow resources to be loaded from ANY directory on the file system. > The JarFileClassLoader should of course only allow resources to be loaded > from within the directory specified. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-3791) Endlesloop in AxisServlet init (Websphere 6.1 deployment)
[
https://issues.apache.org/jira/browse/AXIS2-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-3791.
-
Resolution: Duplicate
DUP of AXIS2-3908
> Endlesloop in AxisServlet init (Websphere 6.1 deployment)
> -
>
> Key: AXIS2-3791
> URL: https://issues.apache.org/jira/browse/AXIS2-3791
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: transports
>Affects Versions: 1.3
> Environment: Solaris-10
> Websphere 6.1
> java version "1.5.0_13"
> Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_13-b05
> 20071004)
> Java HotSpot(TM) Server VM (build 1.5.0_13-b05, mixed mode)
> IBM Java ORB build orb50-20070915 (SR6)
> XML build XSLT4J Java 2.7.9
> XML build IBM JAXP 1.3.7
> XML build XML4J 4.4.11
>Reporter: martin voegeli
>Assignee: Deepal Jayasinghe
>Priority: Minor
> Attachments: diff.txt
>
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> Wrong usage of servlet init procedure leads to endlessloop, if container
> issues init method twice.
> =>
> http://java.sun.com/j2ee/1.4/docs/api/javax/servlet/GenericServlet.html#init(javax.servlet.ServletConfig)
>
> [5/7/08 14:55:37:535 MEST] 0036 ServletWrappe E SRVE0100E: Did not
> realize init() exception thrown by servlet AxisServlet:
> java.lang.StackOverflowError
>at javax.servlet.GenericServlet.init(GenericServlet.java:256)
>at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:413)
>at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:487)
>at javax.servlet.GenericServlet.init(GenericServlet.java:256)
>at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:413)
>at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:487)
> AxisServlet.java:
>public void init(ServletConfig config) throws ServletException {
> 413super.init(config);
>try {
>this.servletConfig = config;
> ...
> GenericServlet.java
>public void init(ServletConfig config)
>throws ServletException
>{
>this.config = config;
>init();
>}
> AxisServlet.java:487:
>/**
> * Convenient method to re-initialize the ConfigurationContext
> *
> * @throws ServletException
> */
>public void init() throws ServletException {
>if (this.servletConfig != null) {
> 487init(this.servletConfig);
>}
>}
> After reinstalling the websphere server, the issue was resolved. Seems, that
> WAS6.1 has some buggy state too. Maybe you can handover the issue to IBM ;-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-4134) JAXWS has problems finding JAXB classes when the application jar file resides in a Windows directory containing spaces
[ https://issues.apache.org/jira/browse/AXIS2-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-4134. - Resolution: Fixed fixed in svn revision 718571. thanks Lizet. -- dims > JAXWS has problems finding JAXB classes when the application jar file resides > in a Windows directory containing spaces > -- > > Key: AXIS2-4134 > URL: https://issues.apache.org/jira/browse/AXIS2-4134 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Affects Versions: 1.4.1 > Environment: Windows >Reporter: Lizet Ernand >Priority: Minor > Original Estimate: 0.17h > Remaining Estimate: 0.17h > > JAXWS has problems finding JAXB classes when users place their application > classes inside a jar file that resides in a Windows directory containing > spaces > i.e For example: > C:\Documents and Settings\mytemp\myApp.jar > Exceptions will be thrown saying the class is not known to the JAXB context, > i.e: > Throwable occurred: javax.xml.ws.WebServiceException: > javax.xml.bind.JAXBException: class nor any of its super class is known > to this context. >at > org.apache.axis2.jaxws.ExceptionFactory.createWebServiceException(ExceptionFactory.java:175) >at > org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException(ExceptionFactory.java:70) > The fix is simple. Create an encoded URI.. which takes care of the spaces in > file URL. > At: > org.apache.axis2.jaxws.message.databinding.impl.ClassFinderImpl.getClassesFromJarFile() > From: > File f = new File(url.getPath()); > To: > File f = new File(url.toURI().getPath()); -- 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: (AXIS2-4126) Remove SOAP Version Restriction from JAX-WS Provider Endpoint
[ https://issues.apache.org/jira/browse/AXIS2-4126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646298#action_12646298 ] Davanum Srinivas commented on AXIS2-4126: - Nikhil, Can you please show example usage? thanks, dims > Remove SOAP Version Restriction from JAX-WS Provider Endpoint > - > > Key: AXIS2-4126 > URL: https://issues.apache.org/jira/browse/AXIS2-4126 > Project: Axis 2.0 (Axis2) > Issue Type: New Feature > Components: jaxws >Reporter: Nikhil Thaker >Assignee: Nikhil Thaker > Attachments: apache_svn_patch.txt > > > This JIRA is for removing SOAP Version Restriction from Provider Endpoints. > Currently a JAX-WS Provider Endpoint can support a SOAP11 or SOAP 12 call > based on the soap version defined in the binding type annotation. With this > JIRA I am introducing a new constant that SOAP_HTTP_BINDING can be used in > @BindingType annotation, when this new constant is used the > javax.xml.ws.Provider java endpoints will cater to SOAP11 and SOAP12 messages. > This JIRA will also add proper validation checks to support the new constant, > for example it will ensure that a SOAP Fault will be thrown when a response > of soap12 is sent on a soap11 request etc. This JIRA also adds code to update > various validation checks for new constant during web services deployment. > This JIRA also adds test cases in JAXWS-Integration module to test various > scenarios for this new constants and validations. -- 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] Assigned: (AXIS2-4072) URLClassloader locking jarfiles on Windows
[ https://issues.apache.org/jira/browse/AXIS2-4072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas reassigned AXIS2-4072: --- Assignee: Jarek Gawor Jarek, Can you please take care of this? thanks, dims > URLClassloader locking jarfiles on Windows > --- > > Key: AXIS2-4072 > URL: https://issues.apache.org/jira/browse/AXIS2-4072 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.4.1 > Environment: Windows XP, Geronimo 2.1.3 >Reporter: Tim McConnell >Assignee: Jarek Gawor > Attachments: AXIS2-4072.patch > > > There is at least one scenario using Axis2 and Geronimo that is causing > jarfiles to get locked on Windows such that a deployed WAR cannot be either > redeployed or uninstalled. Here is a brief description of the failing > scenario: > 1. A WAR file containing various jarfiles in the /lib directory is deployed > on Geronimo 2.1.3 > 2. Navigate to the deployed app's address to generate the WSDL for the web > service > 3. Redeploy or uninstall of the WAR will now fail since all the jarfiles in > the WAR /lib directory are locked by Windows and cannot be deleted. > What appears to be happening is that there are three Axis2 URLClassLoaders in > this scenario and at least two of them are creating their own ClassPath and > URLClassPath$JarLoader objects that apparently are locking the jarfiles in > the /lib directory. -- 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: (AXIS2-4059) JAX-WS services and scope
[ https://issues.apache.org/jira/browse/AXIS2-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636116#action_12636116 ] Davanum Srinivas commented on AXIS2-4059: - Jarek, Where/how do you change the scope? code inside Geronimo? thanks, dims > JAX-WS services and scope > - > > Key: AXIS2-4059 > URL: https://issues.apache.org/jira/browse/AXIS2-4059 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Affects Versions: nightly >Reporter: Jarek Gawor > > By default the JAX-WS web services are deployed with "request" scope. If the > scope was changed to "application" scope the following things break: > 1) @Resource WebServiceContext injection is not performed. That's because the > service class instance is created (and cached) in the DeploymentManager.java > (which doesn't do injection) instead of EndpointLifecycleManagerImpl.java > 2) Updating of WebServiceContextImpl.soapMessageContext is not thread safe. > Since there would be one instance of WebServiceContextImpl associated with > one instance of the service class which is shared for all requests, updating > WebServiceContextImpl.soapMessageContext variable on each request is bad. > That could cause, for example, WebServiceContext.getMessageContext() return > the MessageContext for the last request instead of the current request. > The problem in 2) might also apply to the "session" scope. -- 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: (AXIS2-3957) Adding a Deployment Life cycle listner to Axis2
[ https://issues.apache.org/jira/browse/AXIS2-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619003#action_12619003 ] Davanum Srinivas commented on AXIS2-3957: - s/LISTNER/LISTENER/ (many instances) Looks good! thanks, dims > Adding a Deployment Life cycle listner to Axis2 > --- > > Key: AXIS2-3957 > URL: https://issues.apache.org/jira/browse/AXIS2-3957 > Project: Axis 2.0 (Axis2) > Issue Type: New Feature > Components: kernel >Reporter: Amila Chinthaka Suriarachchi > Attachments: patch.txt > > > Deployment life cycle listener is very useful when restarting some actions > after a server crash. This is specially use full in starting the persisted RM > sequences when a server starts up or at the client side when the client > restarts. -- 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-2828) Enum Pattern for POJO's
[ https://issues.apache.org/jira/browse/AXIS2-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-2828. - Resolution: Won't Fix Marking as wont-fix since we are now java5 only. Let's use the java5 enums instead. -- dims > Enum Pattern for POJO's > --- > > Key: AXIS2-2828 > URL: https://issues.apache.org/jira/browse/AXIS2-2828 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas >Assignee: Deepal Jayasinghe > > Axis 1.X has a pattern which identifies a pojo as an enum (especially for > lower level jdk's). can we please support that both during java2wsdl codegen > and at runtime. > thanks, > dims -- 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: (AXIS2-3883) file handles not being closed after successful call to webservice
[ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609576#action_12609576 ] Davanum Srinivas commented on AXIS2-3883: - What else is on? PARENT_LAST class loading? thanks, dims > file handles not being closed after successful call to webservice > - > > Key: AXIS2-3883 > URL: https://issues.apache.org/jira/browse/AXIS2-3883 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: Windows server 2003 (also Windows XP), axis 2.1.3, > Websphere 6.1 >Reporter: LEE >Priority: Blocker > > We have been regularly experiencing the following problem when trying to call > an axis 2 webservice: > Stack Dump = java.util.zip.ZipException: Too many open files > D:\ibm\profiles\AppSrv02\\xercesImpl-2.8.1.jar > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.(ZipFile.java:238) > at java.util.zip.ZipFile.(ZipFile.java:268) > at > com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405) > at > com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63) > at > com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379) > at > com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474) > at > com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955) > at > com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916) > at > com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913) > at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source) > at > java.security.AccessController.doPrivileged(AccessController.java:192) > at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown > Source) > at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown > Source) > at javax.xml.parsers.FactoryFinder.find(Unknown Source) > at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source) > at > org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151) > at > org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194) > at > org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64) > at > org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72) > at org.apache.axis2.engine.Phase.invoke(Phase.java:292) > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) > at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) > > On closer inspection of the server we noticed that there are a great number > of files in the Windows/Temp directory with names such as > C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar, > C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar, > C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar, > C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc. > The main concern (other than disk space is gradually being taken up) is that > all these files still have open file handles. This is a major problem for us > as each time a call is made to a webservice more of these files eventually > resulting in the application failing due to "too many open files" error. -- 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: (AXIS2-3883) file handles not being closed after successful call to webservice
[ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609557#action_12609557 ] Davanum Srinivas commented on AXIS2-3883: - Also looks like rampart code needs to cache the DocumentBuilderFactory (getDocumentFromSOAPEnvelope) > file handles not being closed after successful call to webservice > - > > Key: AXIS2-3883 > URL: https://issues.apache.org/jira/browse/AXIS2-3883 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: Windows server 2003 (also Windows XP), axis 2.1.3, > Websphere 6.1 >Reporter: LEE >Priority: Blocker > > We have been regularly experiencing the following problem when trying to call > an axis 2 webservice: > Stack Dump = java.util.zip.ZipException: Too many open files > D:\ibm\profiles\AppSrv02\\xercesImpl-2.8.1.jar > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.(ZipFile.java:238) > at java.util.zip.ZipFile.(ZipFile.java:268) > at > com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405) > at > com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63) > at > com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379) > at > com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474) > at > com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955) > at > com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916) > at > com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913) > at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source) > at > java.security.AccessController.doPrivileged(AccessController.java:192) > at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown > Source) > at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown > Source) > at javax.xml.parsers.FactoryFinder.find(Unknown Source) > at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source) > at > org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151) > at > org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194) > at > org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64) > at > org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72) > at org.apache.axis2.engine.Phase.invoke(Phase.java:292) > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) > at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) > > On closer inspection of the server we noticed that there are a great number > of files in the Windows/Temp directory with names such as > C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar, > C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar, > C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar, > C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc. > The main concern (other than disk space is gradually being taken up) is that > all these files still have open file handles. This is a major problem for us > as each time a call is made to a webservice more of these files eventually > resulting in the application failing due to "too many open files" error. -- 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: (AXIS2-3883) file handles not being closed after successful call to webservice
[ https://issues.apache.org/jira/browse/AXIS2-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12609556#action_12609556 ] Davanum Srinivas commented on AXIS2-3883: - Does this happen only when java2 security is on or is this with java2 security off? thanks, dims > file handles not being closed after successful call to webservice > - > > Key: AXIS2-3883 > URL: https://issues.apache.org/jira/browse/AXIS2-3883 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: Windows server 2003 (also Windows XP), axis 2.1.3, > Websphere 6.1 >Reporter: LEE >Priority: Blocker > > We have been regularly experiencing the following problem when trying to call > an axis 2 webservice: > Stack Dump = java.util.zip.ZipException: Too many open files > D:\ibm\profiles\AppSrv02\\xercesImpl-2.8.1.jar > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.(ZipFile.java:238) > at java.util.zip.ZipFile.(ZipFile.java:268) > at > com.ibm.ws.classloader.SinglePathClassProvider$3.run(SinglePathClassProvider.java:405) > at > com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63) > at > com.ibm.ws.classloader.SinglePathClassProvider.getResource(SinglePathClassProvider.java:379) > at > com.ibm.ws.classloader.SinglePathClassProvider.getResourceAsStream(SinglePathClassProvider.java:474) > at > com.ibm.ws.classloader.CompoundClassLoader.localGetResourceAsStream(CompoundClassLoader.java:955) > at > com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:916) > at > com.ibm.ws.classloader.CompoundClassLoader.getResourceAsStream(CompoundClassLoader.java:913) > at javax.xml.parsers.SecuritySupport12$4.run(Unknown Source) > at > java.security.AccessController.doPrivileged(AccessController.java:192) > at javax.xml.parsers.SecuritySupport12.getResourceAsStream(Unknown > Source) > at javax.xml.parsers.FactoryFinder.findJarServiceProvider(Unknown > Source) > at javax.xml.parsers.FactoryFinder.find(Unknown Source) > at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source) > at > org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:151) > at > org.apache.rampart.handler.WSDoAllSender.processBasic(WSDoAllSender.java:194) > at > org.apache.rampart.handler.WSDoAllSender.processMessage(WSDoAllSender.java:64) > at > org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72) > at org.apache.axis2.engine.Phase.invoke(Phase.java:292) > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) > at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) > > On closer inspection of the server we noticed that there are a great number > of files in the Windows/Temp directory with names such as > C:\WINDOWS\Temp\_axis2\axis21568addressing-1.3.mar, > C:\WINDOWS\Temp\_axis2\axis21574soapmonitor-1.3.mar, > C:\WINDOWS\Temp\_axis2\axis21579rampart-1.3.mar, > C:\WINDOWS\Temp\_axis2\axis21577ping-1.3.mar etc. > The main concern (other than disk space is gradually being taken up) is that > all these files still have open file handles. This is a major problem for us > as each time a call is made to a webservice more of these files eventually > resulting in the application failing due to "too many open files" error. -- 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: (AXIS2-3831) Fails to generate wsdl when deploying annotated .class file using POJODeployer in axis2-1.4
[
https://issues.apache.org/jira/browse/AXIS2-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601387#action_12601387
]
Davanum Srinivas commented on AXIS2-3831:
-
that should do it. did you try deploying the same class jarred up in
servicejars directory?
-- dims
> Fails to generate wsdl when deploying annotated .class file using
> POJODeployer in axis2-1.4
> ---
>
> Key: AXIS2-3831
> URL: https://issues.apache.org/jira/browse/AXIS2-3831
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>Priority: Blocker
>
> I deployed the following annotated class in Axis2-1.4 (Copied the .class file
> to Axis2_home/repository/pojo)
> import javax.jws.WebMethod;
> import javax.jws.WebService;
> @WebService
> public class ExamplePOJOService {
> @WebMethod
> public String reverse(String input) {
> StringBuffer buff = new StringBuffer();
> for (int i=input.length()-1; i>=0; i--) {
> buff.append(input.charAt(i));
> }
> return buff.toString();
> }
> }
> When clicking on the servicename of the http://localhost:8080/axis2/services/
> page I got the following exception.
> [ERROR] Error occurred generating WSDL file for Web service implementation
> class
> {ExamplePOJOService}: {java.lang.Exception: A WSDL Definition could not be
> gene
> rated for the implementation class: ExamplePOJOService}
> java.lang.Exception: A WSDL Definition could not be generated for the
> implementation class: ExamplePOJOService
> at
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:177)
> at
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.initialize(JAXWSRIWSDLGenerator.java:371)
> at
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.getWSDL(JAXWSRIWSDLGenerator.java:364)
> at
> org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1319)
> at
> org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:146)
> at
> org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281)
> at
> org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187)
> at
> org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
> at java.lang.Thread.run(Thread.java:595)
--
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: (AXIS2-3831) Fails to generate wsdl when deploying annotated .class file using POJODeployer in axis2-1.4
[
https://issues.apache.org/jira/browse/AXIS2-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601376#action_12601376
]
Davanum Srinivas commented on AXIS2-3831:
-
Did you try under JDK 1.6 or drop JAXWS RI jars (under JDK 1.5)?
-- dims
> Fails to generate wsdl when deploying annotated .class file using
> POJODeployer in axis2-1.4
> ---
>
> Key: AXIS2-3831
> URL: https://issues.apache.org/jira/browse/AXIS2-3831
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Environment: winxp, jdk15
>Reporter: Charitha Kankanamge
>Priority: Blocker
>
> I deployed the following annotated class in Axis2-1.4 (Copied the .class file
> to Axis2_home/repository/pojo)
> import javax.jws.WebMethod;
> import javax.jws.WebService;
> @WebService
> public class ExamplePOJOService {
> @WebMethod
> public String reverse(String input) {
> StringBuffer buff = new StringBuffer();
> for (int i=input.length()-1; i>=0; i--) {
> buff.append(input.charAt(i));
> }
> return buff.toString();
> }
> }
> When clicking on the servicename of the http://localhost:8080/axis2/services/
> page I got the following exception.
> [ERROR] Error occurred generating WSDL file for Web service implementation
> class
> {ExamplePOJOService}: {java.lang.Exception: A WSDL Definition could not be
> gene
> rated for the implementation class: ExamplePOJOService}
> java.lang.Exception: A WSDL Definition could not be generated for the
> implementation class: ExamplePOJOService
> at
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:177)
> at
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.initialize(JAXWSRIWSDLGenerator.java:371)
> at
> org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.getWSDL(JAXWSRIWSDLGenerator.java:364)
> at
> org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1319)
> at
> org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:146)
> at
> org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281)
> at
> org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187)
> at
> org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
> at java.lang.Thread.run(Thread.java:595)
--
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-3782) ComplexDataTypesTest fails under IBM JDK16
ComplexDataTypesTest fails under IBM JDK16 -- Key: AXIS2-3782 URL: https://issues.apache.org/jira/browse/AXIS2-3782 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas junit.framework.AssertionFailedError: org.custommonkey.xmlunit.Diff [not identical] Expected sequence of child nodes '1' but was '6' - comparing at /definitions[1]/types[1]/schema[1]/complexType[1] to at /definitions[1]/types[1]/schema[1]/complexType[6] [not identical] Expected sequence of child nodes '2' but was '7' - comparing at /definitions[1]/types[1]/schema[1]/complexType[2] to at /definitions[1]/types[1]/schema[1]/complexType[7] [not identical] Expected sequence of child nodes '3' but was '1' - comparing at /definitions[1]/types[1]/schema[1]/complexType[3] to at /definitions[1]/types[1]/schema[1]/complexType[1] [not identical] Expected sequence of child nodes '4' but was '2' - comparing at /definitions[1]/types[1]/schema[1]/complexType[4] to at /definitions[1]/types[1]/schema[1]/complexType[2] [not identical] Expected sequence of child nodes '5' but was '3' - comparing at /definitions[1]/types[1]/schema[1]/complexType[5] to at /definitions[1]/types[1]/schema[1]/complexType[3] [not identical] Expected sequence of child nodes '6' but was '4' - comparing at /definitions[1]/types[1]/schema[1]/complexType[6] to at /definitions[1]/types[1]/schema[1]/complexType[4] [not identical] Expected sequence of child nodes '7' but was '5' - comparing at /definitions[1]/types[1]/schema[1]/complexType[7] to at /definitions[1]/types[1]/schema[1]/complexType[5] [different] Expected attribute value 'http://data.complex.tempuri.org/xsd' but was 'http://arrays.data.complex.tempuri.org/xsd' - comparing http://data.complex.tempuri.org/xsd";...> at /definitions[1]/types[1]/schema[2]/import[1] to http://arrays.data.complex.tempuri.org/xsd";...> at /definitions[1]/types[1]/schema[2]/import[1] at org.tempuri.complex.ComplexDataTypesTest.test1(ComplexDataTypesTest.java:51) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:40) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90) -- 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: (AXIS2-3781) ComplexDataTypesDocLitBareTest fails
[ https://issues.apache.org/jira/browse/AXIS2-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594439#action_12594439 ] Davanum Srinivas commented on AXIS2-3781: - java version "1.5.0_15" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04) Java HotSpot(TM) Client VM (build 1.5.0_15-b04, mixed mode, sharing) > ComplexDataTypesDocLitBareTest fails > > > Key: AXIS2-3781 > URL: https://issues.apache.org/jira/browse/AXIS2-3781 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Integration >Reporter: Davanum Srinivas >Priority: Blocker > > --- > Test set: org.apache.axis2.rpc.complex.ComplexDataTypesDocLitBareTest > --- > Tests run: 34, Failures: 0, Errors: 11, Skipped: 0, Time elapsed: 75.937 sec > <<< FAILURE! > testretArrayInt1D(org.apache.axis2.rpc.complex.ComplexDataTypesDocLitBareTest) > Time elapsed: 2.703 sec <<< ERROR! > org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: > Unsupported type null org.tempuri.complex.data.arrays.ArrayOfint > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) > at > org.tempuri.complex.ComplexDataTypesDocLitBareStub.fromOM(ComplexDataTypesDocLitBareStub.java:48033) > at > org.tempuri.complex.ComplexDataTypesDocLitBareStub.retArrayInt1D(ComplexDataTypesDocLitBareStub.java:4910) > at > org.apache.axis2.rpc.complex.ComplexDataTypesDocLitBareTest.testretArrayInt1D(ComplexDataTypesDocLitBareTest.java:108) > 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 junit.framework.TestCase.runTest(TestCase.java:168) > at junit.framework.TestCase.runBare(TestCase.java:134) > at junit.framework.TestResult$1.protect(TestResult.java:110) > at junit.framework.TestResult.runProtected(TestResult.java:128) > at junit.framework.TestResult.run(TestResult.java:113) > at junit.framework.TestCase.run(TestCase.java:124) > at junit.framework.TestSuite.runTest(TestSuite.java:232) > at junit.framework.TestSuite.run(TestSuite.java:227) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) > at junit.extensions.TestSetup$1.protect(TestSetup.java:23) > at junit.framework.TestResult.runProtected(TestResult.java:128) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81) > at > org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) > at > org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165) > at org.apache.maven.surefire.Surefire.run(Surefire.java:107) > 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.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289) > at > org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993) > Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException: > Unsupported type null org.tempuri.complex.data.arrays.ArrayOfint > at > org.tempuri.complex.ComplexDataTypesDocLitBareStub$ArrayOfint$Factory.parse(ComplexDataTypesDocLitBareStub.java:40444) > at > org.tempuri.complex.ComplexDataTypesDocLitBareStub$RetArrayInt1DResult$Factory.parse(ComplexDataTypesDocLitBareStub.java:45228) > at > org.tempuri.complex.ComplexDataTypesDocLitBareStub.fromOM(ComplexDataTypesDocLitBareStub.java:48027) > ... 29 more > Caused by: org.apache.axis2.databinding.ADBException: Unsupported type null > org.tempuri.complex.data.arrays.ArrayOfint > at > org.tempuri.complex.ComplexDataTypesDocLitBareStub$ExtensionMapper.getTypeObject(ComplexDataTypesDocLitBareStub.java:15467) > at > org.tempuri.complex.ComplexDataTypesDocLitBareStub$ArrayOfint$Factory.parse(ComplexDataTypesDocLitBareStub.java:40349) > ... 31 more > testretStructSNSAS(org.apache.axis2.rpc.complex.ComplexDataTypesDocLitBareTest) >
[jira] Created: (AXIS2-3781) ComplexDataTypesDocLitBareTest fails
ComplexDataTypesDocLitBareTest fails Key: AXIS2-3781 URL: https://issues.apache.org/jira/browse/AXIS2-3781 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: Integration Reporter: Davanum Srinivas Priority: Blocker --- Test set: org.apache.axis2.rpc.complex.ComplexDataTypesDocLitBareTest --- Tests run: 34, Failures: 0, Errors: 11, Skipped: 0, Time elapsed: 75.937 sec <<< FAILURE! testretArrayInt1D(org.apache.axis2.rpc.complex.ComplexDataTypesDocLitBareTest) Time elapsed: 2.703 sec <<< ERROR! org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unsupported type null org.tempuri.complex.data.arrays.ArrayOfint at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at org.tempuri.complex.ComplexDataTypesDocLitBareStub.fromOM(ComplexDataTypesDocLitBareStub.java:48033) at org.tempuri.complex.ComplexDataTypesDocLitBareStub.retArrayInt1D(ComplexDataTypesDocLitBareStub.java:4910) at org.apache.axis2.rpc.complex.ComplexDataTypesDocLitBareTest.testretArrayInt1D(ComplexDataTypesDocLitBareTest.java:108) 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 junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) at junit.extensions.TestSetup$1.protect(TestSetup.java:23) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.extensions.TestSetup.run(TestSetup.java:27) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:81) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:165) at org.apache.maven.surefire.Surefire.run(Surefire.java:107) 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.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:289) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:993) Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException: Unsupported type null org.tempuri.complex.data.arrays.ArrayOfint at org.tempuri.complex.ComplexDataTypesDocLitBareStub$ArrayOfint$Factory.parse(ComplexDataTypesDocLitBareStub.java:40444) at org.tempuri.complex.ComplexDataTypesDocLitBareStub$RetArrayInt1DResult$Factory.parse(ComplexDataTypesDocLitBareStub.java:45228) at org.tempuri.complex.ComplexDataTypesDocLitBareStub.fromOM(ComplexDataTypesDocLitBareStub.java:48027) ... 29 more Caused by: org.apache.axis2.databinding.ADBException: Unsupported type null org.tempuri.complex.data.arrays.ArrayOfint at org.tempuri.complex.ComplexDataTypesDocLitBareStub$ExtensionMapper.getTypeObject(ComplexDataTypesDocLitBareStub.java:15467) at org.tempuri.complex.ComplexDataTypesDocLitBareStub$ArrayOfint$Factory.parse(ComplexDataTypesDocLitBareStub.java:40349) ... 31 more testretStructSNSAS(org.apache.axis2.rpc.complex.ComplexDataTypesDocLitBareTest) Time elapsed: 2.063 sec <<< ERROR! org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: Unsupported type null org.tempuri.complex.data.Group at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at org.tempuri.complex.ComplexDataTypesDocLitBareStub.fromOM(ComplexDataTypesDocLitBareStub.java:48033) at org.tempuri.complex.ComplexDataTypesDocLitBareStub.retStructSNSAS(ComplexDataTypesDocLitBareStub.java:4434) at org.apache.axis2.rpc.compl
[jira] Resolved: (AXIS2-3759) REST GET invocations fail with httpLocations of the form foo/{name} when more than one parameter is present
[
https://issues.apache.org/jira/browse/AXIS2-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-3759.
-
Resolution: Fixed
Fixed in svn revision 650212
> REST GET invocations fail with httpLocations of the form foo/{name} when more
> than one parameter is present
> ---
>
> Key: AXIS2-3759
> URL: https://issues.apache.org/jira/browse/AXIS2-3759
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
>Reporter: Keith Godwin Chapman
>Assignee: Davanum Srinivas
>Priority: Blocker
> Fix For: 1.4
>
> Attachments: patch.txt
>
>
> REST GET invocations fail with httpLocations of the form foo/{name} when more
> than one parameter is present. There was a bug in the parameter extractor
> where it looked for the queryParameterSeparator as the next constant. But in
> this case it should have been looking for ? instead.
--
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-3757) Miss behaviour in adding handlers to the phase when the handler has after attribute
[ https://issues.apache.org/jira/browse/AXIS2-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3757. - Resolution: Fixed fixed in svn revision 650212 > Miss behaviour in adding handlers to the phase when the handler has after > attribute > --- > > Key: AXIS2-3757 > URL: https://issues.apache.org/jira/browse/AXIS2-3757 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel >Affects Versions: nightly > Environment: all env >Reporter: Ruwan Linton >Priority: Blocker > Fix For: 1.4 > > Attachments: phase_test.patch > > > Phase.addHandler(HandlerDescription) has some issues when the handler > description has the after attribute, and this behavior causes issues when the > phaseLast is set to true. > Synapse faced a critical issue due to this > [https://issues.apache.org/jira/browse/SYNAPSE-271] to which Deepal submitted > the patch for the axis2 Phase class. > This issue is blocking us and there is no meaning of the after attribute and > also the phaseLast attribute due to this issue. -- 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-3754) Generated ?wsdl2 docs do not contain httpLocation for HttpBinding hence codegen for httpBinding will not work
[ https://issues.apache.org/jira/browse/AXIS2-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3754. - Resolution: Fixed 1.4 branch version - 650005. > Generated ?wsdl2 docs do not contain httpLocation for HttpBinding hence > codegen for httpBinding will not work > - > > Key: AXIS2-3754 > URL: https://issues.apache.org/jira/browse/AXIS2-3754 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Keith Godwin Chapman >Assignee: Davanum Srinivas >Priority: Blocker > Fix For: 1.4 > > Attachments: patch.txt > > > Generated ?wsdl2 docs do not contain httpLocation for HttpBinding hence > codegen for httpBinding will not work. This is because the newly added > endpoint populator did not add this attribute to the httpendpoint. -- 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-3753) Generated ?wsdl2 docs are invalid when a service has more than 1 transport enabled
[ https://issues.apache.org/jira/browse/AXIS2-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3753. - Resolution: Fixed 1.4 branch version - 650005. > Generated ?wsdl2 docs are invalid when a service has more than 1 transport > enabled > -- > > Key: AXIS2-3753 > URL: https://issues.apache.org/jira/browse/AXIS2-3753 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Keith Godwin Chapman >Assignee: Davanum Srinivas >Priority: Blocker > Fix For: 1.4 > > Attachments: patch.txt > > > Generated ?wsdl2 docs are invalid when a service has more than 1 transport > enabled. In this situation the ?wsdl2 has duplicate bindings having the same > name which makes the wsdl invalid. The reason is because of a mistake made in > the service builder. -- 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: (AXIS2-3749) Invalid soap fault
[ https://issues.apache.org/jira/browse/AXIS2-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590375#action_12590375 ] Davanum Srinivas commented on AXIS2-3749: - Amila, Please go ahead and commit this on both trunk and branch. thanks, dims > Invalid soap fault > -- > > Key: AXIS2-3749 > URL: https://issues.apache.org/jira/browse/AXIS2-3749 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Amila Chinthaka Suriarachchi >Priority: Blocker > Attachments: addressing.patch > > > I invoke a service which has engaged Addressing with an invalid action (by a > mistake) and I got this exception > java.lang.NullPointerException > at > org.apache.axis2.handlers.addressing.AddressingInFaultHandler.invoke(AddressingInFaultHandler.java:96) > at org.apache.axis2.engine.Phase.invoke(Phase.java:295) > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163) > at > org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:363) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416) > at > org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:441) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) > at java.lang.Thread.run(Thread.java:595) > this exception happens at here. > faultLocalName = subCode.getValue().getTextAsQName().getLocalPart(); > Then I look at the soap fault. > http://www.w3.org/2003/05/soap-envelope";> > http://www.w3.org/2005/08/addressing";> > http://www.w3.org/2005/08/addressing/fault > > urn:uuid:6C771F78868CBF931B1208441597970 > > > > >soapenv:Sender > > wsa:ActionNotSupported > > > >The [action] cannot be > processed at the receiver. > > > xmlns:wsa="http://www.w3.org/2005/08/addressing";> > urn:PlainTestInOutOperation1 > > > > > > if we look at this line > wsa:ActionNotSupported > the prefix wsa is not declared. > I think this means Axiom does not serialize soap envelop properly when there > a TextQNames. -- 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: (AXIS2-3359) Printing well-formed SOAP message causes OMException
[ https://issues.apache.org/jira/browse/AXIS2-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590211#action_12590211 ] Davanum Srinivas commented on AXIS2-3359: - Steffen, The issue is that you are mixing auto-generated code that parses stax events and trying to access the soap envelope at the same time. Does not work because by the time you try to print the soap envelope the stax events are already consumed by the parser. So, if you really need both to work, then you have to edit InterfacciaEosCpcMessageReceiverInOut.java and add a line to build the soap envelope msgContext.getEnvelope().build() as the first line in the invokeBusinessLogic method. thanks, dims > Printing well-formed SOAP message causes OMException > > > Key: AXIS2-3359 > URL: https://issues.apache.org/jira/browse/AXIS2-3359 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: windows xp, tomcat 6.0.14, jdk 1.6.0_03 >Reporter: Steffen Bartsch > Attachments: ws_axis2_bug_3359.zip > > > I want to access the raw XML message but the function SOAPEnvelope.toString() > fails. > Here is my code to access the raw XML message: > MessageContext mc = MessageContext.getCurrentMessageContext(); > SOAPEnvelope env = mc.getEnvelope(); > String rawXmlMsg = env.toString(); > The SOAP message: > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> xmlns:ns2="http://www.ESB/SOAP/Header"; > soapenv:mustUnderstand="0">bartschpassworduserU2ApasswordU2Aautoma xmlns:ns1="http://sft.telecomitalia.it/cpc/interfacciaEos"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:type="ns1:RepairRequest">012345678912ATMX > The stacktrace: > org.apache.axiom.om.OMException: java.util.NoSuchElementException > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239) > at > org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:552) > at > org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild(OMElementImpl.java:563) > at > org.apache.axiom.om.impl.llom.OMElementImpl.getChildren(OMElementImpl.java:280) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:770) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:772) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345) > at > org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:913) > at > org.apache.log4j.or.DefaultRenderer.doRender(DefaultRenderer.java:35) > at org.apache.log4j.or.RendererMap.findAndRender(RendererMap.java:79) > at > org.apache.log4j.spi.LoggingEvent.getRenderedMessage(LoggingEvent.java:297) > at > org.apache.log4j.helpers.PatternParser$BasicPatternConverter.convert(PatternParser.java:403) > at > org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:64) > at org.apache.log4j.PatternLayout.format(PatternLayout.java:503) > at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301) > at org.apache.log4j.WriterAppender.append(WriterAppender.java:159) > at > org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230) > at > org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65) > at org.apache.log4j.Category.callAppenders(Category.java:203) > at org.apache.log4j.Category.forcedLog(Category.java:388) > at org.apache.log4j.Category.debug(Category.java:257) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcSkeleton.getSOAPMessage(InterfacciaEosCpcSkeleton.java:171) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcSkeleton.repair(InterfacciaEosCpcSkeleton.java:305) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcMessageReceiverInOut.invokeBusinessLogic(InterfacciaEosCpcMessageReceiverInOut.java:51) -- 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-3359) Printing well-formed SOAP message causes OMException
[ https://issues.apache.org/jira/browse/AXIS2-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3359. - Resolution: Won't Fix > Printing well-formed SOAP message causes OMException > > > Key: AXIS2-3359 > URL: https://issues.apache.org/jira/browse/AXIS2-3359 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: windows xp, tomcat 6.0.14, jdk 1.6.0_03 >Reporter: Steffen Bartsch > Attachments: ws_axis2_bug_3359.zip > > > I want to access the raw XML message but the function SOAPEnvelope.toString() > fails. > Here is my code to access the raw XML message: > MessageContext mc = MessageContext.getCurrentMessageContext(); > SOAPEnvelope env = mc.getEnvelope(); > String rawXmlMsg = env.toString(); > The SOAP message: > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> xmlns:ns2="http://www.ESB/SOAP/Header"; > soapenv:mustUnderstand="0">bartschpassworduserU2ApasswordU2Aautoma xmlns:ns1="http://sft.telecomitalia.it/cpc/interfacciaEos"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:type="ns1:RepairRequest">012345678912ATMX > The stacktrace: > org.apache.axiom.om.OMException: java.util.NoSuchElementException > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239) > at > org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:552) > at > org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild(OMElementImpl.java:563) > at > org.apache.axiom.om.impl.llom.OMElementImpl.getChildren(OMElementImpl.java:280) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:770) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:772) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345) > at > org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:913) > at > org.apache.log4j.or.DefaultRenderer.doRender(DefaultRenderer.java:35) > at org.apache.log4j.or.RendererMap.findAndRender(RendererMap.java:79) > at > org.apache.log4j.spi.LoggingEvent.getRenderedMessage(LoggingEvent.java:297) > at > org.apache.log4j.helpers.PatternParser$BasicPatternConverter.convert(PatternParser.java:403) > at > org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:64) > at org.apache.log4j.PatternLayout.format(PatternLayout.java:503) > at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301) > at org.apache.log4j.WriterAppender.append(WriterAppender.java:159) > at > org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230) > at > org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65) > at org.apache.log4j.Category.callAppenders(Category.java:203) > at org.apache.log4j.Category.forcedLog(Category.java:388) > at org.apache.log4j.Category.debug(Category.java:257) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcSkeleton.getSOAPMessage(InterfacciaEosCpcSkeleton.java:171) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcSkeleton.repair(InterfacciaEosCpcSkeleton.java:305) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcMessageReceiverInOut.invokeBusinessLogic(InterfacciaEosCpcMessageReceiverInOut.java:51) -- 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: (AXIS2-3742) Use actaul message to determine the outbound wsa action
[ https://issues.apache.org/jira/browse/AXIS2-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590086#action_12590086 ] Davanum Srinivas commented on AXIS2-3742: - Jarek, Please go ahead and commit to both trunk and branch. -- dims > Use actaul message to determine the outbound wsa action > --- > > Key: AXIS2-3742 > URL: https://issues.apache.org/jira/browse/AXIS2-3742 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement > Components: Addressing, jaxws >Affects Versions: 1.4, nightly >Reporter: Jarek Gawor > Attachments: AXIS2-3742.3.patch, AXIS2-3742.patch, > AXIS2-3742.tests.patch > > > When an anonymous operation is used, the wsa action either has to be > explicitly set on the message context or the default wsa outbound of the > anonymous operation will be used. However, in certain when an anonymous > operation is used, we can use the first body element of the outbound message > to determine the real operation (if any) and use its outbound action value > instead of the anonymous operation. This is necessary for JAX-WS Dispatch > clients that use anonymous operations to send/receive messages but still > might contain all the real operations since the Service class was built from > wsdl or annotations. -- 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-3749) Invalid soap fault
[ https://issues.apache.org/jira/browse/AXIS2-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3749. - Resolution: Fixed Fixed in svn revision 649166. Thanks a ton Amila. -- dims > Invalid soap fault > -- > > Key: AXIS2-3749 > URL: https://issues.apache.org/jira/browse/AXIS2-3749 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Amila Chinthaka Suriarachchi >Priority: Blocker > > I invoke a service which has engaged Addressing with an invalid action (by a > mistake) and I got this exception > java.lang.NullPointerException > at > org.apache.axis2.handlers.addressing.AddressingInFaultHandler.invoke(AddressingInFaultHandler.java:96) > at org.apache.axis2.engine.Phase.invoke(Phase.java:295) > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163) > at > org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:363) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:416) > at > org.apache.axis2.description.OutInAxisOperationClient$NonBlockingInvocationWorker.run(OutInAxisOperation.java:441) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) > at > edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) > at java.lang.Thread.run(Thread.java:595) > this exception happens at here. > faultLocalName = subCode.getValue().getTextAsQName().getLocalPart(); > Then I look at the soap fault. > http://www.w3.org/2003/05/soap-envelope";> > http://www.w3.org/2005/08/addressing";> > http://www.w3.org/2005/08/addressing/fault > > urn:uuid:6C771F78868CBF931B1208441597970 > > > > >soapenv:Sender > > wsa:ActionNotSupported > > > >The [action] cannot be > processed at the receiver. > > > xmlns:wsa="http://www.w3.org/2005/08/addressing";> > urn:PlainTestInOutOperation1 > > > > > > if we look at this line > wsa:ActionNotSupported > the prefix wsa is not declared. > I think this means Axiom does not serialize soap envelop properly when there > a TextQNames. -- 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: (AXIS2-3359) Printing well-formed SOAP message causes OMException
[ https://issues.apache.org/jira/browse/AXIS2-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589914#action_12589914 ] Davanum Srinivas commented on AXIS2-3359: - Steffen, Can you please upload a test case for us to try out? thanks, dims > Printing well-formed SOAP message causes OMException > > > Key: AXIS2-3359 > URL: https://issues.apache.org/jira/browse/AXIS2-3359 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: windows xp, tomcat 6.0.14, jdk 1.6.0_03 >Reporter: Steffen Bartsch > > I want to access the raw XML message but the function SOAPEnvelope.toString() > fails. > Here is my code to access the raw XML message: > MessageContext mc = MessageContext.getCurrentMessageContext(); > SOAPEnvelope env = mc.getEnvelope(); > String rawXmlMsg = env.toString(); > The SOAP message: > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> xmlns:ns2="http://www.ESB/SOAP/Header"; > soapenv:mustUnderstand="0">bartschpassworduserU2ApasswordU2Aautoma xmlns:ns1="http://sft.telecomitalia.it/cpc/interfacciaEos"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:type="ns1:RepairRequest">012345678912ATMX > The stacktrace: > org.apache.axiom.om.OMException: java.util.NoSuchElementException > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239) > at > org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:552) > at > org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild(OMElementImpl.java:563) > at > org.apache.axiom.om.impl.llom.OMElementImpl.getChildren(OMElementImpl.java:280) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:770) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:772) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345) > at > org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:913) > at > org.apache.log4j.or.DefaultRenderer.doRender(DefaultRenderer.java:35) > at org.apache.log4j.or.RendererMap.findAndRender(RendererMap.java:79) > at > org.apache.log4j.spi.LoggingEvent.getRenderedMessage(LoggingEvent.java:297) > at > org.apache.log4j.helpers.PatternParser$BasicPatternConverter.convert(PatternParser.java:403) > at > org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:64) > at org.apache.log4j.PatternLayout.format(PatternLayout.java:503) > at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301) > at org.apache.log4j.WriterAppender.append(WriterAppender.java:159) > at > org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230) > at > org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65) > at org.apache.log4j.Category.callAppenders(Category.java:203) > at org.apache.log4j.Category.forcedLog(Category.java:388) > at org.apache.log4j.Category.debug(Category.java:257) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcSkeleton.getSOAPMessage(InterfacciaEosCpcSkeleton.java:171) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcSkeleton.repair(InterfacciaEosCpcSkeleton.java:305) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcMessageReceiverInOut.invokeBusinessLogic(InterfacciaEosCpcMessageReceiverInOut.java:51) -- 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: (AXIS2-3745) Rampart has dependancies to classes which was in mex-impl
[ https://issues.apache.org/jira/browse/AXIS2-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589593#action_12589593 ] Davanum Srinivas commented on AXIS2-3745: - Will this work? http://svn.apache.org/viewvc?rev=648716&view=rev -- dims > Rampart has dependancies to classes which was in mex-impl > - > > Key: AXIS2-3745 > URL: https://issues.apache.org/jira/browse/AXIS2-3745 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: modules >Reporter: Nandana Mihindukulasooriya >Priority: Blocker > Fix For: 1.4 > > > Rampart uses Axis2 mex impl for exchanging metadata related to WS - Trust > endpoints . As Axis2 now embeds all the mex impl classes in Mex mar, those > classes are not available in lib. Rampart uses following classes. > org.apache.axis2.mex.MexConstants; > org.apache.axis2.mex.MexException; > org.apache.axis2.mex.om.Metadata; > org.apache.axis2.mex.om.MetadataReference; > org.apache.axis2.mex.om.MetadataSection; -- 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-3745) Rampart has dependancies to classes which was in mex-impl
[ https://issues.apache.org/jira/browse/AXIS2-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3745. - Resolution: Fixed am generating another jar now...see last comment. -- dims > Rampart has dependancies to classes which was in mex-impl > - > > Key: AXIS2-3745 > URL: https://issues.apache.org/jira/browse/AXIS2-3745 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: modules >Reporter: Nandana Mihindukulasooriya >Priority: Blocker > Fix For: 1.4 > > > Rampart uses Axis2 mex impl for exchanging metadata related to WS - Trust > endpoints . As Axis2 now embeds all the mex impl classes in Mex mar, those > classes are not available in lib. Rampart uses following classes. > org.apache.axis2.mex.MexConstants; > org.apache.axis2.mex.MexException; > org.apache.axis2.mex.om.Metadata; > org.apache.axis2.mex.om.MetadataReference; > org.apache.axis2.mex.om.MetadataSection; -- 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-3359) Printing well-formed SOAP message causes OMException
[ https://issues.apache.org/jira/browse/AXIS2-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3359. - Resolution: Fixed fixed with axiom changes - 648395 and axis2 test changes - 648397 > Printing well-formed SOAP message causes OMException > > > Key: AXIS2-3359 > URL: https://issues.apache.org/jira/browse/AXIS2-3359 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 > Environment: windows xp, tomcat 6.0.14, jdk 1.6.0_03 >Reporter: Steffen Bartsch > > I want to access the raw XML message but the function SOAPEnvelope.toString() > fails. > Here is my code to access the raw XML message: > MessageContext mc = MessageContext.getCurrentMessageContext(); > SOAPEnvelope env = mc.getEnvelope(); > String rawXmlMsg = env.toString(); > The SOAP message: > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> xmlns:ns2="http://www.ESB/SOAP/Header"; > soapenv:mustUnderstand="0">bartschpassworduserU2ApasswordU2Aautoma xmlns:ns1="http://sft.telecomitalia.it/cpc/interfacciaEos"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:type="ns1:RepairRequest">012345678912ATMX > The stacktrace: > org.apache.axiom.om.OMException: java.util.NoSuchElementException > at > org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239) > at > org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:552) > at > org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild(OMElementImpl.java:563) > at > org.apache.axiom.om.impl.llom.OMElementImpl.getChildren(OMElementImpl.java:280) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:770) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:772) > at > org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:756) > at > org.apache.axiom.om.impl.llom.OMNodeImpl.serialize(OMNodeImpl.java:345) > at > org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:913) > at > org.apache.log4j.or.DefaultRenderer.doRender(DefaultRenderer.java:35) > at org.apache.log4j.or.RendererMap.findAndRender(RendererMap.java:79) > at > org.apache.log4j.spi.LoggingEvent.getRenderedMessage(LoggingEvent.java:297) > at > org.apache.log4j.helpers.PatternParser$BasicPatternConverter.convert(PatternParser.java:403) > at > org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:64) > at org.apache.log4j.PatternLayout.format(PatternLayout.java:503) > at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301) > at org.apache.log4j.WriterAppender.append(WriterAppender.java:159) > at > org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230) > at > org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65) > at org.apache.log4j.Category.callAppenders(Category.java:203) > at org.apache.log4j.Category.forcedLog(Category.java:388) > at org.apache.log4j.Category.debug(Category.java:257) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcSkeleton.getSOAPMessage(InterfacciaEosCpcSkeleton.java:171) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcSkeleton.repair(InterfacciaEosCpcSkeleton.java:305) > at > it.telecomitalia.sft.cpc.interfacciaeos.InterfacciaEosCpcMessageReceiverInOut.invokeBusinessLogic(InterfacciaEosCpcMessageReceiverInOut.java:51) -- 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: (AXIS2-3740) Support for @MTOM Threshold.
[ https://issues.apache.org/jira/browse/AXIS2-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589057#action_12589057 ] Davanum Srinivas commented on AXIS2-3740: - Nikhil, Please commit only in trunk as we already cut Axiom release. -- dims > Support for @MTOM Threshold. > > > Key: AXIS2-3740 > URL: https://issues.apache.org/jira/browse/AXIS2-3740 > Project: Axis 2.0 (Axis2) > Issue Type: New Feature > Components: jaxws >Reporter: Nikhil Thaker >Assignee: Nikhil Thaker > Attachments: JIRA_Axis2-3740.txt > > > I am adding function to support MTOM attachment Threshold. The > implementation will involve reading the MTOM attachment threshold size and > setting it on Messagecontext. During the attachment marshalling process this > threshold value will be read and used to determine if the attachment needs to > be send as inlined or optimized. -- 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-3455) ?wsdl2 does not show engaged security policies
[ https://issues.apache.org/jira/browse/AXIS2-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3455. - Resolution: Fixed 1.4 branch - 648225. trunk - 648224. -- dims > ?wsdl2 does not show engaged security policies > -- > > Key: AXIS2-3455 > URL: https://issues.apache.org/jira/browse/AXIS2-3455 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Keith Godwin Chapman >Assignee: Sanka Samaranayake >Priority: Critical > Attachments: AXIS2_3455.patch > > > ?wsdl2 does not show engaged security policies whereas ?wsdl shows them. > See this in the context of https://wso2.org/jira/browse/WSAS-648 -- 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-3728) Context class loader not restored correctly
[
https://issues.apache.org/jira/browse/AXIS2-3728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-3728.
-
Resolution: Fixed
Fixed in svn revision 648010.
> Context class loader not restored correctly
> ---
>
> Key: AXIS2-3728
> URL: https://issues.apache.org/jira/browse/AXIS2-3728
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
>Reporter: Jarek Gawor
> Fix For: 1.4, nightly
>
>
> has the following code:
> AsyncResponse.java does not restore the context classloader correctly. For
> example:
> protected void onError(Throwable flt, MessageContext mc, ClassLoader cl) {
> setThreadClassLoader(cl);
> onError(flt, mc);
> ClassLoader origClassLoader =
> (ClassLoader)AccessController.doPrivileged(new PrivilegedAction() {
> public Object run() {
> return Thread.currentThread().getContextClassLoader();
> }
> });
> setThreadClassLoader(origClassLoader);
> }
> The origClassLoader is retrieved after new class loader is already set on the
> thread so really origClassLoader == cl. The origClassLoader should be
> obtained before the first setThreadClassLoader(cl) call. Same problem applies
> to onCompleted() call.
--
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-3739) type_substitution sample from website doesn't work
type_substitution sample from website doesn't work -- Key: AXIS2-3739 URL: https://issues.apache.org/jira/browse/AXIS2-3739 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Davanum Srinivas Priority: Critical See "type-substitution" sample application from http://www.javapassion.com/handsonlabs/wscustombinding/ It uses XmlSeeAlso and XmlJavaTypeAdapter. Hence it does not work with Axis2 -- 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-3737) Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is deployed as a jar under servicejars
[ https://issues.apache.org/jira/browse/AXIS2-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3737: Attachment: (was: apples.zip) > Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is > deployed as a jar under servicejars > - > > Key: AXIS2-3737 > URL: https://issues.apache.org/jira/browse/AXIS2-3737 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas >Assignee: Davanum Srinivas >Priority: Critical > Fix For: 1.4 > > Attachments: apples.wsdl, apples.xsd, apples.zip > > > Lots of code in jaxws maven module relies on the TCCL to load classes > specified via annotations. I will upload a sample wsdl/xsd that fails. -- 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-3737) Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is deployed as a jar under servicejars
[ https://issues.apache.org/jira/browse/AXIS2-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3737: Attachment: apples.zip service java file and classes > Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is > deployed as a jar under servicejars > - > > Key: AXIS2-3737 > URL: https://issues.apache.org/jira/browse/AXIS2-3737 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas >Assignee: Davanum Srinivas >Priority: Critical > Fix For: 1.4 > > Attachments: apples.wsdl, apples.xsd, apples.zip > > > Lots of code in jaxws maven module relies on the TCCL to load classes > specified via annotations. I will upload a sample wsdl/xsd that fails. -- 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-3737) Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is deployed as a jar under servicejars
[ https://issues.apache.org/jira/browse/AXIS2-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3737. - Resolution: Fixed Fixed in svn revision 647636. > Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is > deployed as a jar under servicejars > - > > Key: AXIS2-3737 > URL: https://issues.apache.org/jira/browse/AXIS2-3737 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas >Assignee: Davanum Srinivas >Priority: Critical > Fix For: 1.4 > > Attachments: apples.wsdl, apples.xsd, apples.zip > > > Lots of code in jaxws maven module relies on the TCCL to load classes > specified via annotations. I will upload a sample wsdl/xsd that fails. -- 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-3737) Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is deployed as a jar under servicejars
[ https://issues.apache.org/jira/browse/AXIS2-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3737: Attachment: apples.zip generated code and service impl > Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is > deployed as a jar under servicejars > - > > Key: AXIS2-3737 > URL: https://issues.apache.org/jira/browse/AXIS2-3737 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas >Assignee: Davanum Srinivas >Priority: Critical > Fix For: 1.4 > > Attachments: apples.wsdl, apples.xsd, apples.zip > > > Lots of code in jaxws maven module relies on the TCCL to load classes > specified via annotations. I will upload a sample wsdl/xsd that fails. -- 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-3737) Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is deployed as a jar under servicejars
[ https://issues.apache.org/jira/browse/AXIS2-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3737: Attachment: apples.wsdl wsdl > Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is > deployed as a jar under servicejars > - > > Key: AXIS2-3737 > URL: https://issues.apache.org/jira/browse/AXIS2-3737 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas >Assignee: Davanum Srinivas >Priority: Critical > Fix For: 1.4 > > Attachments: apples.wsdl, apples.xsd > > > Lots of code in jaxws maven module relies on the TCCL to load classes > specified via annotations. I will upload a sample wsdl/xsd that fails. -- 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-3737) Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is deployed as a jar under servicejars
[ https://issues.apache.org/jira/browse/AXIS2-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3737: Attachment: apples.xsd xsd > Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is > deployed as a jar under servicejars > - > > Key: AXIS2-3737 > URL: https://issues.apache.org/jira/browse/AXIS2-3737 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Davanum Srinivas >Assignee: Davanum Srinivas >Priority: Critical > Fix For: 1.4 > > Attachments: apples.wsdl, apples.xsd > > > Lots of code in jaxws maven module relies on the TCCL to load classes > specified via annotations. I will upload a sample wsdl/xsd that fails. -- 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-3737) Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is deployed as a jar under servicejars
Problems loading RequestWrapper/ResponseWrapper etc when JAXWS Service is deployed as a jar under servicejars - Key: AXIS2-3737 URL: https://issues.apache.org/jira/browse/AXIS2-3737 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Davanum Srinivas Assignee: Davanum Srinivas Priority: Critical Fix For: 1.4 Attachments: apples.wsdl, apples.xsd Lots of code in jaxws maven module relies on the TCCL to load classes specified via annotations. I will upload a sample wsdl/xsd that fails. -- 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: (AXIS2-3736) java.util.List is not known to this context
[
https://issues.apache.org/jira/browse/AXIS2-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588432#action_12588432
]
Davanum Srinivas commented on AXIS2-3736:
-
Looks like this is related to XmlJavaTypeAdapter processing AXIS2-3590
> java.util.List is not known to this context
> ---
>
> Key: AXIS2-3736
> URL: https://issues.apache.org/jira/browse/AXIS2-3736
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
>Reporter: Davanum Srinivas
> Attachments: apples.zip
>
>
> == SEI
> @WebService
> @XmlSeeAlso({ Apple.class, Fuji.class })
> public interface AppleFinder {
> List getApple(String appType);
> }
> == Impl
> @WebService(endpointInterface =
> "org.apache.cxf.systest.type_substitution.AppleFinder",
> serviceName = "AppleFinder")
> public class AppleFinderImpl implements AppleFinder {
> public List getApple(String appleType) {
> List apples = new ArrayList();
> apples.add(new Fuji("Red", "mild", "Fuji-1"));
> apples.add(new Fuji("Yellow", "sweet", "Fuji-2"));
> return apples;
> }
> }
> = Stack Trace =
> [javax.xml.bind.JAXBException: java.util.List is not known to this context]
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:331)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:175)
> at
> org.apache.axis2.datasource.jaxb.JAXBDSContext$3.run(JAXBDSContext.java:664)
> at
> org.apache.axis2.java.security.AccessController.doPrivileged(AccessController.java:76)
> at
> org.apache.axis2.datasource.jaxb.JAXBDSContext.marshalByType(JAXBDSContext.java:566)
> at
> org.apache.axis2.datasource.jaxb.JAXBDSContext.marshal(JAXBDSContext.java:294)
> at
> org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl._outputFromBO(JAXBBlockImpl.java:175)
> at
> org.apache.axis2.jaxws.message.impl.BlockImpl.outputTo(BlockImpl.java:342)
> at
> org.apache.axis2.jaxws.message.impl.BlockImpl.serialize(BlockImpl.java:266)
> at
> org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume(OMSourcedElementImpl.java:664)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:918)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:918)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
> at
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:240)
> at
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:228)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
> at
> org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:471)
> at
> org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:68)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:330)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:213)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
> at
> org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:210)
> ... 9 more
> Caused by: javax.xml.bind.JAXBException: java.util.List is not known to this
> context
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:242)
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:257)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(ElementBeanInfoImpl.java:143)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(ElementBeanInfoImpl.java:185)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeBody(ElementBeanInfoImpl.java:305)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(ElementBeanInfoImpl.java:312)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(ElementBeanInfoImpl.java:71)
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:490)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:328)
> ... 31 more
> Caused by: javax.xml.bind.JAXBException: java.util.List is not known to this
> c
[jira] Created: (AXIS2-3736) java.util.List is not known to this context
java.util.List is not known to this context
---
Key: AXIS2-3736
URL: https://issues.apache.org/jira/browse/AXIS2-3736
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: jaxws
Reporter: Davanum Srinivas
Attachments: apples.zip
== SEI
@WebService
@XmlSeeAlso({ Apple.class, Fuji.class })
public interface AppleFinder {
List getApple(String appType);
}
== Impl
@WebService(endpointInterface =
"org.apache.cxf.systest.type_substitution.AppleFinder",
serviceName = "AppleFinder")
public class AppleFinderImpl implements AppleFinder {
public List getApple(String appleType) {
List apples = new ArrayList();
apples.add(new Fuji("Red", "mild", "Fuji-1"));
apples.add(new Fuji("Yellow", "sweet", "Fuji-2"));
return apples;
}
}
= Stack Trace =
[javax.xml.bind.JAXBException: java.util.List is not known to this context]
at
com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:331)
at
com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:175)
at
org.apache.axis2.datasource.jaxb.JAXBDSContext$3.run(JAXBDSContext.java:664)
at
org.apache.axis2.java.security.AccessController.doPrivileged(AccessController.java:76)
at
org.apache.axis2.datasource.jaxb.JAXBDSContext.marshalByType(JAXBDSContext.java:566)
at
org.apache.axis2.datasource.jaxb.JAXBDSContext.marshal(JAXBDSContext.java:294)
at
org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl._outputFromBO(JAXBBlockImpl.java:175)
at
org.apache.axis2.jaxws.message.impl.BlockImpl.outputTo(BlockImpl.java:342)
at
org.apache.axis2.jaxws.message.impl.BlockImpl.serialize(BlockImpl.java:266)
at
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume(OMSourcedElementImpl.java:664)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:918)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:918)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:240)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:228)
at
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
at
org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:471)
at
org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:68)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:330)
at
org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:213)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
at
org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:210)
... 9 more
Caused by: javax.xml.bind.JAXBException: java.util.List is not known to this
context
at
com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:242)
at
com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:257)
at
com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(ElementBeanInfoImpl.java:143)
at
com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(ElementBeanInfoImpl.java:185)
at
com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeBody(ElementBeanInfoImpl.java:305)
at
com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(ElementBeanInfoImpl.java:312)
at
com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(ElementBeanInfoImpl.java:71)
at
com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:490)
at
com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:328)
... 31 more
Caused by: javax.xml.bind.JAXBException: java.util.List is not known to this
context
at
com.sun.xml.bind.v2.runtime.JAXBContextImpl.getBeanInfo(JAXBContextImpl.java:587)
at
com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(ElementBeanInfoImpl.java:140)
... 37 more
--
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-3736) java.util.List is not known to this context
[
https://issues.apache.org/jira/browse/AXIS2-3736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas updated AXIS2-3736:
Attachment: apples.zip
CXF sample
> java.util.List is not known to this context
> ---
>
> Key: AXIS2-3736
> URL: https://issues.apache.org/jira/browse/AXIS2-3736
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
>Reporter: Davanum Srinivas
> Attachments: apples.zip
>
>
> == SEI
> @WebService
> @XmlSeeAlso({ Apple.class, Fuji.class })
> public interface AppleFinder {
> List getApple(String appType);
> }
> == Impl
> @WebService(endpointInterface =
> "org.apache.cxf.systest.type_substitution.AppleFinder",
> serviceName = "AppleFinder")
> public class AppleFinderImpl implements AppleFinder {
> public List getApple(String appleType) {
> List apples = new ArrayList();
> apples.add(new Fuji("Red", "mild", "Fuji-1"));
> apples.add(new Fuji("Yellow", "sweet", "Fuji-2"));
> return apples;
> }
> }
> = Stack Trace =
> [javax.xml.bind.JAXBException: java.util.List is not known to this context]
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:331)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:175)
> at
> org.apache.axis2.datasource.jaxb.JAXBDSContext$3.run(JAXBDSContext.java:664)
> at
> org.apache.axis2.java.security.AccessController.doPrivileged(AccessController.java:76)
> at
> org.apache.axis2.datasource.jaxb.JAXBDSContext.marshalByType(JAXBDSContext.java:566)
> at
> org.apache.axis2.datasource.jaxb.JAXBDSContext.marshal(JAXBDSContext.java:294)
> at
> org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl._outputFromBO(JAXBBlockImpl.java:175)
> at
> org.apache.axis2.jaxws.message.impl.BlockImpl.outputTo(BlockImpl.java:342)
> at
> org.apache.axis2.jaxws.message.impl.BlockImpl.serialize(BlockImpl.java:266)
> at
> org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerializeAndConsume(OMSourcedElementImpl.java:664)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:918)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:918)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
> at
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.serializeInternally(SOAPEnvelopeImpl.java:240)
> at
> org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.internalSerialize(SOAPEnvelopeImpl.java:228)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.internalSerializeAndConsume(OMElementImpl.java:947)
> at
> org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:471)
> at
> org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:68)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:330)
> at
> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:213)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:448)
> at
> org.apache.axis2.jaxws.server.JAXWSMessageReceiver.receive(JAXWSMessageReceiver.java:210)
> ... 9 more
> Caused by: javax.xml.bind.JAXBException: java.util.List is not known to this
> context
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:242)
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:257)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(ElementBeanInfoImpl.java:143)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl$1.serializeBody(ElementBeanInfoImpl.java:185)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeBody(ElementBeanInfoImpl.java:305)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(ElementBeanInfoImpl.java:312)
> at
> com.sun.xml.bind.v2.runtime.ElementBeanInfoImpl.serializeRoot(ElementBeanInfoImpl.java:71)
> at
> com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:490)
> at
> com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:328)
> ... 31 more
> Caused by: javax.xml.bind.JAXBException: java.util.List is not known to this
> context
> at
> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getBeanInfo(JAXBConte
[jira] Commented: (AXIS2-3712) Handling of exceptions raised by handlers in one-way invocations
[ https://issues.apache.org/jira/browse/AXIS2-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588151#action_12588151 ] Davanum Srinivas commented on AXIS2-3712: - toggle from axis2.xml, sounds like a good idea. > Handling of exceptions raised by handlers in one-way invocations > > > Key: AXIS2-3712 > URL: https://issues.apache.org/jira/browse/AXIS2-3712 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Affects Versions: 1.4, nightly >Reporter: Jarek Gawor > Attachments: AXIS2-3712.patch > > > As according to some Sun "experts" exceptions raised by handlers in one-way > invocations should be discarded. > Here's some background as the same problem was discovered by CXF folks: > http://www.nabble.com/JAX-WS-spec-interpretation-issue-to15178658.html -- 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: (AXIS2-3712) Handling of exceptions raised by handlers in one-way invocations
[ https://issues.apache.org/jira/browse/AXIS2-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587764#action_12587764 ] Davanum Srinivas commented on AXIS2-3712: - Jarek, +1 from me. -- dims > Handling of exceptions raised by handlers in one-way invocations > > > Key: AXIS2-3712 > URL: https://issues.apache.org/jira/browse/AXIS2-3712 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Affects Versions: 1.4, nightly >Reporter: Jarek Gawor > Attachments: AXIS2-3712.patch > > > As according to some Sun "experts" exceptions raised by handlers in one-way > invocations should be discarded. > Here's some background as the same problem was discovered by CXF folks: > http://www.nabble.com/JAX-WS-spec-interpretation-issue-to15178658.html -- 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-3729) Log.debug statement causes NullPointerException
[
https://issues.apache.org/jira/browse/AXIS2-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-3729.
-
Resolution: Fixed
already fixed. thanks!
-- dims
> Log.debug statement causes NullPointerException
> ---
>
> Key: AXIS2-3729
> URL: https://issues.apache.org/jira/browse/AXIS2-3729
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.3
> Environment: Windows XP SP2, Java 6, log4j
>Reporter: Raul K.
> Original Estimate: 0.08h
> Remaining Estimate: 0.08h
>
> When setting the log4j.category.org.apache.axis2.transport=DEBUG in the
> log4j.properties config file, line 156 from class TransportUtils:
>log.debug("createSOAPEnvelope using Builder (" +
> builder.getClass() + ") selected from type (" +
> type +")");
> causes the following uncontrolled NullPointerException to be thrown:
> 2008-04-10 18:14:10,577 [-] [I/O dispatcher 7] DEBUG ServerHandler HTTP
> connection [localhost/127.0.0.1:2591]: Content decoder [content length: 285; p
> os: 252; completed: false]
> Exception in thread "HttpServerWorker-1" java.lang.NullPointerException
> at
> org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:156)
> at
> org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:111)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:270)
> at
> org.apache.synapse.transport.nhttp.ServerWorker.processPost(ServerWorker.java:226)
> at
> org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:190)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
--
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: (AXIS2-3726) All outbound handlers are invoked when an inbound handler throws exception or returns false
[ https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587733#action_12587733 ] Davanum Srinivas commented on AXIS2-3726: - good catch jarek! > All outbound handlers are invoked when an inbound handler throws exception or > returns false > --- > > Key: AXIS2-3726 > URL: https://issues.apache.org/jira/browse/AXIS2-3726 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Reporter: Jarek Gawor > Fix For: 1.4, nightly > > Attachments: AXIS2-3726.patch > > > All outbound handlers are getting invoked even though an inbound handler > threw an exception or returned false from its handleMessage() method (on the > server side). -- 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: (AXIS2-3726) All outbound handlers are invoked when an inbound handler throws exception or returns false
[ https://issues.apache.org/jira/browse/AXIS2-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587673#action_12587673 ] Davanum Srinivas commented on AXIS2-3726: - Looks good Jarek. thanks. -- dims > All outbound handlers are invoked when an inbound handler throws exception or > returns false > --- > > Key: AXIS2-3726 > URL: https://issues.apache.org/jira/browse/AXIS2-3726 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Reporter: Jarek Gawor > Fix For: 1.4, nightly > > Attachments: AXIS2-3726.patch > > > All outbound handlers are getting invoked even though an inbound handler > threw an exception or returned false from its handleMessage() method (on the > server side). -- 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: (AXIS2-3724) WSDL complex type elements do not comply to JAXB Java bean
[ https://issues.apache.org/jira/browse/AXIS2-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587575#action_12587575 ] Davanum Srinivas commented on AXIS2-3724: - See jaxws-addressbook sample specifically the readme > WSDL complex type elements do not comply to JAXB Java bean > -- > > Key: AXIS2-3724 > URL: https://issues.apache.org/jira/browse/AXIS2-3724 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Affects Versions: nightly > Environment: Win XP Pro, JDK6_04, Tomcat 5.5.26, JAXB 2.1.6 >Reporter: Glen Verran > Fix For: nightly > > > I created a web service which contains one method. It has one parameter of > type RetrieveConfigurationDataRequest and returns > RetrieveConfigurationDataResponse. > Focusing on RetrieveConfigurationDataRequest , the java bean was generated by > JAXB 2.1.6. Here are the variables from the java bean below > @XmlElement(required = true) > protected String echoData; > @XmlElement(required = true) > protected String identifierType; > @XmlElement(required = true) > protected String identifier; > @XmlElement(required = true) > protected String revision; > protected String vintage; > protected Long dataBlockSize; > protected Long dataBlockPosition; > @XmlElement(required = true) > protected DataEncodingType dataEncodingType; > The order of their "getters" and "setters" appear in the same order as the > variables. > The WSDL that gets generated contains this complexType which lools like this. > > > > > type="xs:long"/> > type="xs:long"/> > type="ax21:DataEncodingType"/> > type="xs:string"/> > type="xs:string"/> > type="xs:string"/> > type="xs:string"/> > type="xs:string"/> > > > > > I find that the WSDL does not comply with the JAXB 2.1.6 generated java bean > in the following ways: > 1) The elements are alphabetically sorted and do not appear in the same > order as in the java bean. > 2) Look at the "identifier" element and you'll see that it has a minOccurs > of 0. This is a required field by the java bean and so should not have a > minOccurs modifier in there. > 3) I also noticed that all the fields are set to nullable. I don't know > what the criteria is for this, but I assume it is because these are referring > to java objects and not primitives. I also think that if an object is > required, that it should not be nullable. > At the end of the day, the WSDL must take JAXB and its annotations into > account and reflect the web service and its java beans 100% and it is not > doing that. > I know there is a workaround by inserting a modified wsdl into the aar file, > but I don't want to have to do that since AXIS2 was designed to generate the > WSDL itself when issuing ?WSDL in a browser. -- 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: (AXIS2-3724) WSDL complex type elements do not comply to JAXB Java bean
[ https://issues.apache.org/jira/browse/AXIS2-3724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587569#action_12587569 ] Davanum Srinivas commented on AXIS2-3724: - You really need to use the JAXWS 2.1 support in latest nightly. -- dims > WSDL complex type elements do not comply to JAXB Java bean > -- > > Key: AXIS2-3724 > URL: https://issues.apache.org/jira/browse/AXIS2-3724 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl >Affects Versions: nightly > Environment: Win XP Pro, JDK6_04, Tomcat 5.5.26, JAXB 2.1.6 >Reporter: Glen Verran > Fix For: nightly > > > I created a web service which contains one method. It has one parameter of > type RetrieveConfigurationDataRequest and returns > RetrieveConfigurationDataResponse. > Focusing on RetrieveConfigurationDataRequest , the java bean was generated by > JAXB 2.1.6. Here are the variables from the java bean below > @XmlElement(required = true) > protected String echoData; > @XmlElement(required = true) > protected String identifierType; > @XmlElement(required = true) > protected String identifier; > @XmlElement(required = true) > protected String revision; > protected String vintage; > protected Long dataBlockSize; > protected Long dataBlockPosition; > @XmlElement(required = true) > protected DataEncodingType dataEncodingType; > The order of their "getters" and "setters" appear in the same order as the > variables. > The WSDL that gets generated contains this complexType which lools like this. > > > > > type="xs:long"/> > type="xs:long"/> > type="ax21:DataEncodingType"/> > type="xs:string"/> > type="xs:string"/> > type="xs:string"/> > type="xs:string"/> > type="xs:string"/> > > > > > I find that the WSDL does not comply with the JAXB 2.1.6 generated java bean > in the following ways: > 1) The elements are alphabetically sorted and do not appear in the same > order as in the java bean. > 2) Look at the "identifier" element and you'll see that it has a minOccurs > of 0. This is a required field by the java bean and so should not have a > minOccurs modifier in there. > 3) I also noticed that all the fields are set to nullable. I don't know > what the criteria is for this, but I assume it is because these are referring > to java objects and not primitives. I also think that if an object is > required, that it should not be nullable. > At the end of the day, the WSDL must take JAXB and its annotations into > account and reflect the web service and its java beans 100% and it is not > doing that. > I know there is a workaround by inserting a modified wsdl into the aar file, > but I don't want to have to do that since AXIS2 was designed to generate the > WSDL itself when issuing ?WSDL in a browser. -- 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: (AXIS2-3722) Invalid SOAPMessage caching in SoapMessageContext
[ https://issues.apache.org/jira/browse/AXIS2-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587473#action_12587473 ] Davanum Srinivas commented on AXIS2-3722: - Looks good Jarek. +1 > Invalid SOAPMessage caching in SoapMessageContext > -- > > Key: AXIS2-3722 > URL: https://issues.apache.org/jira/browse/AXIS2-3722 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 1.4, nightly > > Attachments: AXIS2-3722.patch > > > SoapMessageContext.getMessage() will always return a cached copy of the > SOAPMessage even though the underlying message in > org.apache.axis2.jaxws.core.MessageContext was changed (i.e. using > messageCtx.getMEPContext().setMessage()). The SoapMessageContext must not > cache the SOAPMessage or it should detect when the underlying Message changes. -- 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-3717) WSDL2Java fails for WSDL that work for Axis2 1.3
[
https://issues.apache.org/jira/browse/AXIS2-3717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-3717.
-
Resolution: Fixed
Fixed in svn revision 646511
> WSDL2Java fails for WSDL that work for Axis2 1.3
>
>
> Key: AXIS2-3717
> URL: https://issues.apache.org/jira/browse/AXIS2-3717
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.4
> Environment: Java 1.6, Windows
>Reporter: Werner Dittmann
>Assignee: Davanum Srinivas
>Priority: Blocker
> Fix For: 1.4
>
> Attachments: ca-interface.wsdl, ca-types.xsd
>
>
> using Axis2 1.4 RC4 WSDL2Java fails for WSDL files that work for Axis2 1.3
> and without any complaints. Using "urn:" naming scheme. Also fails when using
> http: naming scheme and the document is not referencable (the later used to
> work in RC3).
> For the WSDL files see attachment, command and error output in this message.
> For WSDL2java I use the follwing command:
> wsdl2java.sh -s -ssi -d adb -p caservice \
>-t -wv 2.0 -o buildc -d adb \
>-http-proxy-host proxy.emea.nsn-intra.net \
>-http-proxy-port 81 \
>-ns2p urn:schemas:caTypes=schemas.catypes \
>-uri ca-interface.wsdl
> I got the following error messages:
> Using AXIS2_HOME: d:\devhome\axis2-1.4
> Using JAVA_HOME: d:\jdk1.6.0
> log4j:WARN No appenders could be found for logger
> (org.apache.axis2.description.WSDL20ToAxisServiceBuilder).
> log4j:WARN Please initialize the log4j system properly.
> Woden[Error],0:0,WSDL502,Could not create a URL from context URI "null" and
> location URI "null".
> Woden[Error],0:0,WSDL502,Could not create a URL from context URI "null" and
> location URI "null".
> Woden[Warning],0:0,Description-1001,The targetNamespace 'urn:caService' is
> not dereferencable.
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:153)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Caused by: org.apache.axis2.AxisFault: Unable to find element
> {urn:schemas:caTypes}createPackageSubscription reffered to by operation
> createPackageSubscription
> at
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.createAxisMessage(WSDL20ToAxisServiceBuilder.java:1112)
> at
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.populateOperations(WSDL20ToAxisServiceBuilder.java:1053)
> at
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.processInterface(WSDL20ToAxisServiceBuilder.java:956)
> at
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.processService(WSDL20ToAxisServiceBuilder.java:385)
> at
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.populateService(WSDL20ToAxisServiceBuilder.java:273)
> at
> org.apache.axis2.description.WSDL20ToAllAxisServicesBuilder.populateAllServices(WSDL20ToAllAxisServicesBuilder.java:90)
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:105)
> ... 2 more
--
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-3714) Adding codegen jar to axis2.war and adding mtompolicy jar to distribution
[ https://issues.apache.org/jira/browse/AXIS2-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3714. - Resolution: Fixed Looks like this is already taken care of. C:\Apache\FINAL\axis2\modules\webapp\target>jar -tvf axis2.war | grep codeg 163928 Wed Apr 09 12:34:26 EDT 2008 WEB-INF/lib/axis2-adb-codegen-1.4.jar 236935 Wed Apr 09 12:33:18 EDT 2008 WEB-INF/lib/axis2-codegen-1.4.jar C:\Apache\FINAL\axis2\modules\webapp\target>jar -tvf axis2.war | grep mtomp 5703 Wed Apr 09 12:37:36 EDT 2008 WEB-INF/lib/axis2-mtompolicy-1.4.jar C:\Apache\FINAL\axis2\modules\distribution\target>jar -tvf axis2-1.4-bin.zip | grep codeg 236935 Wed Apr 09 12:33:18 EDT 2008 axis2-1.4/lib/axis2-codegen-1.4.jar 163928 Wed Apr 09 12:34:26 EDT 2008 axis2-1.4/lib/axis2-adb-codegen-1.4.jar C:\Apache\FINAL\axis2\modules\distribution\target>jar -tvf axis2-1.4-bin.zip | grep mtomp 5703 Wed Apr 09 12:37:36 EDT 2008 axis2-1.4/lib/axis2-mtompolicy-1.4.jar thanks, dims > Adding codegen jar to axis2.war and adding mtompolicy jar to distribution > - > > Key: AXIS2-3714 > URL: https://issues.apache.org/jira/browse/AXIS2-3714 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: nightly >Reporter: Amila Chinthaka Suriarachchi >Assignee: Davanum Srinivas >Priority: Blocker > Fix For: 1.4 > > > Rampart requires these jars. -- 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: (AXIS2-3720) MessageContext.REFERENCE_PARAMETERS property not visible in handlers
[ https://issues.apache.org/jira/browse/AXIS2-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587307#action_12587307 ] Davanum Srinivas commented on AXIS2-3720: - Looks good Jarek!. Please go ahead and commit it. -- dims > MessageContext.REFERENCE_PARAMETERS property not visible in handlers > > > Key: AXIS2-3720 > URL: https://issues.apache.org/jira/browse/AXIS2-3720 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Fix For: 1.4, nightly > > Attachments: AXIS2-3720.2.patch, AXIS2-3720.patch > > > The MessageContext.REFERENCE_PARAMETERS property is not accessible in JAX-WS > handlers. -- 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: (AXIS2-3718) If available prefer sending [Subsubcode] as the fault code instead of [Subcode] for SOAP 1.1 faults
[ https://issues.apache.org/jira/browse/AXIS2-3718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586911#action_12586911 ] Davanum Srinivas commented on AXIS2-3718: - Jarek, Looks good. Please go ahead and check it in, -- dims > If available prefer sending [Subsubcode] as the fault code instead of > [Subcode] for SOAP 1.1 faults > --- > > Key: AXIS2-3718 > URL: https://issues.apache.org/jira/browse/AXIS2-3718 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Addressing >Reporter: Jarek Gawor > Fix For: 1.4, nightly > > Attachments: AXIS2-3718.patch > > > If there is a [Subsubcode] available for some WSA fault prefer sending it > instead of [Subcode] for SOAP 1.1 faults. -- 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-3711) axis2-mtompolicy-1.4.jar is missing in the bin dist
[ https://issues.apache.org/jira/browse/AXIS2-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3711. - Resolution: Fixed looks like i had previously missed the entry in bin-assembly.xml. please check now. -- dims > axis2-mtompolicy-1.4.jar is missing in the bin dist > --- > > Key: AXIS2-3711 > URL: https://issues.apache.org/jira/browse/AXIS2-3711 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Ruchith Udayanga Fernando >Priority: Blocker > Fix For: 1.4 > > Attachments: axis2-3711.patch > > -- 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] Reopened: (AXIS2-3711) axis2-mtompolicy-1.4.jar is missing in the bin dist
[ https://issues.apache.org/jira/browse/AXIS2-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas reopened AXIS2-3711: - > axis2-mtompolicy-1.4.jar is missing in the bin dist > --- > > Key: AXIS2-3711 > URL: https://issues.apache.org/jira/browse/AXIS2-3711 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Ruchith Udayanga Fernando >Priority: Blocker > Fix For: 1.4 > > Attachments: axis2-3711.patch > > -- 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] Assigned: (AXIS2-3717) WSDL2Java fails for WSDL that work for Axis2 1.3
[
https://issues.apache.org/jira/browse/AXIS2-3717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas reassigned AXIS2-3717:
---
Assignee: Lawrence Mandel
> WSDL2Java fails for WSDL that work for Axis2 1.3
>
>
> Key: AXIS2-3717
> URL: https://issues.apache.org/jira/browse/AXIS2-3717
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.4
> Environment: Java 1.6, Windows
>Reporter: Werner Dittmann
>Assignee: Lawrence Mandel
>Priority: Blocker
> Fix For: 1.4
>
> Attachments: ca-interface.wsdl, ca-types.xsd
>
>
> using Axis2 1.4 RC4 WSDL2Java fails for WSDL files that work for Axis2 1.3
> and without any complaints. Using "urn:" naming scheme. Also fails when using
> http: naming scheme and the document is not referencable (the later used to
> work in RC3).
> For the WSDL files see attachment, command and error output in this message.
> For WSDL2java I use the follwing command:
> wsdl2java.sh -s -ssi -d adb -p caservice \
>-t -wv 2.0 -o buildc -d adb \
>-http-proxy-host proxy.emea.nsn-intra.net \
>-http-proxy-port 81 \
>-ns2p urn:schemas:caTypes=schemas.catypes \
>-uri ca-interface.wsdl
> I got the following error messages:
> Using AXIS2_HOME: d:\devhome\axis2-1.4
> Using JAVA_HOME: d:\jdk1.6.0
> log4j:WARN No appenders could be found for logger
> (org.apache.axis2.description.WSDL20ToAxisServiceBuilder).
> log4j:WARN Please initialize the log4j system properly.
> Woden[Error],0:0,WSDL502,Could not create a URL from context URI "null" and
> location URI "null".
> Woden[Error],0:0,WSDL502,Could not create a URL from context URI "null" and
> location URI "null".
> Woden[Warning],0:0,Description-1001,The targetNamespace 'urn:caService' is
> not dereferencable.
> Exception in thread "main"
> org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:153)
> at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
> at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
> Caused by: org.apache.axis2.AxisFault: Unable to find element
> {urn:schemas:caTypes}createPackageSubscription reffered to by operation
> createPackageSubscription
> at
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.createAxisMessage(WSDL20ToAxisServiceBuilder.java:1112)
> at
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.populateOperations(WSDL20ToAxisServiceBuilder.java:1053)
> at
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.processInterface(WSDL20ToAxisServiceBuilder.java:956)
> at
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.processService(WSDL20ToAxisServiceBuilder.java:385)
> at
> org.apache.axis2.description.WSDL20ToAxisServiceBuilder.populateService(WSDL20ToAxisServiceBuilder.java:273)
> at
> org.apache.axis2.description.WSDL20ToAllAxisServicesBuilder.populateAllServices(WSDL20ToAllAxisServicesBuilder.java:90)
> at
> org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:105)
> ... 2 more
--
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: (AXIS2-3714) Adding codegen jar to axis2.war and adding mtompolicy jar to distribution
[ https://issues.apache.org/jira/browse/AXIS2-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586838#action_12586838 ] Davanum Srinivas commented on AXIS2-3714: - Patch Please!! or we have to downgrade this bug. > Adding codegen jar to axis2.war and adding mtompolicy jar to distribution > - > > Key: AXIS2-3714 > URL: https://issues.apache.org/jira/browse/AXIS2-3714 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: nightly >Reporter: Amila Chinthaka Suriarachchi >Assignee: Davanum Srinivas >Priority: Blocker > Fix For: 1.4 > > > Rampart requires these jars. -- 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-3711) axis2-mtompolicy-1.4.jar is missing in the bin dist
[ https://issues.apache.org/jira/browse/AXIS2-3711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3711. - Resolution: Fixed looks like this is already applied. > axis2-mtompolicy-1.4.jar is missing in the bin dist > --- > > Key: AXIS2-3711 > URL: https://issues.apache.org/jira/browse/AXIS2-3711 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Ruchith Udayanga Fernando >Priority: Blocker > Fix For: 1.4 > > Attachments: axis2-3711.patch > > -- 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-3716) Various improvements and fixes for ThreadPool
[ https://issues.apache.org/jira/browse/AXIS2-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3716: Fix Version/s: (was: 1.4) > Various improvements and fixes for ThreadPool > - > > Key: AXIS2-3716 > URL: https://issues.apache.org/jira/browse/AXIS2-3716 > Project: Axis 2.0 (Axis2) > Issue Type: Improvement >Affects Versions: 1.3 >Reporter: Michele Mazzucco > Attachments: AXIS2-3716.patch > > > The instance method safeShutDown changes the static field shutDown. The field > should not be static. > Some getter/setter methods are needed to customize the pool size and other > parameters -- 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-3710) fixes for backward compatibility
[
https://issues.apache.org/jira/browse/AXIS2-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-3710.
-
Resolution: Fixed
Checked in an alternate fix (645520 in trunk and 645521 in 1.4 branch)
> fixes for backward compatibility
> -
>
> Key: AXIS2-3710
> URL: https://issues.apache.org/jira/browse/AXIS2-3710
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.4
> Environment: Any
>Reporter: Saminda Wishwajith Abeyruwan
>Assignee: Davanum Srinivas
>Priority: Blocker
> Fix For: 1.4
>
> Attachments: axisservlet.patch
>
>
> Hi,
> Is there a particular reason to add the line.
> msgContext.setProperty(HTTPCon
> stants.MC_HTTP_SERVLETCONTEXT, getServletContext());
> You will be able to access the context from http servlet request object.
> Beside the prior added line will break some of the existing production code.
> getServletContext() will work properly, IFF the user's servlet inherit the
> init method or if over-rides, it should called the parent init method.
> In AxisServlet, yes it dose over-rides the init method and calls the parent
> init.
> But those of us who have extended AxisServlet to work with, where over-rides
> the init method to intialize the AxisConfiguration the way our production
> system wants does not call the parents (AxisServlet) init method.
> ex:
> public class MyServlet extends AxisServlet {
> ...
>public void init(ServletConfig config) {
> // my way of initializing axisconfiguration and listeners rather using
> parent
> // init, but inheriting parents do* from AxisServlet.
> }
> }
> We used AxisServlet as show above for quite a long time.
> I'm afraid the prior line of code has broken the backward compatibility of
> re-using AxisServlet in production environments.
> Thus, the correct way is to obtain the servlet context from request, rather
> setting the property.
> Thus, I would humbly ask to revert the commit to preserve backward
> compatibility.
> Thank you!
--
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: (AXIS2-3710) fixes for backward compatibility
[
https://issues.apache.org/jira/browse/AXIS2-3710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586364#action_12586364
]
Davanum Srinivas commented on AXIS2-3710:
-
Saminda,
Can you please explain How can adding a line here affect your existing code,
especially when you *don't* call AxisServlet 's init?
thanks,
dims
> fixes for backward compatibility
> -
>
> Key: AXIS2-3710
> URL: https://issues.apache.org/jira/browse/AXIS2-3710
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
>Affects Versions: 1.4
> Environment: Any
>Reporter: Saminda Wishwajith Abeyruwan
>Assignee: Davanum Srinivas
>Priority: Blocker
> Fix For: 1.4
>
> Attachments: axisservlet.patch
>
>
> Hi,
> Is there a particular reason to add the line.
> msgContext.setProperty(HTTPCon
> stants.MC_HTTP_SERVLETCONTEXT, getServletContext());
> You will be able to access the context from http servlet request object.
> Beside the prior added line will break some of the existing production code.
> getServletContext() will work properly, IFF the user's servlet inherit the
> init method or if over-rides, it should called the parent init method.
> In AxisServlet, yes it dose over-rides the init method and calls the parent
> init.
> But those of us who have extended AxisServlet to work with, where over-rides
> the init method to intialize the AxisConfiguration the way our production
> system wants does not call the parents (AxisServlet) init method.
> ex:
> public class MyServlet extends AxisServlet {
> ...
>public void init(ServletConfig config) {
> // my way of initializing axisconfiguration and listeners rather using
> parent
> // init, but inheriting parents do* from AxisServlet.
> }
> }
> We used AxisServlet as show above for quite a long time.
> I'm afraid the prior line of code has broken the backward compatibility of
> re-using AxisServlet in production environments.
> Thus, the correct way is to obtain the servlet context from request, rather
> setting the property.
> Thus, I would humbly ask to revert the commit to preserve backward
> compatibility.
> Thank you!
--
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-3709) Improve handler-chains.xml parsing
[ https://issues.apache.org/jira/browse/AXIS2-3709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3709. - Resolution: Fixed trunk = 645366. 1.4 branch = 645368. thanks, dims > Improve handler-chains.xml parsing > -- > > Key: AXIS2-3709 > URL: https://issues.apache.org/jira/browse/AXIS2-3709 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Reporter: Jarek Gawor >Assignee: Jarek Gawor > Attachments: AXIS2-3709.patch > > > Right now the handler-chains.xml file is parsed using JAXB. The problem with > JAXB parsing is that it returns null for an invalid qname. For example, when > the namespace of the qname cannot be resolved. So for example, when the > handler-chains.xml contains an invalid qname for service-name or port-name > and JAXB returns null then the HandlerResolver will treat it as if the > service-name/port-name was not specified at all. And therefore > HandlerResolver will return a handler that it should not. -- 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-3707) httpcore-niossl-LICENSE.txt is no longer needed - should be deleted
[ https://issues.apache.org/jira/browse/AXIS2-3707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3707. - Resolution: Fixed Fixed in svn revision 645105. > httpcore-niossl-LICENSE.txt is no longer needed - should be deleted > --- > > Key: AXIS2-3707 > URL: https://issues.apache.org/jira/browse/AXIS2-3707 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: documentation >Affects Versions: 1.4 >Reporter: Tom Seelbach >Priority: Blocker > Fix For: 1.4 > > > The legal/httpcore-niossl-LICENSE.txt file should be deleted. > As of HTTPCore 4.0 beta1 the httpcore-niossl files were merged into the > httpcore-nio jar. There is no longer a separate httpcore-niossl jar. > See this note in the httpcomponents-core-4.0-beta1.zip RELEASE_NOTES.txt > * HttpCore NIOSSL classes moved to HttpCore NIO. >Contributed by Oleg Kalnichevski -- 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-3706) Methods with multiple faults and wsa actions are not handled correctly
[ https://issues.apache.org/jira/browse/AXIS2-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3706. - Resolution: Fixed fixed in svn revision 645101. thanks, dims > Methods with multiple faults and wsa actions are not handled correctly > -- > > Key: AXIS2-3706 > URL: https://issues.apache.org/jira/browse/AXIS2-3706 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Jarek Gawor > Attachments: AXIS2-3706.patch > > > Methods that throw multiple faults and are annotated with @Action annotation > that defines multiple fault exception -> action mappings are not handled > correctly. That is, the exception -> action mappings are not respected as > specified in the annotation. -- 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: (AXIS2-3702) Backward compatibility, Minor fixes for 1.4 release
[ https://issues.apache.org/jira/browse/AXIS2-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585522#action_12585522 ] Davanum Srinivas commented on AXIS2-3702: - Please go ahead Sanka. (Except for the license header, needs to be on top of the file) -- dims > Backward compatibility, Minor fixes for 1.4 release > --- > > Key: AXIS2-3702 > URL: https://issues.apache.org/jira/browse/AXIS2-3702 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Sanka Samaranayake >Assignee: Sanka Samaranayake > Attachments: AXIS2_3702.patch, AXIS2_3702_R.patch > > > I am proposing the following patch as fix for followings. > (1) Deprecated PolicyInclude class and deprecated all its methods and changed > them to use PolicySubject underlying for backward compatibility reasons. > (2) Fixed ExternalPolicySerializer which serialized wsu:Id attribute of the > Policy object as an unqualified attribute. > (3) Fixed Codegen to use the binding hierarchy when generating, instantiating > stubs. -- 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-3703) Thread safety in XMLFaultCode
[ https://issues.apache.org/jira/browse/AXIS2-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3703. - Resolution: Fixed Fixed in svn revision 644671. > Thread safety in XMLFaultCode > -- > > Key: AXIS2-3703 > URL: https://issues.apache.org/jira/browse/AXIS2-3703 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.4 >Reporter: Jarek Gawor > Fix For: 1.4 > > Attachments: AXIS2-3703.patch > > > The way XMLFaultCode handles custom fault codes by modifying > CUSTOM_SOAP11_ONLY enum value is just not thread safe. I think the > XMLFaultCode should be turned into a class and each custom fault code would > be a separate XMLFaultCode instance. -- 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: (AXIS2-3703) Thread safety in XMLFaultCode
[ https://issues.apache.org/jira/browse/AXIS2-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585474#action_12585474 ] Davanum Srinivas commented on AXIS2-3703: - +1 from me > Thread safety in XMLFaultCode > -- > > Key: AXIS2-3703 > URL: https://issues.apache.org/jira/browse/AXIS2-3703 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.4 >Reporter: Jarek Gawor > Fix For: 1.4 > > Attachments: AXIS2-3703.patch > > > The way XMLFaultCode handles custom fault codes by modifying > CUSTOM_SOAP11_ONLY enum value is just not thread safe. I think the > XMLFaultCode should be turned into a class and each custom fault code would > be a separate XMLFaultCode instance. -- 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: (AXIS2-3702) Backward compatibility, Minor fixes for 1.4 release
[ https://issues.apache.org/jira/browse/AXIS2-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585271#action_12585271 ] Davanum Srinivas commented on AXIS2-3702: - sanka, tooo many whitespace changes to review :( > Backward compatibility, Minor fixes for 1.4 release > --- > > Key: AXIS2-3702 > URL: https://issues.apache.org/jira/browse/AXIS2-3702 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Sanka Samaranayake >Assignee: Sanka Samaranayake > Attachments: AXIS2_3702.patch > > > I am proposing the following patch as fix for followings. > (1) Deprecated PolicyInclude class and deprecated all its methods and changed > them to use PolicySubject underlying for backward compatibility reasons. > (2) Fixed ExternalPolicySerializer which serialized wsu:Id attribute of the > Policy object as an unqualified attribute. > (3) Fixed Codegen to use the binding hierarchy when generating, instantiating > stubs. -- 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: (AXIS2-3275) Add option to enable a wsa:MessageId in repsonse message
[ https://issues.apache.org/jira/browse/AXIS2-3275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585217#action_12585217 ] Davanum Srinivas commented on AXIS2-3275: - Brian, Can we get this in for RC4? Don't really want to "add" new features between RC4 and FINAL. -- dims > 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 >Assignee: Brian DePradine > Fix For: 1.4 > > > 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]
[jira] Updated: (AXIS2-3624) Addressing reference parameter issue
[ https://issues.apache.org/jira/browse/AXIS2-3624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3624: Fix Version/s: (was: 1.4) removing from 1.4 bucket. > Addressing reference parameter issue > > > Key: AXIS2-3624 > URL: https://issues.apache.org/jira/browse/AXIS2-3624 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Addressing >Reporter: Deepal Jayasinghe >Assignee: Deepal Jayasinghe >Priority: Critical > > When I run the test1133 , it seems to me that we are not sending the correct > response > Request > === > http://www.w3.org/2005/08/addressing"; > xmlns:s="http://schemas.xmlsoap.org/soap/envelope/";> s:mustUnderstand="1">http://example.org/action/echoIn > http://www.w3.org/2005/08/addressing/anonymous >xmlns="http://example.org/customer";>Key#123456789 > > http://www.w3.org/2005/08/addressing/anonymous >xmlns="http://example.org/customer";>Fault#123456789 > > urn:uuid:e43eabeb-f0f2-4aec-b2df-63da55e0192d > s:mustUnderstand="1">http://10.10.34.13:8080/axis2/services/WSAddressingCREchoLast >xmlns="http://example.org/echo";>faulttest1133 > > Response > > http://schemas.xmlsoap.org/soap/envelope/";> > http://www.w3.org/2005/08/addressing";> > http://example.org/customer"; > wsa:IsReferenceParameter="true">Key#123456789 > http://example.org/action/echoOut > urn:uuid:e43eabeb-f0f2-4aec-b2df-63da55e0192d > xmlns:ns1="http://example.org/echo";>faulttest1133 > > http://www.w3.org/2002/ws/addr/testsuite/testcases/#test1133 -- 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-3697) WSDL2java does not work correctly if no network or behind Firewall
[ https://issues.apache.org/jira/browse/AXIS2-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3697. - Resolution: Fixed Fixed in woden's pom.xml (svn revision 644424) > WSDL2java does not work correctly if no network or behind Firewall > -- > > Key: AXIS2-3697 > URL: https://issues.apache.org/jira/browse/AXIS2-3697 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: codegen >Affects Versions: 1.4 > Environment: Linux, Windows, Java SDK 1.5 and 1.6 >Reporter: Werner Dittmann >Priority: Critical > Fix For: 1.4 > > > If a systems does have local network only or is behind a firewall WSDL2Java > cannot access the standard *.xsd and *.dtd files. > Digging into the problem: the Woden JAR file bundled with Axis2 1.4 RC3 (and > RC2, RC1) does not contain then necessary > files like *.catalog and the relevant *.xsd and *.dtd files in the META-INF > directory. The Woden AR bundled with Axis2 1.3 > contained these files - thus code generation on an offline system is not > possible. -- 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-3686) Attachments larger than Integer.MAX_VALUE (appr 2.1GB) fails
[ https://issues.apache.org/jira/browse/AXIS2-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3686. - Resolution: Fixed looks like the underlying issue in axiom is already fixed. Please try latest svn of axis2 and axiom thanks, dims > Attachments larger than Integer.MAX_VALUE (appr 2.1GB) fails > > > Key: AXIS2-3686 > URL: https://issues.apache.org/jira/browse/AXIS2-3686 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 >Reporter: Roy Willy Haug > Fix For: 1.4 > > > We have a well working file transfer service that works with files up to > approximately 2.1 GB (probably Integer.MAX_VALUE: 2147483647 bytes?). > When transferring even larger files, Axis2 fails with the following message: > org.apache.axis2.AxisFault: Referenced Attachment not found in the MIME > Message. ContentID:1.urn:uuid:[EMAIL PROTECTED] > What happens is: > The client transfers the complete file to the server. > The server correctly caches the file in the attachmentDIR folder. > The AxisFault is thrown. > The server-side cached file have the exact same byte-length as the file the > client sent, so every byte has been transferred. > I am currently using Windows XP with NTFS and support for files much larger > than 2.1 GB on both sides, Axis2 1.3, Tomcat 5.5.x, document-literal style, > ADB, MTOM and caching to disk. > The DataHandler that is supplied to the client stub is generated like this: > FileDataSource datasource = new FileDataSource(localFile); > dh = new DataHandler(datasource); > > Parts of my Axis2.xml file: > true > false > true > C:/TEMP/da_server_temp/ > 5 > Axis2 mailing list answers to my question: > On Mon, Mar 31, 2008 at 12:01 PM, Andreas Veithen y n e t b e> wrote: > > Roy, > > > > This seems to be a limitation of AXIOM that uses the int type for all > > length variables in the org.apache.axiom.attachments.Attachments class > > and various other classes it depends on. > > > > Regards, > > > > Andreas > > > And: > > From: Thilina Gunarathne [csethil g m a i l co m ] > > Sent: 1. april 2008 00:29 > > To: [EMAIL PROTECTED] > > Subject: Re: MTOM attachments larger than 2.1GB (Integer.MAX_VALUE?) > > > > Please log a Jira with all these details... > > > > I think the fix needs start from the FileAccessor getSize() onwards.. > > > > thanks, > > Thilina -- 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-3685) org.apache.axis2.transport.jms.JMSListener.stop() doesn't shutdown the thread pool created in start() for JMSMessageReceiver
[
https://issues.apache.org/jira/browse/AXIS2-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-3685.
-
Resolution: Fixed
fixed in svn revision 643676.
> org.apache.axis2.transport.jms.JMSListener.stop() doesn't shutdown the thread
> pool created in start() for JMSMessageReceiver
>
>
> Key: AXIS2-3685
> URL: https://issues.apache.org/jira/browse/AXIS2-3685
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: transports
>Affects Versions: 1.3
>Reporter: Raymond Feng
> Attachments: AXIS2-3685.patch
>
>
> In JMSListener.start(), there is a thread pool created for the
> JMSMessageReceiver. But the thread pool is not shutdown in the stop() method.
> As a result, the java process cannot be terminated gracefully unless
> System.exit() is called.
>public void start() throws AxisFault {
> // create thread pool of workers
> ExecutorService workerPool = new ThreadPoolExecutor(
> 1,
> WORKERS_MAX_THREADS, WORKER_KEEP_ALIVE, TIME_UNIT,
> new LinkedBlockingQueue(),
> new org.apache.axis2.util.threadpool.DefaultThreadFactory(
> new ThreadGroup("JMS Worker thread group"),
> "JMSWorker"));
> Iterator iter = connectionFactories.values().iterator();
> while (iter.hasNext()) {
> JMSConnectionFactory conFac = (JMSConnectionFactory) iter.next();
> JMSMessageReceiver msgRcvr =
> new JMSMessageReceiver(conFac, workerPool, configCtx);
--
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-3677) Suggested fixes for 1.4 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3677. - Resolution: Fixed Fixed in svn revision 643008 > Suggested fixes for 1.4 RC3 > --- > > Key: AXIS2-3677 > URL: https://issues.apache.org/jira/browse/AXIS2-3677 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Sanka Samaranayake >Assignee: Sanka Samaranayake >Priority: Critical > Fix For: 1.4 > > Attachments: axis2-3675_and_3677.patch, axis2-3675_and_3677.patch, > suggested-changes-rc2.patch > > > I really like to include the attached patch in rc3 which contains following > fixes > a) Binding Message Level Dispatching -- a minor fix which set the target Axis > binding message in the message context. > b) Minor fix which set policies in the appropriate element of the generated > WSDL based on the Axis Service and Axis Service Binding hierarchy. > c) Support for policy attachments at binding level -- this is a feature that > I would really like to see in Axis2 1.4 release. It allows the user to add > element in the services.xml and specify policies that > applicable bindings. This very useful since it provides a way for the service > authors to specify policies for specific bindings. (Some polices are only > meaningful at binding level (.e.g security) and at the moment this can be > done only by including a WSDL in service archive file) > NOTE: > 1) There are one test failure in JAXWS Integration , and three failures in > the integration modules. I will fix them and submit another patch ASAP -- 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-3675) AxisBindings are created for each and every transport on services deployed
[ https://issues.apache.org/jira/browse/AXIS2-3675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3675. - Resolution: Fixed Fixed in svn revision 643008 > AxisBindings are created for each and every transport on services deployed > -- > > Key: AXIS2-3675 > URL: https://issues.apache.org/jira/browse/AXIS2-3675 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Keith Godwin Chapman >Assignee: Sanka Samaranayake >Priority: Blocker > Fix For: 1.4 > > Attachments: axis2-3675.patch > > > AxisBindings are created for each and every transport on services deployed. > That is a SOAP11, SOAP12 and HTTPBinding is created for each transport. Hence > if both http and https are enabled there will be 6 bindings. This is not > necessary we could have three bindings and both the http and https transport > can share the same binding. > Note. At the moment the HTTPBinding is not shown on the https endpoint. This > should be fixed too. -- 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-3682) MTOM does not work if the file length is zero
[
https://issues.apache.org/jira/browse/AXIS2-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-3682.
-
Resolution: Fixed
Already fixed. Try latest 1.4 RC3 (check email archives for link)
thanks,
dims
> MTOM does not work if the file length is zero
> -
>
> Key: AXIS2-3682
> URL: https://issues.apache.org/jira/browse/AXIS2-3682
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: client-api
>Affects Versions: 1.3
> Environment: axis2 1.3
>Reporter: jason zhang
>
> I have a web service the java method signature is like this
> byte[] getfileContent(String filename);
> My server code is like this
>FileDataSource src=new FileDataSource(file);
> OMFactory fac = OMAbstractFactory.getOMFactory();
> OMNamespace omNs = fac.createOMNamespace(NS, "tns");
> OMElement method = fac.createOMElement("getFileResponse", omNs);
> OMElement value = fac.createOMElement("content", omNs);
> DataHandler dh = new DataHandler(src);
> OMText text = fac.createOMText(dh, true);
> value.addChild(text);
> method.addChild(value);
> return method;
> When the file length is not zero, client-server works fine. If the file is
> zero, the client reports this error
> org.apache.axis2.AxisFault: Referenced Attachment not found in the MIME
> Message. ContentID:1.urn:uuid:[EMAIL PROTECTED]
> at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
> at
> net.sf.webcommand.ws.client.ProgramwsStub.fromOM(ProgramwsStub.java:781)
> at
> net.sf.webcommand.ws.client.ProgramwsStub.getFile(ProgramwsStub.java:175)
> at
> net.sf.webcommand.ws.client.ProgramwsTest.testexecuteProgram(ProgramwsTest.java:102)
> 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:597)
> at junit.framework.TestCase.runTest(TestCase.java:164)
> at junit.framework.TestCase.runBare(TestCase.java:130)
> 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:120)
> at junit.framework.TestSuite.runTest(TestSuite.java:230)
> at junit.framework.TestSuite.run(TestSuite.java:225)
> at
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
> Caused by: org.apache.axiom.om.OMException: Referenced Attachment not found
> in the MIME Message. ContentID:1.urn:uuid:[EMAIL PROTECTED]
> at
> org.apache.axiom.soap.impl.builder.MTOMStAXSOAPModelBuilder.getDataHandler(MTOMStAXSOAPModelBuilder.java:106)
> at
> net.sf.webcommand.ws.client.ProgramwsStub$GetFileResponse$Factory.parse(ProgramwsStub.java:3859)
> at
> net.sf.webcommand.ws.client.ProgramwsStub.fromOM(ProgramwsStub.java:748)
> ... 20 more
> thanks
> -jason
--
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: (AXIS2-3602) NPE in MessageContextBuilder.createFaultEnvelope and SOAP12Constants.SOAP_FAULT_NODE_LOCAL_NAME property set in message context
[ https://issues.apache.org/jira/browse/AXIS2-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583359#action_12583359 ] Davanum Srinivas commented on AXIS2-3602: - Fixed the code to not throw an NPE in svn revision 642592. > NPE in MessageContextBuilder.createFaultEnvelope and > SOAP12Constants.SOAP_FAULT_NODE_LOCAL_NAME property set in message context > --- > > Key: AXIS2-3602 > URL: https://issues.apache.org/jira/browse/AXIS2-3602 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel >Affects Versions: 1.3 > Environment: JRE 1.4.2 >Reporter: Matthias Weber > > Stacktrace: > java.lang.NullPointerException > at > org.apache.axis2.util.MessageContextBuilder.createFaultEnvelope(MessageContextBuilder.java:546) > at > org.apache.axis2.util.MessageContextBuilder.createFaultMessageContext(MessageContextBuilder.java:329) > at > org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:376) > at > org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:366) > at > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:154) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1077) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348) > at > weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:7047) > at > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) > at > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) > at > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3902) > at > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2773) > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) > Seems like fault.getNode() returns null. -- 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-3602) NPE in MessageContextBuilder.createFaultEnvelope and SOAP12Constants.SOAP_FAULT_NODE_LOCAL_NAME property set in message context
[ https://issues.apache.org/jira/browse/AXIS2-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3602. - Resolution: Fixed > NPE in MessageContextBuilder.createFaultEnvelope and > SOAP12Constants.SOAP_FAULT_NODE_LOCAL_NAME property set in message context > --- > > Key: AXIS2-3602 > URL: https://issues.apache.org/jira/browse/AXIS2-3602 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: kernel >Affects Versions: 1.3 > Environment: JRE 1.4.2 >Reporter: Matthias Weber > > Stacktrace: > java.lang.NullPointerException > at > org.apache.axis2.util.MessageContextBuilder.createFaultEnvelope(MessageContextBuilder.java:546) > at > org.apache.axis2.util.MessageContextBuilder.createFaultMessageContext(MessageContextBuilder.java:329) > at > org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:376) > at > org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:366) > at > org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:154) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1077) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465) > at > weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:348) > at > weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:7047) > at > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) > at > weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) > at > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3902) > at > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2773) > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) > Seems like fault.getNode() returns null. -- 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: (AXIS2-3616) Run the JAX-WS 2.1 TCK
[ https://issues.apache.org/jira/browse/AXIS2-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583358#action_12583358 ] Davanum Srinivas commented on AXIS2-3616: - looks like we close the chapter on this...again unless someone steps up. thanks, dims > Run the JAX-WS 2.1 TCK > -- > > Key: AXIS2-3616 > URL: https://issues.apache.org/jira/browse/AXIS2-3616 > Project: Axis 2.0 (Axis2) > Issue Type: Test > Components: jaxws >Affects Versions: 1.4 >Reporter: Brian DePradine >Priority: Critical > > We need to run the JAX-WS 2.1 TCK against our axis2 implementation of JAX-WS > 2.1. -- 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-3616) Run the JAX-WS 2.1 TCK
[ https://issues.apache.org/jira/browse/AXIS2-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3616. - Resolution: Won't Fix > Run the JAX-WS 2.1 TCK > -- > > Key: AXIS2-3616 > URL: https://issues.apache.org/jira/browse/AXIS2-3616 > Project: Axis 2.0 (Axis2) > Issue Type: Test > Components: jaxws >Affects Versions: 1.4 >Reporter: Brian DePradine >Priority: Critical > > We need to run the JAX-WS 2.1 TCK against our axis2 implementation of JAX-WS > 2.1. -- 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-3628) mvn eclipse:eclipse includes all the folders into the build path.
[ https://issues.apache.org/jira/browse/AXIS2-3628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3628. - Resolution: Won't Fix > mvn eclipse:eclipse includes all the folders into the build path. > - > > Key: AXIS2-3628 > URL: https://issues.apache.org/jira/browse/AXIS2-3628 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: samples, build,site >Affects Versions: nightly >Reporter: Michele Mazzucco > > Eclipse does not like nesting -- currently one must manually remove > /test-resources, etc., otherwise eclipse doesn't build the project -- 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: (AXIS2-3654) Client-side role-based mustUnderstand checking for JAXWS Application Handlers
[ https://issues.apache.org/jira/browse/AXIS2-3654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583357#action_12583357 ] Davanum Srinivas commented on AXIS2-3654: - Jeff, Is this something that is needed in 1.4 release? > Client-side role-based mustUnderstand checking for JAXWS Application Handlers > - > > Key: AXIS2-3654 > URL: https://issues.apache.org/jira/browse/AXIS2-3654 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: jaxws >Reporter: Jeff Barrett > > Support for server-side role-based mustUnderstand checking for JAXWS > Application Handlers was added under > https://issues.apache.org/jira/browse/AXIS2-3567. > Similar function is needed for client-side JAXWS Application Handlers. > Note that this requires https://issues.apache.org/jira/browse/AXIS2-3620 to > add client-side mustUnderstand checking based on the application handlers > getHeader(). -- 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-3622) NullPointerExcepetion in AddressingInFaultHandle
[ https://issues.apache.org/jira/browse/AXIS2-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3622: Priority: Critical (was: Blocker) > NullPointerExcepetion in AddressingInFaultHandle > > > Key: AXIS2-3622 > URL: https://issues.apache.org/jira/browse/AXIS2-3622 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Addressing >Affects Versions: 1.3 > Environment: Axis2-1.3,windows,Java >Reporter: T Appasamy >Priority: Critical > > java.lang.NullPointerException > at > org.apache.axis2.handlers.addressing.AddressingInFaultHandler.invoke(AddressingInFaultHandler.java:92) > at org.apache.axis2.engine.Phase.invoke(Phase.java:292) > at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132) > at > org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:336) > at > org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) > at > org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) > at > org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) > at Stub.java:207 -- 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-3659) Wsdl2 code generation falis
[ https://issues.apache.org/jira/browse/AXIS2-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3659: Priority: Critical (was: Blocker) > Wsdl2 code generation falis > --- > > Key: AXIS2-3659 > URL: https://issues.apache.org/jira/browse/AXIS2-3659 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: codegen >Affects Versions: 1.4 > Environment: winxp, jdk15, 1.4-RC1 >Reporter: Charitha Kankanamge >Assignee: Keith Godwin Chapman >Priority: Critical > > I tried to generate code using wsdl2 of default version service. Code gen > fails with the following exception. > C:\Axis2\axis2-1.4\axis2-637511\bin>wsdl2java.bat -uri > http://localhost:8080/axis2/services/Version?wsdl2 -wv 2.0 -o > C:\Axis2\axis2-1.4\axis2-637511\bin\out > Using AXIS2_HOME: C:\Axis2\axis2-1.4\axis2-637511 > Using JAVA_HOME:D:\Program Files\Java\jdk1.5.0_14 > Exception in thread "main" > org.apache.axis2.wsdl.codegen.CodeGenerationException > : Error parsing WSDL > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:159) > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) > Caused by: WSDLException: faultCode=OTHER_ERROR: Fatal error.: > axisversion.sample: java.net.UnknownHostException: axisversion.sample > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177) > at java.net.Socket.connect(Socket.java:520) > at java.net.Socket.connect(Socket.java:470) > at sun.net.NetworkClient.doConnect(NetworkClient.java:157) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:388) > at sun.net.www.http.HttpClient.openServer(HttpClient.java:523) > at sun.net.www.http.HttpClient.(HttpClient.java:231) > at sun.net.www.http.HttpClient.New(HttpClient.java:304) > at sun.net.www.http.HttpClient.New(HttpClient.java:321) > at > sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:813) > at > sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:765) > at > sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:690) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:934) > at java.net.URLConnection.getContent(URLConnection.java:682) > at java.net.URL.getContent(URL.java:1021) > at > org.apache.woden.internal.wsdl20.assertions.Description1001.validate(Description1001.java:28) > at > org.apache.woden.internal.wsdl20.validation.WSDLValidator.checkAssertions(WSDLValidator.java:109) > at > org.apache.woden.internal.wsdl20.validation.WSDLValidator.validate(WSDLValidator.java:77) > at > org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:207) > at > org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:233) > at > org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:268) > at > org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:127) > at > org.apache.axis2.description.WSDL20ToAxisServiceBuilder.readInTheWSDL > File(WSDL20ToAxisServiceBuilder.java:1181) > at > org.apache.axis2.description.WSDL20ToAxisServiceBuilder.(WSDL20ToAxisServiceBuilder.java:151) > at > org.apache.axis2.description.WSDL20ToAllAxisServicesBuilder.(WSDL20ToAllAxisServicesBuilder.java:53) > at > org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:102) > at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) > at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) > at > org.apache.woden.internal.wsdl20.assertions.Description1001.validate(Description1001.java:42) > at > org.apache.woden.internal.wsdl20.validation.WSDLValidator.checkAssertions(WSDLValidator.java:109) > at > org.apache.woden.internal.wsdl20.validation.WSDLValidator.validate(WSDLValidator.java:77) > at > org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:207) > at > org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:233) > at > org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:268) > at > org.apache.woden.internal.DOMWSDLReader.readWSDL(DOMWSDLReader.java:127) > at > org.apache.axis2.description.WSDL20ToAxisServiceBuilder.readInTheWSDL > File(WSDL20ToAxisServiceBuilder.java:1181) > at > org.apache.axis2.description.WSDL20ToAxisServiceBuilder.(WSDL20ToAxisServiceBuilder.java:151) > at > org.apache.axis2.description.WSDL20ToAllAxisServicesBuilder.(WSDL20ToAllAxisServi
[jira] Resolved: (AXIS2-3664) java_first_jaxws sample does not run per README instructions
[ https://issues.apache.org/jira/browse/AXIS2-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas resolved AXIS2-3664. - Resolution: Fixed > java_first_jaxws sample does not run per README instructions > > > Key: AXIS2-3664 > URL: https://issues.apache.org/jira/browse/AXIS2-3664 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Jeff Barrett >Priority: Blocker > Fix For: 1.4 > > > Following the instructions in modules/samples/java_first_jaxws/README does > not get the sample running. I copied java_first_jaxws-1.1.jar and > java_first_jaxws-1.1.war from target to repository/services (note the README > had no detailed instructions on this). After starting the standalone server > java_first_jaxws-1.1 is reported as a fault service. > The README says "Rename the resultant war as your_web_app.war and drop it > into any servlet engine.", which per Dims means an instance of Tomcat (or > such) needs to be running. Or the sample should be changed so it can be run > in the Axis2 server. -- 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: (AXIS2-3664) java_first_jaxws sample does not run per README instructions
[ https://issues.apache.org/jira/browse/AXIS2-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583356#action_12583356 ] Davanum Srinivas commented on AXIS2-3664: - Fixed in svn revision 642590. > java_first_jaxws sample does not run per README instructions > > > Key: AXIS2-3664 > URL: https://issues.apache.org/jira/browse/AXIS2-3664 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Jeff Barrett >Priority: Blocker > Fix For: 1.4 > > > Following the instructions in modules/samples/java_first_jaxws/README does > not get the sample running. I copied java_first_jaxws-1.1.jar and > java_first_jaxws-1.1.war from target to repository/services (note the README > had no detailed instructions on this). After starting the standalone server > java_first_jaxws-1.1 is reported as a fault service. > The README says "Rename the resultant war as your_web_app.war and drop it > into any servlet engine.", which per Dims means an instance of Tomcat (or > such) needs to be running. Or the sample should be changed so it can be run > in the Axis2 server. -- 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-3670) Problem using REUSE_HTTP_CLIENT - Application stalls
[ https://issues.apache.org/jira/browse/AXIS2-3670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3670: Priority: Critical (was: Blocker) > Problem using REUSE_HTTP_CLIENT - Application stalls > > > Key: AXIS2-3670 > URL: https://issues.apache.org/jira/browse/AXIS2-3670 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Affects Versions: 1.3 >Reporter: Alois Reitbauer >Priority: Critical > Attachments: Stalled call vs. executing call.jpg > > > When using REUSE_HTTP_CLIENT on a service client to reuse a http client the > client application hangs after 3 executions. The reason is that it obviously > waits in MultithreadedHttpConnectionManager.getConnectionWithTimeout() -- 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-3664) java_first_jaxws sample does not run per README instructions
[ https://issues.apache.org/jira/browse/AXIS2-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3664: Fix Version/s: 1.4 > java_first_jaxws sample does not run per README instructions > > > Key: AXIS2-3664 > URL: https://issues.apache.org/jira/browse/AXIS2-3664 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Jeff Barrett >Priority: Blocker > Fix For: 1.4 > > > Following the instructions in modules/samples/java_first_jaxws/README does > not get the sample running. I copied java_first_jaxws-1.1.jar and > java_first_jaxws-1.1.war from target to repository/services (note the README > had no detailed instructions on this). After starting the standalone server > java_first_jaxws-1.1 is reported as a fault service. > The README says "Rename the resultant war as your_web_app.war and drop it > into any servlet engine.", which per Dims means an instance of Tomcat (or > such) needs to be running. Or the sample should be changed so it can be run > in the Axis2 server. -- 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-3666) Unable to switch addressing mar on in jaxws-integration tests
[ https://issues.apache.org/jira/browse/AXIS2-3666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3666: Fix Version/s: 1.4 > Unable to switch addressing mar on in jaxws-integration tests > - > > Key: AXIS2-3666 > URL: https://issues.apache.org/jira/browse/AXIS2-3666 > Project: Axis 2.0 (Axis2) > Issue Type: Bug > Components: Addressing >Reporter: Davanum Srinivas >Assignee: Brian DePradine >Priority: Blocker > Fix For: 1.4 > > Attachments: addressing.diff > > > Brian, > I tried switching on addressing mar in the jaxws-integration test suite and i > see lot of failures when i try to enable addressing in > modules/jaxws-integration/test-resources/axis2.xml. Here's the patch i have > so far. > thanks, > dims -- 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-3677) Suggested fixes for 1.4 RC3
[ https://issues.apache.org/jira/browse/AXIS2-3677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davanum Srinivas updated AXIS2-3677: Fix Version/s: 1.4 > Suggested fixes for 1.4 RC3 > --- > > Key: AXIS2-3677 > URL: https://issues.apache.org/jira/browse/AXIS2-3677 > Project: Axis 2.0 (Axis2) > Issue Type: Bug >Reporter: Sanka Samaranayake >Assignee: Sanka Samaranayake >Priority: Critical > Fix For: 1.4 > > Attachments: suggested-changes-rc2.patch > > > I really like to include the attached patch in rc3 which contains following > fixes > a) Binding Message Level Dispatching -- a minor fix which set the target Axis > binding message in the message context. > b) Minor fix which set policies in the appropriate element of the generated > WSDL based on the Axis Service and Axis Service Binding hierarchy. > c) Support for policy attachments at binding level -- this is a feature that > I would really like to see in Axis2 1.4 release. It allows the user to add > element in the services.xml and specify policies that > applicable bindings. This very useful since it provides a way for the service > authors to specify policies for specific bindings. (Some polices are only > meaningful at binding level (.e.g security) and at the moment this can be > done only by including a WSDL in service archive file) > NOTE: > 1) There are one test failure in JAXWS Integration , and three failures in > the integration modules. I will fix them and submit another patch ASAP -- 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]
