[JBoss Cache: Core Edition] - Why concrete region fails override the default one?
by beep_beep
IN JBC 1.4 SP9:
I have found,that with configuration below, more concrete region
(15 nodes maximum) failed to override default one(5 nodes maximum).
Is it ok, what is not OK?
<!--Eviction-->
|
|
| <attribute name="EvictionPolicyConfig">
| <config>
| <attribute name="wakeUpIntervalSeconds">5</attribute>
|
| <!-- This defaults to 200000 if not specified -->
| <attribute name="eventQueueSize">100000</attribute>
|
| <!-- Name of the DEFAULT eviction policy class. -->
| <attribute name="policyClass">org.jboss.cache.eviction.LRUPolicy</attribute>
|
| <!-- Cache wide default -->
| <region name="/_default_">
| <attribute name="timeToLiveSeconds">0</attribute>
| <attribute name="maxNodes">5</attribute>
| </region>
|
| <!-- override policy used for this region -->
| <region name="test.web.TestEntity" eventQueueSize="500000">
| <attribute name="timeToLiveSeconds">0</attribute>
| <attribute name="maxNodes">15</attribute>
| </region>
| </config>
| </attribute>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152675#4152675
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152675
17 years, 11 months
[Microcontainer] - Re: SchemaResolverDeployer is parsing but not deploying
by alesj
"david.lloyd(a)jboss.com" wrote :
|
| | <bean:deployment
| | xmlns:bean="urn:jboss:bean-deployer:2.0"
| | xmlns:io="urn:jboss:io:1.0">
| | <bean:bean ..../>
| | <io:tcp-server> ... </io:tcp-server>
| | <io:tcp-connection> ... </io:tcp-connection>
| | ...etc...
| | </bean:deployment>
| |
|
| In other words I think it would be nice to let the user specify an I/O bean anywhere they'd specify a regular bean.
|
Then each of the corresponding metadata classes (tcp-server --> metadata class, tcp-connection --> metadata class, ...) must implement BeanMetaDatafactory.
Which isn't hard to achieve.
And your top level dlm:deployment can just take all of them, call getBeans on each of them, add those beans to top list, and you have your custom xml functional as well (+ the new deployer that I'm just about to write).
"david.lloyd(a)jboss.com" wrote :
| I'm about 95% sure I can get my tags to work inside a "bean:deployment" tag. But I'm maybe about 60% confident that I can get my bean tags to work in other places where a bean deployer "bean" tag can go.
|
These % are confusing me. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152668#4152668
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152668
17 years, 11 months