[JBoss jBPM] - Re: Ripping out identity component
by jbpmndc
in hibernate.cfg.xml follow the directions to comment out the user,group and membership objects.
Then, you can just delegate the security to your application container and manage access using the container's built in security mechanism.
A lot can be discussed about when you should do this and when you should not. It seems to me that because jbpm is really just a jar, a lot of time you can rely on the app server for security.
|
| <!-- following mapping files have a dependendy on -->
| <!-- 'jbpm-identity-{version}.jar', mapping files -->
| <!-- of the pluggable jbpm identity component. -->
| <!-- comment out the following 3 lines if you don't-->
| <!-- want to use the default jBPM identity mgmgt -->
| <!-- component -->
| <mapping resource="org/jbpm/identity/User.hbm.xml"/>
| <mapping resource="org/jbpm/identity/Group.hbm.xml"/>
| <mapping resource="org/jbpm/identity/Membership.hbm.xml"/>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961123#3961123
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961123
20 years, 1 month
[JBoss Seam] - Re: Outjection of previous value: selectOneMenu : One 2 Many
by kryptontri
When I modifiy the code, just when I think I have cracked it, I get
| java.lang.IllegalStateException: Client-id : _id0 is duplicated in the faces tree.
| at org.apache.myfaces.application.jsp.JspStateManagerImpl.checkForDuplicateIds(JspStateManagerImpl.java:241)
| at org.apache.myfaces.application.jsp.JspStateManagerImpl.checkForDuplicateIds(JspStateManagerImpl.java:255)
| at org.apache.myfaces.application.jsp.JspStateManagerImpl.saveSerializedView(JspStateManagerImpl.java:204)
| at org.jboss.seam.jsf.SeamStateManager.saveSerializedView(SeamStateManager.java:46)
|
I'm trying all sorts of ways, I am setting the @In Rate to be null upon insertion, but this value still shows up in the selectItem value,
I have tried:
- upon insertion, removing the rate in the context
| private void clearRatesOnDisplay() {
| Contexts.getPageContext().remove("rate");
| //Contexts.getPageContext().remove("ratesManager");
| rate = null;
| selectedRate = null;
| }
|
changed the javabean that provides the values in the menu to EVENT
| @Name("ratesManager")
| @Interceptors(SeamInterceptor.class)
| @Scope(ScopeType.EVENT)
| public class Rates {
| public Rates() {
| log.info("** Rates (RatesManager) instantated **");
| }
| ...
|
but stil no luck :-|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961118#3961118
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961118
20 years, 1 month
[EJB/JBoss] - ejbFindByPrimaryKey, locking, and consistency
by dkMazz
I have an inventory system that uses session facade on the backend. The front end is a page that shows inventory items and the user can select one of the items and be taken to a details page.
My question is:
When the user is on the details page, will the JBoss session facade block another user from accessing the details page for the same item? Or do I need to code to prevent this myself? My thinking is that internally, an entity bean exists in memory for the DB rowid of the item being viewed. Then when another user tries to do ejbFindByPrimaryKey for the same item ID, the ejb container should return an error because someone else is already using it, right? Or is the JBoss EJB container smart enough to allow two people to both view and potentially modify the same data while enforcing consistency?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961116#3961116
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961116
20 years, 1 month