December 2011 - jboss-jira - Jboss List Archives

[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

14 years, 7 months

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

14 years, 7 months

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

14 years, 7 months

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

14 years, 7 months

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

14 years, 7 months

1
0
0 / 0

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

by David Lloyd (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] David Lloyd updated AS7-1338: ----------------------------- Fix Version/s: No Release (was: 7.1.0.CR1) Description: 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. was: <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :( <opalka> wolfc, dmlloyd in the config I see the following ports defined <opalka> --- <opalka> <socket-binding name="jndi" port="1099"/> <opalka> <socket-binding name="jmx-connector-registry" port="1090"/> <opalka> <socket-binding name="jmx-connector-server" port="1091"/> <opalka> --- <dmlloyd> we don't do JNDI over RMI anymore <dmlloyd> that listing is an error <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to? <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol? <dmlloyd> no, we will be able to, it'll just work somewhat differently <opalka> dmlloyd, ok, I'm excluding the tests then ... <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment? <dmlloyd> not that I'm aware of, it's just an outstanding task <dmlloyd> remote invocation is not planned to be covered in next months' beta release <opalka> dmlloyd, ok, thx for info ;) Forum Reference: http://community.jboss.org/message/619784#619784 (was: http://community.jboss.org/message/619784#619784) Was previously rejected: <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :( <opalka> wolfc, dmlloyd in the config I see the following ports defined <opalka> --- <opalka> <socket-binding name="jndi" port="1099"/> <opalka> <socket-binding name="jmx-connector-registry" port="1090"/> <opalka> <socket-binding name="jmx-connector-server" port="1091"/> <opalka> --- <dmlloyd> we don't do JNDI over RMI anymore <dmlloyd> that listing is an error <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to? <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol? <dmlloyd> no, we will be able to, it'll just work somewhat differently <opalka> dmlloyd, ok, I'm excluding the tests then ... <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment? <dmlloyd> not that I'm aware of, it's just an outstanding task <dmlloyd> remote invocation is not planned to be covered in next months' beta release <opalka> dmlloyd, ok, thx for info ;) But now it's back :) > 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: Blocker > Fix For: No Release > > > 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

14 years, 7 months

1
0
0 / 0

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

by Jason Greene (Commented) (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] Jason Greene commented on AS7-1338: ----------------------------------- We have decided to implement a pure jndi forwarding remote jndi solution for everyone that is used to the old behavior. > 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: Blocker > Fix For: 7.1.0.CR1 > > > <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :( > <opalka> wolfc, dmlloyd in the config I see the following ports defined > <opalka> --- > <opalka> <socket-binding name="jndi" port="1099"/> > <opalka> <socket-binding name="jmx-connector-registry" port="1090"/> > <opalka> <socket-binding name="jmx-connector-server" port="1091"/> > <opalka> --- > <dmlloyd> we don't do JNDI over RMI anymore > <dmlloyd> that listing is an error > <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to? > <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol? > <dmlloyd> no, we will be able to, it'll just work somewhat differently > <opalka> dmlloyd, ok, I'm excluding the tests then ... > <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment? > <dmlloyd> not that I'm aware of, it's just an outstanding task > <dmlloyd> remote invocation is not planned to be covered in next months' beta release > <opalka> dmlloyd, ok, thx for info ;) -- 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

14 years, 7 months

1
0
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.CR1 (was: No Release) Forum Reference: http://community.jboss.org/message/619784#619784 (was: http://community.jboss.org/message/619784#619784) > 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: Blocker > Fix For: 7.1.0.CR1 > > > <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :( > <opalka> wolfc, dmlloyd in the config I see the following ports defined > <opalka> --- > <opalka> <socket-binding name="jndi" port="1099"/> > <opalka> <socket-binding name="jmx-connector-registry" port="1090"/> > <opalka> <socket-binding name="jmx-connector-server" port="1091"/> > <opalka> --- > <dmlloyd> we don't do JNDI over RMI anymore > <dmlloyd> that listing is an error > <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to? > <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol? > <dmlloyd> no, we will be able to, it'll just work somewhat differently > <opalka> dmlloyd, ok, I'm excluding the tests then ... > <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment? > <dmlloyd> not that I'm aware of, it's just an outstanding task > <dmlloyd> remote invocation is not planned to be covered in next months' beta release > <opalka> dmlloyd, ok, thx for info ;) -- 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

14 years, 7 months

1
0
0 / 0

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

by Jason Greene (Assigned) (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] Jason Greene reassigned AS7-1338: --------------------------------- Assignee: John Bailey (was: David Lloyd) > 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: Blocker > Fix For: 7.1.0.CR1 > > > <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :( > <opalka> wolfc, dmlloyd in the config I see the following ports defined > <opalka> --- > <opalka> <socket-binding name="jndi" port="1099"/> > <opalka> <socket-binding name="jmx-connector-registry" port="1090"/> > <opalka> <socket-binding name="jmx-connector-server" port="1091"/> > <opalka> --- > <dmlloyd> we don't do JNDI over RMI anymore > <dmlloyd> that listing is an error > <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to? > <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol? > <dmlloyd> no, we will be able to, it'll just work somewhat differently > <opalka> dmlloyd, ok, I'm excluding the tests then ... > <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment? > <dmlloyd> not that I'm aware of, it's just an outstanding task > <dmlloyd> remote invocation is not planned to be covered in next months' beta release > <opalka> dmlloyd, ok, thx for info ;) -- 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

14 years, 7 months

1
0
0 / 0

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

by Jason Greene (Reopened) (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] Jason Greene reopened AS7-1338: ------------------------------- It's back! > 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: David Lloyd > Priority: Blocker > Fix For: No Release > > > <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :( > <opalka> wolfc, dmlloyd in the config I see the following ports defined > <opalka> --- > <opalka> <socket-binding name="jndi" port="1099"/> > <opalka> <socket-binding name="jmx-connector-registry" port="1090"/> > <opalka> <socket-binding name="jmx-connector-server" port="1091"/> > <opalka> --- > <dmlloyd> we don't do JNDI over RMI anymore > <dmlloyd> that listing is an error > <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to? > <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol? > <dmlloyd> no, we will be able to, it'll just work somewhat differently > <opalka> dmlloyd, ok, I'm excluding the tests then ... > <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment? > <dmlloyd> not that I'm aware of, it's just an outstanding task > <dmlloyd> remote invocation is not planned to be covered in next months' beta release > <opalka> dmlloyd, ok, thx for info ;) -- 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

14 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2011