March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMETA-261) EE 6 module-name concept in common metadata

by Brian Stansberry (JIRA)

EE 6 module-name concept in common metadata ------------------------------------------- Key: JBMETA-261 URL: https://jira.jboss.org/jira/browse/JBMETA-261 Project: JBoss Metadata Issue Type: Sub-task Security Level: Public (Everyone can see) Components: common Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: jboss-metadata-common-2.0.0-alpha-14 -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7633) Allow for configuring default resource adaptor name for the EJB3 MDBs

by jaikiran pai (JIRA)

Allow for configuring default resource adaptor name for the EJB3 MDBs --------------------------------------------------------------------- Key: JBAS-7633 URL: https://jira.jboss.org/jira/browse/JBAS-7633 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: JBossAS-6.0.0.M3 Allow a configurable approach for setting the *default* resource adaptor name on MDB within a runtime (ex: AS, EAP). The default resource adaptor names currently is set in EJB3 code to jms-ra.rar. Instead, it's the runtime environment which should set this default value. So for AS 6, once it moves to HornetQ, it can set it to the HornetQ resource adaptor name and for EAP-5, it can be set to the jms-ra.rar. See the referenced forum thread for details. -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBREM-1167) Add simple socket based protocol to Remoting 3 samples

by Ron Sigal (JIRA)

Add simple socket based protocol to Remoting 3 samples ------------------------------------------------------ Key: JBREM-1167 URL: https://jira.jboss.org/jira/browse/JBREM-1167 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 3.1.0.Beta1 A simple protocol might help to clarify the concepts of Remoting 3. -- 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

16 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-1189) Graceful connection close

by David Lloyd (JIRA)

Graceful connection close ------------------------- Key: JBREM-1189 URL: https://jira.jboss.org/jira/browse/JBREM-1189 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: r3 core: api, r3 core: remote Reporter: David Lloyd Fix For: 3.1.0.Beta1 Design a mechanism for graceful connection shutdown. This could work in one of a few ways: 1. Refuse new clients, immediately close all clients, allow outstanding requests to finish 2. Refuse new clients, keep connection up until all clients are closed and all outstanding requests to finish #1 might be better - since requests have a finite lifespan but clients can hang around indifinitely. -- 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

16 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-7789) Allow the default jmx name of EJB(2.x) deployments to be deterministic

by jaikiran pai (JIRA)

Allow the default jmx name of EJB(2.x) deployments to be deterministic ---------------------------------------------------------------------- Key: JBAS-7789 URL: https://jira.jboss.org/jira/browse/JBAS-7789 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Deployers, EJB2 Affects Versions: JBossAS-6.0.0.M2, JBossAS-6.0.0.M1 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: JBossAS-6.0.0.M3 The fix for https://jira.jboss.org/jira/browse/JBPAPP-2419 resulted in the default jmx name of the EJB2 deployment, non-deterministic. Many users depend on this default jmx name to add a dependency between deployments. For example, JBAS-7760 illustrates one such use case. Making the default, jmx name deterministic will allow users to use this in the <depends> element of deployments. At the same time, care has to be taken that the original bug reported in JBPAPP-2419 is not reintroduced as part of this change. -- 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

16 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7760) Error when defining dependency between an EAR and its related WAR

by denis boutin (JIRA)

