>please don't expect us to be clairvoyant
Plz don't be satirical. If you found that my description is not sufficient tell me.
All what I want to say are the following: normal procedures that causes a change in the database, don't cause any change at all, i.e. if I create a ProcessDefinition and deploy it, I should navigate to JBPM_PROCESSDEFINITION table to find that it has 1 new row, I found that it contains 0 rows.
What makes me not to describe the details of the problem, is that I'm new to JBPM, and i think that a lot of you have faced this problem before.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035413#4035413
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035413
What is the local interface for SessionBeanB? I'm guessing you are injecting into a field of the bean tye not the interface type (i.e. SessionBeanBLocal not SessionBeanB). Are you seeing anything in the logs at deployment time?
The default JNDI bindings for an EJB3 are ejbName/remote and ejbName/local for the remote and local business interfaces. If the EJB3 is deployed in an .ear, the default jndi bindings are earName/ejbName/remote and earName/ejbName/local. You can override the default with the @RemoteBinding and @LocalBinding annotations or the <jndi-name> and <local-jndi-name> in jboss.xml
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035410#4035410
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035410