July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBREM-433) point to multipoint invocation api

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-433?page=all ] David Lloyd reassigned JBREM-433: --------------------------------- Assignee: David Lloyd (was: Tom Elrod) > point to multipoint invocation api > ---------------------------------- > > Key: JBREM-433 > URL: http://jira.jboss.com/jira/browse/JBREM-433 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta1 > Reporter: Tom Elrod > Assigned To: David Lloyd > Fix For: 2.4.0.Beta1 (Pinto) > > > Would like to provide API where client could make single invocation that would be made on multiple remoting servers at one time. The responses for each target server would be aggregated into one response as return to the client call. Basically want to mimic same behavior found within jgroups for this, but provide support over all the transports for this. -- 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

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-433) point to multipoint invocation api

by David Lloyd (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-433?page=comments#action_12367938 ] David Lloyd commented on JBREM-433: ----------------------------------- This can definitely be done in terms of a one-way invocation. But how would the response aggregation work in a request-reply scenario? Using a connection-oriented protocol, you'd be no better off than if you iterated over a series of connections, sending a request to each, and then waiting until a reply is received for each. It seems like you'd want to utilize UDP broadcast or multicast for this sort of thing. But in this case, you have no reliable way to figure out how many responses to expect. > point to multipoint invocation api > ---------------------------------- > > Key: JBREM-433 > URL: http://jira.jboss.com/jira/browse/JBREM-433 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta1 > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.4.0.Beta1 (Pinto) > > > Would like to provide API where client could make single invocation that would be made on multiple remoting servers at one time. The responses for each target server would be aggregated into one response as return to the client call. Basically want to mimic same behavior found within jgroups for this, but provide support over all the transports for this. -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-730) "Copy" should copy the live revision

by Sohil Shah (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-730?page=all ] Sohil Shah updated JBPORTAL-730: -------------------------------- Fix Version/s: 2.8 Final > "Copy" should copy the live revision > ------------------------------------ > > Key: JBPORTAL-730 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-730 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.6.Beta1 > Reporter: Thomas Heute > Assigned To: Sohil Shah > Priority: Optional > Fix For: 2.8 Final > > > The current "copy" feature using Jackrabbit Workspace.copy() seems to copy the latest revision and only that one. > Jackrabbit implementation won't help here (since it should be faster to do it at this level) > If we decide to copy a unique revision we should copy the Live version. (can be different from the latest) > Now the question is: should we copy all revisions or only the live one ? -- 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

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-57) SOAP Layer to construct SAML Payload

by Anil Saldhana (JIRA)

SOAP Layer to construct SAML Payload ------------------------------------ Key: SECURITY-57 URL: http://jira.jboss.com/jira/browse/SECURITY-57 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Interoperability Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.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

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-55) Burton XACML Interoperability Container Task

by Anil Saldhana (JIRA)

Burton XACML Interoperability Container Task -------------------------------------------- Key: SECURITY-55 URL: http://jira.jboss.com/jira/browse/SECURITY-55 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Interoperability Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 Container Task for Burton Catalyst Conference Interoperability Event at the end of June. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1126) CMS needs to store contributing version for new versions of pages

by Alex Pinkin (JIRA)

CMS needs to store contributing version for new versions of pages ----------------------------------------------------------------- Key: JBPORTAL-1126 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1126 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Reporter: Alex Pinkin Assigned To: Roy Russo -CMS needs to store contributing version for new versions of pages (1.1 was created from 1.0, etc). To prevent locking the edit of a content item, it is useful to allow multiple drafts to be created of a content item. This situation can cause problems for approvers if there are multiple drafts needing approval. It would be helpful if approvers could see what version was the contributing version for a particular content item version. -- 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

3
2
0 / 0

