[JBoss JIRA] Created: (JBWS-3013) maven-jaxws-tools-plugin has an issue with the lack of tools.jar on OSX Snow Leopard.
by Shawn Jones (JIRA)
maven-jaxws-tools-plugin has an issue with the lack of tools.jar on OSX Snow Leopard.
-------------------------------------------------------------------------------------
Key: JBWS-3013
URL: https://jira.jboss.org/jira/browse/JBWS-3013
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: tools-jaxws
Environment: Mac OSX 10.6.3; Darwin Kernel Version 10.3.0; 2.53 GHz Intel Core 2 Duo processor; 4 GB 1067 MHz DDR 3 RAM; Java version 1.6.0_17
Reporter: Shawn Jones
Within a pom.xml that uses maven-jaxws-tools-plugin, the following error appears on OSX Snow Leopard:
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Template Web Service
[INFO] task-segment: [generate-sources]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) com.sun:tools:jar:1.5.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.sun -DartifactId=tools -Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=com.sun -DartifactId=tools -Dversion=1.5.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.jboss.ws.plugins:maven-jaxws-tools-plugin:maven-plugin:1.0.0.GA
2) com.sun:tools:jar:1.5.0
----------
1 required artifact is missing.
for artifact:
org.jboss.ws.plugins:maven-jaxws-tools-plugin:maven-plugin:1.0.0.GA
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
repository.jboss.org (http://repository.jboss.org/maven2),
snapshots.jboss.org (http://snapshots.jboss.org/maven2),
eviwarePluginRepository (http://www.eviware.com/repository/maven2),
Main Maven repo (http://repo1.maven.org/maven2),
JBOSS-WS (http://repository.jboss.org/maven2)
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Wed Apr 28 21:41:40 EDT 2010
[INFO] Final Memory: 45M/81M
[INFO] ------------------------------------------------------------------------
According to various posts on the Internet about this same error with other maven plugins, the problem is connected to the fact that the JDK for OSX does not include the tools.jar file. The objects within this file are, instead, available in the classes.jar file.
The pom at http://repository.jboss.org/maven2/org/jboss/ws/plugins/maven-jaxws-tools... does contain the following entry:
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.5.0</version>
<scope>system</scope>
<systemPath>${java.home}/../lib/tools.jar</systemPath> <!-- Required by wsprovide with Metro stack (because of APT) -->
</dependency>
which appears to affix the plugin to version 1.5.0 of the JDK's tools.jar. Obviously, according to the comment, this is needed. Again, tools.jar is not present on OSX and its objects are present in classes.jar.
This error does not occur with the JDK of Windows XP, Windows 7, or Red Hat Linux.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBWS-2742) Getting Classcast Exception Inconsistently with the WSAddressing Implemented Services
by vinoth kumar (JIRA)
Getting Classcast Exception Inconsistently with the WSAddressing Implemented Services
-------------------------------------------------------------------------------------
Key: JBWS-2742
URL: https://jira.jboss.org/jira/browse/JBWS-2742
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.0
Environment: Linux - Ubuntu
Reporter: vinoth kumar
We are using JBOSS 4.2.3 with JBOSSWS Native 3.1.0 deployed.
We had implemented WSAddressing for Our Services as per the Steps given in the link : http://www.jboss.org/community/wiki/JBossWS-NativeUserGuide.
This WSAddressing implementation works fine without any issues if we give a single hit to the Services from the client for a given time. But if we have multiple simultaneous hits, we are getting the Classcast Exception inconsistently.
We had done the following changes in Client,
Code:
Service service = Service.create(wsdlURL, serviceName);
port1 = (IdentityServiceImpl)service.getPort(IdentityServiceImpl.class);
BindingProvider bindingProvider = (BindingProvider)port1;
List<Handler> customHandlerChain = new ArrayList<Handler>();
customHandlerChain.add(new ClientHandler());
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
The Exception that we are getting is,
Code:
javax.xml.ws.WebServiceException:
java.lang.ClassCastException:
com.mobax.signage.ws.RemoveDeviceResponse cannot be cast to com.mobax.signage.ws.GetDeviceResponseRe
sponse
at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
at $Proxy103.removeDevice(Unknown Source)
at com.mobax.mashup.webserviceconsumer.SignageServiceConsumer.removeDevices(SignageServiceConsumer.j
ava:264)
at com.mobax.mashup.responsebuilder.EnablerResponseParser.removeDevice(EnablerResponseParser.java:14
89)
at com.mobax.mashup.servlet.signage.RemoveDevice.processRequest(RemoveDevice.java:60)
at com.mobax.mashup.servlet.signage.RemoveDevice.doGet(RemoveDevice.java:88)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)
As per Our understanding,
We are invoking the method port1.getDeviceResponse() . Before receiving the response for this request, we are invoking another method port1.removeDevice() . The Proxy seems to be waiting for the Response for the second request removeDevice() . When it receives the Response for the first request getDeviceResponse(), the proxy tries to parse this response assuming that this response belongs to the Second request, thus Resulting in Classcast Exception.
We would like to know whether anybody have Successfully implemented the WSAddressing in their Services without having any issues.
Interestingly, we had find out a WORKAROUND for this issue. The workaround is to generate the following code for every Request. i.e., before calling any Requests, if we generate the following proxy every time newly, then the Exception does not Occurs.
Code:
port1 = (IdentityServiceImpl)service.getPort(IdentityServiceImpl.class);
BindingProvider bindingProvider = (BindingProvider)port1;
List<Handler> customHandlerChain = new ArrayList<Handler>();
customHandlerChain.add(new ClientHandler());
customHandlerChain.add(new WSAddressingClientHandler());
bindingProvider.getBinding().setHandlerChain(customHandlerChain);
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBWS-2939) Handler chain file not found
by Gary Brown (JIRA)
Handler chain file not found
----------------------------
Key: JBWS-2939
URL: https://jira.jboss.org/jira/browse/JBWS-2939
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.2.2
Environment: Fedora 12
JDK 6
JBossAS 5.1.0.GA
JBossWS-native-3.2.2.GA.
Reporter: Gary Brown
Attachments: Component-SMSCTBC-1.0.0.war
A RiftSaw user submitted an example to demonstrate an issue, but when I tried to install it I got the following exception:
12:47:08,079 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/home/gbrown/testing/riftsaw/test/jboss-5.1.0.GA/server/default/deploy/Component-SMSCTBC-1.0.0.war/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/home/gbrown/testing/riftsaw/test/jboss-5.1.0.GA/server/default/deploy/Component-SMSCTBC-1.0.0.war/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
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.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.ws.WSException: Cannot process handler chain: http://localhost:8080/Component-SMSCTBC-1.0.0/myhandler.xml
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.getHandlerChainsMetaData(JAXWSMetaDataBuilder.java:290)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.processHandlerChain(JAXWSMetaDataBuilder.java:189)
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:194)
at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:62)
at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:64)
at org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer.internalDeploy(WSDeploymentAspectDeployer.java:107)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
... 24 more
Caused by: java.io.FileNotFoundException: http://localhost:8080/Component-SMSCTBC-1.0.0/myhandler.xml
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1311)
at java.net.URL.openStream(URL.java:1010)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.getHandlerChainsMetaData(JAXWSMetaDataBuilder.java:268)
... 32 more
12:47:08,098 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
Related to the handle chain:
@HandlerChain(file="http://localhost:8080/Component-SMSCTBC-1.0.0/myhandler.xml")
The referenced file is present.
The user did not experience the problem, however they were using the jbossws version 3.1.2.GA bundled with JBossAS 5.1.0.GA. So I tried reproducing the problem in vanilla JBossAS 5.1.0.GA (with no riftsaw installed) - and it did not complain when I deployed the attached war.
However when I updated to jbossws-3.2.2.GA, it generated the exception.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBWS-2460) wsconsume --verbose does not show full error trace
by Thomas Diesler (JIRA)
wsconsume --verbose does not show full error trace
--------------------------------------------------
Key: JBWS-2460
URL: https://jira.jboss.org/jira/browse/JBWS-2460
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: tools-jaxws
Affects Versions: jbossws-native-3.0.4
Environment: JBoss-5.0.0.GA
Reporter: Thomas Diesler
Hi Folks,
when I invoke plain wsconsume, I get
> wsconsume ws-humantask-api.wsdl
parsing WSDL...
Failed to parse the WSDL.
Failed to invoke WsImport
java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:233)
at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:222)
at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:80)
Error: Could not import. (use --verbose to see full traces)
Error: WsImport invocation failed. Try the verbose switch for more information
When I use the verbose switch, I get
> wsconsume --verbose ws-humantask-api.wsdl
parsing WSDL...
Failed to parse the WSDL.
Failed to invoke WsImport
java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:233)
at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:222)
at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:80)
Error: Could not import. (use --verbose to see full traces)
java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:233)
at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:222)
at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:80)
The (invalid) wsdl itself you can get from here
http://www.oasis-open.org/committees/download.php/27599/ws-humantask-1.1-...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months