August 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: How to get EntityManager without @In?

by gothmog

Thanks guys for all your help, I learnt a lot on this thread. In the end I just wrote a SLSB using a @PersistenceContext annotation to get my EntityManager then I just did a lookup via JNDI in the housekeeping thread to get it then called a write method on it passing the object requiring the housekeeping. Thanks Troy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079958#4079958 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079958

16 years, 10 months

1
0
0 / 0

[JBoss Seam] - Re: Exception calling stateful session bean default @Remove

by wise_guybg

anonymous wrote : (check that it is declared on the session bean business interface) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079956#4079956 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079956

16 years, 10 months

1
0
0 / 0

[JBoss Seam] - Re: Seam conflict with a4j:include and a4j:support

by pete.muir＠jboss.org

jgilbert: I'm going to need a test case for this. Create a new seam-gen'd app, add enough code to reproduce your problem, remove the lib directory, zip it up, email it to me (or add to a new jira issue) and include reproduction steps. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079955#4079955 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079955

16 years, 10 months

1
0
0 / 0

[JBoss jBPM] - Help on Best Practice

by tweedledee

Hi, I'm looking for some guidance on best practice with jBPM; I have a scenario where a process forks into two nodes that perform some business validation by calling separate independent services before returning and continuing the process flow. My question concerns the reporting of business exceptions thrown by the services; I need to return the exceptions (note the plural) to the UI layer, which in this case is a web page. What is considered to be best practice in this scenario? Should I be using process variables to hold the exceptions or use some other approach? Any guidance would be greatly appreciated. Reagrds, Paul. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079954#4079954 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079954

16 years, 10 months

1
0
0 / 0

[EJB/JBoss] - Re: how to exclude a caller in interceptor

by john_woo＠canada.com

"waynebaylor" wrote : you could try something like: | | | | <typedef | | name="intercept_this" | | expr="class(my.package.*)"/> | | | | <typedef | | name="dont_intercept" | | expr="class($instanceof{@MessageDriven})"/> | | | | <pointcut name="myPointcut" | | expr="execution(public * $typedef{intercept_this}->*(..)) | | AND !execution(publiic * $typedef{dont_intercept}->*(..))"/> | | | | <bind pointcut="myPointcut"> | | <interceptor class="the.interceptor.MyInterceptor"/> | | </bind> | | | | notice the use of AND along with the !(not). Thanks lots. Can you tell where I can find more examples and the explanation for the descriptor? John Toronto View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079953#4079953 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079953

16 years, 10 months

1
0
0 / 0

[JBoss Seam] - Exception calling stateful session bean default @Remove meth

by urswag

This method generates an exception Exception calling stateful session bean default @Remove method What have I to change? | @End | @Destroy | @Remove | public void destroy() { | | } | | 13:36:23,086 WARN [Component] Exception calling stateful session bean default @Remove method: missionService | java.lang.IllegalArgumentException: method not found: destroy for component: missionService (check that it is declared on the session bean business interface) | at org.jboss.seam.Component.callComponentMethod(Component.java:1975) | at org.jboss.seam.Component.callDefaultRemoveMethod(Component.java:1868) | at org.jboss.seam.Component.destroy(Component.java:1227) | at org.jboss.seam.contexts.Contexts.destroy(Contexts.java:251) | at org.jboss.seam.contexts.Contexts.destroyConversationContext(Contexts.java:413) | at org.jboss.seam.contexts.Lifecycle.endSession(Lifecycle.java:236) | at org.jboss.seam.contexts.ServletLifecycle.endSession(ServletLifecycle.java:132) | at org.jboss.seam.servlet.SeamListener.sessionDestroyed(SeamListener.java:49) | at org.apache.catalina.session.StandardSession.expire(StandardSession.java:702) | at org.apache.catalina.session.StandardSession.expire(StandardSession.java:660) | at org.apache.catalina.session.StandardSession.invalidate(StandardSession.java:1111) | at org.apache.catalina.session.StandardSessionFacade.invalidate(StandardSessionFacade.java:150) | 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.seam.contexts.FacesLifecycle.invalidateSession(FacesLifecycle.java:112) | at org.jboss.seam.contexts.FacesLifecycle.endRequest(FacesLifecycle.java:89) | at org.jboss.seam.jsf.SeamPhaseListener.afterRender(SeamPhaseListener.java:515) | at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:230) | at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:184) | at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) | at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) | at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) | at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:87) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:63) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:46) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) | at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) | at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:40) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:63) | at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) | at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:140) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | 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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:619) | Caused by: java.lang.NoSuchMethodException: org.javassist.tmp.java.lang.Object_$$_javassist_14.destroy() | at java.lang.Class.getMethod(Class.java:1605) | at org.jboss.seam.Component.callComponentMethod(Component.java:1954) | ... 58 more | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079952#4079952 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079952

