February 2007 - jboss-user - Jboss List Archives

[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

1
0
0 / 0

[JBoss Seam] - Invalidating Seam sessions when logging out of JBoss Portal

by endremr

Hi! We use Seam as framework when writing portlets deployed in JBoss Portal. This works pretty good, but we have problems finding out how we should take care of cleaning up our ejb's when the user logs out of the portal using the standard UserLogin-portlet. I have seen this post, but there's no answer: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008272#4008272 Seam has the method "Seam.invalidateSession", but shouldn't this be invoked automatically when the portal session ends? What are the proper way of handling this? Thanks in advance! Best regards Endre View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013890#4013890 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013890

19 years, 2 months

1
0
0 / 0

[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

1
0
0 / 0

[JBoss Seam] - Re: SMPC and forcing a transaction to commit

by SmokingAPipe

"gavin.king(a)jboss.com" wrote : This is very dangerous stuff. Hibernate entities should never be used in two concurrent transactions/persistence contexts. You will need some kind of DTOish thing to work around. Wait are you saying that even if I use this events trick to send the message AFTER the transaction has committed, that's still dangerous? Because it's working fine right now, but that doesn't mean it's correct or stable, so I'm curious. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013888#4013888 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013888

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: SMPC and forcing a transaction to commit

by SmokingAPipe

I tried that and IT WORKED! The message-sending method gets called after the transaction has committed successfully and then the message processor can see the entity in the persistence context, as is needed. My one suggestion would be, in the raiseTransactionSuccessEvent, if the components.xml is not correct, instead of throwing a mysterious NullPointerException, maybe give a little more info, like a message that says "is core:transactionListener in your components.xml file?" I say this because this is a problem that will come up any time a Seam component method sends an entity to a message queue and the message queue needs to attach the entity. That's something that should be a fairly common usage in cases where messages are being used. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013883#4013883 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013883

19 years, 2 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: Please help I am very close here

by PeterJ

The application you deployed is looking for a datasource by that name. Did you set up a *-ds.xml file? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013874#4013874 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013874

19 years, 2 months

1
0
0 / 0

[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

1
0
0 / 0

[JBoss Portal] - Re: Blobs are not cacheable

by dduchaine

Deleted the data directory (belonged to a previous 2.4 installation) That did it. Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013871#4013871 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013871

19 years, 2 months

1
0
0 / 0

[JBoss jBPM] - Transaction problem in JBPM via EJB

by skpeddi

Transaction problem: Scenario:EJB(Transaction starts)------------>JBPM(creating a processInstance)One more transaction starts If we say jbpmContext.close() ,new processInstanceid should be created but transaction will not be committing. EJB starts one transaction and internally EJB calls jBPM related method. We are setting TransactionEnabled as "false" which means EJB related transaction should be continue. But we are not able to commit in to the JBPM database (not updating into the database). If we say transactionEnabled as "true" that will be working Could any body can help me on this issue Any one can suggest how to set the two transactions continuous Thanks Suresh View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013869#4013869 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013869

19 years, 2 months

1
0
0 / 0

[JBoss Portal] - Re: Blobs are not cacheable

by sohil.shah＠jboss.com

Try this- go to jboss-portal.sar/portal-cms.sar/META-INF/jboss-service.xml In there wherever you find HibernatePeristenceManager replace with JBossCachePeristenceManager then go to your server configuration and blow away your data folder Restart and see if this fixes it Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013865#4013865 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013865

19 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user February 2007