November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-408) Figure out a way to use alternate pom files in modules.

by Paul Gier (JIRA)

Figure out a way to use alternate pom files in modules. ------------------------------------------------------- Key: JBBUILD-408 URL: http://jira.jboss.com/jira/browse/JBBUILD-408 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server Currently the jdk14 builds have to be done as separate modules, because maven is not able to use alternate files (pom-jdk14.xml) in modules. This issue has been created to address this in maven: http://jira.codehaus.org/browse/MNG-3150 Until this issue is resolved, maybe an ant script can be created to build the modules as an aggregate. -- 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

17 years

1
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-417) Change maven classpath ordering for dependencies

by Paul Gier (JIRA)

Change maven classpath ordering for dependencies ------------------------------------------------ Key: JBBUILD-417 URL: http://jira.jboss.com/jira/browse/JBBUILD-417 Project: JBoss Build System Issue Type: Feature Request Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 Currently maven puts transitive dependencies first in the compile and test classpaths. It would be better to have direct dependencies listed first. See this maven issue: http://jira.codehaus.org/browse/MNG-3197 -- 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

17 years

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-391) Create jboss.org site for maven-jdocbook-plugin

by Paul Gier (JIRA)

Create jboss.org site for maven-jdocbook-plugin ----------------------------------------------- Key: JBBUILD-391 URL: http://jira.jboss.com/jira/browse/JBBUILD-391 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - Maint 2007 Steve created the jdocbook plugin for maven. This should be the new standard docbook configuration within jboss. A site needs to be created for the plugin documentation on jboss.org. -- 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

17 years

1
4
0 / 0

[JBoss JIRA] Created: (JGRP-628) Discovery: add cluster name to discovery request to be able to discard responses from different clusters

by Bela Ban (JIRA)

Discovery: add cluster name to discovery request to be able to discard responses from different clusters -------------------------------------------------------------------------------------------------------- Key: JGRP-628 URL: http://jira.jboss.com/jira/browse/JGRP-628 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.1, 2.7 When we have 2 groups ONE and TWO: ONE: 228.8.8.8:7500 and TWO: 228.1.2.3:7500 In some cases, they will receive each other's traffic (http://wiki.jboss.org/wiki/Wiki.jsp?page=PromiscuousTraffic). Assume ONE has members {A,B,C} and TWO has no members yet. When D (in cluster TWO) starts up and sends out a discovery request, it might also receive discovery responses from ONE (A,B,C). D might now identify A as coordinator and send a JOIN-REQ to A. However, A will discard that request as the group name of D's request is TWO rather than ONE ! Result: D's JOIN-REQ will hang ! Note that the transport (TP) does drop messages from different clusters, but this happens only after the new member has joined the group, so discovery requests/responses from different groups are *not* discarded. Tasks: - Verify that the transport-name matching algorithm in TP is correct - Confirm that - on initial discovery - discovery requests and responses are not matched -- 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

17 years

1
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1138) Create a set of Persistence Unit deployers

by Carlo de Wolf (JIRA)

Create a set of Persistence Unit deployers ------------------------------------------ Key: EJBTHREE-1138 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1138 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Critical Fix For: AS 5.0.0.Beta3 -- 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

17 years

1
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1134) Move JNDI Binding Policy to its own Project

by Andrew Lee Rubinger (JIRA)

Move JNDI Binding Policy to its own Project ------------------------------------------- Key: EJBTHREE-1134 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1134 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Priority: Blocker Currently in Ext-API, move into new Project with its own lifecycle. -- 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

17 years

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1133) Resolve API Leaks in Ext-API

by Andrew Lee Rubinger (JIRA)

Resolve API Leaks in Ext-API ---------------------------- Key: EJBTHREE-1133 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1133 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger The following are internals and must be moved outside the external API: org.jboss.ejb3.remoting.RemoteProxyFactory org.jboss.ejb3.ProxyFactory -- 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

17 years

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1127) Rework implementation requirements for @Remote, @RemoteHome

by Andrew Lee Rubinger (JIRA)

Rework implementation requirements for @Remote, @RemoteHome ----------------------------------------------------------- Key: EJBTHREE-1127 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1127 Project: EJB 3.0 Issue Type: Task Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.Beta3 @RemoteHome is sufficient for a 2.1 view; the Remote Interface can be inferred from the return type of the create method. @Remote specifying a 2.1 Interface requires a @RemoteHome. @Remote specifying a Business Interface does not require a home; results in remote 3.0 view. -- 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

17 years

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1126) Lifecycle-callback-class and around-invoke class are ignored

by Carlo de Wolf (JIRA)

Lifecycle-callback-class and around-invoke class are ignored ------------------------------------------------------------ Key: EJBTHREE-1126 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1126 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Critical Fix For: AS 5.0.0.Beta3 This leads to the following exception: java.lang.RuntimeException: around-invoke-method must contain a valid method name for interceptor com.sun.ts.tests.ejb30.common.callback.InterceptorB at org.jboss.ejb3.interceptor.InterceptorInfoRepository$XmlInitialiser.findInterceptorMethodFromXml(InterceptorInfoRepository.java:872) at org.jboss.ejb3.interceptor.InterceptorInfoRepository$XmlInitialiser.findInterceptorMethodFromXml(InterceptorInfoRepository.java:837) at org.jboss.ejb3.interceptor.InterceptorInfoRepository$XmlInitialiser.getInfo(InterceptorInfoRepository.java:819) at org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialiseSuperClassesFirstFromXmlOrAnnotations(InterceptorInfoRepository.java:398) at org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialiseInfosFromXml(InterceptorInfoRepository.java:375) at org.jboss.ejb3.interceptor.InterceptorInfoRepository.initialise(InterceptorInfoRepository.java:108) at org.jboss.ejb3.Ejb3HandlerFactory$DDFactory.<init>(Ejb3HandlerFactory.java:48) at org.jboss.ejb3.Ejb3HandlerFactory.getInstance(Ejb3HandlerFactory.java:83) at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:417) at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:361) at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:134) ... 63 more -- 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

17 years

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1125) getEJBHome and getEJBLocalHome should throw IllegalStateException instead of EJBException

by Carlo de Wolf (JIRA)

getEJBHome and getEJBLocalHome should throw IllegalStateException instead of EJBException ----------------------------------------------------------------------------------------- Key: EJBTHREE-1125 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1125 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: AS 5.0.0.Beta3 getEJBHome and getEJBLocalHome should throw IllegalStateException instead of EJBException when there is no home interface. See http://java.sun.com/javaee/5/docs/api/javax/ejb/EJBContext.html#getEJBHome() -- 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

17 years

1
2
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 2007