July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-453) Change signature of Channel.down() to return Object, rename downcall() to down()

by Bela Ban (JIRA)

Change signature of Channel.down() to return Object, rename downcall() to down() -------------------------------------------------------------------------------- Key: JGRP-453 URL: http://jira.jboss.com/jira/browse/JGRP-453 Project: JGroups Issue Type: Task Affects Versions: 2.5 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 3.0 We had to make Channel.down() return void, otherwise JGroups would not have been backwards compatible with JBoss 4.0.5 -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-513) Remove deprecated system properties (non 'jboss' namespace)

by Brian Stansberry (JIRA)

Remove deprecated system properties (non 'jboss' namespace) ----------------------------------------------------------- Key: JGRP-513 URL: http://jira.jboss.com/jira/browse/JGRP-513 Project: JGroups Issue Type: Task Reporter: Brian Stansberry Assigned To: Bela Ban Priority: Minor As discussed on http://wiki.jboss.org/wiki/Wiki.jsp?page=SystemProps there are a number of deprecated, 'legacy' system properties. This is just a JIRA entry to track remembering to clean them up. This JIRA is for the non-'jboss' namespaced properties, which perhaps we would keep around longer than the 'jboss' ones. -- 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
2
0 / 0

[JBoss JIRA] Created: (JGRP-512) Remove support for deprecated 'jboss' namespaced system properties

by Brian Stansberry (JIRA)

Remove support for deprecated 'jboss' namespaced system properties ------------------------------------------------------------------ Key: JGRP-512 URL: http://jira.jboss.com/jira/browse/JGRP-512 Project: JGroups Issue Type: Task Reporter: Brian Stansberry Assigned To: Bela Ban Priority: Minor As discussed on http://wiki.jboss.org/wiki/Wiki.jsp?page=SystemProps there are a number of deprecated, 'legacy' system properties. This is just a JIRA entry to track remembering to clean them up. I'm creating a separate JIRA for the non-'jboss' namespaced properties. Use of the 'jboss' namespace isn't too good, so it might be justified removing those earlier, e.g. 2.5, so users won't use them in AS 5.x and expect them to work. -- 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
4
0 / 0

[JBoss JIRA] Created: (JGRP-563) Consolidate state transfer API to use streams

by Vladimir Blagojevic (JIRA)

Consolidate state transfer API to use streams --------------------------------------------- Key: JGRP-563 URL: http://jira.jboss.com/jira/browse/JGRP-563 Project: JGroups Issue Type: Task Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 3.0 Although streaming state transfer has its advantages over byte based state transfer, byte based state transfer is absolutely necessary since streaming based transfer relies on plain sockets that are not firewall friendly. However, that does not mean that we cannot consolidate state transfer API at application level and mask byte based transfer with streams. We have already done this in JBC 2.0 so there is no reason not to do it on JGroups level as well. Advantages: - simpler state transfer API - interchangeable state transfer mechanism without affect on application - simplification of client application Disadvantages: - we break current API by eliminating getState(byte[]) and setState(byte []) -- 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
2
0 / 0

[JBoss JIRA] Created: (JGRP-567) Add one shot state transfer for multiple substates

by Vladimir Blagojevic (JIRA)

Add one shot state transfer for multiple substates -------------------------------------------------- Key: JGRP-567 URL: http://jira.jboss.com/jira/browse/JGRP-567 Project: JGroups Issue Type: Feature Request Affects Versions: 2.x Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Currently (2.5) each sub state transfer requires separate state transfer invocation for each sub state. It would be very convenient if we could transfer a list of substates all in one underlying state transfer. This would require introduction of a new method in JChannel API, however we should avoid additional callbacks on application level. Proposed API for additional JChannel method is: public boolean getState(Address target, List<String> state_ids, long timeout) throws ChannelNotConnectedException, ChannelClosedException; -- 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
9
0 / 0

[JBoss JIRA] Created: (SECURITY-31) White Paper on JMX Security

by Anil Saldhana (JIRA)

White Paper on JMX Security --------------------------- Key: SECURITY-31 URL: http://jira.jboss.com/jira/browse/SECURITY-31 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: White Papers Reporter: Anil Saldhana Assigned To: Anil Saldhana There is a need for a simple technical white paper that talks about the various scenarios involved in security jmx in JBoss. This includes the jmx consoles as well as the invokers. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBRULES-842) Extract/index rule fact info on save

by Michael Neale (JIRA)

Extract/index rule fact info on save ------------------------------------ Key: JBRULES-842 URL: http://jira.jboss.com/jira/browse/JBRULES-842 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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
3
0 / 0

[JBoss JIRA] Created: (JBRULES-836) DSL expression browser

by Michael Neale (JIRA)

DSL expression browser ---------------------- Key: JBRULES-836 URL: http://jira.jboss.com/jira/browse/JBRULES-836 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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
3
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-4078) DeploymentManager.getAvailableModules() returns null

by Libor Kotouc (JIRA)

DeploymentManager.getAvailableModules() returns null ---------------------------------------------------- Key: JBAS-4078 URL: http://jira.jboss.com/jira/browse/JBAS-4078 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Environment: JBoss 5.0.0.beta2 trunk build 20070206, JDK 1.5.0_08 Reporter: Libor Kotouc Assigned To: Dimitris Andreadis Priority: Critical This issue blocks an integration of JBoss AS 5 into NetBeans IDE. Steps to reproduce the behavior: 1. create a simple web application and copy the .war file into the deploy directory (I used the 'default' server) 2. start JBoss server (./run.sh) 3. run the following code from a J2SE application (I added JBoss jars to the classpath): public class Main { public static void main(String[] args) { try { javax.enterprise.deploy.spi.factories.DeploymentFactory df = new org.jboss.deployment.spi.factories.DeploymentFactoryImpl(); javax.enterprise.deploy.spi.DeploymentManager dm; dm = df.getDeploymentManager("http://org.jboss.deployment/jsr88", null, null); javax.enterprise.deploy.spi.Target[] targets = dm.getTargets(); javax.enterprise.deploy.spi.TargetModuleID[] modules; modules = dm.getAvailableModules(javax.enterprise.deploy.shared.ModuleType.WAR, targets); System.out.println(targets.length + " " + targets[0]); System.out.println(modules); } catch (javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException ex) { } catch (javax.enterprise.deploy.spi.exceptions.TargetException ex) { } } } The output of System.out.println statements is: 1 org.jboss.deployment.spi.JMXTarget@161d36b null I expect the module representing the web application, but null is returned. -- 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

4
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007