[Design the new POJO MicroContainer] - Re: MutableClassInfo?
by stale.pedersen@jboss.org
im just wondering a bit about the usage of SignatureKey in JavassistMethodInfo. it doesnt seem to add any vaule that i can see. first of all its only used in the method JavassistMethodInfo.getName() where the name can be fetched from the CtMethod object instead.
with a mutable methodinfo it lack even more meaning since the method parameters and name dont need to be defined when creating the method.
i can understand the usage of SignatureKey in JavassistTypeInfo as it is used as a key for the maps that hold methods, fields, and constructors.
- even though a better solution would probably to use the signature of the method/field/constructor as the map key instead of SignatureKey (atleast it would be more efficient).
please explain the reason of having the SignatureKey in JavassistMethodInfo, and if there isnt a good reason ill remove it.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210967#4210967
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210967
17 years, 1 month
[Design of Messaging on JBoss (Messaging/JBoss)] - invmacceptor auto created in remotingserviceimpl
by timfox
| // when JMX is enabled, it requires a INVM acceptor to send the core messages
| // corresponding to the JMX management operations (@see ReplicationAwareStandardMBeanWrapper)
| if (jmxEnabled)
| {
| boolean invmAcceptorConfigured = false;
| for (TransportConfiguration config : transportConfigs)
| {
| if (InVMAcceptorFactory.class.getName().equals(config.getFactoryClassName()))
| {
| invmAcceptorConfigured = true;
| }
| }
| if (!invmAcceptorConfigured)
| {
| transportConfigs.add(new TransportConfiguration(InVMAcceptorFactory.class.getName(), new HashMap<String, Object>(), "in-vm"));
| }
| }
|
I don't understand why it's necessary....
If you want to send a management message from inside the server, no need for a session factory. just create a serversession directly and use that.
Also I notice that *gulp* you're creating a new session for every invocation in replicationAwareInvoke.
That's a performance killer!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210963#4210963
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210963
17 years, 1 month
[Design of JBoss jBPM] - statefull vs stateless delegation classes
by tom.baeyens@jboss.com
can we safely assume that all delegation classes are stateless ?
when a process calls out to a user class, this can be done by specifying the classname and some configuration injections. there are various use cases of delegation classes: Assigner's (aka AssignmentHandlers), EventListeners (aka Actions) and so on.
with delegation classes being stateless i mean that execution of those delegation classes will not update their member field. so after construction (incl injecting configuration) they can be considered immutable.
if that is the case, those objects become thread safe and cacheble.
we didn't assume this in jbpm 3 and hence instantiated each object each time as there is no good way of introducing caching.
so...
can we safely assume that all delegation classes are stateless as the default ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210958#4210958
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210958
17 years, 1 month