Re: Error handling for WS-Security enabled services
Chinmoy,
When an exception occurs on the server end...and if you know the kind of
exception...try wrapping it as a fault. In most cases it has worked for me
as expected.
Preetham
On Wed, Jul 29, 2009 at 9:14 AM, Chinmoy Chakraborty cch...@gmail.comwrote:
Hi All,
I am using rampart 1.4 and Axis2 1.4. I have parameterbased ws-security
enabled services. In normal cases when there is no error at the time of
invocation (invocation of business logic) of the service, it works fine.
Following is the SOAP is returned by axis2 (captured in TCPMon):
*Good One*
--
HTTP/1.1 200 OK
Content-Type: text/xml;charset=UTF-8
Transfer-Encoding: chunked
Date: Wed, 29 Jul 2009 12:56:25 GMT
Server: Apache-Coyote/1.1
?xml version='1.0' encoding='UTF-8'?
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/
soapenv:Body
ns:invokeResponse xmlns:ns=http://www.abc.com/webservice;
ns:return5.5/ns:return
/ns:invokeResponse
/soapenv:Body
/soapenv:Envelope
So far so good. Now when some error happens at the time of service
invocation it does not return SOAP fault back. I got following things
(captured in TCPMon):
Bad One
--
HTTP/1.1 500 Internal Server Error
Content-Type: text/html;charset=UTF-8
Content-Language: en-US
Content-Length: 980
Date: Wed, 29 Jul 2009 12:58:29 GMT
Server: Apache-Coyote/1.1
Connection: close
htmlheadtitleApache Tomcat/5.0.19 - Error report/titlestyle!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--/style
/headbodyh1HTTP Status 500 - /h1HR size=1 noshadepbtype/b
Status report/ppbmessage/b u/u/ppbdescription/b uThe
server encountered an internal error () that prevented it from fulfilling
this request./u/pHR size=1 noshadeh3Apache
Tomcat/5.0.19/h3/body/html
I have no clue what went wrong. Am I missing something? Do I need to
configure anything in services.xml (inside inflowsecurity)/axis2.xml? or is
this a bug?
Chinmoy
Kerberos support in Axis/Rampart?
All, I have seen some third party implementations such as http://thejavamonkey.blogspot.com/2008/09/axis-2-kerberos-web-services-featuring.html. I have also seen some posts on people willing to combine these kind of implementations for kerberos into axis 1.4/1.5. So...what is the progress on it...has it already been integrated? Also the above implementation is a bit old...uses Rampart 1.3. Thanks Preetham
error in jboss5.1 while deploying axis 1.4.1
All, I get the following error while deploying the axis 1.4.1 war in jboss 5.1.0GA. I have removed the xercesImpl jar and the xml-apis jar. Any idea why is this showing up? I have rampart jar files and my web service classes as part of the axis2.war. Thanks Preetham 16:24:24,912 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console' 16:24:28,209 INFO [TomcatDeployment] deploy, ctxPath=/ 16:24:28,381 INFO [TomcatDeployment] deploy, ctxPath=/axis 16:24:28,912 ERROR [[/axis]] StandardWrapper.Throwable *java.lang.ExceptionInInitializerError at org.apache.axis2.deployment.DescriptionBuilder.buildOM(DescriptionBuilder.java:97) * at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:86) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:641) at org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxisConfigurator.java:157) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:516) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:950) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4122) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4421) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) at org.jboss.web.deployers.WebModule.start(WebModule.java:97) 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 org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) at $Proxy38.start(Unknown Source) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42) at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37) at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContext Action.java:62) at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java: 71) at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:5 1) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.ServiceController.doChange(ServiceController.java:688) at org.jboss.system.ServiceController.start(ServiceController.java:460) at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99) at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46) at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer .java:62) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at
how to retrieve rampart username/password from within a JAX-WS service?
All, On the Client Side: I am using JAX-WS Client + Axis Transport. On the Server Side: I am using JAX-WS webservice + Axis Transport. For WS-Security I am using Rampart on the client and the server side. I have a requirement that...once I authenticate the user...on the server I need to retrieve the username and the password from within the @WebService class for further processing. Is there a way I can achieve this from within JAX-WS service wrapped around by Axis2? Any configuration in Axis where I set this to happen? Any message context instance that I get is probably related to JAX-WS right?...since I am completely using JAX-WS web service implementations. I am confused...any help would really be appreciated! Thanks Preetham
Re: jax-ws client with Rampart
Anybody? has this question been dealt with before?
Thanks
Preetham
-- Forwarded message --
From: Axis PC pc.a...@gmail.com
Date: Mon, Jun 29, 2009 at 5:13 PM
Subject: jax-ws client with Rampart
To: axis-user@ws.apache.org
All,
I am trying to engage Rampart with JAX-WS client. I am trying to use the
example from AXIS_HOME\samples\jaxws-samples.
1. In this example...it creates the configurationContext and initializes the
repository and the axis2.xml as required.
private ClientConfigurationFactory initConfigurationFactory() {
String axis2xml =
System.getProperty(org.apache.axis2.jaxws.config.path);
if (axis2xml == null) {
throw new RuntimeException(Please set
org.apache.axis2.jaxws.config.path system property to a valid axis2.xml file
(with addressing module enabled));
}
ClientConfigurationFactory factory = null;
try {
FileSystemConfigurator configurator = new
FileSystemConfigurator(null, axis2xml);
factory = new ClientConfigurationFactory(configurator);
MetadataFactoryRegistry.setFactory(ClientConfigurationFactory.class,
factory);
} catch (AxisFault axisFault) {
throw new RuntimeException(axisFault);
}
return factory;
}
2. Then the service call is made to the server using the following code:
void CallService() {
if (clientConfigurationFactory == null) {
ClientConfigurationFactory factory =
initConfigurationFactory();
*buildAsync*(uriString + urlSuffix, null, message,
timeout, wireasync);
destroyConfigurationFactory(factory);
} else {
buildAsync(uriString + urlSuffix, null, message,
timeout, wireasync);
}
}//truncated/removed some code.
3. The buildAsync does not contain anything that engages a module or the
configContext to the javax.xml.ws.Service. Neither is there any conversion
between javax.xml.ws.Service and Axis's ServiceClient. So as
expected...when the request is sent...the server throws the exception that
the security header is missing.
Do you know if there is a legit way of engaging jax-ws with Rampart from the
client. Am I missing something? I was successful in doing this from the
server side. But I would like to engage jax-ws with ws-security from the
server side as well through Axis. Any help will be appreciated.
Thanks
Preetham
jax-ws client with Rampart
All,
I am trying to engage Rampart with JAX-WS client. I am trying to use the
example from AXIS_HOME\samples\jaxws-samples.
1. In this example...it creates the configurationContext and initializes the
repository and the axis2.xml as required.
private ClientConfigurationFactory initConfigurationFactory() {
String axis2xml =
System.getProperty(org.apache.axis2.jaxws.config.path);
if (axis2xml == null) {
throw new RuntimeException(Please set
org.apache.axis2.jaxws.config.path system property to a valid axis2.xml file
(with addressing module enabled));
}
ClientConfigurationFactory factory = null;
try {
FileSystemConfigurator configurator = new
FileSystemConfigurator(null, axis2xml);
factory = new ClientConfigurationFactory(configurator);
MetadataFactoryRegistry.setFactory(ClientConfigurationFactory.class,
factory);
} catch (AxisFault axisFault) {
throw new RuntimeException(axisFault);
}
return factory;
}
2. Then the service call is made to the server using the following code:
void CallService() {
if (clientConfigurationFactory == null) {
ClientConfigurationFactory factory =
initConfigurationFactory();
*buildAsync*(uriString + urlSuffix, null, message,
timeout, wireasync);
destroyConfigurationFactory(factory);
} else {
buildAsync(uriString + urlSuffix, null, message,
timeout, wireasync);
}
}//truncated/removed some code.
3. The buildAsync does not contain anything that engages a module or the
configContext to the javax.xml.ws.Service. Neither is there any conversion
between javax.xml.ws.Service and Axis's ServiceClient. So as
expected...when the request is sent...the server throws the exception that
the security header is missing.
Do you know if there is a legit way of engaging jax-ws with Rampart from the
client. Am I missing something? I was successful in doing this from the
server side. But I would like to engage jax-ws with ws-security from the
server side as well through Axis. Any help will be appreciated.
Thanks
Preetham
jax-ws war issues with axis 1.5
All, I get the following error when I deploy a sample jax-ws war (which is part of the samples directory) using axis 1.5. INFO: Deploying web application archive java_first_jaxws-1.1.war [ERROR] org.apache.axis2.transport.local.LocalTransportSender *org.apache.axis2.deployment.DeploymentException: org.apache.axis2.transport.local.LocalTransportSender* at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:694) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:121) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:707) at org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxisConfigurator.java:157) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1139) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:966) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3956) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4230) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:831) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:720) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1150) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) 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.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) *Caused by: java.lang.ClassNotFoundException: org.apache.axis2.transport.local.LocalTransportSender* at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1386) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1232) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at org.apache.axis2.util.Loader.loadClass(Loader.java:261) at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:669) ... 31 more [INFO] org.apache.axis2.deployment.DeploymentException: org.apache.axis2.transport.local.LocalTransportSender [ERROR] Servlet /java_first_jaxws-1.1 threw load() exception java.lang.ClassNotFoundException: org.apache.axis2.transport.local.LocalTransportSender at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1386) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1232) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at org.apache.axis2.util.Loader.loadClass(Loader.java:261) at org.apache.axis2.deployment.AxisConfigBuilder.processTransportSenders(AxisConfigBuilder.java:669) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:121) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:707) at org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxisConfigurator.java:157) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:525) at
issues with xmlschema1.4.2.jar and jaxb
All, Has anyone faced the following issue?: 1. I have a wsdl which has multiple schema imports. For example abc.wsdl has x.xsd and y.xsd imports. y.xsd in turn imports x.xsd. 2. From what I see...xmlschema-1.4.2.jar doesnt like it. In XmlSchema 1.4.x, the schema collection can only have a single schema instance for a sysid+ns combination? (read this somewhere). So once I reverted back to xmlSchema-1.3.x.jar, my scenario started working fine. Is there any work around for this - without having to replace the newer jar with the older jar? I am using axis 1.4.1 and am using jax-ws style web services. Thanks Preetham
Re: issues with xmlschema1.4.2.jar and jaxb
Also...attached is the stacktrace when I use xmlschema-1.4.x.jar
[ERROR] Error occurred while attempting to read generated schema file
{org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in
collection. Namespace: http://schemas.x.com/y/2007/09/mc-description}
[ERROR] Error occurred generating WSDL file for Web service implementation
class {com.x.schemas.y._2008._01.admin.XPortImpl}: {java.lang.Exception:
Error occurred while attempting to read generated schema file
{org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in
collection. Namespace: http://schemas.x.com/y/2007/09/mc-description}}
java.lang.Exception: Error occurred while attempting to read generated
schema file {org.apache.ws.commons.schema.XmlSchemaException: Schema name
conflict in collection. Namespace:
http://schemas.x.com/y/2007/09/xjob-description}
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.readInSchema(JAXWSRIWSDLGenerator.java:330)
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:180)
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:1322)
at
org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:287)
at
org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:242)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:595)
Thanks
Preetham
On Mon, Jun 8, 2009 at 2:52 PM, Axis PC pc.a...@gmail.com wrote:
All,
Has anyone faced the following issue?:
1. I have a wsdl which has multiple schema imports. For example
abc.wsdl has x.xsd and y.xsd imports. y.xsd in turn imports
x.xsd.
2. From what I see...xmlschema-1.4.2.jar doesnt like it. In XmlSchema
1.4.x, the schema collection can only have a single schema instance for a
sysid+ns combination? (read this somewhere). So once I reverted back to
xmlSchema-1.3.x.jar, my scenario started working fine.
Is there any work around for this - without having to replace the newer jar
with the older jar?
I am using axis 1.4.1 and am using jax-ws style web services.
Thanks
Preetham
axis.war issue with jboss4.2.2
All, I know this issue has been discussed earlier in a lot of forums...but I couldnt find a definitive answer. How can I get over this issue? One of the users had suggested commenting out the JAXWSDeployer...which i cannot, because I need to use it. Here is the error: 12:55:29,028 INFO [STDOUT] [INFO] Deploying Exception Occured with java.io.FileNotFoundException: C:\work\jboss-4.2.2.GA\server\default\.\tmp\deploy\tmp25140java_first_jaxws-1.1-exp.war\WEB-INF (Access is denied) java.lang.RuntimeException: java.io.FileNotFoundException: C:\work\ jboss-4.2.2.GA\server\default\.\tmp\deploy\tmp25140java_first_jaxws-1.1-exp.war\WEB-INF (Access is denied) at org.apache.axis2.deployment.util.Utils.findLibJars(Utils.java:870) at org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:918) at org.apache.axis2.jaxws.framework.JAXWSDeployer.deployServicesInWARClassPath(JAXWSDeployer.java:100) at org.apache.axis2.jaxws.framework.JAXWSDeployer.init(JAXWSDeployer.java:80) at org.apache.axis2.deployment.DeploymentEngine.initializeDeployers(DeploymentEngine.java:928) at org.apache.axis2.deployment.DeploymentEngine.setConfigContext(DeploymentEngine.java:919) at org.apache.axis2.deployment.WarBasedAxisConfigurator.setConfigContext(WarBasedAxisConfigurator.java:350) at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:76) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:516) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:436) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:981) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4071) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4375) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553) 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.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5312) 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.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:301) at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375) at org.jboss.web.WebModule.startModule(WebModule.java:83) at org.jboss.web.WebModule.startService(WebModule.java:61) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at
Re: axis.war issue with jboss4.2.2
I know :)...but I need a solution on windowsanyone? Thanks Preetham On Fri, Jun 5, 2009 at 1:09 PM, robert lazarski robertlazar...@gmail.comwrote: On Fri, Jun 5, 2009 at 2:04 PM, Axis PC pc.a...@gmail.com wrote: All, I know this issue has been discussed earlier in a lot of forums...but I couldnt find a definitive answer. How can I get over this issue? One of the users had suggested commenting out the JAXWSDeployer...which i cannot, because I need to use it. Here is the error: 12:55:29,028 INFO [STDOUT] [INFO] Deploying Exception Occured with java.io.FileNotFoundException: C:\work\jboss-4.2.2.GA \server\default\.\tmp\deploy\tmp25140java_first_jaxws-1.1-exp.war\WEB-INF (Access is denied) Well, you probably won't get that error on linux :-) . Or at least there you have lots of well understoold OS ways to get around it. - R
generating skeleton interfaces alone
All, I am using axis2 with JAXB. I am trying to generate the skeleton interfaces alone using the -ssi option in the wsdl2java tool. However I havent had any luck. I know at times we have to use certain combination of options. Is that the case with -ssi as well? Eagerly waiting for your reply. Thanks Chand
Re: generating skeleton interfaces alone
Sebastian, When I try to generate the interfaces using the following command: %AXIS2_HOME%/bin/wsdl2java -uri %WSDL% -d jaxbri -ssi , I get the same result as I do: %AXIS2_HOME%/bin/wsdl2java -uri %WSDL% -d jaxbri -ss. I dont want any of the stubs. I just need the interface. I dont get any error messages as such. Thanks Preetham 2009/5/29 Sebastian Just - RÖPERWEISE Systems j...@roeperweise.de Hi Chand, What is exactly your problem? Can you give some exceptions or error messages? Best regards, Sebastian
Rampart with JAX-WS
All, I have been working on JAX-WS for close to a year now and have started working on Axis lately. Each of the stacks have their pros and cons. One major roadblock I see in jax-ws is the lack of independent WSIT modules that implement the various WS-* standards. However I was wondering if anyone had any success in implementing Rampart with JAX-WS. If so...could you please brief on it? Thanks Preetham
jaxb issues with Axis2 - while using the wsdl2java tool
All, We were previously using adb with Axis2 and all was working fine. Recently we have been prototyping jaxb with Axis2. We have a complex wsdl which imports several schemas and in turn the schema has additional schema imports. In this scenario...errors are thrown. When we researched into it...we figured out the code generation tool of Axis (JAxB) is not able to handle a chain of schema imports based on the scenario described above. I get the following error: Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:271) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException at org.apache.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:112) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:224) ... 2 more Caused by: java.lang.reflect.InvocationTargetException 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.axis2.wsdl.codegen.extension.JAXBRIExtension.engage(JAXBRIExtension.java:101) ... 3 more Caused by: java.lang.NoClassDefFoundError: javax/activation/DataHandler at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl.clinit(RuntimeBuiltinLeafInfoImpl.java:224) at com.sun.xml.bind.v2.model.impl.RuntimeTypeInfoSetImpl.init(RuntimeTypeInfoSetImpl.java:61) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:127) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.createTypeInfoSet(RuntimeModelBuilder.java:79) at com.sun.xml.bind.v2.model.impl.ModelBuilder.init(ModelBuilder.java:152) at com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.init(RuntimeModelBuilder.java:87) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:422) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.init(JAXBContextImpl.java:286) at com.sun.tools.xjc.reader.xmlschema.bindinfo.BindInfo.getJAXBContext(BindInfo.java:332) at com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImpl$1.init(AnnotationParserFactoryImpl.java:80) at com.sun.tools.xjc.reader.xmlschema.bindinfo.AnnotationParserFactoryImpl.create(AnnotationParserFactoryImpl.java:79) at com.sun.xml.xsom.impl.parser.NGCCRuntimeEx.createAnnotationParser(NGCCRuntimeEx.java:323) at com.sun.xml.xsom.impl.parser.state.annotation.action0(annotation.java:48) at com.sun.xml.xsom.impl.parser.state.annotation.enterElement(annotation.java:73) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.NGCCHandler.spawnChildFromEnterElement(NGCCHandler.java:74) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:294) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.NGCCHandler.revertToParentFromEnterElement(NGCCHandler.java:111) at com.sun.xml.xsom.impl.parser.state.foreignAttributes.enterElement(foreignAttributes.java:50) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.NGCCHandler.spawnChildFromEnterElement(NGCCHandler.java:74) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:200) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:246) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:238) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:226) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:262) at com.sun.xml.xsom.impl.parser.state.NGCCRuntime.sendEnterElement(NGCCRuntime.java:378) at com.sun.xml.xsom.impl.parser.state.Schema.enterElement(Schema.java:270) at
Re: jaxb issues with Axis2 - while using the wsdl2java tool
Sebastin I thought so too...in the very beginning. But it is there in AXIS_HOME directory (activation-1.1.jar). Also...if that was the case wouldnt it be failing for all cases. Why is it specifically for the chain-import scenario I described. Thanks Preetham 2009/5/29 Sebastian Just - RÖPERWEISE Systems j...@roeperweise.de Hi! Caused by: java.lang.NoClassDefFoundError: javax/activation/DataHandler I guess you're missing the activation framework in your classpath. Best regards, Sebastian
