Dims, Now it works fine. Thank you.
-- Jérôme Mainaud Klee Group [EMAIL PROTECTED] <http://www.kleegroup.com/> + 33 146 295 825 Tel: + 33 146 292 525 Fax: + 33 146 292 529 Davanum Srinivas a écrit : > Jérôme, > > We have already fixed this problem in Axiom 1.2.1 release [1] > > thanks, > dims > > [1] http://svn.apache.org/viewvc?view=rev&revision=476358 > > On 12/27/06, Jérôme Mainaud <[EMAIL PROTECTED]> wrote: >> That's the same as the one for which you gave the endorsed dir solution. >> And copy deploy stax-api.jar in jre/lib/endorsed make it work for >> testing purposes. >> My real problem is I cannot ask this from the end-users, so I have to >> find another solution. >> >> Here is the stacktrace : >> >> javax.xml.stream.FactoryConfigurationError: Provider >> javax.xml.stream.XMLInputFactory could not be instantiated: >> java.lang.InstantiationException >> at javax.xml.stream.XMLInputFactory.newInstance(Unknown Source) >> at >> org.apache.axiom.om.util.StAXUtils.getXMLInputFactory(StAXUtils.java:40) >> at >> org.apache.axiom.om.util.StAXUtils.createXMLStreamReader(StAXUtils.java:66) >> >> at >> org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilder.java:86) >> >> at >> org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:58) >> >> at >> org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:690) >> >> at >> org.apache.axis2.deployment.FileSystemConfigurator.getAxisConfiguration(FileSystemConfigurator.java:109) >> >> at >> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:61) >> >> at >> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:180) >> >> at >> org.apache.axis2.client.ServiceClient.initializeTransports(ServiceClient.java:189) >> >> at >> org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:118) >> >> at >> org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:114) >> at >> org.apache.axis2.client.ServiceClient.<init>(ServiceClient.java:207) >> at >> upload.client.service.UploadServiceSoapStub.initUpload(UploadServiceSoapStub.java:55) >> >> at upload.client.service.UploadClient.init(UploadClient.java:30) >> at upload.client.Upload.<init>(Upload.java:56) >> at upload.client.swing.UploadApplet.init(UploadApplet.java:50) >> at sun.applet.AppletPanel.run(Unknown Source) >> at java.lang.Thread.run(Unknown Source) >> >> -- >> Jérôme Mainaud Klee Group >> [EMAIL PROTECTED] <http://www.kleegroup.com/> >> + 33 146 295 825 Tel: + 33 146 292 525 >> Fax: + 33 146 292 529 >> >> >> >> Davanum Srinivas a écrit : >> > Can u please paste the exception you get with JDK 1.6? >> > >> > thanks, >> > dims >> > >> > On 12/27/06, Jérôme Mainaud <[EMAIL PROTECTED]> wrote: >> >> Hello, >> >> >> >> I have a ws client (using Axis2) that is an applet. >> >> It must work on any jre since 1.4.2 but do not work on clients >> that have >> >> java 1.6 since Sun added stax-api in jdk. >> >> >> >> I cannot deploy stax-api.jar in jre/lib/endorsed folder on every >> Java 6 >> >> client. >> >> Because there are many clients, because them do not have any >> computer's >> >> skill, because they often are not allowed to install anything in >> their >> >> computer, because their administrator will never accept that there is >> >> anything to deploy but standard jvm... >> >> >> >> How can I make Axis2 work on any client (from 1.4.2 to 1.6.0) ? >> >> >> >> Thank you. >> >> >> >> -- >> >> Jérôme Mainaud Klee Group >> >> [EMAIL PROTECTED] <http://www.kleegroup.com/> >> >> + 33 146 295 825 Tel: + 33 146 292 525 >> >> Fax: + 33 146 292 529 >> >> >> >> >> >> >> >> Sathija Pavuluri a écrit : >> >> > Hello, >> >> > >> >> > An issue had been posted earlier about axis2 issues when running on >> >> jdk 6. - >> >> > http://marc.theaimsgroup.com/?l=axis-user&m=116593301416986&w=2 >> >> > >> >> > And the proposed solution was to copy the stax-api.jar from axis2 >> >> distribution to jre's endorsed folder. >> >> > >> >> > The issue was actually resolved by copying the jar to tomcat's >> >> common/endorsed folder. >> >> > Didnt have to copy to jre's endorsed. >> >> > >> >> > Just an FYI. >> >> > >> >> > - Sathija Pavuluri. >> >> > >> >> > >> >> > >> --------------------------------------------------------------------- >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> > >> >> > >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
