[JBoss JIRA] Created: (EJBTHREE-655) Refactor @Service beans
by Bill Burke (JIRA)
Refactor @Service beans
-----------------------
Key: EJBTHREE-655
URL: http://jira.jboss.com/jira/browse/EJBTHREE-655
Project: EJB 3.0
Issue Type: Task
Reporter: Bill Burke
Assigned To: Carlo de Wolf
Fix For: EJB 3.0 RC9 - FD
Refactor @Service beans to fix a number of problems:
* magic methods for lifecycle methods:
- create/start/stop/destroy
* lifecycle methods are not required to be in @Management (MBean) interface.
* @Management interface is not registered with the ServiceController (Controller in MC land). It *IS* registered as a regular MBean though.
* If lifecycle methods exist on @Management interface, they must be intercepted on the container so that the appropriate Controler start/stop is done on the container. This would mean that you have to specify a <bind> in the Service aspect domain in ejb3-interceptors-aop.xml
--
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, 11 months
[JBoss JIRA] Created: (JBAS-3495) Windows service for JBossAS
by Luc Texier (JIRA)
Windows service for JBossAS
---------------------------
Key: JBAS-3495
URL: http://jira.jboss.com/jira/browse/JBAS-3495
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Other
Environment: Win32
Reporter: Luc Texier
Fix For: JBossAS-5.0.0.Beta
Windows users have a hard time deploying JBossAS as a Windows service. Most of them try to use JavaService from ObjectWeb which is too generic to support properly an application server instance. For exemple, generating thread dumps is impossible. Also the experience has shown that this tool is fairly broken causing hang-ups.
--
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
16 years
[JBoss JIRA] Created: (JBAS-3544) org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails bcasue service modules are unavailable
by Jaroslaw Kijanowski (JIRA)
org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails bcasue service modules are unavailable
------------------------------------------------------------------------------------------------------------
Key: JBAS-3544
URL: http://jira.jboss.com/jira/browse/JBAS-3544
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Test Suite
Environment: win xp
Reporter: Jaroslaw Kijanowski
Fix For: JBossAS-5.0.0.Beta
org.jboss.test.management.test.DeploymentDescriptorUnitTestCase fails because the services jbossweb-tomcat55.sar and jboss-aop.deployer can't be registered, becasue in JB5.0 they changed their names to jbossweb-tomcat6.sar and jboss-aop-jdk50.deployer.
FIX:
change
testsuite/src/main/org/jboss/test/management/test/DeploymentDescriptorUnitTestCase.java
.
.
.
public void testGetSarDescriptor() throws Exception
{
// String moduleName = "jbossweb-tomcat55.sar";
String moduleName = "jbossweb-tomcat6.sar";
.
.
.
public void testGetDeployerDescriptor() throws Exception
{
// String moduleName = "jboss-aop.deployer";
String moduleName = "jboss-aop-jdk50.deployer";
--
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
16 years, 3 months
[JBoss JIRA] Created: (JBAS-3591) For SESSION and ATTRIBUTE don't marshal values if UseRegionBasedMarshalling is on
by Brian Stansberry (JIRA)
For SESSION and ATTRIBUTE don't marshal values if UseRegionBasedMarshalling is on
---------------------------------------------------------------------------------
Key: JBAS-3591
URL: http://jira.jboss.com/jira/browse/JBAS-3591
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Clustering, Web (Tomcat) service
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
Storing session or attributes in the cache as byte[] or MarshalledValue is unnecessary if region based marshalling is used. Doing it greatly increases the memory footprint of distributed sessions.
Need to benchmark the performance impact of this (could be positive or negative), although the memory savings would outweigh all but a major performance loss.
Can't do this in Branch_4_0 is it breaks binary compatibility.
--
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
16 years, 4 months