July 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3927) Update naming service to using remoting based proxy

by Scott M Stark (JIRA)

Update naming service to using remoting based proxy --------------------------------------------------- Key: JBAS-3927 URL: http://jira.jboss.com/jira/browse/JBAS-3927 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Naming, Remoting Reporter: Scott M Stark Assigned To: Scott M Stark The integration of the NamingService with the legacy detached invoker needs to be factored out and replaced with a remoting based proxy. -- 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

3
4
0 / 0

[JBoss JIRA] Moved: (JBAS-8158) Multiple EARs with same EJB fail to deploy

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8158?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELDINT-67 to JBAS-8158: ---------------------------------------- Project: JBoss Application Server (was: Weld Integration) Key: JBAS-8158 (was: WELDINT-67) Affects Version/s: (was: 6.0.0.Beta9) Security: Public Component/s: Weld/CDI (was: Weld Bootstrapper) (was: JBoss EJB 3.0 integration) > Multiple EARs with same EJB fail to deploy > ------------------------------------------ > > Key: JBAS-8158 > URL: https://jira.jboss.org/browse/JBAS-8158 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Environment: Win7 x64, JBoss 6.0.0.M3 > Reporter: Greg Peterson > Attachments: patch1.patch, test.zip > > > When there are two ear's, each containing the same EJB, the first ear deploys correctly, the second gets an error due to a binder component with the same name being deployed to the microcontainer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3151) Convert HA-JNDI stubs to Remoting

by Ron Sigal (JIRA)

[ https://jira.jboss.org/browse/JBAS-3151?page=com.atlassian.jira.plugin.sy... ] Ron Sigal updated JBAS-3151: ---------------------------- Fix Version/s: 7.0.0.M1 (was: 6.0.0.M4) I just heard that Remoting 3 will not be completely integrated into the Application Server until AS 7. Until the nature of connection management is resolved, which affects Naming, this issue cannot be resolved. > Convert HA-JNDI stubs to Remoting > --------------------------------- > > Key: JBAS-3151 > URL: https://jira.jboss.org/browse/JBAS-3151 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Clustering, Naming, Remoting > Reporter: Brian Stansberry > Assignee: Ron Sigal > Fix For: 7.0.0.M1 > > > The HA-JNDI naming service proxy is based on the old HARMIClient and HARMIServer code. We should convert this to use Remoting. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JBNAME-50) Refactor to allow for Remoting 3 support

by Scott M Stark (JIRA)

Refactor to allow for Remoting 3 support ---------------------------------------- Key: JBNAME-50 URL: https://jira.jboss.org/browse/JBNAME-50 Project: JBoss Naming Issue Type: Feature Request Components: jnp-client, jnpserver, Microcontainer, naming Affects Versions: 5.0.5.Final Reporter: Scott M Stark Assignee: Ron Sigal Fix For: 6.0.0.Beta1 To support AS6 and other MC work we need to refactor the server and proxy layer to allow for remoting 3 based transport -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
2
0 / 0

[JBoss JIRA] Created: (GPD-395) Fields for decision handlers are lost

by Koen Aers (JIRA)

Fields for decision handlers are lost ------------------------------------- Key: GPD-395 URL: https://jira.jboss.org/browse/GPD-395 Project: jBPM GPD Issue Type: Feature Request Reporter: Koen Aers Assignee: Koen Aers Fix For: jBPM jPDL Designer 4.x see jBPM-380 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

2
6
0 / 0

[JBoss JIRA] Created: (JBJCA-375) Jetty 7.1.5

by Jesper Pedersen (JIRA)

Jetty 7.1.5 ----------- Key: JBJCA-375 URL: https://jira.jboss.org/browse/JBJCA-375 Project: JBoss JCA Issue Type: Component Upgrade Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha14 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
0 / 0

[JBoss JIRA] Created: (GPD-389) Add more Items into Eclipse Property View

by Daniel Schaaf (JIRA)

Add more Items into Eclipse Property View ----------------------------------------- Key: GPD-389 URL: https://jira.jboss.org/jira/browse/GPD-389 Project: jBPM GPD Issue Type: Feature Request Components: jpdl Affects Versions: jBPM jPDL Designer 4.3 Environment: JBPM 4.3 Eclipse Plugin Reporter: Daniel Schaaf Assignee: Koen Aers Fix For: jBPM jPDL Designer 4.4 Hello to the jBOSS Developers Community. There is a small missing feature in the JBPM GPD Eclipse Plugin, which makes our work together with the business side really hard. The expectation of the business side is to view (and perhaps one time alter) Workflow definitions graphically. To analyse and work with XML Code is not acceptable for them. Though the Flow Graphs already look impressing, real work on this level is not possible because of the poor functionality of the Properties View. Out of my point of view it should be a little change to provide here some additional information and functionality, which would bring us forward a big step: Can you add the following Properties for the Workflow Items: For Tasks: Form, DueDate, Notification Template; Assignment handler For Java: A possibility to see and add a variable number of method arguments For Transitions: Timer duedate (it´s there but only named timer); repeat and condition is missing For Subprocesses: Parameter in; Parameter out each with var and subvar. For Java Tasks: arg and field parameters For Custom Tasks: field parameters I know, that this set is not complete, but the actual is definitely too small for working and I think the once I suggested to add will enable a better Business Analyst work. -- 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

16 years

3
2
0 / 0

[JBoss JIRA] Updated: (GPD-378) Extend GPD to make it possible to set a task description

by Koen Aers (JIRA)

[ https://jira.jboss.org/browse/GPD-378?page=com.atlassian.jira.plugin.syst... ] Koen Aers updated GPD-378: -------------------------- Fix Version/s: jBPM jPDL Designer 4.x (was: jBPM jPDL Designer 4.4) I need to verify the provided patch more in detail. Postpone to next release. > Extend GPD to make it possible to set a task description > -------------------------------------------------------- > > Key: GPD-378 > URL: https://jira.jboss.org/browse/GPD-378 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Environment: not relevant > Reporter: Sebastian Schneider > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.x > > > At the moment it is not possible to set the task description of a task in the GPD. This is due to 2 things. The task description attribute was forgotten in the jPDL schema definition and there is no field for the description of task when you click on properties in the GPD having a task selected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-374) Split library structure

by Jesper Pedersen (JIRA)

Split library structure ----------------------- Key: JBJCA-374 URL: https://jira.jboss.org/browse/JBJCA-374 Project: JBoss JCA Issue Type: Task Components: Build Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha14 Split the library into common, embedded, jetty, sjc and test such that a distribution is easier to create -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
1
0 / 0

[JBoss JIRA] Updated: (GPD-378) Extend GPD to make it possible to set a task description

by Koen Aers (JIRA)

[ https://jira.jboss.org/browse/GPD-378?page=com.atlassian.jira.plugin.syst... ] Koen Aers updated GPD-378: -------------------------- Fix Version/s: jBPM jPDL Designer 4.4 (was: jBPM jPDL Designer 4.x) Labels: description task (was: description task) > Extend GPD to make it possible to set a task description > -------------------------------------------------------- > > Key: GPD-378 > URL: https://jira.jboss.org/browse/GPD-378 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Environment: not relevant > Reporter: Sebastian Schneider > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 4.4 > > > At the moment it is not possible to set the task description of a task in the GPD. This is due to 2 things. The task description attribute was forgotten in the jPDL schema definition and there is no field for the description of task when you click on properties in the GPD having a task selected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years

1
0
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 July 2010