November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBFORUMS-122) Links should be recognized

by Thomas Diesler (JIRA)

Links should be recognized -------------------------- Key: JBFORUMS-122 URL: http://jira.jboss.com/jira/browse/JBFORUMS-122 Project: JBoss Forums Issue Type: Feature Request Components: Forum Enhancements Reporter: Thomas Diesler Assigned To: Sohil Shah Instead of [url]http://jira.jboss.com/jira/secure/CreateIssue.jspa[/url] I like to simply use http://jira.jboss.com/jira/secure/CreateIssue.jspa There are a lot of user provided links that I cannot click on. -- 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

12 years, 8 months

4
3
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-140) Examine need for a distributed service registry outside the AS

by Brian Stansberry (JIRA)

Examine need for a distributed service registry outside the AS -------------------------------------------------------------- Key: JBCLUSTER-140 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-140 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Is something like DRM needed outside the AS? If it is, do we want to use the JBoss Cache based version (creates JBC dependency.) DRM is used in two ways: 1) To maintain a distributed registry of remote invocation targets. 2) To maintain a distributed registry of services, which is done by having the service register a meaningless token under its key rather than a target. This is used by HASingleton. Need to examine whether this kind of thing is needed by Messaging, or whether simple listening for view changes is sufficient. Listening for view changes could be sufficient if each group member knew how to create a Remoting InvokerLocator for the other members based on the JGroups Address. But, this presupposes use of consistent ports across the cluster, and that the IP address used by JGroups is the one that Messaging traffic should use. -- 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

12 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-144) Consider other clustering code that can be removed from the AS

by Brian Stansberry (JIRA)

Consider other clustering code that can be removed from the AS -------------------------------------------------------------- Key: JBCLUSTER-144 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-144 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q4Y6 Things like the http session replication code that we've considered integrating into Tomcat. -- 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

12 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-141) Create a generic HA Singleton API

by Brian Stansberry (JIRA)

Create a generic HA Singleton API --------------------------------- Key: JBCLUSTER-141 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-141 Project: JBoss Clustering Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y6 Also want to extract the HASingletonElectionPolicy code from the AS codebase. -- 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

12 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-540) Create a Java Interface to allow JavaBeans to work more seamlessly as Facts

by Mark Proctor (JIRA)

Create a Java Interface to allow JavaBeans to work more seamlessly as Facts ----------------------------------------------------------------------------- Key: JBRULES-540 URL: http://jira.jboss.com/jira/browse/JBRULES-540 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 3.1-m1 We want to move management of the bean and its working memory up a layer. When a bean is instantiated by an IoC framework it should weave in an interface to provide better background interoprability between the bean and working memories. further the IoC container should control the life cycle, assert and retract, of that bean in various working memories. -- 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

12 years, 11 months

3
6
0 / 0

[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: (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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2006