I wonder if anyone has encountered the same problem described here?
I am having the same problem. My EAR contains a module app.jar, which contains the persistence.xml file:
| <persistence-unit name="myDB">
Where the appDS is deployed with a xxx-ds.xml file with no problem. However, I am getting the same NoInitialContextException.
I tried to deploy the app.jar under module/java as well as module/ejb but same problem. I also tried to add:
| <property name="java.naming.factory.initial" value="org.jnp.interfaces.NamingContextFactory" />
| <property name="java.naming.factory.url.pkgs" value="org.jboss.naming:org.jnp.interfaces" />
to the persistence.xml file and same error.
I have no clue what is wrong. It's deployed to the server so no jndi.properties file should be needed. If so, why this error occurs?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109449#4109449
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109449
I've seen reference to a book: Business Process Management with JBoss jBPM book by Matt Cumberlidge which you may want to check, but I have doubts on whether it can be up-to-date, unless there is an online version that he constantly updates.
I too wish jBPM was better documented, that is it's main weakness as a "product" for developers such as myself who need to integrate workflow into their system in a timely manner. My opinion is that right now, jBPM is not so much a product that is ready to be easily used by developers, but more of a toolkit for consultants who want to provide workflow solutions for their customers. Such consultants are prepared to thoroughly read all the code and reverse-engineer how it all works and somewhat specialize in workflow solutions. jBPM seems to be beautifully written code but not much guidance for best practice usage or thorough explanation of the concepts and features. As time goes on hopefully better documentation will arise.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109441#4109441
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109441
Those are good ideas. I'll have to check more into the "script" tag, there are many features in jBPM which I'm not very familiar with yet that could provide solutions.
I'd also like the designers to consider adding a "user object" property (setUserObject(Object userObject), getUserObject()) to most of the main jBPM objects (ProcessDefinition, ProcessInstance, Task, TaskInstance, ...). The only requirement is that the user object be serializable.
It would also be nice to be able to create such a user object in the processdefinition.xml file using the same delegation syntax as for custom classes (such as ActionHandler classes). The tag or tag attribute and location would indicate if it belongs to the ProcessDefinition, ProcessInstance, Task, TaskInstance, Node, NodeInstance etc. The versatility of a user object is very great.
As a matter of fact, the open source JGraph (which we use to draw our workflow graphs based on the gpd.xml file and ProcessDefinition), allows a "user object" for each object in the graph (vertices and edges). It is immensely useful.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109439#4109439
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109439
"phejl" wrote : I some did more investigation with jboss 4.2.2 and jboss 5 beta2, here is what I observed (don't take it as an unchangeable fact).
| With jboss 4 it seems to me that PersistentContext in servlet or webservice is ignored completely (jboss 4 is not ee 5 certified - provides ejb3 and ee5 web apps, however not sure if wired properly).
| When using jboss 5 server noticed the annotation however wasn't able to load the proper context (maybe really problem with wiring jpa and web, since it is still beta).
| Maybe somebody from jboss could tell you more...
Thanks for doing some checking.
I have been trying some of the Seam 2.0.0 demos (deploying to my 4.2.2 JBoss) and tutorials and ran seam-gen using my database.
I got this to work. And in the set of generated files I see a persistence.xml and a components.xml.
I think I see some interesting bits:
In the generated persistence.xml I see:
| <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
| <property name="hibernate.hbm2ddl.auto" value="validate"/>
| <property name="hibernate.show_sql" value="true"/>
| <property name="hibernate.format_sql" value="true"/>
| <property name="jboss.entity.manager.factory.jndi.name" value="java:/AfmsttModernizationSeamEntityManagerFactory"/>
and in components.xml I see:
These seem like config options that may help the wiring to complete the circuit if I add them in the right place in my war file.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109438#4109438
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109438