[JBoss JIRA] Created: (BPEL-206) activity readers file is reparsed every time a bpelReader is instantiated
by Alejandro Guizar (JIRA)
activity readers file is reparsed every time a bpelReader is instantiated
-------------------------------------------------------------------------
Key: BPEL-206
URL: http://jira.jboss.com/jira/browse/BPEL-206
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 1
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 beta 2
The activity readers file, located by default in org/jbpm/bpel/xml/activity.readers.xml, contains the activity tag names available to the process along with the ActivityReader capable of unmarshalling the XML element to a definition object.
Each bpelReader contains its own set of activityReaders. To instantiate them, it parses the activity readers file, retrieves the ActivityReader class names, loads the classes and instantiates them. This is wasteful.
We need to parse the resource and keep a reference to the loaded classes in advance so that the bpelReader instance only instantiates the classes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months
[JBoss JIRA] Closed: (BPEL-191) automatic node creation does not preserve source prefix
by Alejandro Guizar (JIRA)
[ http://jira.jboss.com/jira/browse/BPEL-191?page=all ]
Alejandro Guizar closed BPEL-191.
---------------------------------
> automatic node creation does not preserve source prefix
> -------------------------------------------------------
>
> Key: BPEL-191
> URL: http://jira.jboss.com/jira/browse/BPEL-191
> Project: JBoss jBPM BPEL
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Engine
> Affects Versions: jBPM BPEL 1.1 beta 1
> Reporter: Alejandro Guizar
> Assigned To: Alejandro Guizar
> Fix For: jBPM BPEL 1.1 beta 2
>
>
> When assigning a value to a nonexistent location, e.g.
> <assign name="AssignOutPut" xmlns:client="http://example.com/SyncSample">
> <copy>
> <from variable="InvokeBalance_queryBalance_OutputVariable" part="balance"/>
> <to variable="outputVariable" part="payload1" query="/payload1/client:result"/>
> </copy>
> </assign>
> the engine does not preserve the prefix that appears in the process definition ("client" in the above example). In fact, it does not set a prefix at all. This is not a problem per se, but may have negative consequences as described below.
> When copying an element from a variable to a SOAP envelope, if the element has a namespace but not a prefix, XmlUtil looks for the declaration of that namespace in the SOAP envelope. In extreme cases, the declaration could be placed in an ancestor of the target element, and the declared prefix be in use by another namespace in the target element.
> The following is a possible value of the payload1 part after the assignment:
> <result xmlns:env='http://schemas.xmlsoap.org/soap/envelope/' xmlns:ns1='urn:samples:account' xmlns='http://example.com/SyncSample' />
> The default namespace declaration results from failing to preserve the prefix. When the above element is copied to a soap envelope that already contains a declaration for the 'http://example.com/SyncSample' namespace, the declared prefix 'ns1' will be used. However, our element uses that prefix for a different namespace!! See the result below:
> <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'>
> <env:Header/>
> <env:Body>
> <ns1:processResponse xmlns:ns1='http://example.com/SyncSample'>
> <payload1>
> <ns1:result xmlns:env='http://schemas.xmlsoap.org/soap/envelope/' xmlns:ns1='urn:samples:account'>50.0</ns1:result>
> </payload1>
> </ns1:processResponse>
> </env:Body>
> </env:Envelope>
> When read, the 'result' element is in the 'urn:samples:account' namespace, which leads the reader to misinterpret the result.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months
[JBoss JIRA] Closed: (BPEL-196) jbpm and bpel services do not play together well
by Alejandro Guizar (JIRA)
[ http://jira.jboss.com/jira/browse/BPEL-196?page=all ]
Alejandro Guizar closed BPEL-196.
---------------------------------
> jbpm and bpel services do not play together well
> ------------------------------------------------
>
> Key: BPEL-196
> URL: http://jira.jboss.com/jira/browse/BPEL-196
> Project: JBoss jBPM BPEL
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Engine
> Affects Versions: jBPM BPEL 1.1 beta 1
> Reporter: Alejandro Guizar
> Assigned To: Alejandro Guizar
> Priority: Critical
> Fix For: jBPM BPEL 1.1 beta 2
>
> Attachments: jbpm-bpel-1.1-beta1-bpel-196.zip, jbpmBpel.properties, jbpmBpel.script
>
>
> When deploying a jPDL process or even accessing the jbpm web application, the following exception arises:
> java.lang.NullPointerException
> at org.jbpm.JbpmContext.setActorId(JbpmContext.java:453)
> at org.jbpm.web.JbpmContextFilter.doFilter(JbpmContextFilter.java:81)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:59)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
> at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
> at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
> at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
> at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months
[JBoss JIRA] Created: (BPEL-197) integers are represented with a decimal point when used as source content
by Alejandro Guizar (JIRA)
integers are represented with a decimal point when used as source content
-------------------------------------------------------------------------
Key: BPEL-197
URL: http://jira.jboss.com/jira/browse/BPEL-197
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 1
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 beta 2
When the evaluation of an expression results in a Number value, and this value is latter used to compute a source content TII, the resulting TII contains a decimal point and a trailing zero.
The BPEL 2 spec, section 8.4.2, states:
> Once the information item is returned from the source, a TII will be computed based upon it. [...] This is analogous to the XPath 1.0 string() function.
However, jBPM BPEL converts an object of a type other than node-set to a string by calling the toString() method. This method does not match the behavior of the string() function for a number.
In particular, the XPath 1 spec, section 4.2 states:
> if the number is an integer, the number is represented in decimal form as a Number with no decimal point and no leading zeros, preceded by a minus sign (-) if the number is negative
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 6 months