You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Sam Ruby <ru...@apache.org> on 2002/09/24 23:01:19 UTC
[VOTE] Axis 1.0 release plan
BACKGROUND:
Many users have requested a v1.0 so that they can work from a relatively
stable base. Some users have even remained on Apache SOAP until v1.0 of
Axis is available. Now Axis has surpassed Apache SOAP in function,
performance, and interoperability and, in particular, has passed Sun's
JAX-RPC and SAAJ compliance tests, we are planning to ship v1.0
essentially as it currently stands.
However, this is far from the end of the road for Axis. There is more
documentation to be written; the SOAP v1.2 spec. needs to be tracked to
completion and implemented fully; major functional enhancements and
architectural improvements are being considered. We particularly
encourage you to submit improvements to the documentation, however large
or small and in any format, to axis-dev@xml.apache.org.
PLAN:
We have achieved nearly a steady state whereby the number of fixes
targeting a 1.0 release seems to remain constant at 12 +/- 6. At the
bottom of this note is the current list. The oldest bug was reported
against a nightly build in June, the newest was opened yesterday. In
order for us to ship, we need to look at this differently, and not aim
for perfection. Once we get over the hurdle of shipping this release,
maintenance and followon releases should come more quickly. The main
thing to focus on is to get control over the rate at which new bugs are
injected.
This does not imply a moratorium on the opening of new bugs that can be
considered as candidate for release. Instead, the focus needs to shift
from fixing problems that we have lived with for months to fixing and
eliminating regressions that can be, and are being, introduced late in
the cycle.
Therefore, the following release plan is proposed for Axis 1.0:
Code Freeze / Tag Date - Wed, 25 Sept, 2002, early a.m.
Target for release - first week in October
Release Manager - Sam Ruby
Release Announcement -
announcements@xml.apache.org
axis-dev@xml.apache.org
axis-users@xml.apache.org
soap-dev@xml.apache.org
soap-users@xml.apache.org
soapbuilders@yahoogroups.com
Once release freeze is achieved, inclusion of fixes into the release
requires consensus of active axis committers. Deferring of a fix
requires simple majority.
Fixes are to continue to be made on the "HEAD" of the release. Once
there is consensus that a particular fix is to be included in the
release, I'll merge it into the branch. In order to make this as smooth
and as painless a process as possible for the release manager, I'll ask
that committers show restraint in committing unrelated fixes to the HEAD
during this time in areas of the code that might interfere with the
merge process.
RELEASE CRITERIA:
* all Axis unit and functional tests pass.
* SAAJ and JAXRPC TCKs pass.
* All fixes targeted to 1.0 are either fixed or reassigned.
* Confirmation that the released version works on all servlet containers
for which there is a volunteer, including at a minimum Tomcat, JRun, and
WebSphere.
CURRENT BUG LIST:
ID Sev Pri Owner State Summary
10585 Blo Hig axis-dev REOP No serializer error is generated
12636 Blo Oth axis-dev REOP Axis rc1 support for multiple output
12886 Blo Hig gdaniels NEW Axis serializes when it shouldn't
12923 Blo Hig axis-dev NEW Message Services don't support muliple
12753 Cri Oth axis-dev REOP problem while deserializing output
12833 Cri Hig tomj NEW Axis clients fail to extract the value
12367 Maj Oth axis-dev NEW re: java2wsdl fails when parameter
12685 Maj Oth axis-dev NEW RC1 - Setting "PROP_DOMULTIREFS" looses
12758 Maj Oth axis-dev NEW Deserialization of complex classes
10365 Nor Hig tomj NEW If input/output names don't match,
10944 Nor Oth gdaniels NEW Soap envelope cleared after onFault() in
11595 Nor Oth gdaniels NEW AxisServlet ignores wsdd: "service"
12803 Nor Oth axis-dev NEW (de)serialization of an object which
12867 Nor Oth scheu NEW array of bean_b inside bean_a
- Sam Ruby
Re: [VOTE] Axis 1.0 release plan
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
+1
----- Original Message -----
From: "Sam Ruby" <ru...@apache.org>
To: <ax...@xml.apache.org>
Cc: <ax...@xml.apache.org>
Sent: Wednesday, September 25, 2002 3:01 AM
Subject: [VOTE] Axis 1.0 release plan
> BACKGROUND:
>
> Many users have requested a v1.0 so that they can work from a relatively
> stable base. Some users have even remained on Apache SOAP until v1.0 of
> Axis is available. Now Axis has surpassed Apache SOAP in function,
> performance, and interoperability and, in particular, has passed Sun's
> JAX-RPC and SAAJ compliance tests, we are planning to ship v1.0
> essentially as it currently stands.
>
> However, this is far from the end of the road for Axis. There is more
> documentation to be written; the SOAP v1.2 spec. needs to be tracked to
> completion and implemented fully; major functional enhancements and
> architectural improvements are being considered. We particularly
> encourage you to submit improvements to the documentation, however large
> or small and in any format, to axis-dev@xml.apache.org.
>
> PLAN:
>
> We have achieved nearly a steady state whereby the number of fixes
> targeting a 1.0 release seems to remain constant at 12 +/- 6. At the
> bottom of this note is the current list. The oldest bug was reported
> against a nightly build in June, the newest was opened yesterday. In
> order for us to ship, we need to look at this differently, and not aim
> for perfection. Once we get over the hurdle of shipping this release,
> maintenance and followon releases should come more quickly. The main
> thing to focus on is to get control over the rate at which new bugs are
> injected.
>
> This does not imply a moratorium on the opening of new bugs that can be
> considered as candidate for release. Instead, the focus needs to shift
> from fixing problems that we have lived with for months to fixing and
> eliminating regressions that can be, and are being, introduced late in
> the cycle.
>
> Therefore, the following release plan is proposed for Axis 1.0:
>
> Code Freeze / Tag Date - Wed, 25 Sept, 2002, early a.m.
> Target for release - first week in October
> Release Manager - Sam Ruby
> Release Announcement -
> announcements@xml.apache.org
> axis-dev@xml.apache.org
> axis-users@xml.apache.org
> soap-dev@xml.apache.org
> soap-users@xml.apache.org
> soapbuilders@yahoogroups.com
>
> Once release freeze is achieved, inclusion of fixes into the release
> requires consensus of active axis committers. Deferring of a fix
> requires simple majority.
>
> Fixes are to continue to be made on the "HEAD" of the release. Once
> there is consensus that a particular fix is to be included in the
> release, I'll merge it into the branch. In order to make this as smooth
> and as painless a process as possible for the release manager, I'll ask
> that committers show restraint in committing unrelated fixes to the HEAD
> during this time in areas of the code that might interfere with the
> merge process.
>
> RELEASE CRITERIA:
>
> * all Axis unit and functional tests pass.
>
> * SAAJ and JAXRPC TCKs pass.
>
> * All fixes targeted to 1.0 are either fixed or reassigned.
>
> * Confirmation that the released version works on all servlet containers
> for which there is a volunteer, including at a minimum Tomcat, JRun, and
> WebSphere.
>
> CURRENT BUG LIST:
>
> ID Sev Pri Owner State Summary
> 10585 Blo Hig axis-dev REOP No serializer error is generated
> 12636 Blo Oth axis-dev REOP Axis rc1 support for multiple output
> 12886 Blo Hig gdaniels NEW Axis serializes when it shouldn't
> 12923 Blo Hig axis-dev NEW Message Services don't support muliple
> 12753 Cri Oth axis-dev REOP problem while deserializing output
> 12833 Cri Hig tomj NEW Axis clients fail to extract the value
> 12367 Maj Oth axis-dev NEW re: java2wsdl fails when parameter
> 12685 Maj Oth axis-dev NEW RC1 - Setting "PROP_DOMULTIREFS" looses
> 12758 Maj Oth axis-dev NEW Deserialization of complex classes
> 10365 Nor Hig tomj NEW If input/output names don't match,
> 10944 Nor Oth gdaniels NEW Soap envelope cleared after onFault() in
> 11595 Nor Oth gdaniels NEW AxisServlet ignores wsdd: "service"
> 12803 Nor Oth axis-dev NEW (de)serialization of an object which
> 12867 Nor Oth scheu NEW array of bean_b inside bean_a
>
> - Sam Ruby
Re: [VOTE] Axis 1.0 release plan - addendum
Posted by Sam Ruby <ru...@apache.org>.
Not part of the release plan per se, but I am going to see what I can do
to get coverage of this event on Slashdot.
Also, I would greatly appreciate it if someone can help me reproduce
success for the JAX RPC TCK by the time 1.0 ships. If for some reason
this can't be done by the end of next week, the following week I plan to
be in the boston area...
- Sam Ruby
Re: [VOTE] Axis 1.0 release plan
Posted by David Chappell <ch...@sonicsoftware.com>.
+1
Dave
Sam Ruby wrote:
>
> BACKGROUND:
>
> Many users have requested a v1.0 so that they can work from a relatively
> stable base. Some users have even remained on Apache SOAP until v1.0 of
> Axis is available. Now Axis has surpassed Apache SOAP in function,
> performance, and interoperability and, in particular, has passed Sun's
> JAX-RPC and SAAJ compliance tests, we are planning to ship v1.0
> essentially as it currently stands.
>
> However, this is far from the end of the road for Axis. There is more
> documentation to be written; the SOAP v1.2 spec. needs to be tracked to
> completion and implemented fully; major functional enhancements and
> architectural improvements are being considered. We particularly
> encourage you to submit improvements to the documentation, however large
> or small and in any format, to axis-dev@xml.apache.org.
>
> PLAN:
>
> We have achieved nearly a steady state whereby the number of fixes
> targeting a 1.0 release seems to remain constant at 12 +/- 6. At the
> bottom of this note is the current list. The oldest bug was reported
> against a nightly build in June, the newest was opened yesterday. In
> order for us to ship, we need to look at this differently, and not aim
> for perfection. Once we get over the hurdle of shipping this release,
> maintenance and followon releases should come more quickly. The main
> thing to focus on is to get control over the rate at which new bugs are
> injected.
>
> This does not imply a moratorium on the opening of new bugs that can be
> considered as candidate for release. Instead, the focus needs to shift
> from fixing problems that we have lived with for months to fixing and
> eliminating regressions that can be, and are being, introduced late in
> the cycle.
>
> Therefore, the following release plan is proposed for Axis 1.0:
>
> Code Freeze / Tag Date - Wed, 25 Sept, 2002, early a.m.
> Target for release - first week in October
> Release Manager - Sam Ruby
> Release Announcement -
> announcements@xml.apache.org
> axis-dev@xml.apache.org
> axis-users@xml.apache.org
> soap-dev@xml.apache.org
> soap-users@xml.apache.org
> soapbuilders@yahoogroups.com
>
> Once release freeze is achieved, inclusion of fixes into the release
> requires consensus of active axis committers. Deferring of a fix
> requires simple majority.
>
> Fixes are to continue to be made on the "HEAD" of the release. Once
> there is consensus that a particular fix is to be included in the
> release, I'll merge it into the branch. In order to make this as smooth
> and as painless a process as possible for the release manager, I'll ask
> that committers show restraint in committing unrelated fixes to the HEAD
> during this time in areas of the code that might interfere with the
> merge process.
>
> RELEASE CRITERIA:
>
> * all Axis unit and functional tests pass.
>
> * SAAJ and JAXRPC TCKs pass.
>
> * All fixes targeted to 1.0 are either fixed or reassigned.
>
> * Confirmation that the released version works on all servlet containers
> for which there is a volunteer, including at a minimum Tomcat, JRun, and
> WebSphere.
>
> CURRENT BUG LIST:
>
> ID Sev Pri Owner State Summary
> 10585 Blo Hig axis-dev REOP No serializer error is generated
> 12636 Blo Oth axis-dev REOP Axis rc1 support for multiple output
> 12886 Blo Hig gdaniels NEW Axis serializes when it shouldn't
> 12923 Blo Hig axis-dev NEW Message Services don't support muliple
> 12753 Cri Oth axis-dev REOP problem while deserializing output
> 12833 Cri Hig tomj NEW Axis clients fail to extract the value
> 12367 Maj Oth axis-dev NEW re: java2wsdl fails when parameter
> 12685 Maj Oth axis-dev NEW RC1 - Setting "PROP_DOMULTIREFS" looses
> 12758 Maj Oth axis-dev NEW Deserialization of complex classes
> 10365 Nor Hig tomj NEW If input/output names don't match,
> 10944 Nor Oth gdaniels NEW Soap envelope cleared after onFault() in
> 11595 Nor Oth gdaniels NEW AxisServlet ignores wsdd: "service"
> 12803 Nor Oth axis-dev NEW (de)serialization of an object which
> 12867 Nor Oth scheu NEW array of bean_b inside bean_a
>
> - Sam Ruby
--
Sonic Software - Backbone of the Extended Enterprise
--
David Chappell <ch...@sonicsoftware.com> Office: (781)999-7099
Mobile: (617)510-6566
Vice President and Chief Technology Evangelist, Sonic Software
co-author,"Java Web Services", (O'Reilly 2002)
"The Java Message Service", (O'Reilly 2000)
"Professional ebXML Foundations", (Wrox 2001)
--
Re: [VOTE] Axis 1.0 release plan
Posted by Davanum Srinivas <di...@yahoo.com>.
+1 from me.
Thanks,
dims
--- Sam Ruby <ru...@apache.org> wrote:
> BACKGROUND:
>
> Many users have requested a v1.0 so that they can work from a relatively
> stable base. Some users have even remained on Apache SOAP until v1.0 of
> Axis is available. Now Axis has surpassed Apache SOAP in function,
> performance, and interoperability and, in particular, has passed Sun's
> JAX-RPC and SAAJ compliance tests, we are planning to ship v1.0
> essentially as it currently stands.
>
> However, this is far from the end of the road for Axis. There is more
> documentation to be written; the SOAP v1.2 spec. needs to be tracked to
> completion and implemented fully; major functional enhancements and
> architectural improvements are being considered. We particularly
> encourage you to submit improvements to the documentation, however large
> or small and in any format, to axis-dev@xml.apache.org.
>
> PLAN:
>
> We have achieved nearly a steady state whereby the number of fixes
> targeting a 1.0 release seems to remain constant at 12 +/- 6. At the
> bottom of this note is the current list. The oldest bug was reported
> against a nightly build in June, the newest was opened yesterday. In
> order for us to ship, we need to look at this differently, and not aim
> for perfection. Once we get over the hurdle of shipping this release,
> maintenance and followon releases should come more quickly. The main
> thing to focus on is to get control over the rate at which new bugs are
> injected.
>
> This does not imply a moratorium on the opening of new bugs that can be
> considered as candidate for release. Instead, the focus needs to shift
> from fixing problems that we have lived with for months to fixing and
> eliminating regressions that can be, and are being, introduced late in
> the cycle.
>
> Therefore, the following release plan is proposed for Axis 1.0:
>
> Code Freeze / Tag Date - Wed, 25 Sept, 2002, early a.m.
> Target for release - first week in October
> Release Manager - Sam Ruby
> Release Announcement -
> announcements@xml.apache.org
> axis-dev@xml.apache.org
> axis-users@xml.apache.org
> soap-dev@xml.apache.org
> soap-users@xml.apache.org
> soapbuilders@yahoogroups.com
>
> Once release freeze is achieved, inclusion of fixes into the release
> requires consensus of active axis committers. Deferring of a fix
> requires simple majority.
>
> Fixes are to continue to be made on the "HEAD" of the release. Once
> there is consensus that a particular fix is to be included in the
> release, I'll merge it into the branch. In order to make this as smooth
> and as painless a process as possible for the release manager, I'll ask
> that committers show restraint in committing unrelated fixes to the HEAD
> during this time in areas of the code that might interfere with the
> merge process.
>
> RELEASE CRITERIA:
>
> * all Axis unit and functional tests pass.
>
> * SAAJ and JAXRPC TCKs pass.
>
> * All fixes targeted to 1.0 are either fixed or reassigned.
>
> * Confirmation that the released version works on all servlet containers
> for which there is a volunteer, including at a minimum Tomcat, JRun, and
> WebSphere.
>
> CURRENT BUG LIST:
>
> ID Sev Pri Owner State Summary
> 10585 Blo Hig axis-dev REOP No serializer error is generated
> 12636 Blo Oth axis-dev REOP Axis rc1 support for multiple output
> 12886 Blo Hig gdaniels NEW Axis serializes when it shouldn't
> 12923 Blo Hig axis-dev NEW Message Services don't support muliple
> 12753 Cri Oth axis-dev REOP problem while deserializing output
> 12833 Cri Hig tomj NEW Axis clients fail to extract the value
> 12367 Maj Oth axis-dev NEW re: java2wsdl fails when parameter
> 12685 Maj Oth axis-dev NEW RC1 - Setting "PROP_DOMULTIREFS" looses
> 12758 Maj Oth axis-dev NEW Deserialization of complex classes
> 10365 Nor Hig tomj NEW If input/output names don't match,
> 10944 Nor Oth gdaniels NEW Soap envelope cleared after onFault() in
> 11595 Nor Oth gdaniels NEW AxisServlet ignores wsdd: "service"
> 12803 Nor Oth axis-dev NEW (de)serialization of an object which
> 12867 Nor Oth scheu NEW array of bean_b inside bean_a
>
> - Sam Ruby
>
=====
Davanum Srinivas - http://xml.apache.org/~dims/
__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com
Re: [VOTE] Axis 1.0 release plan
Posted by Jinghua Gu <eg...@cisco.com>.
Hi All,
It is really painful to try each new version of AXIS. Does anybody has
successful experience
in deploy AdminService in newest AXIS 1.0RC1? I have AXIS validation page
running correctly
and all jar files are in my class path. But when I tried to deploy
AdminService, using command:
java org.apache.axis.client.AdminClient
-lhttp://localhost:8080/axis/services/AdminService deploy.wsdd
I Always get (500)internal server error. I am using Tomcat4.0.3.
- Exception:
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultString: (500)Internal Server Error
faultActor: null
faultDetail:
null: return code: 500
<html><head><title>Apache Tomcat/4.0.3 - Error
report</title><STYLE><!--H1{font-family :
sans-serif,Arial,Tahoma;color : white;background-color : #0086b2;}
BODY{font-family : sans-serif,Arial,Tahoma;color : black;background-color :
white;} B{color : white;background-color : #0086b2;} HR{color : #0086b2;}
--></STYLE> </head><body><h1>Apache Tomcat/4.0.3
- HTTP Status 500 - Internal Server Error</h1><HR
size="1" noshade><p><b>type</b> Exception
report</p><p><b>message</b> <u>Internal
Server Error</u></p><p><b>description</b>
<u>The server encountered an internal error (Internal Server Error)
that prevented it from fulfilling this
request.</u></p><p><b>exception</b>
<pre>javax.servlet.ServletException: Servlet execution threw an exception
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
at java.lang.Thread.run(Thread.java:536)
</pre></p><p><b>root cause</b>
<pre>java.lang.NoClassDefFoundError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:207)
at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:179)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:171)
at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:112)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableItem.java:391)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:333)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:312)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:298)
at
org.apache.axis.deployment.wsdd.WSDDDeployment.getHandler(WSDDDeployment.java:445)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:314)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:298)
at
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:168)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:312)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:298)
at
org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewInstance(WSDDTargetedChain.java:190)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:312)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:298)
at
org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport(WSDDDeployment.java:460)
at
org.apache.axis.configuration.FileProvider.getTransport(FileProvider.java:282)
at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:283)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:271)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:558)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:335)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
at java.lang.Thread.run(Thread.java:536)
</pre></p><HR size="1"
noshade></body></html>
(500)Internal Server Error
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:628)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:129)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:153)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:123)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:181)
at org.apache.axis.client.Call.invokeEngine(Call.java:2084)
at org.apache.axis.client.Call.invoke(Call.java:2073)
at org.apache.axis.client.Call.invoke(Call.java:1287)
at org.apache.axis.client.AdminClient.process(AdminClient.java:318)
at org.apache.axis.client.AdminClient.process(AdminClient.java:297)
at org.apache.axis.client.AdminClient.process(AdminClient.java:304)
at org.apache.axis.client.AdminClient.process(AdminClient.java:255)
at org.apache.axis.client.AdminClient.main(AdminClient.java:340)
Re: [VOTE] Axis 1.0 release plan
Posted by Jinghua Gu <eg...@cisco.com>.
Hi All,
It is really painful to try each new version of AXIS. Does anybody has
successful experience
in deploy AdminService in newest AXIS 1.0RC1? I have AXIS validation page
running correctly
and all jar files are in my class path. But when I tried to deploy
AdminService, using command:
java org.apache.axis.client.AdminClient
-lhttp://localhost:8080/axis/services/AdminService deploy.wsdd
I Always get (500)internal server error. I am using Tomcat4.0.3.
- Exception:
AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultString: (500)Internal Server Error
faultActor: null
faultDetail:
null: return code: 500
<html><head><title>Apache Tomcat/4.0.3 - Error
report</title><STYLE><!--H1{font-family :
sans-serif,Arial,Tahoma;color : white;background-color : #0086b2;}
BODY{font-family : sans-serif,Arial,Tahoma;color : black;background-color :
white;} B{color : white;background-color : #0086b2;} HR{color : #0086b2;}
--></STYLE> </head><body><h1>Apache Tomcat/4.0.3
- HTTP Status 500 - Internal Server Error</h1><HR
size="1" noshade><p><b>type</b> Exception
report</p><p><b>message</b> <u>Internal
Server Error</u></p><p><b>description</b>
<u>The server encountered an internal error (Internal Server Error)
that prevented it from fulfilling this
request.</u></p><p><b>exception</b>
<pre>javax.servlet.ServletException: Servlet execution threw an exception
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
at java.lang.Thread.run(Thread.java:536)
</pre></p><p><b>root cause</b>
<pre>java.lang.NoClassDefFoundError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:207)
at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:179)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:171)
at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:112)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableItem.java:391)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:333)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:312)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:298)
at
org.apache.axis.deployment.wsdd.WSDDDeployment.getHandler(WSDDDeployment.java:445)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:314)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:298)
at
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:168)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:312)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:298)
at
org.apache.axis.deployment.wsdd.WSDDTargetedChain.makeNewInstance(WSDDTargetedChain.java:190)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:312)
at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:298)
at
org.apache.axis.deployment.wsdd.WSDDDeployment.getTransport(WSDDDeployment.java:460)
at
org.apache.axis.configuration.FileProvider.getTransport(FileProvider.java:282)
at org.apache.axis.AxisEngine.getTransport(AxisEngine.java:283)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:271)
at
org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:558)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at
org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:335)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
at java.lang.Thread.run(Thread.java:536)
</pre></p><HR size="1"
noshade></body></html>
(500)Internal Server Error
at
org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:628)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:129)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:153)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:123)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:181)
at org.apache.axis.client.Call.invokeEngine(Call.java:2084)
at org.apache.axis.client.Call.invoke(Call.java:2073)
at org.apache.axis.client.Call.invoke(Call.java:1287)
at org.apache.axis.client.AdminClient.process(AdminClient.java:318)
at org.apache.axis.client.AdminClient.process(AdminClient.java:297)
at org.apache.axis.client.AdminClient.process(AdminClient.java:304)
at org.apache.axis.client.AdminClient.process(AdminClient.java:255)
at org.apache.axis.client.AdminClient.main(AdminClient.java:340)
Re: [VOTE] Axis 1.0 release plan
Posted by Richard Sitze <rs...@us.ibm.com>.
+1
*******************************************
Richard A. Sitze
IBM WebSphere WebServices Development
Sam Ruby <ru...@apache.org>
09/24/2002 04:01 PM
Please respond to axis-dev
To: axis-dev@xml.apache.org
cc: axis-user@xml.apache.org
Subject: [VOTE] Axis 1.0 release plan
BACKGROUND:
Many users have requested a v1.0 so that they can work from a relatively
stable base. Some users have even remained on Apache SOAP until v1.0 of
Axis is available. Now Axis has surpassed Apache SOAP in function,
performance, and interoperability and, in particular, has passed Sun's
JAX-RPC and SAAJ compliance tests, we are planning to ship v1.0
essentially as it currently stands.
However, this is far from the end of the road for Axis. There is more
documentation to be written; the SOAP v1.2 spec. needs to be tracked to
completion and implemented fully; major functional enhancements and
architectural improvements are being considered. We particularly
encourage you to submit improvements to the documentation, however large
or small and in any format, to axis-dev@xml.apache.org.
PLAN:
We have achieved nearly a steady state whereby the number of fixes
targeting a 1.0 release seems to remain constant at 12 +/- 6. At the
bottom of this note is the current list. The oldest bug was reported
against a nightly build in June, the newest was opened yesterday. In
order for us to ship, we need to look at this differently, and not aim
for perfection. Once we get over the hurdle of shipping this release,
maintenance and followon releases should come more quickly. The main
thing to focus on is to get control over the rate at which new bugs are
injected.
This does not imply a moratorium on the opening of new bugs that can be
considered as candidate for release. Instead, the focus needs to shift
from fixing problems that we have lived with for months to fixing and
eliminating regressions that can be, and are being, introduced late in
the cycle.
Therefore, the following release plan is proposed for Axis 1.0:
Code Freeze / Tag Date - Wed, 25 Sept, 2002, early a.m.
Target for release - first week in October
Release Manager - Sam Ruby
Release Announcement -
announcements@xml.apache.org
axis-dev@xml.apache.org
axis-users@xml.apache.org
soap-dev@xml.apache.org
soap-users@xml.apache.org
soapbuilders@yahoogroups.com
Once release freeze is achieved, inclusion of fixes into the release
requires consensus of active axis committers. Deferring of a fix
requires simple majority.
Fixes are to continue to be made on the "HEAD" of the release. Once
there is consensus that a particular fix is to be included in the
release, I'll merge it into the branch. In order to make this as smooth
and as painless a process as possible for the release manager, I'll ask
that committers show restraint in committing unrelated fixes to the HEAD
during this time in areas of the code that might interfere with the
merge process.
RELEASE CRITERIA:
* all Axis unit and functional tests pass.
* SAAJ and JAXRPC TCKs pass.
* All fixes targeted to 1.0 are either fixed or reassigned.
* Confirmation that the released version works on all servlet containers
for which there is a volunteer, including at a minimum Tomcat, JRun, and
WebSphere.
CURRENT BUG LIST:
ID Sev Pri Owner State Summary
10585 Blo Hig axis-dev REOP No serializer error is generated
12636 Blo Oth axis-dev REOP Axis rc1 support for multiple output
12886 Blo Hig gdaniels NEW Axis serializes when it shouldn't
12923 Blo Hig axis-dev NEW Message Services don't support muliple
12753 Cri Oth axis-dev REOP problem while deserializing output
12833 Cri Hig tomj NEW Axis clients fail to extract the value
12367 Maj Oth axis-dev NEW re: java2wsdl fails when parameter
12685 Maj Oth axis-dev NEW RC1 - Setting "PROP_DOMULTIREFS" looses
12758 Maj Oth axis-dev NEW Deserialization of complex classes
10365 Nor Hig tomj NEW If input/output names don't match,
10944 Nor Oth gdaniels NEW Soap envelope cleared after onFault() in
11595 Nor Oth gdaniels NEW AxisServlet ignores wsdd: "service"
12803 Nor Oth axis-dev NEW (de)serialization of an object which
12867 Nor Oth scheu NEW array of bean_b inside bean_a
- Sam Ruby