September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (BPEL-85) Docu on the purpose of BPEL

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-85?page=all ] Alejandro Guizar updated BPEL-85: --------------------------------- Fix Version/s: jBPM BPEL 1.1 (was: jBPM BPEL 1.1 beta 2) > Docu on the purpose of BPEL > --------------------------- > > Key: BPEL-85 > URL: http://jira.jboss.com/jira/browse/BPEL-85 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documents > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Thomas Diesler > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 > > > Please expand the user documentation to a section about the purpose of BPEL. It should show a not so trivial use case that illustrates (with pictures) why I should care about BPEL -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-168) soap header processing

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-168?page=all ] Alejandro Guizar updated BPEL-168: ---------------------------------- Fix Version/s: jBPM BPEL 1.1 (was: jBPM BPEL 1.1 beta 3) > soap header processing > ---------------------- > > Key: BPEL-168 > URL: http://jira.jboss.com/jira/browse/BPEL-168 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 > > > Extract the WSDL message parts carried in SOAP headers and add them to incoming requests. > Make sure this mechanism properly makes WS-Addressing headers available to the process. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-151) export the reference of the published endpoint

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-151?page=all ] Alejandro Guizar updated BPEL-151: ---------------------------------- Fix Version/s: jBPM BPEL 1.1 (was: jBPM BPEL 1.1 beta 3) > export the reference of the published endpoint > ---------------------------------------------- > > Key: BPEL-151 > URL: http://jira.jboss.com/jira/browse/BPEL-151 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 3 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Priority: Critical > Fix For: jBPM BPEL 1.1 > > > Provide the endpoint reference of the process with respect to partner links. Implement its use as the source of assignment, as described in section 9.4 of the spec. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-193) template for new projects

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-193?page=all ] Alejandro Guizar updated BPEL-193: ---------------------------------- Fix Version/s: jBPM BPEL 1.1 (was: jBPM BPEL 1.1 beta 3) > template for new projects > ------------------------- > > Key: BPEL-193 > URL: http://jira.jboss.com/jira/browse/BPEL-193 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documents > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 > > > Burr Sutter wrote: > "I was only hoping for an easy way to build, modify and redeploy HelloWorld or ATM with the least amount of effort. Something like > 1. Edit BPEL file > 2. Deploy > 3. In the browser view the WSDL > Having Ant tasks that make it this easy and a template project and build script for getting started would be great for the first release of our BPEL engine." -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-59) get original BPEL document after deployment

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-59?page=all ] Alejandro Guizar updated BPEL-59: --------------------------------- Fix Version/s: jBPM BPEL 1.1 (was: jBPM BPEL 1.1 beta 3) > get original BPEL document after deployment > ------------------------------------------- > > Key: BPEL-59 > URL: http://jira.jboss.com/jira/browse/BPEL-59 > Project: JBoss jBPM BPEL > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 3 > Reporter: Dmitry > Assigned To: Alejandro Guizar > Priority: Minor > Fix For: jBPM BPEL 1.1 > > > i'm developing a BAM system(http://sourceforge.net/projects/jbam). and i need on my presentation part of the system show the user on what step of the execution of the process are we currently on. i'm intercepting JBPM system ivents via JBossAOP framework, and as a reason of it have no problem to know on which step of process instance execution are we currently on and what is my input data, but i can't meanwhile to find way to get process flow definition. according to my design i would like to get on each processinstance start a process xml model so i could transform it to SVG and show to end user on portal(the representation on my system). this is needed becouse process might have different versions and i'd like to show to user the updated one or busuness analyst might what to know how did the process flow looked two month ago, and this information i can give him from my database if i have xml definition stored inside it. > Regards, > Dmitry. -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-10) compensation handling

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-10?page=all ] Alejandro Guizar updated BPEL-10: --------------------------------- Fix Version/s: jBPM BPEL 1.1 (was: jBPM BPEL 1.1 beta 3) > compensation handling > --------------------- > > Key: BPEL-10 > URL: http://jira.jboss.com/jira/browse/BPEL-10 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Juan Cantu > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1 > > > -Implement the state transitions for scope instances when compensate / compensated signals are received > -support implicit compensation -- 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3659) Increase ClusterPartition buffers to support farming of large files

by Brian Stansberry (JIRA)

Increase ClusterPartition buffers to support farming of large files ------------------------------------------------------------------- Key: JBAS-3659 URL: http://jira.jboss.com/jira/browse/JBAS-3659 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-4.0.5.GA The receive buffers in the cluster-service.xml UDP protocol are only 150K. Farming sends files around the cluster in 512K chunks. With the default config, the receive buffer sizes are not even large enough to hold one chunk. This can lead to problems where the packets that make up part of a chunk get dropped and have to be retransmitted. With very large files, this can slow things down to the point that timeouts start getting tripped and the transfer fails. We had a support case where increasing the buffers to the sizes used by the fc-fast-minimalthreads config took care of the problem. That config uses 25MB send buffers for both mcast and unicast; don't think we need to increase to such a high number for this. But, I will bump the receive buffers to 640K and the sends to perhaps 2MB. -- 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

19 years, 8 months

2
4
0 / 0

[JBoss JIRA] Closed: (JBCACHE-465) Refactor state transfer code out of TreeCache

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-465?page=all ] Brian Stansberry closed JBCACHE-465. ------------------------------------ Resolution: Done > Refactor state transfer code out of TreeCache > --------------------------------------------- > > Key: JBCACHE-465 > URL: http://jira.jboss.com/jira/browse/JBCACHE-465 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: 2.0.0 > > > The TreeCache class now has a ton of code related to state transfer. Need to look into refactoring that out into a separate class or 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCOMMON-11) Add a default client socket factory which supports setBindAddress

by Scott M Stark (JIRA)

Add a default client socket factory which supports setBindAddress ----------------------------------------------------------------- Key: JBCOMMON-11 URL: http://jira.jboss.com/jira/browse/JBCOMMON-11 Project: JBoss Common Issue Type: Sub-task Security Level: Public (Everyone can see) Components: core Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: 1.0.0.GA We need to have a default RMIClientSocketFactory impl that supports setBindAddress(String) for use in the invokers/naming service. -- 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

19 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1047) Design ldap implementation for identity modules

by Boleslaw Dawidowicz (JIRA)

Design ldap implementation for identity modules ----------------------------------------------- Key: JBPORTAL-1047 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1047 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6.Alpha1 Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Fix For: 2.6.Alpha1 - Identity modules must handle both user/role retreival and creation - User and roles can be mapped in ldap directory tree in several different ways. - There should be some flexible implementation desinged to handle different user/roles relations mapping strategies. (roles, group, both static and dynamic) - This should also be opened for additional specific features for main LDAP implementations (RH, Sun, MSAD...) -- 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

19 years, 8 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006