November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6003) jboss.entity.manager.jndi.name in persistence.xml doesn't work

by Xavier Jodoin (JIRA)

jboss.entity.manager.jndi.name in persistence.xml doesn't work -------------------------------------------------------------- Key: JBAS-6003 URL: https://jira.jboss.org/jira/browse/JBAS-6003 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.CR2 Environment: Ubuntu 8.04 java 1.6 Reporter: Xavier Jodoin Works under jboss 5 CR1 and not under CR2 the jndi name is not bound: <property name="jboss.entity.manager.jndi.name" value="securityEntityManager"/> new InitialContext().lookup("securityEntityManager"); <?xml version="1.0" encoding="UTF-8"?> <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation = "http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0"> <persistence-unit name="NAIDsecurity" transaction-type="JTA"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <jta-data-source>java:/SECURITYDS</jta-data-source> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.SQLServerDialect"/> <property name="hibernate.show_sql" value="false"/> <property name="jboss.entity.manager.jndi.name" value="securityEntityManager"/> <property name="hibernate.hbm2ddl.auto" value="update"/> </properties> </persistence-unit> </persistence> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5993) Need to add ProfileService failed deployment tests

by Scott M Stark (JIRA)

Need to add ProfileService failed deployment tests -------------------------------------------------- Key: JBAS-5993 URL: https://jira.jboss.org/jira/browse/JBAS-5993 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ProfileService Reporter: Scott M Stark Assignee: Scott M Stark Fix For: JBossAS-5.0.0.GA We need to add ProfileService failed deployment tests to validate that the reason for the failure is being propagated back to the ProfileService.DeploymentManager client -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBREM-1039) Release 2.2.2.SP11

by Ron Sigal (JIRA)

Release 2.2.2.SP11 ------------------ Key: JBREM-1039 URL: https://jira.jboss.org/jira/browse/JBREM-1039 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP11 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5529) Add for JBAS, JBossWeb, JBossWeb connector components

by Charles Crouch (JIRA)

Add for JBAS, JBossWeb, JBossWeb connector components ----------------------------------------------------- Key: JBAS-5529 URL: http://jira.jboss.com/jira/browse/JBAS-5529 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Charles Crouch -- 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

15 years, 10 months

4
19
0 / 0

[JBoss JIRA] Created: (JBAOP-666) Reimplement classpools for AS

by Kabir Khan (JIRA)

Reimplement classpools for AS ----------------------------- Key: JBAOP-666 URL: https://jira.jboss.org/jira/browse/JBAOP-666 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 2.1.0.GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
6
0 / 0

[JBoss JIRA] Created: (JBAOP-283) Better documentation for metadata and CallLoggingInterceptor

by Kabir Khan (JIRA)

Better documentation for metadata and CallLoggingInterceptor ------------------------------------------------------------ Key: JBAOP-283 URL: http://jira.jboss.com/jira/browse/JBAOP-283 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0 -- 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

15 years, 10 months

2
15
0 / 0

[JBoss JIRA] Created: (JBAOP-309) Investigate pointcut matching on annotation attributes

by Kabir Khan (JIRA)

Investigate pointcut matching on annotation attributes ------------------------------------------------------ Key: JBAOP-309 URL: http://jira.jboss.com/jira/browse/JBAOP-309 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha3 -- 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

15 years, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAOP-334) Add Before/After/Throwing to array interception

by Kabir Khan (JIRA)

Add Before/After/Throwing to array interception ----------------------------------------------- Key: JBAOP-334 URL: http://jira.jboss.com/jira/browse/JBAOP-334 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan -- 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

15 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAOP-333) Make Array interception aware of scoped classloading

by Kabir Khan (JIRA)

Make Array interception aware of scoped classloading ---------------------------------------------------- Key: JBAOP-333 URL: http://jira.jboss.com/jira/browse/JBAOP-333 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0.0.alpha3 -- 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

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAOP-355) Improve aopc

by Kabir Khan (JIRA)

Improve aopc ------------ Key: JBAOP-355 URL: http://jira.jboss.com/jira/browse/JBAOP-355 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0.0.alpha3 Hey Kabir, Some hopefully more constructive inputs on aopc: 1) It appears that if any jboss-aop.xml is on the classpath defined by the "classpath" element, it gets applied. In the testsuite, I used a broad classpath, and it picks up a file with the same bindings as the file I name in aoppath. This causes aopc to fail; javaassist complains about seeing the same field twice. The workaround is to not specify anything in aoppath. But that's confusing. Seems to me that if aoppath is used, only bindings specified on the files in that path should be applied. 2) When trying to figure the above out, I look at the Reference Guide and then get really confused. classpath/classpathref -- simple enough. src -- isn't really source (i.e. .java) it's class files. It's basically a subset of classpath, right? This isn't spelled out clearly in the docs and the name of the element is confusing. aopclasspath -- Huh??? 3) Also, having "include" as a nested element within src would be more consistent with normal ant usage. Cheers, Brian Stansberry Lead, AS Clustering JBoss, a division of Red Hat Ph: 510-396-3864 skype: bstansberry -- 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

15 years, 10 months

2
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008