[JBoss JIRA] Created: (JBPM-2352) jPDL Schema definition needs some tweaks
by Phil Bingley (JIRA)
jPDL Schema definition needs some tweaks
----------------------------------------
Key: JBPM-2352
URL: https://jira.jboss.org/jira/browse/JBPM-2352
Project: JBoss jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.0.CR1
Reporter: Phil Bingley
The jpdl schema needs to be updated to be in line with the features of the supported jpdl attributes.
Some specific differences are apparent in the task definitions where the schema does not support the form or due date attributes of a task. A complex type currently exists that covers the attributes but is not referenced.
There are likely to be other differences between the schema and supported jpdl so the whole thing may need reviewing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBPM-2183) process conversion tool
by Tom Baeyens (JIRA)
process conversion tool
-----------------------
Key: JBPM-2183
URL: https://jira.jboss.org/jira/browse/JBPM-2183
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Assignee: Jim Ma
Fix For: jBPM 4.0.0.GA
add a class org.jbpm.jpdl.internal.convert.JpdlConverterTool to the jPDL classes.
syntax of the tool should be like this:
java org.jbpm.jpdl.internal.convert.JpdlConverterTool filename
The filename represents a jPDL 3 process file. The tool must place a new jPDL 4 file next to the given file. the new file must end with .converted.jpdl.xml The prefix must be the same as the original minus the .xml.
The tool must build a DOM model of the the jPDL 3 process file, modify that DOM model and then serialize that modified DOM back to the new file. As a basis, a ConversionParser must inherit from org.jbpm.pvm.internal.xml.Parser and overwrite the parseDocument(Document, Parse); method. That way, you'll have the line number information available for proper error generation.
In the jPDL test suite of jBPM 4, in package org.jbpm.jpdl.internal.convert, build a minimal test that converts the simplest possible jPDL 3 process file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBPM-2374) image problem
by Tom Baeyens (JIRA)
image problem
-------------
Key: JBPM-2374
URL: https://jira.jboss.org/jira/browse/JBPM-2374
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Console, Runtime Engine
Reporter: Tom Baeyens
Assignee: Heiko Braun
Fix For: jBPM 4.0
heiko, can you have a look at this stack trace ?
is that something in the engine or in the console?
22:19:19,546 ERROR [[Resteasy]] Servlet.service() for servlet Resteasy threw exception
org.jboss.resteasy.spi.UnhandledException: java.lang.RuntimeException: Unexpected invocation exception: null
at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319)
at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230)
at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.RuntimeException: Unexpected invocation exception: null
at org.jboss.bpm.console.server.util.InvocationProxy.invoke(InvocationProxy.java:80)
at $Proxy140.getProcessImage(Unknown Source)
at org.jboss.bpm.console.server.ProcessMgmtFacade.getProcessImage(ProcessMgmtFacade.java:281)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117)
at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166)
at org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
... 28 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.bpm.console.server.util.InvocationProxy.invoke(InvocationProxy.java:64)
... 40 more
Caused by: java.lang.RuntimeException: Failed to retrieve image resource: null
at org.jbpm.integration.console.graphView.GraphViewerPluginImpl.getProcessImage(GraphViewerPluginImpl.java:77)
... 45 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBPM-2364) split mail documentation in userguide and devguide part
by Tom Baeyens (JIRA)
split mail documentation in userguide and devguide part
-------------------------------------------------------
Key: JBPM-2364
URL: https://jira.jboss.org/jira/browse/JBPM-2364
Project: JBoss jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Assignee: Joram Barrez
Fix For: jBPM 4.0
user guide should only explain the supported installations style. where mail properties should be specifyable as input for the installation scripts. (scripts would have to be revisited to support that) only the mail.properties properties (host, port,...) should be configurable in the userguide
dev guide should explain the configuration files to developers. also multiple mail servers and mail filters and mail templates can be explained here.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years