[JBossCache] - Re: JBossCache with Hibernate on Glassfish v2
by manik.surtani@jboss.com
"eric.hubert" wrote : "genman" wrote :
| | I don't personally have a problem with wanting to know about these things
| |
| With due respect I wouldn't care much about you having those problems. ;)
|
lol!
"eric.hubert" wrote :
| So at the moment I have to think about how to solve my problem best. I could write my own implementation of the CacheProvider interface. But would that be clever? It seems to be a good idea to also use the underlying logic of the CacheFactory.
|
| If I got it right I had to register the CacheJmxWrapperBean with Glassfish's MBean-Server and change the way how the MBeanServer is located. Seems pretty simple, If that would be all. Well, I guess I'll see.
| It might be a good idea to make the MBeanLookup-Code exchangeable.
|
|
I haven't looked into it much, but if you can write a CacheProvider that *does* in fact use a generic lookup - perhaps try a JBoss-specific lookup as in the current provider, and if that fails, fall back to a generic getPlatformMBeanServer(), and failing that as well, perhaps look in a "known location" in JNDI.
This is a part of the Hibernate codebase though, and it may be a good idea to make suggestions there as well.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108052#4108052
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108052
18 years, 5 months
[JBoss jBPM] - Re: JBoss jBPM - BPeL - eclipse
by Pebbels
Hi Agus,
I thank you a lot for the hints. I now unserstand a lot more but I have new problems:
When calling ant deploy-definition in the directory examples/hello I get the following error:
BUILD FAILED
| C:\downloads\jbpm-bpel-1.1.Beta3\jbpm-bpel-1.1.Beta3\jbpm-bpel-1.1.Beta3\example
| s\common\bpel-build.xml:60: deployment failed, see details in the server console
The server console says
13:53:01,921 ERROR [[processDeployServlet]] Servlet.service() for servlet processDeployServlet threw exception
| java.lang.AbstractMethodError: org.jbpm.bpel.xml.ArchiveWsdlLocator.close()V
| at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2339)
| at org.jbpm.bpel.xml.BpelReader.readWsdlDocument(BpelReader.java:420)
| at org.jbpm.bpel.par.DefDescriptorArchiveParser.readDocuments(DefDescriptorArchiveParser.java:102)
| at org.jbpm.bpel.par.DefDescriptorArchiveParser.readFromArchive(DefDescriptorArchiveParser.java:59)
| at org.jbpm.jpdl.par.ProcessArchive.parseProcessDefinition(ProcessArchive.java:81)
| at org.jbpm.bpel.web.ProcessDeployServlet.doGet(ProcessDeployServlet.java:50)
| 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)
Do you have an idea what the problem is?
Thanks Tina
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108051#4108051
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108051
18 years, 5 months
[JBoss Seam] - transaction failed" using injected JavaBean
by d00roth
Hi all,
I have struggled some time with a problem I get when trying to persist some objects. I use the exact same setup as jboss-seam-jpa running om tomcat6 without jboss embedded. (JavaBean an POJO:s).
Persisting an object with
| @Name("register")
| public class RegisterAction {
| @In
| private EntityManager em;
|
| public void register() {
| em.persist(someObject);
| }
| }
|
works perfectly, even without the @Transactional annotation. However this:
| @Name("register")
| public class RegisterAction {
| @In
| private MyService service;
|
| public void register() {
| service.register(someObject);
| }
| }
|
| @Name("service")
| @AutoCreate
| public class MyService {
| @In
| private EntityManager em;
|
| public void register(Object someObject) {
| em.persist(someObject);
| }
| }
|
does not work(and I have tried using @Transactional on 'register' and MyService). I get a "Transaction failed" in my jsf h:messages, but apart from that, there is no error message what so ever.
I guess I have missed something fundamental, especially when I read this in the Seam doc:
anonymous wrote : 25.3... Seam JavaBean components do not provide declarative transaction demarcation like session beans do. You could manage your transactions manually using the JTA UserTransaction or declaratively using Seam's @Transactional annotation. But most applications will just use Seam managed transactions when using Hibernate with JavaBeans.
anonymous wrote : 1.2.1.2... Our session bean action listener performs the business and persistence logic for our mini-application. In more complex applications, we might need to layer the code and refactor persistence logic into a dedicated data access component. That's perfectly trivial to do. But notice that Seam does not force you into any particular strategy for application layering.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108048#4108048
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108048
18 years, 5 months