[Design of Clustering on JBoss] - API modifications for better extensibility ?
by deruelle_jean
Hi all,
I'm starting to work on the task of providing clustering and failover capabilities to our Mobicents Sip Servlets container working on top of JBoss AS 5.1.CR1. See http://code.google.com/p/mobicents/issues/detail?id=521
I took the AS 5.1.CR1 as a basis for my work and the corresponding 2.0.0.GA tags for the different HA sub projects.
the initial import of my code is located here :
http://code.google.com/p/mobicents/source/detail?r=6013
This is not working yet but as I extended the JBoss cluster classes I noticed that few API changes would make my life a lot easier and would provide better integration, so here are my requests, please comment or tell me if I need to open one or multiple JIRA issues if you do agree with the changes :
JBossCacheManager
* initSnapshotManager to be made protected so that it can be overriden (so that we can set our own converged snapshotManager)
* getSnapshotManager() and setSnapshotManager() public methods or snapShotManager_ field to be made protected
* installValves and installValve methods to be made protected so that they can be overriden (we need that to install our custom JVMRouteValve)
* Ideally, methods such as start/stopEmbedded and UnEmbedded and the methods they use internally should be made protected too
AbstractJBossCacheService
* make the storeSessionOwners protected so that we can reuse it
IntervalSnapshotManager
* make the fields protected
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231452#4231452
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231452
16 years, 10 months
[Design of Management Features on JBoss] - KnownComponentTypes usage
by scott.stark＠jboss.org
I'm thinking current request to expand the MCBean and MBean component subtypes to include some of the recent additions is heading in the wrong direction. For example:
| /**
| * An enum of additional MBean:* ManagedComponent types not defined in {@link KnownComponentTypes}.
| */
| public enum MBean
| {
| Platform,
| Servlet,
| Web,
| WebApplication,
| WebApplicationManager,
| WebHost,
| WebRequestProcessor,
| WebThreadPool;
|
| public String type()
| {
| return this.getClass().getSimpleName();
| }
|
| public String subtype()
| {
| return this.name();
| }
|
| public ComponentType getType()
| {
| return new ComponentType(type(), subtype());
| }
| }
|
| /**
| * An enum of additional MCBean:* ManagedComponent types not defined in {@link KnownComponentTypes}.
| */
| public enum MCBean
| {
| JTA,
| MCServer,
| Security,
| ServerConfig,
| ServerInfo,
| ServicebindingManager,
| ServicebindingMetadata,
| ServiceBindingSet,
| ServiceBindingStore;
|
| public String type()
| {
| return this.getClass().getSimpleName();
| }
|
| public String subtype()
| {
| return this.name();
| }
|
| public ComponentType getType()
| {
| return new ComponentType(type(), subtype());
| }
| }
|
The issue is that whether or not these are MCBeans or MBeans is largely an irrelevant implementation detail. I'm thinking that we should be classifying these more like the datasource, jms destinations.
I'm not going to change the component types we are currently using this late in the release. Rather, I'm thinking of adding support for multiple component types similar to the alias notion.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231417#4231417
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231417
16 years, 10 months
[JBoss Portal Documentation] - PHARMACY ONLINE!
by whelth
<a href=http://www.linkbrander.com/go/76486>PURCHASE ABOUT PHARMACY ONLINE! !
<a href=http://www.linkbrander.com/go/76486>about pharmacy
* lowest prices!
* Imposing slacken up on!
* No vie with required
* UNBIND next heyday emancipation
* Patron be encouraging of 24/7 at
* Harmless shopping guaranteed :
<a href=http://www.linkbrander.com/go/76486>http://s52.radikal.ru/i135/0905/08/f61660434c6e.jpg
<a href=http://www.linkbrander.com/go/76486>PURCHASE ABOUT PHARMACY ONLINE! !
<a href=http://www.linkbrander.com/go/76486>http://s54.radikal.ru/i145/0905/db/fb390bfc28ad.gif
<a href=http://www.linkbrander.com/go/76486>PURCHASE ABOUT PHARMACY ONLINE! !
<a href=http://www.kaboodle.com/blogs/bum/dupast>buying duphaston online in canada
<a href=http://www.kaboodle.com/blogs/bum/dupast>duphaston no prescription required
<a href=http://www.kaboodle.com/blogs/bum/dupast>buy duphaston online paypal
<a href=http://www.kaboodle.com/blogs/bum/yuiy>overnight Femcare without prescription
<a href=http://www.kaboodle.com/blogs/bum/yuiy>Femcare overnight saturday delivery
<a href=http://www.kaboodle.com/blogs/bum/yuiy>order Femcare online without prescription
<a href=http://www.kaboodle.com/blogs/bum/yuiy>order Femcare online canada
<a href=http://www.youtube.com/user/trampampamnew>overnight Viagra without prescriptio
<a href=http://www.youtube.com/user/trampampamnew>order Viagra
<a href=http://www.youtube.com/user/trampampamnew>buy Viagra
<a href=http://www.youtube.com/user/bypremarin>overnight premarin without prescriptio
<a href=http://www.youtube.com/user/bypremarin>order premarin
<a href=http://www.youtube.com/user/bypremarin>buy premarin
<a href=http://www.youtube.com/user/fosamaxby>overnight fosamax without prescriptio
<a href=http://www.youtube.com/user/fosamaxby>order fosamax
<a href=http://www.youtube.com/user/fosamaxby>buy fosamax
<a href=http://www.youtube.com/user/zelnormby>Zelnorm overnight delivery no rx
<a href=http://www.youtube.com/user/zelnormby>Zelnorm shipped overnight without a prescription
<a href=http://www.youtube.com/user/noriminby>Norimin no prescription usa fedex shipping
<a href=http://www.youtube.com/user/noriminby>Buy Norimin for cash on delivery
<a href=http://www.youtube.com/user/clomidby>Buy Clomid
<a href=http://www.youtube.com/user/proveraby>Buy Provera
<a href=http://www.youtube.com/user/dostinexby>Buy Dostinex
<a href=http://www.youtube.com/user/Zoloftby>Buy Zoloft
<a href=http://www.youtube.com/user/paxilby>Buy Paxil
<a href=http://www.youtube.com/user/effexorby>Buy Effexol
<a href=http://www.youtube.com/user/celexaby>Buy Celexa
<a href=http://www.youtube.com/user/lexaproby>Buy Lexapro
<a href=http://www.youtube.com/user/freetub23>free porn tube
<a href=http://www.youtube.com/user/MrFreetube>free latina pic porn star
<a href=http://xvideos.blog.de> bangbros, bang bros, bang bros network, bang broscom, bang bros com, bang bros video
<a href=http://twitter.com/eaby> eaby,eba,eby,ebby,eebay,ebey,ebya
<a href=http://adultfrienddinder.gog.pl> Adultfriendrfinder
<a href=http://www.kaboodle.com/leapussy/youporn-redtube-pornhub-xnxx-tube8-...> youporn-redtube-pornhub-xnxx-tube8-xvideos-utube
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231404#4231404
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231404
16 years, 10 months
[Design of JBoss jBPM] - Re: super-state, scope or something else
by brittm
I found "super-state" to be a poor term initially, as Ronald described.
Using 'scope' opens up a myriad of issues in my mind, since really everything has a scope. I would tend to start looking for how the same scope info was being applied in the data model to all levels of the process hierarchy.
"Group" would be confusing to me as well (but only because I already use that term in all my assignment handler configurations)--never the less, I think Ronald is right--and just because a particular language uses a term doesn't mean jpdl/jbpm has to, or should, avoid it. If it's the right word, then it's the right word.
In the end, I tend to go with naming things what they are, even if it's a little inconvenient initially--everyone seems to be happier in the long term. I would love to be able to use the terms 'wait' and 'group' for 'state' and 'super-state'.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231403#4231403
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231403
16 years, 10 months
[Design the new POJO MicroContainer] - POST_CLASSLOADER not having a fully usable class loader
by scott.stark＠jboss.org
An issue Emanuel is running into is that a DeploymentStages.REAL deployer does not have a deployment class loader capbable of loading classes referenced by deployment metadata. This is apparently due to the deployment class loader being injected:
| <deployment xmlns="urn:jboss:bean-deployer:2.0">
|
| <classloader><inject bean="bindings-classloader:0.0.0"/></classloader>
|
| <classloader name="bindings-classloader" xmlns="urn:jboss:classloader:1.0" export-all="NON_EMPTY" import-all="true">
| <root>${jboss.common.lib.url}jboss-bindingservice.jar</root>
| </classloader>
| ...
|
Its one thing for this to be an arbitrary bean, but in this case it seems that we should be able to create the class loader in prior to the POST_CLASSLOADER.
In general, what is the point of having a class loader not be usable until the REAL phase?
Every POST_CLASSLOADER and later deployer that needs to load classes via the deployment class loader will fail.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231372#4231372
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4231372
16 years, 10 months
