October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (BPEL-281) apache ant support

by Alejandro Guizar (JIRA)

apache ant support ------------------ Key: BPEL-281 URL: http://jira.jboss.com/jira/browse/BPEL-281 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA The web console provides a user interface to perform the following tasks. 1. Database administration 2. Process deployment 3. Partner registration For integration purposes, the ability to invoke the above tasks from an Ant script is highly desirable. -- 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

16 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (BPEL-275) web module deployment tool

by Alejandro Guizar (JIRA)

web module deployment tool -------------------------- Key: BPEL-275 URL: http://jira.jboss.com/jira/browse/BPEL-275 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA Develop a tool for deploying web modules to the application server. Use JSR-88 APIs if possible. -- 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

16 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (BPEL-276) generate bpel application descriptor along with wsdl service description

by Alejandro Guizar (JIRA)

generate bpel application descriptor along with wsdl service description ------------------------------------------------------------------------ Key: BPEL-276 URL: http://jira.jboss.com/jira/browse/BPEL-276 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA -- 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

16 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (BPEL-278) endpoint reference in <from> is not validated against the available partner link roles

by Alejandro Guizar (JIRA)

endpoint reference in <from> is not validated against the available partner link roles -------------------------------------------------------------------------------------- Key: BPEL-278 URL: http://jira.jboss.com/jira/browse/BPEL-278 Project: JBoss jBPM BPEL Issue Type: Bug Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA Consider the following partner link declaration. <partnerLink name="ConfiscationTaskMngLink" partnerLinkType="wsdl:ConfiscationTaskMngLink" partnerRole="ConfiscationTaskMngProvider" /> The following from-spec is invalid because the above partner link does not specify myRole: <from endpointReference="myRole" partnerLink="ConfiscationTaskMngLink" /> This error is not caught during static analysis. -- 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

16 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (BPEL-280) redeploy web modules upon server restart

by Alejandro Guizar (JIRA)

redeploy web modules upon server restart ---------------------------------------- Key: BPEL-280 URL: http://jira.jboss.com/jira/browse/BPEL-280 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA PROBLEM With the automated deployment procedure in place, new processes and the associated web services can be deployed on the fly. There is an issue, however. Upon server restart, web modules deployed through the JBoss AS main deployer dissapear. Three approaches come quickly to mind to address this situation: PROPOSAL 1. Place the modules directly in the deployment directory of the application server * Pros. The engine needs not perform any task at startup. The server is responsible for reading and deploying the modules. * Cons. Loss of portability. Servers other than JBoss AS use different deployment directories. Some may not even support the concept of a deployment directory. Furthermore, what if the modules are deleted? Because the responsibility is trasferred to the server, there can be a disconnection between the process definitions in the jBPM database and the deployed web services. PROPOSAL 2. Save the prefabricated deployment artifacts in the process definition. Rebuild the module at startup. * Pros. No external location is required to place the modules. All information required to rebuild them is saved along the process definition. The disconnection between the process definitions and the deployed web services dissapear. * Cons. The engine has to process each process definition at startup to rebuild the modules. This could result in a significant startup time. Plus, database space consumption might become excessive. PROPOSAL 3. Save the prefabricated module in a content repository. Leverage the repository facilities provided by jBPM. * Pros. Same as 2. Plus, no large database storage requirements. * Cons. The engine still has to process each process definition at startup. Plus, an external content repository introduces new dependencies and installation complexities to the product. Among these proposals, #1 looks good because it neither imposes large database storage requirements nor a significant startup processing time. It is also the easiest to implement, at the expense of brittleness due to the reliance on the app server. Any comments or new proposals welcome. -- 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

16 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (BPEL-272) allow xpath expression/query to create more than one occurrence of an element

by Alejandro Guizar (JIRA)

