[Design of POJO Server] - Re: State of the integration of the latest MC into AS
by adrian@jboss.org
"alesj" wrote : "adrian(a)jboss.org" wrote :
| | This isn't ideal, but with Ales's latest change to add support for private
| | field injection, despite my request NOT to do major changes until I'd updated the latest
| | (split up) MC in to JBossAS
| | http://www.jboss.com/index.html?module=bb&op=viewtopic&t=130461
| | I don't feel confident about putting the latest stuff in there.
| |
| | Reflection and MDR which is what Ales is changing are the only projects
| | I'd done beta11 releases for, but they are obviously out-of-date now. ;-(
| My changes don't affect the previous code, at least that's what the tests said. :-)
|
I don't care what the tests said. I've spent the best part of the last two weeks
doing "releases" of the latest MC code fixing problems while
I try to split it up and integrate the latest stuff into JBossAS and test it.
All that work would now be out of the window because of this fundamental change
which isn't tested enough for me for me to take at the moment.
Let's get it to a proper state this week then we can do proper releases
all the way through the MC dependencies.
The alternative, is to revert the changes in the kernel project so I can
do a proper MC release off what I've tested (using beta11 of reflection/mdr).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137166#4137166
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137166
18 years
[Design of JBoss jBPM] - Re: LDAP assignment handler
by alex.guizar@jboss.com
@Ronald
How is replacing the IdentityService useful? The IdentityService is used by the IdentityLoginModule to authenticate users. Conversely, the ExpressionAssignmentHandler invokes ExpressionSession to resolve group memberships.
The responsibilities of IdentityService and ExpressionSession overlap to such degree that IdentitySession implements both. For some reason, they currently are separate interfaces. I believe ExpressionSession should be merged into IdentityService and the latter turned into a context service (i. e. a subinterface of org.jbpm.svc.Service) configurable in jbpm.cfg.xml.
The reason to subclass ExpressionAssignmentHandler is that it explicitly instantiates IdentitySession in method getExpressionSession(). No other changes were introduced. If ExpressionSession was merged into IdentityService and the latter was an actual context service, then no subclassing would be needed.
Is this the kind of cleanup you did?
@Tom
The facade between the ExpressionAssignmentHandler and the identity component already exists, it is the ExpressionSession. However, one cannot specify a different implementation of the session without subclassing the handler. We need to address this, as well as the overlap with IdentityService.
Relationship navigation could also be implemented by returning hand-made proxies just like those generated by Hibernate. However, the navigation requirements imposed on implementors would be made implicit instead of stated explicitly as methods in the facade. I believe explicit is better.
Identity components that cannot be exposed as our model are out of scope, but they can always use the existing model as a starting point.
Earlier I proposed merging ExpressionSession into IdentityService. On a second thought, the separation between the interfaces also corresponds to the separate requirements of each client of the identity service. Identity implementors could choose to implement only those interfaces that correspond to the features in use.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137162#4137162
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137162
18 years