Error when defining dependency between an EAR and its related WAR ----------------------------------------------------------------- Key: JBAS-7760 URL: https://jira.jboss.org/jira/browse/JBAS-7760 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: System service Affects Versions: JBossAS-6.0.0.M1 Environment: JBOSS6.0.0M1 Windows XP Reporter: denis boutin Assignee: Dimitris Andreadis Hi, When JBoss 6.0M1 starts, I've got the following error : << 18:06:32,754 INFO [AbstractServer] JBossAS [6.0.0.M1 (build: SVNTag=JBoss_6_0_0_M1 date=200912040958)] Started in 43s:204ms 18:07:56,352 WARN [HDScanner] Failed to process changes org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES: Deployment "jboss.web.deployment:war=/myapp" is missing the following dependencies: Dependency "jboss.j2ee:module="company-agents-ejb.jar",service=EjbModule" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.j2ee:module="company-agents-ejb.jar",serv ice=EjbModule' **") Dependency "jboss.j2ee:module="company-engine-ejb.jar",service=EjbModule" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.j2ee:module="company-engine-ejb.jar",serv ice=EjbModule' **") Dependency "jboss.j2ee:module="company-data-readwrite-ejb.jar",service=EjbModule" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.j2ee:module="company-data-readwri te-ejb.jar",service=EjbModule' **") DEPLOYMENTS IN ERROR: Deployment "jboss.j2ee:module="company-agents-ejb.jar",service=EjbModule" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.j2ee:module="company-agents-ejb.jar",service=EjbModule' ** Deployment "jboss.j2ee:module="company-engine-ejb.jar",service=EjbModule" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.j2ee:module="company-engine-ejb.jar",service=EjbModule' ** Deployment "jboss.j2ee:module="company-data-readwrite-ejb.jar",service=EjbModule" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.j2ee:module="company-data-readwrite-ejb.jar",se rvice=EjbModule' ** at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1002) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:948) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:870) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:378) >> The EAR is well deployed, however the WAR application seems not to detect that the module set in the jboss-web.xml of WEB-INF folder in WAR. Jboss-web.xml << <?xml version="1.0" encoding="utf-8"?> <jboss-web> <context-root>/myapp</context-root> <security-domain>java:jaas/myapp-web</security-domain>  <depends>jboss.j2ee:module="company-agents-ejb.jar",service=EjbModule</depends> <depends>jboss.j2ee:module="company-data-readwrite-ejb.jar",service=EjbModule</depends> <depends>jboss.j2ee:module="company-engine-ejb.jar",service=EjbModule</depends> </jboss-web> >> The following modules are well deployed in the JMX console : - jboss.j2ee:module="company-agents-ejb.jar",service=EjbModule - jboss.j2ee:module="company-data-readwrite-ejb.jar",service=EjbModule - jboss.j2ee:module="company-engine-ejb.jar",service=EjbModule If I query the JMX console with exactly those strings those modules are well found but it is not the case inside JBoss 6.0M1. Those kind of settings works well under JBoss 4.0.0. Does something changed inside JBoss 6.0M1 related to those dependencies between WAR & EAR ? The idea beyond that is to be sure that the EAR is loaded before the WAR file. Do you need more elements regarding that case ? Regards, Denis. -- 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

16 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-7488) Web Console: getServerBaseURL() undefined for ServerConfigImplMBean

by Ondrej Žižka (JIRA)

Web Console: getServerBaseURL() undefined for ServerConfigImplMBean ------------------------------------------------------------------- Key: JBAS-7488 URL: https://jira.jboss.org/jira/browse/JBAS-7488 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ondrej Žižka Fix For: JBossAS-6.0.0.M1 Run Jboss AS 6M1, open the console. You'll see: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 87 in the jsp file: /ServerInfo.jsp The method getServerBaseURL() is undefined for the type ServerConfigImplMBean 84: <h4>Environment</h4> 85: Start date: <%=server.getStartDate()%> 86: Host: <%=serverInfo.getHostName()%> (<%=serverInfo.getHostAddress ()%>) 87: Base Location: <%=serverConfig.getServerBaseURL()%> 88: Base Location (local): <%=serverConfig.getServerBaseDir()%> 89: Running config: '<%= serverConfig.getServerHomeDir().getName()%>'</td> 90: </tr> -- 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

16 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2444) Named Consequences

by Mark Proctor (JIRA)

Named Consequences ------------------ Key: JBRULES-2444 URL: https://jira.jboss.org/jira/browse/JBRULES-2444 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-compiler (expert), drools-core (expert) Reporter: Mark Proctor Assignee: Mark Proctor Fix For: 5.1.0.M2 Allow for multiple named consequences, which can be used for "branch" conditional elements. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBEE-18) Create org.jboss.javaee:jboss-interceptors-api

by Carlo de Wolf (JIRA)

Create org.jboss.javaee:jboss-interceptors-api ---------------------------------------------- Key: JBEE-18 URL: https://jira.jboss.org/jira/browse/JBEE-18 Project: JBoss JavaEE APIs Issue Type: Task Reporter: Carlo de Wolf Assignee: Carlo de Wolf -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBEE-10) JavaEE 6.0 Alpha1 Release

by Shelly McGowan (JIRA)

JavaEE 6.0 Alpha1 Release ------------------------- Key: JBEE-10 URL: https://jira.jboss.org/jira/browse/JBEE-10 Project: JBoss JavaEE APIs Issue Type: Release Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 6.0.0.Alpha1 Release of EE 6 APIs needed for JCA project. -- 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

16 years, 4 months

1
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 2010