[JBoss JIRA] Resolved: (JBPM-378) Broken support for SwimlaneInstance PooledActor reassignment

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-378?page=all ] Ronald van Kuijk resolved JBPM-378. ----------------------------------- Resolution: Out of Date Please validate and close if agreed > Broken support for SwimlaneInstance PooledActor reassignment > ------------------------------------------------------------ > > Key: JBPM-378 > URL: http://jira.jboss.com/jira/browse/JBPM-378 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.1 > Environment: JBPM 3.0.1, JBoss 4.0.2, JDK 1.5, Oracle and PostgresSQL > Reporter: Britt Miner > Assigned To: Ronald van Kuijk > Fix For: jBPM 3.3 > > Attachments: SwimlaneInstPoolAssignmentTest.java, SwimlaneInstPoolAssignmentTests.java > > > The second post of the referenced thread more accurately describes the scope of the problem. > Thanks, > Britt -- 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

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-378) Broken support for SwimlaneInstance PooledActor reassignment

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-378?page=comments#action_12367854 ] Ronald van Kuijk commented on JBPM-378: --------------------------------------- After adapting this test to be a real unittest, I observer the following: - test 1 fully works - test 2 fully works - test 3 not needed anymore, so it became what was test 4 --> swimlane is not initialized, task is created (no pooled actors) swimlane is reassigned (works) ti.getPooledActors() returns the pooledActors of the swimlane. This is as designed: /** * gets the pool of actors for this task instance. If this task has a swimlaneInstance * and no pooled actors, the pooled actors of the swimlane instance are returned. */ public Set getPooledActors() { if ( (swimlaneInstance!=null) && ( (pooledActors==null) || (pooledActors.isEmpty()) ) ){ return swimlaneInstance.getPooledActors(); } return pooledActors; } So imo this 'issue' can be closed with an 'out of date' for 3.0 (it will not be fixed there and works in 3.2) See the attachment > Broken support for SwimlaneInstance PooledActor reassignment > ------------------------------------------------------------ > > Key: JBPM-378 > URL: http://jira.jboss.com/jira/browse/JBPM-378 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.1 > Environment: JBPM 3.0.1, JBoss 4.0.2, JDK 1.5, Oracle and PostgresSQL > Reporter: Britt Miner > Assigned To: Ronald van Kuijk > Fix For: jBPM 3.3 > > Attachments: SwimlaneInstPoolAssignmentTest.java, SwimlaneInstPoolAssignmentTests.java > > > The second post of the referenced thread more accurately describes the scope of the problem. > Thanks, > Britt -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBPM-378) Broken support for SwimlaneInstance PooledActor reassignment

by Ronald van Kuijk (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-378?page=all ] Ronald van Kuijk updated JBPM-378: ---------------------------------- Attachment: SwimlaneInstPoolAssignmentTest.java > Broken support for SwimlaneInstance PooledActor reassignment > ------------------------------------------------------------ > > Key: JBPM-378 > URL: http://jira.jboss.com/jira/browse/JBPM-378 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.1 > Environment: JBPM 3.0.1, JBoss 4.0.2, JDK 1.5, Oracle and PostgresSQL > Reporter: Britt Miner > Assigned To: Ronald van Kuijk > Fix For: jBPM 3.3 > > Attachments: SwimlaneInstPoolAssignmentTest.java, SwimlaneInstPoolAssignmentTests.java > > > The second post of the referenced thread more accurately describes the scope of the problem. > Thanks, > Britt -- 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

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-731) File with no "live" version

by Sohil Shah (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-731?page=all ] Sohil Shah resolved JBPORTAL-731. --------------------------------- Fix Version/s: 2.6 Final Resolution: Done CMS Workflow based publishing is now integrated in 2.6 > File with no "live" version > --------------------------- > > Key: JBPORTAL-731 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-731 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal CMS > Affects Versions: 2.6 CR3 > Reporter: Thomas Heute > Assigned To: Sohil Shah > Fix For: 2.6 Final > > > There is probably a need to avoid having a "live" version of a content, that could be used to: > 1) Save a file without publishing it yet (because it is on-going work for example) > 2) Write a file to be published later. -- 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

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 2007