[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, 6 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, 6 months
[JBoss JIRA] Created: (JBAS-3755) Expose all SSL socket factory settings via properties or attributes for UIL2
by Scott M Stark (JIRA)
Expose all SSL socket factory settings via properties or attributes for UIL2
----------------------------------------------------------------------------
Key: JBAS-3755
URL: http://jira.jboss.com/jira/browse/JBAS-3755
Project: JBoss Application Server
Issue Type: Support Patch
Security Level: Public (Everyone can see)
Components: JMS service, Security
Affects Versions: JBossAS-4.0.4.GA
Reporter: Scott M Stark
Assigned To: Adrian Brock
Currently the ssl socket factories don't have any notion of picking up settings like the enabled cipher suites from system properties or the security domain in the case of the org.jboss.security.ssl.DomainSocketFactory. We should be able to set any JSSE SSLSocketFactory setting from these external values by injecting a fully configured socket factory:
<mbean code="org.jboss.mq.il.uil2.UILServerILService"
name="jboss.mq:service=InvocationLayer,type=SSLUIL2">
...
<attribute name="ServerSocketFactoryBean">
attributeClass="org.jboss.security.ssl.DomainServerSocketFactory"
serialDataType="javaBean">
<property name="bindAddress">${jboss.bind.address}</property>
<property name="securityDomain">java:/jaas/rmi-ssl</property>
<property name="wantsClientAuth">true</property>
<property name="needsClientAuth">true</property>
<property name="CiperSuites">TLS_DHE_DSS_WITH_AES_128_CBC_SHA</property>
<property name="Protocols">SSLv2Hello,SSLv3,TLSv1</property>
</attribute>
</mbean>
--
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, 6 months
[JBoss JIRA] Created: (JBREM-581) can not do connection validation with ssl transport (only impacts detection)
by Tom Elrod (JIRA)
can not do connection validation with ssl transport (only impacts detection)
----------------------------------------------------------------------------
Key: JBREM-581
URL: http://jira.jboss.com/jira/browse/JBREM-581
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: detection
Affects Versions: 2.0.0.CR1 (Boon)
Reporter: Tom Elrod
Assigned To: Tom Elrod
Fix For: 2.2.0.Beta1 (Bluto)
When a detector gets the detection message from a server, the detection message does not include (nor should it), the ssl info needed to make the ping invocation on that server to verify it is indeed dead. Per JBREM-580, will currently just avoid making ping invocation if transport supports ssl. This means that never does the ping invocation to ensure that the server is really down (and not just lack of getting detection message update), but instead will just consider it dead if detection message is stale.
--
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, 6 months
[JBoss JIRA] Created: (JBRULES-504) Cannot use the object's property named as "attributes" in a rule
by Vineeth Varghese (JIRA)
Cannot use the object's property named as "attributes" in a rule
----------------------------------------------------------------
Key: JBRULES-504
URL: http://jira.jboss.com/jira/browse/JBRULES-504
Project: JBoss Rules
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Drl Parser/Builder
Affects Versions: 3.0.4
Environment: Windows 2000 with Jdk1.5
Reporter: Vineeth Varghese
Assigned To: Mark Proctor
Attachments: src.zip
The word "attributes" seem to be a keyword in JBoss Rules. Basically if I have an Object that has a property named as "attributes", I cannot use it in the IDE or create a rulebase out of it. We end up getting the following error:-
org.drools.rule.InvalidRulePackage: unknown:9:19 Unexpected token 'attributes'
at org.drools.rule.Package.checkValidity(Unknown Source)
at org.drools.common.AbstractRuleBase.addPackage(Unknown Source)
at com.sample.DroolsTest.readRule(DroolsTest.java:72)
at com.sample.DroolsTest.main(DroolsTest.java:23)
Even the IDE highlights this as an error.
--
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, 6 months