[Design of Clustering on JBoss (Clusters/JBoss)] - Re: ClusterPartition vs HAPartition
by bstansberry@jboss.com
ClusterPartition/HAPartitionImpl will no longer accept an XML element with the JGroups protocol stack. Rather it uses injected refs to a JChannelFactory and the name of the stack config to use. The JChannelFactory is then responsible for providing the channel.
So, the configuration requirements for HAPartitionImpl are pretty simple -- injection of needed services, plus a few primitive properties. Were you talking about a separate configuration pojo largely because of complexity related to the protocol stack config (which no longer exist) or is that a general approach to service configuration that you want in AS 5?
The above doesn't remove the issue of XML-based configuration of JGroups; it just moves it to a different place (the JChannelFactory.) Configuring a JChannel via a POJO is something I'll have to take up with Bela; JBoss Cache is going to need the same kind of thing.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966759#3966759
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966759
18 years, 1 month
[Design of AOP on JBoss (Aspects/JBoss)] - Re: using CallLoggingInterceptor on existing web app
by kabir.khan@jboss.com
"cpmcda01" wrote : I can not express how frustrated I was and how much my impression of the JBoss product diminished when I found that the source of the problem was buried in the interceptor code and was not reasonably documented.
It seems like you are doing a pretty good job to me :-)
I've added a JIRA issue to deal with the documentation issues you mention
http://jira.jboss.com/jira/browse/JBAOP-283
I think the following should do the job:
| <metadata tag="logging" class="org.blah.MyClass">
| <default>
| <call-logging>true</call-logging>
| </default>
| </metadata>
|
More flexible class expressions are supported as well, e.g
| <metadata tag="logging" class="$instanceof{(a)org.blah.Loggable}">
| <default>
| <call-logging>true</call-logging>
| </default>
| </metadata>
|
Or you can narrow it down for particular fields, methods, ctors
| <metadata tag="logging" class="$instanceof{(a)org.blah.Loggable}">
| <method expr="void some*(..)">
| <call-logging>true</call-logging>
| </method>
| <method expr="void more*(..)">
| <call-logging>true</call-logging>
| </method>
| <field name="somefield">
| <call-logging>true</call-logging>
| </field></metadata>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966738#3966738
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966738
18 years, 1 month
[Design of JBoss ESB] - Re: Registry Design
by mugdho
anonymous wrote : So if we're saying that it's going to be a SOAP based endpoint, can't we assume that this endpoint is going to be deployed inside a servlet container?? If so, can't we rely on the container clustering capabilities?
Essentially yeah, if we are deploying the Registry in a servlet container we can use the container's capabilities. That would essentially save us a lot of trouble. But wouldn't that mean shipping a container along with the registry?
anonymous wrote : Also, what are we talking about here? We're not building a registry. We're simply generalising a registry Inquiry abstraction that acts as a facade to some underlying concrete implementation (UDDI etc).
Right. But our aim is also to keep the Registry getting tied to a concrete implementation like UDDI. I think that's where the plug-in came in didn't it?
anonymous wrote : In reality, if that underlying concrete impl is not clusterable, there's no big gain in clustering the facade! Yeah/no??
True. In that case we would need to build our own cluster layer for serving the purpose. Wouldn't we?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966736#3966736
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966736
18 years, 1 month
[Design of JBoss jBPM] - tx configs and command interface for web app
by tom.baeyens@jboss.com
i'm starting to see a problem here. please think along and give your opinion:
currently the webapp just uses creates jbpmContexts and performs operations on the jbpmContext in the backing beans. there can only be 1 hibernate configuration that is used in the webapp. so you need to do a non-CMT based configuration. in case users want to use the enterprise beans, this would imply that we have to create 2 jbpm configurations on jboss: one for the webapp (without CMT configurations) and one for the CMT enterprise beans. hmmm let me know if you don't follow this then i'll try to explain in different words.
could it be that we need to solve this by implementing the command based interface between the web app and the jbpm command service ? that way, the command service implementation can be the enterprise command service SLSB or in a plain web application packaging, the command service bean could be a simple POJO based command service.
makes sense ?
i'll sleep on it. maybe that helps
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966732#3966732
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966732
18 years, 1 month