July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBRULES-350) client/server API for rule deployment and management

by Mark Proctor (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-350?page=all ] Mark Proctor closed JBRULES-350. -------------------------------- Resolution: Duplicate Issue > client/server API for rule deployment and management > ---------------------------------------------------- > > Key: JBRULES-350 > URL: http://jira.jboss.com/jira/browse/JBRULES-350 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assigned To: Mark Proctor > Fix For: 4.0.0.MR4 > > > We need a API to handle package and rulebase deployment as well as management. Initially research shows that Jboss Remoting will be an ideal solution to provide a remote access API. -- 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

17 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1456) It is impossible to delete once entered user profile property

by Ryszard Kozmik (JIRA)

It is impossible to delete once entered user profile property ------------------------------------------------------------- Key: JBPORTAL-1456 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1456 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.CR2, 2.4.1 Final, 2.2.1 Final Reporter: Ryszard Kozmik Priority: Minor Fix For: 2.2.2 Final, 2.6 Final, 2.8 Final, 2.4.2 Final, 2.4.3 Final Reproducing the bug: 1) login to portal 2) enter edit user profile information view 3) Add something (name, ICQ, AIM whatever) 4) Save changes 5) enter edit user profile information view again 6) delete previously entered info 7) save changes 8) enter edit user profile information view and notice that information was not deleted -- 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

17 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1307) Add Google Talk / Jabber to list of "Instant Message Identities".

by oberiko (JIRA)

Add Google Talk / Jabber to list of "Instant Message Identities". ----------------------------------------------------------------- Key: JBPORTAL-1307 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1307 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha2 Reporter: oberiko Priority: Minor It'd be nice if the "Instant Message Identities" section of the user profile included a field for Google Talk / Jabber. -- 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

17 years, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-446) Support rulebase configuration via jsr94 registerRuleExecutionSet properties

by Juergen none (JIRA)

Support rulebase configuration via jsr94 registerRuleExecutionSet properties ---------------------------------------------------------------------------- Key: JBRULES-446 URL: http://jira.jboss.com/jira/browse/JBRULES-446 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JSR94 Affects Versions: 3.0.4 Reporter: Juergen none Assigned To: Mark Proctor Priority: Minor Is it possible to support rulebase configuration via jsr94 registerRuleExecutionSet properties? Suggestion: - new property in org.drools.jsr94.rules.Constants.java:41: //jh: added to support handing a rulebase config via jsr94 /** <code>RuleExecutionSet</code> rulebase config constant. */ public static final String RES_CONFIG = "javax.rules.admin.RuleExecutionSet.config"; - modification of method (probably secure against ClassCastException) org.drools.jsr94.rules.admin.RuleExecutionSetImpl.java:118:RuleExecutionSetImpl(...): //jh: support rulebase configuration via jsr94 final org.drools.reteoo.ReteooRuleBase ruleBase = new org.drools.reteoo.ReteooRuleBase((org.drools.RuleBaseConfiguration)properties.get(org.drools.jsr94.rules.Constants.RES_CONFIG), new Jsr94FactHandleFactory() ); /* final org.drools.reteoo.ReteooRuleBase ruleBase = new org.drools.reteoo.ReteooRuleBase( new Jsr94FactHandleFactory() ); */ -- 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

17 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-528) Implementation for Decision tables, and compiler options in DroolsJSR

by Vignesh S (JIRA)

Implementation for Decision tables, and compiler options in DroolsJSR --------------------------------------------------------------------- Key: JBRULES-528 URL: http://jira.jboss.com/jira/browse/JBRULES-528 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JSR94 Reporter: Vignesh S Assigned To: Mark Proctor Priority: Optional The implementation for Decision tables and compiler options can be given in drools JSR and to my knowledge it can done easily in the method public RuleExecutionSet createRuleExecutionSet(final Reader ruleExecutionSetReader, final Map properties) throws RuleExecutionSetCreateException org.drools.jsr94.rules.admin.LocalRuleExecutionSetProviderImpl class By adding one more condition for ".xsl" for decision tables and setting a new property for the compiler in map parameter -- 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

17 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1006) We should throw an exception if recoverDelivery fails

by Clebert Suconic (JIRA)

We should throw an exception if recoverDelivery fails ----------------------------------------------------- Key: JBMESSAGING-1006 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1006 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.3.0.GA Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.4.0.GA If recoverDelivery can't find a message, it means that another consumer already received that message during mergeQueue What means... failover should fail on that situation. -- 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

17 years, 7 months

1
7
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1513) build.sh and build.bat into testsuite project

by Luca Stancapiano (JIRA)

build.sh and build.bat into testsuite project --------------------------------------------- Key: JBPORTAL-1513 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1513 Project: JBoss Portal Issue Type: Patch Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6 CR3 Environment: jboss portal from http://anonsvn.jboss.org/repos/portal/trunk since 27 jun 2007 Reporter: Luca Stancapiano Assigned To: Julien Viet Fix For: 2.6 Final .....but build.bat and build.sh into testsuite project.....do you want to use them? -- 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

17 years, 7 months

3
4
0 / 0

[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

17 years, 7 months

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

17 years, 7 months

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

17 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007