December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1387) Enable SSL for the Remoting/Native Interface

by Darran Lofthouse (JIRA)

Enable SSL for the Remoting/Native Interface -------------------------------------------- Key: AS7-1387 URL: https://issues.jboss.org/browse/AS7-1387 Project: Application Server 7 Issue Type: Task Components: Domain Management, Remoting, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1642) If --domain-config is used in domain.sh, changes to the configuration using the web console are not correctly persisted

by Georges Berscheid (JIRA)

If --domain-config is used in domain.sh, changes to the configuration using the web console are not correctly persisted ----------------------------------------------------------------------------------------------------------------------- Key: AS7-1642 URL: https://issues.jboss.org/browse/AS7-1642 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.1.Final Environment: RHEL6 Reporter: Georges Berscheid Assignee: Brian Stansberry When AS7 is started using $JBOSS_HOME/bin/domain.sh --domain-config=/etc/as7/domain.xml, all changes made through the web console are persisted in $JBOSS_HOME/domain/configuration/domain.xml. That means for example that deployments don't survive server restarts. Also trying to add the same deployment again does not seem to work, probably because the files already exist in the $JBOSS_HOME/domain/content directory. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

5
6
0 / 0

[JBoss JIRA] (AS7-2697) Recomended changes to the standard-ha.xml file to make clustering easier for demos

by Jim Tyrrell (Created) (JIRA)

Recomended changes to the standard-ha.xml file to make clustering easier for demos ---------------------------------------------------------------------------------- Key: AS7-2697 URL: https://issues.jboss.org/browse/AS7-2697 Project: Application Server 7 Issue Type: Feature Request Components: Clustering Reporter: Jim Tyrrell Assignee: Paul Ferraro <socket-binding-group name="standard-sockets" default-interface="public"> should become <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.default.port-offset:0}"> <native-interface interface="management" port="${jboss.native.managementport:9999}"/> <http-interface interface="management" port="${jboss.http.managementport:9990}"/> -- 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

13 years

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1994) access to the ModelNodeRegistration during handling of an operation and during deployment

by Stefano Maestri (JIRA)

access to the ModelNodeRegistration during handling of an operation and during deployment ----------------------------------------------------------------------------------------- Key: AS7-1994 URL: https://issues.jboss.org/browse/AS7-1994 Project: Application Server 7 Issue Type: Task Affects Versions: 7.1.0.Alpha1 Reporter: Stefano Maestri Assignee: Brian Stansberry Fix For: 7.1.0.CR1 Hi All, I'm trying to resume here the discussion I had yesterday on IRC with Brian and Jesper. Basically JCA needs to have and already deployed instance of ResourceAdapter when adding its metrics and some operation. The reason for that is because some operation and metrics availability are known only at runtime, depending from RA status and/or vendor specific feature known only. Speaking from a Model point of view the basically issue is to have access to the ModelNodeRegistration when the RA instance is created and these runtime infos are available. There are 2 cases: 1) during handling ADD operation for a DataSource or special ResourceAdapter creation withour rar deployment (like hornetQ). 2) during foo.rar deployment chain We have also discussed where we can put these operation in the model tree. Also in this case there are two possible places: 1) at subsystem level for special no-deployment RA (DataSources and HornetQ atm). So we will obtain something like /subsystem=datasource/data-source=myDS and /subsystem=hq/ra 2) at DUP level /deployment=foo.rar Having this deployment support we can remove the current operation in /subsystem=resource-adapters that is redudant, referring the same RA (or better a subset of deployed ones) Hoping to have written all the matters discussed, feel free to integrate and/or ask. regards S. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

7
9
0 / 0

[JBoss JIRA] Created: (AS7-1388) Certificate based authentication.

by Darran Lofthouse (JIRA)

Certificate based authentication. --------------------------------- Key: AS7-1388 URL: https://issues.jboss.org/browse/AS7-1388 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

5
6
0 / 0

[JBoss JIRA] (AS7-2890) Unable to remove CONSOLE logging from standalone.xml

by William DeCoste (Created) (JIRA)

