November 2006 - jboss-jira - Jboss List Archives

[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.1 (was: jBPM BPEL 1.1) > 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.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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-7) Nested units of work

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-7?page=all ] Alejandro Guizar updated BPEL-7: -------------------------------- Fix Version/s: jBPM BPEL 1.1.1 (was: jBPM BPEL 1.1) > Nested units of work > -------------------- > > Key: BPEL-7 > URL: http://jira.jboss.com/jira/browse/BPEL-7 > Project: JBoss jBPM BPEL > Issue Type: Task > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Juan Cantu > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1.1 > > > Implement fault, compensation and event handling as specified in ws-bpel 2.0 -- 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, 6 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.1 (was: jBPM BPEL 1.1) > 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.1 > > > Extract the WSDL message parts carried in SOAP headers and add them to incoming requests. > Ensure this mechanism 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-131) bpel web service consumption

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-131?page=all ] Alejandro Guizar updated BPEL-131: ---------------------------------- Fix Version/s: jBPM BPEL 1.1.1 (was: jBPM BPEL 1.1) > bpel web service consumption > ---------------------------- > > Key: BPEL-131 > URL: http://jira.jboss.com/jira/browse/BPEL-131 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 3 > Environment: saaj, w3c dom > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1.1 > > -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-144) publish document/literal endpoints

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-144?page=all ] Alejandro Guizar updated BPEL-144: ---------------------------------- Fix Version/s: jBPM BPEL 1.1.1 (was: jBPM BPEL 1.1) > publish document/literal endpoints > ---------------------------------- > > Key: BPEL-144 > URL: http://jira.jboss.com/jira/browse/BPEL-144 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Environment: jaxrpc, saaj, w3c dom > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1.1 > > > jBPM BPEL currently generates service WSDL documents and processes SOAP request/response messages only for RPC/literal web services. Enhancing the service generation tool and the JAX-RPC handler to cover the document style is crucial for interoperability, particulary with .NET. -- 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, 6 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.1 (was: jBPM BPEL 1.1) > 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.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, 6 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: ---------------------------------- Description: Extract the WSDL message parts carried in SOAP headers and add them to incoming requests. Ensure this mechanism makes WS-Addressing headers available to the process. was: 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. > 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. > Ensure this mechanism 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-159) isolation

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-159?page=all ] Alejandro Guizar updated BPEL-159: ---------------------------------- Fix Version/s: jBPM BPEL 1.1.1 (was: jBPM BPEL 1.1) > isolation > --------- > > Key: BPEL-159 > URL: http://jira.jboss.com/jira/browse/BPEL-159 > Project: JBoss jBPM BPEL > Issue Type: Sub-task > Components: Engine > Affects Versions: jBPM BPEL 1.0 alpha 4 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.1.1 > > > Control concurrency of access to shared variables. Section 13.6 explains in detail. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-352) Calling JChannelFactory.setExposeProtocols() always turns on exposing channels

by Brian Stansberry (JIRA)

Calling JChannelFactory.setExposeProtocols() always turns on exposing channels ------------------------------------------------------------------------------ Key: JGRP-352 URL: http://jira.jboss.com/jira/browse/JGRP-352 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.5 This public void setExposeProtocols(boolean expose_protocols) { this.expose_protocols=expose_protocols; this.expose_channels=true; } should be public void setExposeProtocols(boolean expose_protocols) { this.expose_protocols=expose_protocols; if (expose_protocols) this.expose_channels=true; } -- 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, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-746) injection of clustered SFSB fails during activation

by William DeCoste (JIRA)

injection of clustered SFSB fails during activation --------------------------------------------------- Key: EJBTHREE-746 URL: http://jira.jboss.com/jira/browse/EJBTHREE-746 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: William DeCoste Assigned To: William DeCoste https://na1.salesforce.com/50030000002WIyz -- 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, 6 months

3
5
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 November 2006