[JBoss Seam] - Re: Persistence context propagation.
by mangri3000
I try to explain a little more.
Our system has two interfaces, a web-ui and a messaging based interface to another system.
Messaging requests come this way:
MessageController (MDB) -> Core (SLSB and Entities) -> DAOs (SLSBs) -> Hibernate
UI requests go the other way:
Web-UI -> Application (Seam components) -> Core -> DAOs -> Hibernate
DAOs use entity managers injected by "@PersistenceContext". I cannot use @In because otherwise the messaging scenario wouldn't work.
For messaging requests I need a transaction-scoped PC which I get for free by the default EJB PC propagation.
For the Web-Client requests I need a conversation-scoped PC. I thougth I could simply attach a SMPC or BMPC to every transaction (EntityManager.joinTransaction) in the application-layer and do not have to change the layers below.
Maybe there is not such a simple solution.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069692#4069692
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069692
18Â years, 8Â months
[JBoss jBPM] - Re: java.lang.NoClassDefFoundError: javax/transaction/Synchr
by mr.lou
Hmm, right.
The database tables are not created autmatically. At least not until you write an additional property to the hibernate.cfg.xml file. I have found a smal section about this in the User Guide.
7.6.2. The jBPM DB schema:
http://docs.jboss.com/jbpm/v3/userguide/persistence.html#thejbpmdbschema"
So far so good.
I have added this property and ran the class again. The deployment seems to work. There is no exception at this point any longer. But now - I got another exception (Of course!) and I don't know what to do. It allways occurses when I try to close a JBPMContext in the following way: jbpmContext.close();
The exception:
anonymous wrote :
| problem closing service 'persistence'
| org.jbpm.JbpmException: no jbpm tx service configured
| at org.jbpm.persistence.db.DbPersistenceService.isRollbackOnly(DbPersistenceService.java:390)
| at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:212)
| at org.jbpm.svc.Services.close(Services.java:222)
| at org.jbpm.JbpmContext.close(JbpmContext.java:139)
|
Seems like there is something wrong with that 'tx service'. I have investigated a long time, but still have no idea what this tx service is about. I found a class called org.jbpm.tx.TxService but there is no real description about this class or even the hole package.
Maybe there is someone out there who can tell me how to fix this problem and what this "tx service" is about. I really would like to know! :)
thank!
lou
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069691#4069691
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069691
18Â years, 8Â months
[JBoss Seam] - Re: external authentication-any pointers for a beginner?
by mwkohout
It's still not working. Setting the pages.xml entries(and updating to HEAD of cvs) like so:
| <navigation>
| <rule if-outcome="home">
| <redirect view-id="/home.xhtml"/>
| </rule>
| </navigation>
| </page>
|
| <page view-id="/home.xhtml" scheme="https">
| <restrict>#{identity.isLoggedIn(true)}</restrict>
| </page>
|
resulted in identical behavior.
Setting the login-requred parameter to true resulted in me being forwarded to seam-gen's login.xhtml view. I understand why that's happening-because of the exception handler listed below...but I'm not sure what I should do to make it hit my authentication code. Subclass Pages?
| <page view-id="*">
| <navigation>
| <rule if-outcome="home">
| <redirect view-id="/home.xhtml"/>
| </rule>
| </navigation>
| </page>
|
| <page view-id="/home.xhtml" login-required="true" scheme="https">
| </page>
| <exception class="org.jboss.seam.security.NotLoggedInException">
| <redirect view-id="/login.xhtml"/>
| </exception>
|
any ideas? where in the seam code itself should I be looking so I can debug this behavior?
thanks again
Mike Kohout
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069684#4069684
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069684
18Â years, 8Â months
[JBoss Seam] - EntityConverter: Entity Manager not found
by Newlukai
Hi there,
I've encountered a strange behavior in my application. There are several s:selectItems on a page using s:convertEntity to display dropdown-boxes filled with entities.
<ice:selectOneMenu value="#{userSelector.selectedUser}" partialSubmit="true">
| <s:selectItems value="#{userSelector.users}" var="user" label="#{user.ID} - #{user.name}" noSelectionLabel="#{ares_messages.filter_all}" />
| <s:convertEntity />
| </ice:selectOneMenu>
When the page is rendered the first time, the dropdowns are rendered as they should be. So I think everything is fine with the EntityManager.
Below the dropdowns there's a dataTable. The dataTable shows some information according to the selected items in those drop-downs. With a commandLink you can select an entry to display further information.
<h:column>
| <f:facet name="header">
| <ice:commandSortHeader columnName="id">
| <h:outputText value="#{ares_messages.label_testaction_ID}" />
| </ice:commandSortHeader>
| </f:facet>
| <ice:commandLink value="#{testaction_var.ID}" action="#{testactionDeveloper.select(testaction_var)}" />
| </h:column>
As you can see I use Seam's EL enhancement to let the backing bean know which item was clicked.
OK. Let's remember that the page was displayed normally. Now I click on a commandLink to display further information resulting in a message "Error selecting object" in the h:message tag. The console tells me that "ERROR [EntityConverter] Entity Manager not found".
But why? The EntityConverter has already converted the entities from the database. Why isn't it possible to select an item in the datatable?
Thanks in advance
Newlukai
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069683#4069683
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069683
18Â years, 8Â months