If I take the process line out, I'd expect the jbpm component still to be initialized and the jbpm-related tables to be created. Just the actual process definition shouldn't be deployed to the database, right?
Instead of getting this behavior, none of the jbpm_* named tables are created at startup anymore.
Interestingly, the component org.jboss.seam.core.jbpm shows up in the list of managed components at server startup, but no tables are created, even if auto.ddl is set to create.
Is the property "processDefinitions" mandatory?
If I put the line back in, everythings fine again.
Regards, Kurt
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968004#3968004
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968004
One other thing to say about Tomahawk: I have never written AJAX-type JavaScript in my life. I am almost completely ignorant of how JavaScript works. And now I'm using Tomahawk and adding some very cool AJAX-style features to my pages, like popups, sortable tables, etc, without knowing a single thing about JS. This is cool! I don't want to learn JS, I just want to make cool web applications.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968003#3968003
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968003
I just read from a different topic (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89223) that I started that it isn't possible to resolve entity beans over JNDI but that you have to add them to each ear project.
I already got this working but there is a trapdoor. Each ejb jar that needs to be able to work with the entity-manager needs a persistence.xml. The problem lies in the ejb jar that doesn't house the entity classes but only uses them. In the persistence.xml in this ejb you need to define, next to the datasource, which classes are entity classes. Normally the easiest way to do this is as following:
| <?xml version="1.0" encoding="UTF-8"?>
| <persistence xmlns="http://java.sun.com/xml/ns/persistence"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/persistencehttp://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
| version="1.0">
|
| <persistence-unit name="MyEntityManager" transaction-type="JTA">
| <jta-data-source>java:/MyDS</jta-data-source>
| <jar-file>../dataEJB.jar</jar-file>
| <properties></properties>
| </persistence-unit>
|
| </persistence>
|
The jar-file property links to the jar file where the entity beans can be found. The entityManager should scan this jar for the entities and the problems is solved. But because of a bug in the jboss implementation of ejb3 the path to the jar file isn't resolved correctly.
Luckily there is another way to define the entity classes. It isn't pretty but the only solution until they fix the bug (I hope they will do that soon). By using the class tag you can define each class that are entity classes:
|
| <?xml version="1.0" encoding="UTF-8"?>
| <persistence xmlns="http://java.sun.com/xml/ns/persistence"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/persistencehttp://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"
| version="1.0">
|
| <persistence-unit name="MyEntityManager" transaction-type="JTA">
| <jta-data-source>java:/MyDS</jta-data-source>
| <class>my.package.User</class>
| <class>my.package.SomeOtherEntity</class>
| <properties></properties>
| </persistence-unit>
|
| </persistence>
|
|
I hope this prevents hours of work ;).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967998#3967998
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3967998
