You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2006/02/21 17:50:22 UTC
[jira] Created: (AXIS2-458) Axis2 should be able to start a server
without needing the WSDL
Axis2 should be able to start a server without needing the WSDL
---------------------------------------------------------------
Key: AXIS2-458
URL: http://issues.apache.org/jira/browse/AXIS2-458
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: deployment
Versions: 0.95
Reporter: Steve Loughran
Serving up WSDL from an endpoint is an entirely optional feature of SOAP. If I choose not to do it, the endpoint is still valid.
But Axis2 will fail if it cannot get the WSDL. Specifically, if there is no configuration pointing to the WSDL file, it tries to create an AxisService instance using axis-wsdl4j for some reason, with a dependency on both javax.wsdl.*; and com.ibm.wsdl.extensions.soap.*;
Axis2 could maybe warn that there is no WSDL, but it should not be necessary either to have axis-wsdl4j on the classpath for servers, or to serve up WSDL at an endpoint.
This is the stack trace if wsdl4j is absent:
Caused by: java.lang.NoClassDefFoundError: javax/wsdl/extensions/soap/SOAPBinding
at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:84)
at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:109)
at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:228)
at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:373)
at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:196)
at org.apache.axis2.deployment.listener.RepositoryListenerImpl.update(RepositoryListenerImpl.java:197)
at org.apache.axis2.deployment.listener.RepositoryListenerImpl.checkServices(RepositoryListenerImpl.java:147)
at org.apache.axis2.deployment.DeploymentEngine.load(DeploymentEngine.java:514)
at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:59)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:34)
at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:50)
at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:223)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:198)
at org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:220)
at org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:445)
at org.mortbay.jetty.servlet.ServletHandler.start(ServletHandler.java:414)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS2-458) Axis2 should be able to start a
server without needing the WSDL
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-458?page=comments#action_12413865 ]
Davanum Srinivas commented on AXIS2-458:
----------------------------------------
I agree that we have a hard dependency. I am going to review the code just one more time just in case this is a low hanging fruit...before we close this for good.
thanks,
dims
> Axis2 should be able to start a server without needing the WSDL
> ---------------------------------------------------------------
>
> Key: AXIS2-458
> URL: http://issues.apache.org/jira/browse/AXIS2-458
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: deployment
> Versions: 0.95
> Reporter: Steve Loughran
>
> Serving up WSDL from an endpoint is an entirely optional feature of SOAP. If I choose not to do it, the endpoint is still valid.
> But Axis2 will fail if it cannot get the WSDL. Specifically, if there is no configuration pointing to the WSDL file, it tries to create an AxisService instance using axis-wsdl4j for some reason, with a dependency on both javax.wsdl.*; and com.ibm.wsdl.extensions.soap.*;
> Axis2 could maybe warn that there is no WSDL, but it should not be necessary either to have axis-wsdl4j on the classpath for servers, or to serve up WSDL at an endpoint.
> This is the stack trace if wsdl4j is absent:
> Caused by: java.lang.NoClassDefFoundError: javax/wsdl/extensions/soap/SOAPBinding
> at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:84)
> at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:109)
> at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:228)
> at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:373)
> at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:196)
> at org.apache.axis2.deployment.listener.RepositoryListenerImpl.update(RepositoryListenerImpl.java:197)
> at org.apache.axis2.deployment.listener.RepositoryListenerImpl.checkServices(RepositoryListenerImpl.java:147)
> at org.apache.axis2.deployment.DeploymentEngine.load(DeploymentEngine.java:514)
> at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:59)
> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:34)
> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:50)
> at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:223)
> at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:198)
> at org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:220)
> at org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:445)
> at org.mortbay.jetty.servlet.ServletHandler.start(ServletHandler.java:414)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-458) Axis2 should be able to start a server
without needing the WSDL
Posted by "Ajith Harshana Ranabahu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-458?page=all ]
Ajith Harshana Ranabahu resolved AXIS2-458:
-------------------------------------------
Resolution: Won't Fix
We have taken a hard dependancy on wsdl4j and even if there is no WSDL processing the dependancy cannot be removed
> Axis2 should be able to start a server without needing the WSDL
> ---------------------------------------------------------------
>
> Key: AXIS2-458
> URL: http://issues.apache.org/jira/browse/AXIS2-458
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: deployment
> Versions: 0.95
> Reporter: Steve Loughran
>
> Serving up WSDL from an endpoint is an entirely optional feature of SOAP. If I choose not to do it, the endpoint is still valid.
> But Axis2 will fail if it cannot get the WSDL. Specifically, if there is no configuration pointing to the WSDL file, it tries to create an AxisService instance using axis-wsdl4j for some reason, with a dependency on both javax.wsdl.*; and com.ibm.wsdl.extensions.soap.*;
> Axis2 could maybe warn that there is no WSDL, but it should not be necessary either to have axis-wsdl4j on the classpath for servers, or to serve up WSDL at an endpoint.
> This is the stack trace if wsdl4j is absent:
> Caused by: java.lang.NoClassDefFoundError: javax/wsdl/extensions/soap/SOAPBinding
> at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:84)
> at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:109)
> at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:228)
> at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:373)
> at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:196)
> at org.apache.axis2.deployment.listener.RepositoryListenerImpl.update(RepositoryListenerImpl.java:197)
> at org.apache.axis2.deployment.listener.RepositoryListenerImpl.checkServices(RepositoryListenerImpl.java:147)
> at org.apache.axis2.deployment.DeploymentEngine.load(DeploymentEngine.java:514)
> at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:59)
> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:34)
> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:50)
> at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:223)
> at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:198)
> at org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:220)
> at org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:445)
> at org.mortbay.jetty.servlet.ServletHandler.start(ServletHandler.java:414)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-458) Axis2 should be able to start a
server without needing the WSDL
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/AXIS2-458?page=comments#action_12413870 ]
Davanum Srinivas commented on AXIS2-458:
----------------------------------------
the WSDLLocator makes things worse. let's just leave it for now.
thanks,
dims
> Axis2 should be able to start a server without needing the WSDL
> ---------------------------------------------------------------
>
> Key: AXIS2-458
> URL: http://issues.apache.org/jira/browse/AXIS2-458
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: deployment
> Versions: 0.95
> Reporter: Steve Loughran
>
> Serving up WSDL from an endpoint is an entirely optional feature of SOAP. If I choose not to do it, the endpoint is still valid.
> But Axis2 will fail if it cannot get the WSDL. Specifically, if there is no configuration pointing to the WSDL file, it tries to create an AxisService instance using axis-wsdl4j for some reason, with a dependency on both javax.wsdl.*; and com.ibm.wsdl.extensions.soap.*;
> Axis2 could maybe warn that there is no WSDL, but it should not be necessary either to have axis-wsdl4j on the classpath for servers, or to serve up WSDL at an endpoint.
> This is the stack trace if wsdl4j is absent:
> Caused by: java.lang.NoClassDefFoundError: javax/wsdl/extensions/soap/SOAPBinding
> at org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:84)
> at org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:109)
> at org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:228)
> at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:373)
> at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:196)
> at org.apache.axis2.deployment.listener.RepositoryListenerImpl.update(RepositoryListenerImpl.java:197)
> at org.apache.axis2.deployment.listener.RepositoryListenerImpl.checkServices(RepositoryListenerImpl.java:147)
> at org.apache.axis2.deployment.DeploymentEngine.load(DeploymentEngine.java:514)
> at org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:59)
> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:34)
> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:50)
> at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:223)
> at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:198)
> at org.mortbay.jetty.servlet.ServletHolder.start(ServletHolder.java:220)
> at org.mortbay.jetty.servlet.ServletHandler.initializeServlets(ServletHandler.java:445)
> at org.mortbay.jetty.servlet.ServletHandler.start(ServletHandler.java:414)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org