[JBossWS] - Jboss-5.0.0.Beta1 JSR-181 Endpoint ClassCastException
by volna
I am trying to deploy a WebService using JSR-181 with Jboss-5.0.0.Beta1. If I have understood correctly this includes support for JBossWS-2.0
package testService;
@WebService( serviceName="TestService", name="Testing",
targetNamespace="urn:Testing" )
@SOAPBinding( style = SOAPBinding.Style.DOCUMENT,
use = SOAPBinding.Use.LITERAL,
parameterStyle=SOAPBinding.ParameterStyle.WRAPPED)
public class TestUI {
@WebMethod()
public String Test(String tString) {
return "Hello " + tString;
}
}
I have the following web.xml file
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
<servlet-name>TestService</servlet-name>
<servlet-class>testService.TestUI</servlet-class>
<servlet-mapping>
<servlet-name>TestService</servlet-name>
<url-pattern>/testService</url-pattern>
</servlet-mapping>
</web-app>
I am getting the following error
javax.servlet.ServletException: Class testService.TestUI is not a Servlet
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:174)
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:86)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:212)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:818)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:624)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
java.lang.Thread.run(Thread.java:595)
root cause
java.lang.ClassCastException: testService.TestUI
org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:174)
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:86)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:212)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:818)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:624)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
java.lang.Thread.run(Thread.java:595)
Any pointers to help me out are appreciated
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013891#4013891
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013891
19Â years, 2Â months
[JBossCache] - Re: JbossCache 1.4.1 problem/bug
by vbatista
Hi!
Thanks for your reply.
I confirm the error. I checked out the JBossCache src code and inserted some debug.
When I run JBoss configured to use the default JVM MBeanServer (JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"), the call server.getDefaultDomain() returns null (It seems that the JVM is starting its MBean server with a null Default Domain). If I start the JVM without sharing the MBeanServers, the call server.getDefaultDomain() returns "jboss". In both cases I have obly one MBeanServer (It seems that the default JVM MBeanServer isn't created by default, only when it is needed).
Below we can see the Debug I have inserted. If I got a null Default Domain I was printing its domains (there are no java domains).
2007-02-09 18:10:05,340 INFO [org.jboss.cache.TreeCache] PTECH Found 1 MBean Servers.
2007-02-09 18:10:05,340 INFO [org.jboss.cache.TreeCache] .PTECH:null (server.getDefaultDomain())
2007-02-09 18:10:05,340 INFO [org.jboss.cache.TreeCache] PTECH MBean Server Default DOMAIN is NULL. Ignoring it. MBeanServer:org.jboss.system.server.jmx.LazyMBeanServer@166f936
2007-02-09 18:10:05,340 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.deployment
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jmx.loading
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.web
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.rmi
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:pt.ptinovacao.wappremium
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.security
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:Catalina
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.jdbc
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.mq
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.jca
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.bean
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.j2ee
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.jms
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.aop
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.net
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.jmx
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.web.deployment
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.cache
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.mq.destination
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:JMImplementation
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.deployer
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.ejb
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.system
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.alerts
2007-02-09 18:10:05,341 INFO [org.jboss.cache.TreeCache] ..PTECH: Domain:jboss.management.local
I started with JbossCache-1.4.1.GA. I repeated the process with JbossCache-1.4.1.SP1 and I have exactly the same problem.
Thanks in advance.
Regards,
Victor Batista
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013889#4013889
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013889
19Â years, 2Â months
[JBoss jBPM] - Re: Choosing JBPM?
by alex.guizarï¼ jboss.com
jBPM offers two different process languages. Any of them let you to orchestrate web services. BPEL is fully oriented to web services, but it does not let you directly incorporate user tasks or Java components. Conversely, jPDL lets you easily incorporate Java code and human intervention. Currently no special support exists for web services, but you can use existing Java APIs to consume and produce web services.
Since both languages are implemented with the same building blocks, you can use a common API to manage and monitor processes in either language. The Console subproject provides you with JSF-based web interface to examine and manipulate process definitions, instances, task lists and more.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013873#4013873
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013873
19Â years, 2Â months