16 years, 10 months

1
0
0 / 0

[JBossCache] - Re: How to configure JGroups on hosts with redundant network

by bela＠jboss.com

You can set a bind address using bind_addr="1.2.3.4" in the XML file, or overriding this with -Djgroups.bind_addr=1.2.3.4 (or -Dbind.address=1.2.3.4). Again, IP Bonding would probably solve your issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079951#4079951 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079951

16 years, 10 months

1
0
0 / 0

[JBossCache] - Re: How to configure JGroups on hosts with redundant network

by mkrzemien

It is probably due to my configuration. E.g. when starting an instance, the GMS address presented is always eth0 (single NIC address; though I don't know whether GMS part has anything to do with this problem). Another test that failed (environment and configuration like in previous post): - before starting JBossCache instances disconnected link eth0-to-eth0 - started both JBossCache instances ! instances work but there is no replication But if the link eth1-to-eth1 was disconnected at the beginning, the replication would work fine. Obviously it is not how it should work. Kind regards Mariusz View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079950#4079950 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079950

16 years, 10 months

1
0
0 / 0

[EJB/JBoss] - Re: Thread.getContextClassLoader() and scoped classloading

by be326814

Found my own answer. I did use local ejb-refs, when I switched to remote it worked ok. Man, somethimes the cause can be so far from the problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079947#4079947 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079947

16 years, 10 months

1
0
0 / 0

[JBoss Seam] - Re: How to get EntityManager without @In?

by gothmog

Thanks for the suggestions, I tried the beginCall() ... endCall() on the lifecycle and yes that does work, I can get an EntityManager in my thread however back to the original problem, the entity manager has not started a transaction for me, so nothing gets posted to the db and when I flush I get | 23:15:43,708 ERROR [STDERR] Exception in thread "Thread-21" | 23:15:43,708 ERROR [STDERR] javax.persistence.TransactionRequiredException: no transaction is in progress | 23:15:43,708 ERROR [STDERR] at org.hibernate.ejb.AbstractEntityManagerImpl.flush(AbstractEntityManagerImpl.java:293) | 23:15:43,708 ERROR [STDERR] at org.jboss.seam.persistence.EntityManagerProxy.flush(EntityManagerProxy.java:90) | 23:15:43,708 ERROR [STDERR] at model.EXAccessPoint.flushToDb(EXAccessPoint.java:236) | 23:15:43,708 ERROR [STDERR] at model.EXBackgroundThread.run(EXBackgroundThread.java:36) | 23:15:44,282 INFO [EXAccessPoint] calculateEx():from=11:15:39 PM;now=11:15:44 PM;exs.size()=3;currentStartIndex=2 | The code inside the thread does this at the moment | Lifecycle.beginCall(); | EntityManager em = (EntityManager)Component.getInstance("em", true); | ... | em.persist(...); | ... | em.flush(); | Lifecycle.endCall(); | I'll try JNDI directly... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079946#4079946 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4079946

16 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user August 2007