"org.apache.axis2.spring.SpringServiceTest$1" That class doesn't even exist. I'm not sure what you are running, but it's definitely not genuine Axis2 source code.
Andreas On Tue, May 23, 2017 at 7:11 PM, Martin Gainty <[email protected]> wrote: > maven-surefire-plugin classloader issues when running SpringServiceTest > > > ------------------------------------------------------------------------------- > Test set: org.apache.axis2.spring.SpringServiceTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.643 sec > <<< FAILURE! > org.apache.axis2.spring.SpringServiceTest(org.apache.axis2.spring.SpringServiceTest$1) > Time elapsed: 0 sec <<< ERROR! > org.apache.axiom.om.OMException: No meta factory found for feature > 'default'; this usually means that axiom-impl.jar is not in the classpath or > that the META-INF/axiom.xml resource can't be read > at > org.apache.axiom.om.OMAbstractFactory.getMetaFactory(OMAbstractFactory.java:180 > > I'll satisfy both conditions and report back > Any progress on your end? > > Thanks > > Martin > ______________________________________________ > > > ________________________________ > From: Martin Gainty <[email protected]> > Sent: Monday, May 15, 2017 9:06 AM > > To: [email protected] > Subject: Re: Axis2 Webservice WSDL not accessible [I] > > > > > i am not sure about axis2-1.6.2 integration with spring-4.3.2? > > > if you run SpringServiceTest from your integration folder if you dont see > failures/errors axis2-1.6.2 *should* integrate with spring-4.3.2 > > > in any event I will test SpringServiceTest here to verify > > please keep me apprised > > Martin > ______________________________________________ > > > > > ________________________________ > From: Jagadeesh Umapathi <[email protected]> > Sent: Monday, May 15, 2017 5:14 AM > To: [email protected] > Subject: RE: Axis2 Webservice WSDL not accessible [I] > > > Classification: For internal use only > > Dear Martin, > > > > Thanks for your response. > > > > Yes, it does work fine if I revert back the latest versions of spring, > hibernate and quartz. But however as you may have guessed already we are > trying to upgrade components to latest version so reverting back is not an > option. We moved from Spring 3.1.0 to 4.3.2. hibernate from 3.6.10 to 5.2.1. > and quartz from 1.8.6 to 2.x.x. > > > > Modules List file contents. > > > > addressing-1.6.2.mar > > mex-1.6.2.mar > > mtompolicy-1.6.2.mar > > ping-1.6.2.mar > > scripting-1.6.2.mar > > soapmonitor-1.6.2.mar > > > > Unfortunately nothing shows in my application log or catalina.log. but if I > select the deployed service and click on it from the axis deployed services > page it goes to 500 internal server error page. I try to find out compatible > version of axis for Spring 4.3.2, but could not find anywhere. Does axis > 1.6.2 compatible with spring 4.3.2 in general? > > > > Kind regards, > ____________________________________________________ > > > > Jagadeesh Umapathi > IMS Engineering > > > > COO Chief Information Security Office - Identity & Access - Access Lifecycle > Solutions > Deutsche Bank AG, Filiale London > > 99 BishopsGate EC2M 3XD, United Kingdom > > Tel. +44 20 754-19391 > Fax +44 2075 45216 > Mobile +44 7886245799 > Email [email protected] > > > > > > > From: Martin Gainty [mailto:[email protected]] > Sent: 12 May 2017 19:59 > To: [email protected] > Subject: Re: Axis2 Webservice WSDL not accessible [I] > > > > this is actually a users question but nonetheless > > > > if you restore your versions of Spring, hibernate, Quartz to original > version ...everything works > > > > As a computer professional i am sure you know how to smoke-test new versions > of an upgraded component > > > > which version of spring were you using before upgrade? > > which version of spring are you using after upgrade? > > > > which version quartz were you using before upgrade? > > which version of quartz are you uding after upgrade? > > > > which version hibernate were you using before upgrade? > > which version hibernate are you using after upgrade? > > > > you will need to show the stacktrace of the error > > you will need to show a copy of the logs..if tomcat log would be > $TOMCAT_HOME/logs/localhost*.log > > > > it would also be helpful to see: > > ./WEB-INF/conf/axis2.xml > > ./WEB-INF/services/services.list > > ./WEB-INF/services/services.xml > > ./WEB-INF/web.xml > > ./WEB-INF/modules/modules.list > > > > Regards > > Martin > ______________________________________________ > > > > > > ________________________________ > > From: Jagadeesh Umapathi <[email protected]> > Sent: Friday, May 12, 2017 8:18 AM > To: [email protected] > Subject: Axis2 Webservice WSDL not accessible [I] > > > > Classification: For internal use only > > Hi, > > > > Could someone in your group help me identify the issue and help me resolve > this. We have deployed 2 web services one is http basic protected and > another one kerbrose protected within Axis framework as .aar files. This > deployment was done long ago around 2013, since now we have no issues. > Recently we decided to do the upgrade of software components like Spring, > hibernate, Quartz and other components to latest available version. But our > Axis version remains the same at 1.6.2. > > > > With the new version of software I have deployed on Axis 1.6.2 and I can see > the services from front end using the Axis administrative portal and also > validation also passes but however when I click on one of the deployed > webservices I get Internal server 500 error. I am using Jdk 1.7.0.25. I also > used xalan-2.7.0.jar. > > > > I have seen this FAQ entry in your website. > > > > https://axis.apache.org/axis2/java/core/faq.html#f1 ( > > Frequently Asked Questions on Apache Axis2 > > axis.apache.org > > General I'm having a problem using Axis2. What should I do? First make sure > you go through the user guide and this FAQ. If you are using a ... > > > see an internal server error page when I try to view the WSDL file.) > > > > At the moment I don’t have anything to share in terms of stack trace or > anything. When I try to access the wsdl I get 500 internal server on > browser. We also tried from http client and we get > com.sun.xml.ws.client.ClientTransportException: The server sent HTTP status > code 500: Internal Server Error. > > > > Could you help me pin point where the issue could be? > > > > > > > > Kind regards, > ____________________________________________________ > > > > Jagadeesh Umapathi > IMS Engineering > > > > COO Chief Information Security Office - Identity & Access - Access Lifecycle > Solutions > Deutsche Bank AG, Filiale London > > 99 BishopsGate EC2M 3XD, United Kingdom > > Tel. +44 20 754-19391 > Fax +44 2075 45216 > Mobile +44 7886245799 > Email [email protected] > > > > > > > > > --- > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and delete this e-mail. Any > unauthorized copying, disclosure or distribution of the material in this > e-mail is strictly forbidden. > > Please refer to https://www.db.com/disclosures for additional EU corporate > and regulatory disclosures and to > http://www.db.com/unitedkingdom/content/privacy.htm for information about > privacy. > > > > --- > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and delete this e-mail. Any > unauthorized copying, disclosure or distribution of the material in this > e-mail is strictly forbidden. > > Please refer to https://www.db.com/disclosures for additional EU corporate > and regulatory disclosures and to > http://www.db.com/unitedkingdom/content/privacy.htm for information about > privacy. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