Unable to remove CONSOLE logging from standalone.xml ---------------------------------------------------- Key: AS7-2890 URL: https://issues.jboss.org/browse/AS7-2890 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.1.Final Reporter: William DeCoste Assignee: Jason Greene Remove CONSOLE from the logging module in standalone, start AS7.0.1, and it comes back! If I remove CONSOLE from logging.properties too then it won't start. -- 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

13 years

5
5
0 / 0

[JBoss JIRA] (AS7-2889) Upagrade to Hibernate Commons Annotations 4.0.1.Final

by Sanne Grinovero (Created) (JIRA)

Upagrade to Hibernate Commons Annotations 4.0.1.Final ----------------------------------------------------- Key: AS7-2889 URL: https://issues.jboss.org/browse/AS7-2889 Project: Application Server 7 Issue Type: Task Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 7.1.0.CR1 -- 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

13 years

2
1
0 / 0

[JBoss JIRA] (AS7-2203) Add Arquillian Container support for AS 7 domain controller

by Rajesh Rajasekaran (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-2203?page=com.atlassian.jira.plugin.s... ] Rajesh Rajasekaran updated AS7-2203: ------------------------------------ Labels: arq_qe_blocker (was: ) > Add Arquillian Container support for AS 7 domain controller > ------------------------------------------------------------ > > Key: AS7-2203 > URL: https://issues.jboss.org/browse/AS7-2203 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Affects Versions: 7.1.0.CR1 > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Labels: arq_qe_blocker > > A container for AS 7 domain controller would be very helpful for it's integration testsuite. > Such container should support: > * Attaching hosts to a domain > * Start, stop a domain with multiple hosts > * Configuration (creation) of the domain using domain config file > * Configuration (creation) of a profile using a CLI batch > * Configuration (creation) of a profile using a callback class which would handle communication with Java API > More requirements to come. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBEE-98) Fix compiler warnings in RMI spec build

by Paul Gier (Created) (JIRA)

Fix compiler warnings in RMI spec build --------------------------------------- Key: JBEE-98 URL: https://issues.jboss.org/browse/JBEE-98 Project: JBoss JavaEE Spec APIs Issue Type: Enhancement Components: jboss-rmi-api Reporter: Paul Gier Priority: Optional Fix For: JavaEE 6 Spec APIs 3.0.0 There are some compiler warnings when using JDK 6 to build the RMI spec APIs {quote} [WARNING] /home/pgier/projects/jboss-specs/jboss-rmi-api_spec/src/main/java/org/jboss/sun/corba/Bridge.java:[140,22] sun.misc.Unsafe is Sun proprietary API and may be removed in a future release [WARNING] /home/pgier/projects/jboss-specs/jboss-rmi-api_spec/src/main/java/org/jboss/sun/corba/Bridge.java:[157,29] sun.reflect.ReflectionFactory is Sun proprietary API and may be removed in a future release {quote} -- 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

13 years

4
3
0 / 0

[JBoss JIRA] (AS7-1338) Remote JNDI support for AS7

by Jason Greene (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1338: ------------------------------ Fix Version/s: 7.1.0.Final (was: No Release) Priority: Critical (was: Blocker) Forum Reference: http://community.jboss.org/message/619784#619784 (was: http://community.jboss.org/message/619784#619784) This is a usability improvement so I'm assigning it to Final > Remote JNDI support for AS7 > --------------------------- > > Key: AS7-1338 > URL: https://issues.jboss.org/browse/AS7-1338 > Project: Application Server 7 > Issue Type: Task > Components: Naming > Reporter: Richard Opalka > Assignee: John Bailey > Priority: Critical > Fix For: 7.1.0.Final > > > Add support for remote JNDI after all. It was agreed that: > * Remote JNDI would run over Remoting > * Remote JNDI for EJB is strictly a legacy access protocol, deprecated in favor of "ejb:" > * The Remote JNDI service would proxy to a specific Context of the server JNDI tree - maybe "java:jboss/shared", maybe something else > * Server-side services would opt-in to Remote JNDI; initially we'd only support: > ** Remote EJB interfaces > ** HornetQ connection factories > * In the future we may support: > ** User bindings, so long as they're serializable > * In the future we will never support: > ** Proxied DataSources > ** Proxied JMS invocations > Initial project tree is at https://github.com/dmlloyd/jboss-remote-jndi for now. -- 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

13 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2011