May 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMETA-37) Expand determineResolvedJndiName behavior to handle targeted business interfaces

by Scott M Stark (JIRA)

Expand determineResolvedJndiName behavior to handle targeted business interfaces -------------------------------------------------------------------------------- Key: JBMETA-37 URL: http://jira.jboss.com/jira/browse/JBMETA-37 Project: JBoss Metadata Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta13 Reporter: Scott M Stark Assigned To: Scott M Stark The ejb3 proxy factory needs to know the specific business local or remote interface a reference resolves to, so the determineResolvedJndiName needs to build jndi names of the form: base-name/remote-FQN base-name/local-FQN where FQN is the fully qualified name of the business interface. Input interfaces need to be mapped to the local/remote business interface for this to be done. -- 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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2011) HelloWorldPortal: can not access /portal/portal/HelloPortal

by Murray McAllister (JIRA)

HelloWorldPortal: can not access /portal/portal/HelloPortal ----------------------------------------------------------- Key: JBPORTAL-2011 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2011 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4.3 Final Environment: OS: Red Hat Enterprise Linux Client release 5.1 (Tikanga) JBoss AS 4.2.2 JDK 1.5 build 14 Java Packages: - java-1.5.0-sun-plugin-1.5.0.15-1jpp.2.el5 - java-1.5.0-sun-1.5.0.15-1jpp.2.el5 - java-1.5.0-sun-devel-1.5.0.15-1jpp.2.el5 Reporter: Murray McAllister Assigned To: Julien Viet Priority: Minor http://docs.jboss.com/jbportal/v2.6.4/referenceGuide/html/xmldescriptors.... To reproduce: 1. Download http://anonsvn.jboss.org/repos/portletswap/portlets/2_4/bundles/HelloWorl... 2. Copy helloworldportal.war to the /deploy/ directory. 3. Navigate to http://localhost:8080/portal/portal/HelloPortal Results: a log in prompt. I tried logging in with the default credentials, then a "403, Access to the specified resource () has been forbidden." error occurred. Navigating to http://localhost:8080/portal/portal/HelloPortal/foobar works as expected. Thanks! -- 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

18 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5516) Redirects DLQ messages to working queue once problem fixed with message.

by Nanda Cheluvadi (JIRA)

Redirects DLQ messages to working queue once problem fixed with message. ------------------------------------------------------------------------ Key: JBAS-5516 URL: http://jira.jboss.com/jira/browse/JBAS-5516 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.2.2.GA Environment: JMS, EJB3,JTA Reporter: Nanda Cheluvadi Assigned To: Carlo de Wolf Hi, I have a queue which produces tons of messages. if nay message fails it route to DLQ. here is the question: I wanted fix the problem with message which are in DLQ and redirects to working queue from DLQ.. HOw do i do that? -Nanda -- 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

18 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5476) JDK6: org.jboss.test.jbossmx.compliance.objectname

by Shelly McGowan (JIRA)

JDK6: org.jboss.test.jbossmx.compliance.objectname -------------------------------------------------- Key: JBAS-5476 URL: http://jira.jboss.com/jira/browse/JBAS-5476 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX Reporter: Shelly McGowan Assigned To: Shelly McGowan >From the JDK 6 adoption guide: The ObjectName functionality has been extended in Java SE 6 such that you can put a wildcard (* and/or ?) anywhere in a value, e.g., key=a*b as well as key=*. The asterisk matches any sequence of zero or more characters, while the question mark matches any single character. The tests using the following BAD_KEYVALS no longer throw the expected MalformedObjectNameException when running with JDK 6 // strings containing illegal chars to use in key or value positions public static final String[] BAD_KEYVALS = { "som?thing", // cannot contain pattern chars "som*thing", // cannot contain pattern chars }; AssertionFailedError: invalid object name: domain:key1=som*thing invalid object name: domain:key1=som?thing -- 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

18 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-5497) JDK6: org.jboss.test.cmp2.commerce.

by Shelly McGowan (JIRA)

JDK6: org.jboss.test.cmp2.commerce. ----------------------------------- Key: JBAS-5497 URL: http://jira.jboss.com/jira/browse/JBAS-5497 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assigned To: Shelly McGowan -- 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

18 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-5498) JDK6: org.jboss.test.security.test.LoginModulesUnitTestCase

by Shelly McGowan (JIRA)

JDK6: org.jboss.test.security.test.LoginModulesUnitTestCase ----------------------------------------------------------- Key: JBAS-5498 URL: http://jira.jboss.com/jira/browse/JBAS-5498 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan Assigned To: Shelly McGowan -- 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

18 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-5514) Deprecate JBoss Realms in favor of JBossWebRealm

by Anil Saldhana (JIRA)

Deprecate JBoss Realms in favor of JBossWebRealm ------------------------------------------------ Key: JBAS-5514 URL: http://jira.jboss.com/jira/browse/JBAS-5514 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.CR1 JBossSecurityMgrRealm extends JBossWebRealm JaccAuthorizationRealm extends JBossWebRealm -- 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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Updated: (HIBERNATE-84) Create a new tag for the standalone application

by Gail Badner (JIRA)

[ http://jira.jboss.com/jira/browse/HIBERNATE-84?page=all ] Gail Badner updated HIBERNATE-84: --------------------------------- Summary: Create a new tag for the standalone application (was: Check in Hibernate dependencies shipped with the standalone application) Assignee: Gail Badner > Create a new tag for the standalone application > ----------------------------------------------- > > Key: HIBERNATE-84 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-84 > Project: Hibernate > Issue Type: Task > Reporter: Gail Badner > Assigned To: Gail Badner > > The Hibernate dependencies will be replaced by the brew build to be the jars shipped with EAP 4.2 CP03. Since those jars may not exist at the time that Branch_3_2_4_SP1_CP is tagged for EAP 4.2 CP03, they will have to be checked in after the fact and a new tag will need to be created that corresponds with the Enterprise Hibernate 3.2.4.sp1.cp03 standalone distribution. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-215) Auth Config Registration should consider blank string for app context id

by Anil Saldhana (JIRA)

Auth Config Registration should consider blank string for app context id ------------------------------------------------------------------------ Key: SECURITY-215 URL: http://jira.jboss.com/jira/browse/SECURITY-215 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2.Beta7 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.CR1 -- 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

18 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-214) Add HttpServlet as layer to auth config provider

by Anil Saldhana (JIRA)

Add HttpServlet as layer to auth config provider ------------------------------------------------ Key: SECURITY-214 URL: http://jira.jboss.com/jira/browse/SECURITY-214 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2.Beta7 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2.CR1 -- 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

18 years, 2 months

1
1
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 May 2008