Dear Mr
you have to integrate identity managment system used in your ERP system in jbpm;
its easy because jbpm use seperate jar file and loosely coupled interface for identity managment ;
then its better to use specific features for jbpm general nodes to specify Graph nodes for your own system ;
you have to handle taskinstance and GUI for them in your manner;
i suggest to dont change jbpm core for compatiblity
use general controllers , assignements , Handlers for your needs
best regard
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971229#3971229
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971229
Do you see a jbpm.war in the jboss console?
It appears that jboss is running fine, but for some reasons its not letting you deploy the app.
Try putting the war
anonymous wrote :
| D:\Binaries\jbpm-3.1.2/build/jbpm.war
|
into jboss jbpm config deploy folder.
This should work as long as the war file was successfully created.
Also you will need to run create-db task in the deploy.build.xml.
Regards,
Jitendra
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971226#3971226
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971226
No, he means source tag files such as
| <h:composition>
| <my:input value="#{entity.property}" />
| </h:composition>
|
my.input.xhtml
| <h:input value="#{value}" >
| <s:validate />
| </h:input>
|
The consensus seems to be that this a limitation in EL that should be fixed. I work around it by specifying the entity.property as a string as well as a value binding for my source tags
| <h:composition>
| <my:input value="#{entity.property}" id="entity.property"/>
| </h:composition>
|
my.input.xhtml
| <h:input value="#{value}" >
| <s:validate for="#{id}" />
| </h:input>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971225#3971225
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971225
@denis-karpov:
You mean, something like this does fail?:
template (common stuff like the form or action buttons)
| <h:form>
| <s:validateAll>
| <ui:insert name="stuffToEdit" />
| <... save, delete and cancel button.... >
| </s:validateAll>
| </h:form>
|
concrete input fields
| <ui:define name="stuffToEdit">
| <h:inputText....>
| ....
| </ui:define>
|
I can only say that this works perfectly for me. I just tested it with an org.hibernate.validator.Pattern annotation on an Entity bean. And the annotated property is correctly marked as invalid during process_validations phase :).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971222#3971222
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971222
Im running jboss-4.0.4.GA with EJB3, where webpart is clustered.
In my web.xml i have this:
| <servlet>
| <servlet-name>StartupServlet</servlet-name>
| <servlet-class>no.tv2.nettavisen.privateeconomicadvice.StartupServlet</servlet-class>
| <load-on-startup>1</load-on-startup>
| </servlet>
What happend is the only one Servlet is started in the cluster, how can I force it to start one for each server ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971218#3971218
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971218
