March 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-108) Backport JSF API Spec update to JSF 2.1

by Karel Piwko (JIRA)

Karel Piwko created JBEE-108: -------------------------------- Summary: Backport JSF API Spec update to JSF 2.1 Key: JBEE-108 URL: https://issues.jboss.org/browse/JBEE-108 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: jboss-javaee-specs Affects Versions: JavaEE 6 Spec APIs 3.0.0.Beta1 Reporter: Karel Piwko Assignee: Paul Gier Priority: Critical Fix For: JavaEE 6 Spec APIs 3.0.0 JSF API SPEC was updated to 2.1 in version 2.1.0.Beta1, however 3.0.0.Beta1 still contains JSF 2.0 spec. https://issues.jboss.org/browse/JBEE-88 -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] (AS7-2801) Certificate to principal mapping

by Yves Peter (Created) (JIRA)

Certificate to principal mapping -------------------------------- Key: AS7-2801 URL: https://issues.jboss.org/browse/AS7-2801 Project: Application Server 7 Issue Type: Feature Request Components: Security, Web Affects Versions: 7.1.0.Beta1 Reporter: Yves Peter Assignee: Anil Saldhana In JBoss 7 it is no longer possible to configure how a certificate is mapped to a principal using client-cert authentication. The dynamic code was removed in JBoss 7 in the JBossWebRealm and is now hard coded to use the SubjectDNMapping: http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/... http://grepcode.com/file/repository.jboss.org/nexus/content/repositories/... Also the JBossWebRealm does only consider role- but no principal-mapping modules. We use this for authentication of users against an ldap server where the dn of the user doesn't match the dn in the ldap server. Also it's useful for display purpose in an application. An example and some further information is in the linked user form thread. -- 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, 1 month

6
6
0 / 0

[JBoss JIRA] (AS7-4205) Infinispan subsystem should configure GlobalConfiguration with ModularClassResolver.

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-4205: --------------------------------- Summary: Infinispan subsystem should configure GlobalConfiguration with ModularClassResolver. Key: AS7-4205 URL: https://issues.jboss.org/browse/AS7-4205 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.2.Final -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-109) Create a servlet 2.5 osgi bundle

by Paul Gier (JIRA)

Paul Gier created JBEE-109: ------------------------------ Summary: Create a servlet 2.5 osgi bundle Key: JBEE-109 URL: https://issues.jboss.org/browse/JBEE-109 Project: JBoss JavaEE Spec APIs Issue Type: Task Components: jboss-servlet-api Reporter: Paul Gier Assignee: Paul Gier The jbosgi project uses the servlet spec 2.5. The JBoss specs project should make this available as an osgi bundle similar to the 3.0 version. -- 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, 1 month

1
2
0 / 0

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

by Alexey S. (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] Alexey S. commented on AS7-1338: -------------------------------- OK,thnx > 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 > Labels: eap6_prd_req > 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, 1 month

1
0
0 / 0

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

by Justin Bertram (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] Justin Bertram commented on AS7-1338: ------------------------------------- Alexey, please take this to the AS 7 User Forum (https://community.jboss.org/en/jbossas7?view=discussions). A closed JIRA is not the place to discuss problems like these. > 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 > Labels: eap6_prd_req > 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, 1 month

1
0
0 / 0

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

by Alexey S. (JIRA)

[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ] Alexey S. commented on AS7-1338: -------------------------------- Hello. I have the experience of 11 years with JBOSS. Recently we wanna to migrate from JBOSS 6 to JBOSS 7.1.0 final Here is a part of my code final Hashtable jndiProperties = new Hashtable(); jndiProperties.put(Context.PROVIDER_URL, "remote://localhost:4447"); jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory"); jndiProperties.put("remote.connection.default.username","usera"); jndiProperties.put("remote.connection.default.password","passa"); Context context; try { context = new InitialContext(jndiProperties); I may put username and password, I may not put it - all the time I got ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed] at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:36) at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:117) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307) at javax.naming.InitialContext.init(InitialContext.java:242) at javax.naming.InitialContext.<init>(InitialContext.java:216) JBoss is of course running and the user added to application users. Any help? Is JBoss 7.1.0 robust enough to port the system from Jboss 6 to it? > 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 > Labels: eap6_prd_req > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (AS7-3043) RESTEasy: Setting cfg. param resteasy.scan.resources=false causes that servlet-name javax.ws.rs.core.Application is not defined

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-3043?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-3043. --------------------------------- Fix Version/s: 7.1.0.CR1 Resolution: Done Do not re-open JIRA issues resolved against released versions, file new a new JIRA instead. > RESTEasy: Setting cfg. param resteasy.scan.resources=false causes that servlet-name javax.ws.rs.core.Application is not defined > ------------------------------------------------------------------------------------------------------------------------------- > > Key: AS7-3043 > URL: https://issues.jboss.org/browse/AS7-3043 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: 7.1.0.Beta1b, 7.1.1.Final, 7.1.2.Final > Reporter: Pavel Janousek > Assignee: Weinan Li > Priority: Blocker > Fix For: 7.1.0.CR1 > > > When I set {code:xml} > <context-param> > <param-name>resteasy.scan.resources</param-name> > <param-value>false</param-value> > </context-param> > {code} in web.xml, I can't use{code:xml} > <servlet-mapping> > <servlet-name>javax.ws.rs.core.Application</servlet-name> > <url-pattern>/myjaxrs/*</url-pattern> > </servlet-mapping> > {code} because _javax.ws.rs.core.Application_ is not defined yet. > I got exception like this:{code}java.lang.IllegalArgumentException: Servlet mapping specifies an unknown servlet name javax.ws.rs.core.Application{code} > I'm not sure, but I think that declaration of servlet-name _javax.ws.rs.core.Application_ should be independent to setting this parameter to *any* value. It should only impact scanning user-defined (= included in WAR) resources. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBEE-106) make jboss-servlet-api JAR an OSGi bundle.

by Paul Gier (JIRA)

Paul Gier created JBEE-106: ------------------------------ Summary: make jboss-servlet-api JAR an OSGi bundle. Key: JBEE-106 URL: https://issues.jboss.org/browse/JBEE-106 Project: JBoss JavaEE Spec APIs Issue Type: Enhancement Components: jboss-servlet-api Reporter: Paul Gier Assignee: Paul Gier Fix For: JavaEE 6 Spec APIs 3.0.0 Make servlet-api into a valid OSGi bundle -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] (AS7-3954) TS: clustering: test with different JGroups stack

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3954: ----------------------------------- Summary: TS: clustering: test with different JGroups stack Key: AS7-3954 URL: https://issues.jboss.org/browse/AS7-3954 Project: Application Server 7 Issue Type: Feature Request Components: Clustering, Test Suite Affects Versions: 7.1.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 7.1.1.Final Just like we did in AS4/5/6. -- 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, 1 month

2
3
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 March 2012