December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-568) IDE to understand new XXX.package rule package config file, and support 1 rule per file "convention" to sync with repository

by Michael Neale (JIRA)

IDE to understand new XXX.package rule package config file, and support 1 rule per file "convention" to sync with repository ---------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-568 URL: http://jira.jboss.com/jira/browse/JBRULES-568 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.1-m3 Reporter: Michael Neale Assigned To: Kris Verlaenen Fix For: 3.1-m3 package layout will be something like: /<RulePackageName>.package - has imports in it etc... /Rule Name 1.rule (vanilla DRL) /Rule Name 2.brule (uses DSL) /XXX.dsl (used by brule file) None of the atomic rule files will have package name, or anything other then when/then/attributes, the IDE will have to look in to the .package file to find this out. .drl files can work as they do now. Let me know if this is a dupe ;) -- 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
7
0 / 0

[JBoss JIRA] Created: (JBRULES-493) Remember selected working memory for debug views

by Mark Proctor (JIRA)

Remember selected working memory for debug views ------------------------------------------------ Key: JBRULES-493 URL: http://jira.jboss.com/jira/browse/JBRULES-493 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m1 When you select working memory it should remember that instance, so when you are propagating through the network you shouldn't have to keep re-selecting it to view data. Better yet we should have another debug view that collects working memory instances as it "realises" them during debug runtime, the current one is highlighed and a different current can easily be selected. -- 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

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-396) Replace all uses of Vector, ArrayList etc with interfaces

by Bela Ban (JIRA)

Replace all uses of Vector, ArrayList etc with interfaces --------------------------------------------------------- Key: JGRP-396 URL: http://jira.jboss.com/jira/browse/JGRP-396 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 - E.g. - Vector --> Collection - ArrayList --> List -- 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

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3816) Wildcard handling in "org.jboss.metadata.MethodAttributes.patternMatches()" isn't correct (or documentation problem)

by Anders Welen (JIRA)

Wildcard handling in "org.jboss.metadata.MethodAttributes.patternMatches()" isn't correct (or documentation problem) -------------------------------------------------------------------------------------------------------------------- Key: JBAS-3816 URL: http://jira.jboss.com/jira/browse/JBAS-3816 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: Anders Welen Priority: Minor Attachments: JBossBug.tgz The method "patternMatches" in "org.jboss.metadata.MethodAttributes" just stops at the first wildcard ("*") found and assumes that match is ok. Either this is a bug or the documentation ("http://docs.jboss.com/jbossas/guides/j2eeguide/r2/en/html_single/#d0e11084") should be changed and clearly inform that the wildcard must be the last character. If you specify for example "*get*" than all methods will be matched.... -- 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, 2 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-3703) Update JRMPInvoker to not cast exported object to RemoteStub

by Scott M Stark (JIRA)

Update JRMPInvoker to not cast exported object to RemoteStub ------------------------------------------------------------ Key: JBAS-3703 URL: http://jira.jboss.com/jira/browse/JBAS-3703 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Remoting Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.3 SP1 Reporter: Scott M Stark Assigned To: Tom Elrod Fix For: JBossAS-4.0.6.CR1 If one runs with the jdk5 java.rmi.server.ignoreStubClasses dynamic stub override to force the server to generate stubs for exported objects, the JRMPInvoker fails to start with the following exception: [starksm@succubus bin]$ run.sh -D-Djava.rmi.server.ignoreStubClasses=true ========================================================================= ... 11:55:52,477 WARN [ServiceController] Problem starting service jboss:service=invoker,type=jrmp java.lang.ClassCastException: $Proxy13 at org.jboss.invocation.jrmp.server.JRMPInvoker.exportCI(JRMPInvoker.java:437) at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMPInvoker.java:359) at org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JRMPInvoker.java:136) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274) The reason is that the code creating the remote object is explictly casting the export result to a RemoteStub: protected void exportCI() throws Exception { this.invokerStub = (RemoteStub) UnicastRemoteObject.exportObject (this, rmiPort, clientSocketFactory, serverSocketFactory); } even though the public contract for this stub only requires a Serializable instance. The type of the invokerStub should just be relaxed to Serializable. -- 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, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-3778) AttributePersistenceService does not allow absolute path for data-directory value

by Darran Lofthouse (JIRA)

AttributePersistenceService does not allow absolute path for data-directory value --------------------------------------------------------------------------------- Key: JBAS-3778 URL: http://jira.jboss.com/jira/browse/JBAS-3778 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX Affects Versions: JBossAS-4.0.4.GA Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: JBossAS-4.0.6.CR1 AttributePersistenceService does not allow absolute path for data-directory value, any value specified even with a leading '/' is created within the folder of the configuration being executed. Also the default configuration in the jboss-service.xml should take into account the setting for jboss.server.data.dir -- 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

4
4
0 / 0

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006