[JBossWS] - Re: WS-RM Exception: cannot be cast to org.jboss.ws.core.Stu
by moweis
Hi Richard,
You were right.
I went ahead and added all the jboss/jbossws jars to my classpath, and I no longer get the cannot be cast exception.
However, I get a new exception now:
anonymous wrote : Exception in thread "main" org.jboss.ws.extensions.wsrm.api.RMException: Unable to create WSRM sequence
| at org.jboss.ws.core.jaxws.client.ClientImpl.createSequence(ClientImpl.java:563)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
| at $Proxy16.ping(Unknown Source)
| at org.jboss.test.ws.jaxws.samples.wsrm.client.SimpleServiceTestCase.main(SimpleServiceTestCase.java:33)
| Caused by: javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
| at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:410)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:316)
| at org.jboss.ws.core.jaxws.client.ClientImpl.createSequence(ClientImpl.java:550)
| ... 4 more
| Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
| at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441)
| at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:84)
| at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
| at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
| at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
| at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:292)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:304)
| ... 5 more
|
Here is my client code:
package org.jboss.test.ws.jaxws.samples.wsrm.client;
|
| import java.net.URL;
| import javax.xml.namespace.QName;
| import javax.xml.ws.Service;
| import org.jboss.ws.core.StubExt;
| import org.jboss.ws.extensions.wsrm.api.RMProvider;
|
| import org.jboss.test.ws.jaxws.samples.wsrm.generated.SimpleService;
|
|
| public final class SimpleServiceTestCase
| {
|
| private static final String serviceURL = "http://localhost:8080/jaxws-samples-wsrm/SimpleService";
|
| public static void main(String[] args) throws Exception
| {
| String url = null;
| if ( args != null && args.length > 0 && args[0] != null )
| url = args[0];
| else
| url = serviceURL;
| System.out.println("Calling wsdl");
| QName serviceName = new QName("http://www.jboss.org/jbossws/ws-extensions/wsrm", "SimpleService");
| QName portName = new QName("http://www.jboss.org/jbossws/ws-extensions/wsrm", "SimpleServicePort");
| URL wsdlURL = new URL(url + "?wsdl");
| Service service = Service.create(wsdlURL, serviceName);
| SimpleService proxy = (SimpleService)service.getPort(SimpleService.class);
|
| ((StubExt)proxy).setConfigName("Standard Anonymous WSRM Client", "META-INF/wsrm-jaxws-client-config.xml");
|
| proxy.ping(); // one way call
| proxy.echo("Hello World!"); // request responce call
| ((RMProvider)proxy).closeSequence();
| }
|
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168502#4168502
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168502
17 years, 8 months
[Beginners Corner] - Re: Application Error - Resource not Found
by PeterJ
If the application.xml, jboss-app.xml and jboss-web.xml files appear in the tmp directory, then they must be in the EAR and WAR war files. Therefore, your ant script is placing them in the those files as part of the build. Since it is your ant script and your build, you should know where those files are coming from. When you find them, post the jboss-web.xml file that gets packaged inside the csa.war.
Also, is your build placing both the csa.war and csa-turtle.ear files into the deploy directory? Or is the csa.war file embedded within csa-turtle.ear? I ask because based on your third post (where you gave the full path) the war is embedded within the ear but your latest post claims that the war is not in embedded within the ear (you said the war appears in the deploy directory). Run an "ls -al" on the deploy directory and post the results.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168499#4168499
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168499
17 years, 8 months
[JBossWS] - javax.naming.Name is an interface, and JAXB can't handle int
by kosulin
Hi,
I have a single POJO with 2 methods, first method accesses filesystem, and second - invokes SLSB. When I deploy it to JBoss 5.0.0CR1 (jre 1.6.0_07, Windows Vista SP1), I am getting the following error message:
10:16:02,418 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/C:/java/jboss-5.0.0.CR1/server/cpportal2/deploy/cpportal2-ear.ear state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/C:/java/jboss-5.0.0.CR1/server/cpportal2/deploy/cpportal2-ear.ear/statements-web.war
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:180)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:970)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1023)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:911)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1392)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:784)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:672)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:594)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.IllegalStateException: Cannot build JAXB context
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:955)
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:156)
at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:52)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:63)
at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:67)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.start(DeploymentAspectManagerImpl.java:146)
at org.jboss.wsf.container.jboss50.BareWSFRuntime.start(BareWSFRuntime.java:66)
at org.jboss.wsf.container.jboss50.deployer.JAXWSDeployerHookPostJSE.deploy(JAXWSDeployerHookPostJSE.java:54)
at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174)
... 23 more
Caused by: org.jboss.ws.WSException: Failed to create JAXBContext
at org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:116)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:951)
... 33 more
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of IllegalAnnotationExceptions
javax.naming.Name is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at javax.naming.Name
at private javax.naming.Name com.wsc.cp.web.statements.jaxws.NamingExceptionBean.remainingName
at com.wsc.cp.web.statements.jaxws.NamingExceptionBean
javax.naming.Name does not have a no-arg default constructor.
this problem is related to the following location:
at javax.naming.Name
at private javax.naming.Name com.wsc.cp.web.statements.jaxws.NamingExceptionBean.remainingName
at com.wsc.cp.web.statements.jaxws.NamingExceptionBean
java.lang.StackTraceElement does not have a no-arg default constructor.
this problem is related to the following location:
at java.lang.StackTraceElement
at public java.lang.StackTraceElement[] java.lang.Throwable.getStackTrace()
at java.lang.Throwable
at private java.lang.Throwable com.wsc.cp.web.statements.jaxws.NamingExceptionBean.rootCause
at com.wsc.cp.web.statements.jaxws.NamingExceptionBean
at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438)
at com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:286)
at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139)
at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105)
at org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory.createContext(CustomizableJAXBContextFactory.java:110)
... 34 more
10:16:03,189 WARN [HDScanner] Failed to process changes
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** CONTEXTS IN ERROR: Name -> Error
vfszip:/C:/java/jboss-5.0.0.CR1/server/cpportal2/deploy/cpportal2-ear.ear -> com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 3 counts of IllegalAnnotationExceptions
javax.naming.Name is an interface, and JAXB can't handle interfaces.
this problem is related to the following location:
at javax.naming.Name
at private javax.naming.Name com.wsc.cp.web.statements.jaxws.NamingExceptionBean.remainingName
at com.wsc.cp.web.statements.jaxws.NamingExceptionBean
javax.naming.Name does not have a no-arg default constructor.
this problem is related to the following location:
at javax.naming.Name
at private javax.naming.Name com.wsc.cp.web.statements.jaxws.NamingExceptionBean.remainingName
at com.wsc.cp.web.statements.jaxws.NamingExceptionBean
java.lang.StackTraceElement does not have a no-arg default constructor.
this problem is related to the following location:
at java.lang.StackTraceElement
at public java.lang.StackTraceElement[] java.lang.Throwable.getStackTrace()
at java.lang.Throwable
at private java.lang.Throwable com.wsc.cp.web.statements.jaxws.NamingExceptionBean.rootCause
at com.wsc.cp.web.statements.jaxws.NamingExceptionBean
at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:676)
at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291)
at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
===============================================
Here is my code which causes the problem:
@WebMethod(operationName = "GetStatements")
public StatementListDO getReportingDates(@WebParam(name = "Username") final String user,
@WebParam(name = "ClientId") final String clientId,
@WebParam(name = "TaxYear") final String taxYear,
@WebParam(name = "AccountNo") final String custAccountNo)
throws IncorrectParameterException, DBConnectionException, NamingException
{
StatementHandler.logger.info("Received request from user '" + user +
"' for a list of statements available for Client Id " + clientId + ", Tax Year " +
taxYear + ", AccountNo " + custAccountNo);
StatementListDO sldo = new StatementListDO();
try
{
InitialContext ic = new InitialContext();
// Statements stmts = (Statements)ic.lookup(Statements.class.getName());
// sldo = stmts.getReportingDates(clientId, taxYear, custAccountNo);
}
catch(NamingException e)
{
StatementHandler.logger.error(e);
throw new DBConnectionException("Processing error");
}
return sldo;
}
If I comment InitalContext out (as I did for the SLSB invocation code), it deploys fine. But how can I resolve my SLSB then?
I'd prefer not to expose SLSB directly through WS annotations, becuase this means having 2 endpoints and 2 WSDL definitions.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168479#4168479
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168479
17 years, 8 months
[JBoss jBPM] - reopen a process instance ?
by memius
Is it conceptually correct (and if so, technically possible) to reopen a closed process instance ?
Consider next situation : you have an insurance dossier that is functionally 'closed' (all payments done, everyone happy, etc...)
But ... there is always the option that new data pops up and this dossier has to be 'reopened'. Let's say that this can happen within 5 years after 'closing' the dossier.
How do you put this in a process ?
You could eg. create a time for five years and after that, close the process instance (but even then it seems to be functionally possible to have the need to reopen a dossier).
or you could leave the process instance open (but all process instances would stay alive then :s).
What is the normal way of doing this ? It appears to me that this kind of process occurs a lot (medical files, accountancy, law suit, ...)
Btw, I consider the correct concept more important than the technical jbpm possible solutions.
Sincerely,
Dieter D'haeyere.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168471#4168471
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168471
17 years, 8 months