November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3630) JMSTransportSupport is not portable across different JMS providers.

by Darran Lofthouse (JIRA)

JMSTransportSupport is not portable across different JMS providers. ------------------------------------------------------------------- Key: JBAS-3630 URL: http://jira.jboss.com/jira/browse/JBAS-3630 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: JBossAS-4.0.4.GA Reporter: Darran Lofthouse Assigned To: Thomas Diesler Fix For: JBossAS-4.0.6.CR1 JMSTransportSupport is not portable across different JMS providers, the queue name is retrieved using the following code: - String fromName = null; Destination destination = message.getJMSDestination(); if (destination instanceof Queue) fromName = "queue/" + ((Queue)destination).getQueueName(); if (destination instanceof Topic) fromName = "topic/" + ((Topic)destination).getTopicName(); For JBossMQ this is fine and it results in a name that matches the JNDI name of the queue, for WebSphereMQ this returns the name of the queue as configured on WebSphere not the JNDI name the queue is bound to in JBoss. The Javadoc for Queue describes the getQueueName as not being suitable for portable clients: - http://java.sun.com/j2ee/1.4/docs/api/javax/jms/Queue.html A more portable solution could be to lookup a variable in the ENC that contains the name of the web service, this could either be provided by the user deploying the MDB or the web service deployer could bind a value to the ENC of the message driven bean as the web service is deployed. -- 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

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-430) Rule document editor

by Michael Neale (JIRA)

Rule document editor -------------------- Key: JBRULES-430 URL: http://jira.jboss.com/jira/browse/JBRULES-430 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale Need a document editor/viewer to be part of the rule editor. Ideally will be rich text, but is essentually a souped up text area. -- 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

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-432) DSL aware editor

by Michael Neale (JIRA)

DSL aware editor ---------------- Key: JBRULES-432 URL: http://jira.jboss.com/jira/browse/JBRULES-432 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale In this editor, drop downs will be provided to choose expressions from the lists of templates (it won't be a text editor), with the "data" being populated with a text box. The work for parsing can be done server side, the editor only has to display+capture data values from the user. A basic implementation would be something like: * A DSL aware editor would be good. This works as the following (assuming Google GWT): - Is implemented as a subclass of Widget or Composite in GWT (refer to the GWT manual) -Takes in a DSL via public methods: setDSLConditionList(String[] list) and setDSLActionList(String[] list) for completion lists. -Takes in rule in the form of: -setLHS(String[]) -lists of conditions -setRHS(String[]) - list of actions -After a rule has been edited, the resulting text can be obtained by String getLHS(), getRHS etc. -User can chose an icon to popup a list of conditions to add, actions to add (chosing from respective list) -User can chose to remove a condition, or an action (by clicking on a "-" next to a condition or action) COMPLEX BITS: -User can choose to edit a line of the rule (if they are allowed to). In this case, it may get a bit complicated. It may go back to the server and get a list of labels/fields which it can then display to the user so they only edit the fields. An alternative, is to do some processing on the server before the rule is loaded, and provide all the lines not as a string, but as a list of labels/fields. -- 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

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-431) Basic/default rule editor

by Michael Neale (JIRA)

Basic/default rule editor ------------------------- Key: JBRULES-431 URL: http://jira.jboss.com/jira/browse/JBRULES-431 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale This is the default editor, which will just provide text (click to edit) for LHS and RHS of a rule. The rule attributes may be included, but most likely better as part of the meta-data editor widget. -- 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

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-428) Access Control List - each node to be protected

by Michael Neale (JIRA)

Access Control List - each node to be protected ------------------------------------------------ Key: JBRULES-428 URL: http://jira.jboss.com/jira/browse/JBRULES-428 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale Rule nodes (at least) need to have an ACL: what groups can access it in what capacity. First need to have a structure for ACLs to be stored. They should be tied to user groups/roles, not individual logins. JAAS should provide the user name and the users context (group membership) I believe. When there is an ACL, it must be checked to see if the user (via their group membership) can do one of the following: Edit, change status, view, delete. If they can't view, ideally it will not be shown in any "lists", but if that is not feasable, it would be acceptable to list it, but not show the contents. -- 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

13 years, 5 months

6
13
0 / 0

[JBoss JIRA] Created: (JBRULES-433) decision table editor

by Michael Neale (JIRA)

decision table editor --------------------- Key: JBRULES-433 URL: http://jira.jboss.com/jira/browse/JBRULES-433 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale A grid based decision table editor. Can be based on the concepts in 3.0.4 decision tables. Obviously, this entails a grid, with the ability to add rows, columns and shuffle data along. It also needs a "header" area where rule snippets are setup, like the excel equivalent. -- 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

13 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-429) Rule meta data viewer/editor

by Michael Neale (JIRA)

Rule meta data viewer/editor ---------------------------- Key: JBRULES-429 URL: http://jira.jboss.com/jira/browse/JBRULES-429 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale Need to have a meta-data editor that is rule specific (including dublin core, but also perhaps rule attributes). Does not include documentation (that will be a seperate editor). -- 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

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBRULES-411) JBRMS Front End - parent task

by Michael Neale (JIRA)

JBRMS Front End - parent task ----------------------------- Key: JBRULES-411 URL: http://jira.jboss.com/jira/browse/JBRULES-411 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale This is the parent task for BRMS front end activities (which use the drools-repository component). No work should be done directly on this issue, only subtasks. -- 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

13 years, 5 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-412) Create web app component infrastructure

by Michael Neale (JIRA)

Create web app component infrastructure --------------------------------------- Key: JBRULES-412 URL: http://jira.jboss.com/jira/browse/JBRULES-412 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Michael Neale Using Seam, or otherwise, need a "back end" web component framework which will work with the GWT generated UI, and use the drools-repository api. This task is just to setup the initial skeleton for development -- 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

13 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1108) Re-factor WSRPProducer to extract a MetaData interface

by Chris Laprun (JIRA)

Re-factor WSRPProducer to extract a MetaData interface ------------------------------------------------------ Key: JBPORTAL-1108 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1108 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.DR1, 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.Alpha1 Methods pertaining to registration, cookies and session expiration should all be part of the MetaData... -- 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

13 years, 6 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2006