October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2380) Decide how to distribute jars that are intended for client use only

by Thomas Diesler (Created) (JIRA)

Decide how to distribute jars that are intended for client use only ------------------------------------------------------------------- Key: AS7-2380 URL: https://issues.jboss.org/browse/AS7-2380 Project: Application Server 7 Issue Type: Task Reporter: Thomas Diesler Assignee: Jason Greene Fix For: 7.1.0.Beta1 Shelly says: One question I have, though, is the jar, jboss-as-ee-deployment-7.1.0.Alpha2-SNAPSHOT.jar, is not even part of the build. How do we ship a compliant EE implementation with JSR-88 if it is not included? I have to pick this jar up from jboss-as/ee-deployment/target -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
5
0 / 0

[JBoss JIRA] (AS7-2361) It appears there is no external JNDI port like 1099, even though the ports are in the console

by Jim Tyrrell (Created) (JIRA)

It appears there is no external JNDI port like 1099, even though the ports are in the console --------------------------------------------------------------------------------------------- Key: AS7-2361 URL: https://issues.jboss.org/browse/AS7-2361 Project: Application Server 7 Issue Type: Feature Request Components: Naming Reporter: Jim Tyrrell Assignee: John Bailey Many many customers use client lookups of JNDI contexts to get at what used to be called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is this be design? If so, this is going to be a problem for many current customers, as they do this today. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

9
15
0 / 0

[JBoss JIRA] Created: (JBAS-8320) Logging initialization

by Alexey Loubyansky (JIRA)

Logging initialization ---------------------- Key: JBAS-8320 URL: https://jira.jboss.org/browse/JBAS-8320 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Modules Reporter: Alexey Loubyansky Assignee: David Lloyd Fix For: 7.0.0.M1 The following exception is thrown during the start-up on windows (Sun JDK). The system property is in fact set as the error message suggests and I can successfully invoke java.util.logging.Logger logger = java.util.logging.Logger.getLogger("mylogger"); System.out.println(logger.getClass().getName() + " " + logger.getClass().getClassLoader().getClass().getName() + " " + logger.getClass().getClassLoader()); from ManagedProcess just before this.log = Logger.getLogger("org.jboss.process." + processName); (which causes the error) and output will be org.jboss.logmanager.Logger org.jboss.modules.ModuleClassLoader ClassLoader for Module "module:org.jboss.logmanager:jboss-logmanager" Exception in thread "main" java.lang.IllegalStateException: The LogManager was not properly installed (you must set the "java.util.logging.manager" system property to "org.jboss.logmanager.LogManager") at org.jboss.logmanager.Logger.getLogger(Logger.java:60) at org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:55) at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:46) at org.jboss.logging.Logger.getLogger(Logger.java:2222) at org.jboss.as.process.ManagedProcess.<init>(ManagedProcess.java:66) at org.jboss.as.process.ProcessManagerMaster.addProcess(ProcessManagerMaster.java:64) at org.jboss.as.process.ProcessManagerMaster.main(ProcessManagerMaster.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.modules.Module.run(Module.java:105) at org.jboss.modules.Main.main(Main.java:169) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
13
0 / 0

[JBoss JIRA] Created: (JBJCA-655) ResourceAdapter level config properties are not being set

by Weston M. Price (JIRA)

ResourceAdapter level config properties are not being set --------------------------------------------------------- Key: JBJCA-655 URL: https://issues.jboss.org/browse/JBJCA-655 Project: IronJacamar Issue Type: Bug Components: Deployer Affects Versions: 1.0.3.Final Environment: JBoss AS7 7.1.0.Alpha1-SNAPSHOT, built from GitHub master branch Reporter: Weston M. Price Assignee: Stefano Maestri In attempting to deploy a RA in AS7 with ResourceAdapter configuration properties, these properties do not appear to be getting set. Sample: <resource-adapters> <resource-adapter> <archive> qpid-ra-0.10.rar </archive> <config-property name="TransactionManagerLocatorClass"> org.apache.qpid.ra.tm.JBoss7TransactionManagerLocator </config-property> <config-property name="TransactionManagerLocatorMethod"> getTm </config-property> </resource-adapter> </resource-adapters> Running via a debugger never shows the setter methods being invoked. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
2
0 / 0

[JBoss JIRA] (AS7-2098) Add missing attribute to the JBoss JMS XML Schema

by Andrig Miller (Created) (JIRA)

Add missing attribute to the JBoss JMS XML Schema ------------------------------------------------- Key: AS7-2098 URL: https://issues.jboss.org/browse/AS7-2098 Project: Application Server 7 Issue Type: Task Components: JMS Affects Versions: 7.1.0.Alpha1 Reporter: Andrig Miller Assignee: Clebert Suconic Fix For: 7.1.0.Beta1 I have been looking over all the XML schemas for my performance tuning work. In the JMS schema I don't see anything to configure a server as the active or backup. Maybe I'm missing something, but that seems to be missing. Also, I don't see anything on load balancing, between active servers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
4
0 / 0

[JBoss JIRA] Created: (SECURITY-45) Assimilate the Higgins Project SPI

by Anil Saldhana (JIRA)

Assimilate the Higgins Project SPI ---------------------------------- Key: SECURITY-45 URL: http://jira.jboss.com/jira/browse/SECURITY-45 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Security SPI Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 There is a need to get the SPI for Project Higgins Trust Framework into the JBoss Security SPI. -- 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

2
5
0 / 0

[JBoss JIRA] (AS7-2383) Implement CSRF Protection for HTTP Interface

by Darran Lofthouse (Created) (JIRA)

Implement CSRF Protection for HTTP Interface -------------------------------------------- Key: AS7-2383 URL: https://issues.jboss.org/browse/AS7-2383 Project: Application Server 7 Issue Type: Bug Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 7.1.0.CR1 For the HTTP interface we need some form of cross site request forgery protection to cover scenarios where an administrator has already authenticated against AS so the web browser has cached credentials - we need to prevent malicious requests from the same web browser. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (SECURITY-618) PicketBoxSecurityVault should add an INFO log entry after starting

by Anil Saldhana (JIRA)

PicketBoxSecurityVault should add an INFO log entry after starting ------------------------------------------------------------------ Key: SECURITY-618 URL: https://issues.jboss.org/browse/SECURITY-618 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Anil Saldhana After starting, the default vault implementation should have a log INFO entry. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (SECURITY-609) PicketBox exception messages should have error IDs

by Anil Saldhana (JIRA)

PicketBox exception messages should have error IDs -------------------------------------------------- Key: SECURITY-609 URL: https://issues.jboss.org/browse/SECURITY-609 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Marcus Moyses Fix For: PicketBox_v4_0_2 Based on http://community.jboss.org/wiki/HowToLogInJBossProjects we should look for all the exceptions that we throw and add in PBox error codes such that they can be documented properly -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
5
0 / 0

[JBoss JIRA] Created: (SECURITY-625) Retrofit standard login modules with the vault stuff

by Anil Saldhana (JIRA)

Retrofit standard login modules with the vault stuff ---------------------------------------------------- Key: SECURITY-625 URL: https://issues.jboss.org/browse/SECURITY-625 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v4_0_6 We need to retrofit all the standard login modules to able to get the password from the vault. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011