[JBoss jBPM] - Re: Indentityservice- Jbpm4
by nilspreusker
Hi shekharv, thanks for the hint. However, I've seen your post before and tried the configuration that you mentioned there, but it doesn't seem to work with the current trunk version of jBPM4. I just realized, though, that there might be a better way to achieve what I'm trying. I'm integrating jBPM with an application that has its own User implementation. Now I want jBPM to use the same user table that my application is using. My initial idea was to implement my own IdentitySession and cast the users that I retrieve into org.jbpm.api.identity.User objects. But now I'm thinking that it would probably be better to just tell jBPM how to access the user table of my application by modifying the hibernate mapping of org.jbpm.api.identity.User. Maybe someone can give me a hint whether I'm heading into the right direction and (if you're feeling very generous:) give me some hints which files to edit to get the user mapping tweaked to my needs. Thanks in advance!
Nils
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240512#4240512
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240512
16 years, 10 months
[Installation, Configuration & DEPLOYMENT] - Migrating JBoss 4.0.2 -> JBoss 5.0.0
by joaocarlos86
All,
i've suceffull migrate from jboss 4.0.2 to jboss 5.0.0, but when i try to deploy my app the exception is related:
|
| org.hibernate.AnnotationException: @OneToOne or @ManyToOne on br.unp.portal.menuPaginas.dominio.Item
| AdministrativoPagina.itemAdministrativo references an unknown entity: br.unp.portal.usuariosPermisso
| es.dominio.ItemAdministrativo
| at org.hibernate.cfg.FkSecondPass.doSecondPass(FkSecondPass.java:56)
| at org.hibernate.cfg.AnnotationConfiguration.processFkSecondPassInOrder(AnnotationConfiguration.jav
| a:474)
| at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:295)
| at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1319)
| at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915)
| at br.unp.arq.dao.Database.getSessionFactory(Database.java:56)
| at br.unp.arq.dao.Database.getSessionRequest(Database.java:111)
| at br.unp.arq.dao.Database.getSessionNoLog(Database.java:76)
| at br.unp.arq.dao.GenericDAO.getSession(GenericDAO.java:299)
| at br.unp.arq.dao.GenericDAO.<init>(GenericDAO.java:42)
| at br.unp.arq.dao.GenericDAO.<init>(GenericDAO.java:53)
| at br.unp.arq.controller.AbstractControllerCadastro.<init>(AbstractControllerCadastro.java:29)
| at br.unp.portal.controller.AbstractControllerPortal.<init>(AbstractControllerPortal.java:33)
| at br.unp.portal.menuPaginas.controller.JPortalMBean.<init>(JPortalMBean.java:199)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java
| :27)
| at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
| at java.lang.Class.newInstance0(Class.java:355)
| at java.lang.Class.newInstance(Class.java:308)
| at org.apache.myfaces.config.annotation.TomcatAnnotationLifecycleProvider.newInstance(TomcatAnnotat
| ionLifecycleProvider.java:48)
| at org.apache.myfaces.config.ManagedBeanBuilder.buildManagedBean(ManagedBeanBuilder.java:85)
| at org.apache.myfaces.el.unified.resolver.ManagedBeanResolver.createManagedBean(ManagedBeanResolver
| .java:198)
| at org.apache.myfaces.el.unified.resolver.ManagedBeanResolver.getValue(ManagedBeanResolver.java:164
| )
| at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
| at org.apache.myfaces.el.unified.resolver.FacesCompositeELResolver.getValue(FacesCompositeELResolve
| r.java:140)
| at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
| at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:61)
| at org.apache.el.parser.AstValue.getValue(AstValue.java:107)
| at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186)
| at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:925)
| at org.apache.jsp.jportal.sites.sistemas.autoatendimento.principal.cpdj5_jsp._jspService(cpdj5_jsp.
| java:111)
| at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
| at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
| at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322)
| at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
| 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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638)
| at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:444)
| at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382)
| at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310)
| at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImp
| l.java:341)
| at org.apache.myfaces.application.jsp.JspViewHandlerImpl.buildView(JspViewHandlerImpl.java:486)
| at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:337)
| at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41)
| at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:155)
| at org.apache.myfaces.webapp.MyFacesServlet.service(MyFacesServlet.java:103)
| at br.unp.arq.controller.ArquiteturaFacesController.service(ArquiteturaFacesController.java:43)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290
| )
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
| at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:341)
| 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:235)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
|
| at org.jboss.web.tomcat.service.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:109
| )
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablish
| mentValve.java:126)
| at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishm
| entValve.java:70)
| 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:158)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
| at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
|
| at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
| at java.lang.Thread.run(Thread.java:619)
|
|
i'm using the default version of hibernate/annotation that come on with jboss 5.0.0.
after reading some in google about this i've found conflicting versions of hibernate/annotation and i'm adjusting this, removing the old implementation on lib folder of my project. the same annotations works in jboss 4.0.2 and i just dont know what to do. thanks folks.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240508#4240508
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240508
16 years, 10 months
[JBoss Messaging] - Questions on JBoss Messaging 1.4
by unwavering
Dear all,
I have some questions:
Q1: How can I override the message header fields from JBoss Messaging 1.4? The reason is that I don't want the clients to control the message expiry and priority information.
Q2: What's the complete scenario which will cause a message to be moved to the DLQ? Does this happen when the consumer fails to process the message and sends a special acknowledgment as a result?
Q3: If I configure the server to set the expiration time to any message to infinity (no expiration), do I still need to have a default expiry queue?
Q4: Is moving a message to a DLQ dependent only on the consumer response? In other words, is there any scenario which will cause the server to move a message to a DLQ without the consumer's intervention?
Thanks a lot for your time.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240504#4240504
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240504
16 years, 10 months
[JBoss jBPM] - Re: Help needed in deploying 'par' to JBoss server
by vignesh57
Hi ronald,
Thanks for the reply & the humorous quote !
And F.Y.K.I, i am trying this for more than 2 days & also this is the first ever FORUMN POST in my life !!!
And Sorry for giving less information. i am a newbie to jBPM and NOT a jBPM architect(like u).
There are two ways i know of deploying a process definition.
O Use the DEPLOYMENT tab while designing the jPDL in Eclipse IDE
O Use the "Deploy Process" option in jBPM console, choose the par file & deploy it.
Automating deployment....
These are manual tasks. I am trying to automate it. I also saw Ant Scripts that deploy a par but i want to do it through java code.
What i tried...
What i posted previously is a stand-alone java code. I found that it is not able to connect to the jBPM database.
-> While parsing the source file with parsePar, i got a classNotFound exception which i got rid of by importing the Java Transaction API(jta.jar) to Eclipse Build path.
-> Now the Code runs successfully without any errors but the file is not deployed when i checked in jBPM console.
-> I tried to get the list of process definitions. The size of List is found to be ZERO. This means that my code is not able to reach the jBPM hypersonic DB.
I used these two methods.
O ProcessDefinition.parseParZipInputStream
O deployProcessDefinition
What is the jBPM class that i should actually use ?
Is there a jBPM community article that discuss this scenario ?
How can i gain visiblity to the jBOSS deployment directory and connectivity to the jBPM database ?
Do i need to specify somewhere, like the jBPM database used & server path in a config file ?
My Enviroment:
Server : JBoss 4.2.X
jBPM : 3.X
Database : Default db. (Hypersonic)
Please ask me if you need any other information regarding this.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240493#4240493
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240493
16 years, 10 months
[JBoss jBPM] - Re: EJB Timer Lookup problem in BPEL
by zoegraddy
I am also seeing the "org.jbpm.JbpmException: ejb timer entity lookup" exception but it appears to be some sort of bootstrap issue. My process definition has a decision node where one possible path goes to a task-node with a task that has a timer. The other path does not have any timers. This exception is thrown each time a process instance reaches the timer and the timer does not fire when the due date is reached. This results in process instances sitting at the timer indefinitely.
The only workaround I have found is to immediate walk a process instance through the non-timer path of the process definition after jboss starts up (we have jbpm deployed inside jboss). Then, when any subsequent processes take the timer path, no exception is thrown and everything works perfectly. This is of course not an ideal solution as we have to remember to do this hack each time our server starts up.
Any help is much appreciated!
Zoe
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240487#4240487
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240487
16 years, 10 months