[JBoss JIRA] Created: (JBCACHE-702) PojoCache to specify a user-defined region option for buddy replication and eviction policy
by Ben Wang (JIRA)
PojoCache to specify a user-defined region option for buddy replication and eviction policy
-------------------------------------------------------------------------------------------
Key: JBCACHE-702
URL: http://jira.jboss.com/jira/browse/JBCACHE-702
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: PojoCache
Reporter: Ben Wang
Assigned To: Ben Wang
Fix For: POJOCache
Currently, the design of flat space mapping in 2.0 means that the object graph doesn't reside under the same tree. When we have buddy replication, eviction or cacheloader, this can be a problem to implement. The best solution is to have an notion of region. For example, something toward this line:
cache.attach(region, id, pojo)
will ensure everything is put under /region/id, and __JBOSS_INTERNAL__/region/guid
I am thinking to put this in an Option class such as:
cache.attach(id, pojo, option)
so it is more generic.
--
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
19 years, 8 months
[JBoss JIRA] Created: (JBAS-3409) Deploy a .ear file with no deployment descriptor(META-INF/application.xml)
by Rajesh Rajasekaran (JIRA)
Deploy a .ear file with no deployment descriptor(META-INF/application.xml)
--------------------------------------------------------------------------
Key: JBAS-3409
URL: http://jira.jboss.com/jira/browse/JBAS-3409
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Deployment services
Affects Versions: JBossAS-5.0.0.Beta
Reporter: Rajesh Rajasekaran
Assigned To: Dimitris Andreadis
Priority: Blocker
Fix For: JBossAS-5.0.0.Beta
The javaee5 spec (EE8.4.2 Deploying a Java EE application) has a set of rules to deploy an application .ear file which does not have a deployment descriptor. (descriptorMETA-INF/application.xml)
Currently we get a RunTimeException when the application.xml is not found.
org.jboss.deployment.spi.DeploymentManagerImpl@16b8f8eb
java.lang.RuntimeException: cannot obtain module type
07-21-2006 13:12:57: Harness - Deployment of app(s) from: /home/rrajasekaran/tck5/javaeetck/dist/com/sun/ts/tests/samples/javamail/ee/transport failed!
at org.jboss.deployment.spi.DeploymentManagerImpl.createDeployment(DeploymentManagerImpl.java:481)
at org.jboss.deployment.spi.DeploymentManagerImpl.distribute(DeploymentManagerImpl.java:348)
The moduleType in org.jboss.deployment.spi.DeploymentManageImpl.createDeployment() is not set when the application.xml is not set.
All CTS tests deploy .ear files with no application.xml
I ve made this issue a blocker because unless this is fixed we would be unable to run the cts tests.
--
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
19 years, 8 months