allow xpath expression/query to create more than one occurrence of an element ----------------------------------------------------------------------------- Key: BPEL-272 URL: http://jira.jboss.com/jira/browse/BPEL-272 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Priority: Critical Fix For: jBPM BPEL 1.1 GA PROBLEM The current XPath sublanguage implementation automatically creates nodes missing from location paths during assignment. This facility has a number of conceptual limitations. One of them is the inability to append a child element to an existing element if the latter already has a child element with the same name. There is no XPath syntax to express that a new element is required! It is tempting to think of a numeric XPath predicate as an array index, leading to the next snippet: <copy> <from><literal>haha</literal></from> <to variable='laughter' xmlns:ex='http://jbpm.org/bpel/examples'> <query>ex:laugh[last() + 1]</query> </to> </copy> However, such an interpretation of a predicate is wrong. Consider the following extract from XPath 1.0 specification on predicates: "A PredicateExpr is evaluated by evaluating the Expr and converting the result to a boolean. If the result is a number, the result will be converted to true if the number is equal to the context position and will be converted to false otherwise." The description of the last() function reads: "The last function returns a number equal to the context size from the expression evaluation context." Noticed the problem? The context position is never greater than the context size. Therefore the predicate [last() + 1] does not represent the position "one past the context size" but the boolean value false. Unfortunately, no other predicate seems appropriate. PROPOSAL Introduce a minor deviation from the XPath 1.0 specification. Interpret the result of a numeric predicate that equals the context size plus one as a request to create a new occurrence of the node. -- 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

16 years, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (BPEL-273) provide a declarative way to install new evaluator factories in the sublanguage framework

by Alejandro Guizar (JIRA)

provide a declarative way to install new evaluator factories in the sublanguage framework ----------------------------------------------------------------------------------------- Key: BPEL-273 URL: http://jira.jboss.com/jira/browse/BPEL-273 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA PROBLEM The sublanguage framework is extensible; however, it only provides programmatic means to register evaluator factories for new languages. PROPOSAL Involves two actions: 1. Apply the resource-based declarative pattern currently employed in activity readers, catalog readers and endpoint reference factories to evaluator factories. 2. Remove programmatic registration as well. It would allow the addition of new languages at runtime, which is untested and not currently required. -- 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

16 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (BPEL-274) wsdl service generator: eliminate reliance on transitive imports

by Alejandro Guizar (JIRA)

wsdl service generator: eliminate reliance on transitive imports ---------------------------------------------------------------- Key: BPEL-274 URL: http://jira.jboss.com/jira/browse/BPEL-274 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA PROBLEM Consider the following network of WSDL documents. <definitions name="d1" targetNamespace="ns1"> <import namespace="ns2" location="d2" /> <binding name="b" type="ns3:pt" /> </definitions> <definitions name="d2" targetNamespace="ns2"> <import namespace="ns3" location="d3" /> <partnerLinkType name="plt"> <role portType="ns3:pt" /> </partnerLinkType> </definitions> <definitions name="d3" targetNamespace="ns3"> <portType name="pt" /> </definitions> ns2:plt is able to resolve the reference tons3:pt, but ns1:b is not. The import element in d1 is not scanned because the binding refers to a port type in namespace ns3 and the import namespace URI is ns2. jBPM BPEL is able to resolve such transitive references, but products like the Eclipse BPEL designer and JBossWS are not. PROPOSAL While generating d1, create a direct import for d3. -- 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

16 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (BPEL-269) enhance assignment logging capabilities

by Alejandro Guizar (JIRA)

enhance assignment logging capabilities --------------------------------------- Key: BPEL-269 URL: http://jira.jboss.com/jira/browse/BPEL-269 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA PROBLEM When a bpel:uninitializedVariable fault is thrown, it does not log which variable was uninitialized. Further, logging of extraction and assignment of values is generally scarce. SOLUTION Log the uninitialized variables. Add extraction/assignment logs to all from/to variants. -- 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

16 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (BPEL-270) Add support for extensionAssignOperation

by Alejandro Guizar (JIRA)

Add support for extensionAssignOperation ---------------------------------------- Key: BPEL-270 URL: http://jira.jboss.com/jira/browse/BPEL-270 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA PROBLEM In BPEL 2, <extensibleAssignOperation> elements can appear as children of the <assign> activity, alongside standard <copy> elements. Our current design does not permit the addition of custom assign operations. SOLUTION Generalize Copy to AssignOperation. Introduce a parsing framework that permits the creation of custom operations. -- 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

16 years, 7 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007