[Design of JBoss ESB] - Re: Registry Design
by tfennelly
anonymous wrote : Next thing that I can think of is the Distributed nature of the Registry. Clustered Registry I should say. And it would be stand alone as well. So the first thing we need is a listener for requests. Would we grow this from scratch or we reuse currently available listeners from some application?
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?
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). In reality, if that underlying concrete impl is not clusterable, there's no big gain in clustering the facade! Yeah/no??
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966728#3966728
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966728
18 years, 1 month
[Design of AOP on JBoss (Aspects/JBoss)] - Re: using CallLoggingInterceptor on existing web app
by cpmcda01
This is an old post, but I'm resurrecting it because it seems it was never resolved, and I think I know why. The following code in CallLoggingInterceptor is evaluating to false:
| boolean callLogging = log.isDebugEnabled();
| if (callLogging)
| callLogging = Boolean.valueOf((String)invocation.getMetaData(LOGGING,
| CALL_LOGGING)).booleanValue();
|
First, let me say that key configuration like this should be mentioned in the Javadoc API for this class. I spent nearly two days trying to get call logging to work and all the while I kept thinking that JBoss AOP was broken or I was doing something fundamentally wrong. 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.
So I gave up and I made my own Interceptor, copy-pasting most of the code from CallLoggingInterceptor, leaving out the above. Everything is working fine. Curious as to how this meta-data stuff worked, I went to the JBoss AOP documentation and found it sorely lacking. See for yourself:
http://labs.jboss.com/portal/jbossaop/docs/1.5.0.GA/docs/aspect-framework...
How would I configure this meta-data in my -aop.xml file to get the CallLoggingInterceptor to actually log something?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966720#3966720
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966720
18 years, 1 month
[Design of JBoss ESB] - Re: Registry Design
by tfennelly
anonymous wrote : How about the users trying to add a new service to be registered? We would need to provide a way for that I guess. Perhaps thru an admin console?
Exactly! I'd expect this type of info to be added to the registry via whatever admin console comes with the reg product. I don't think this is something we need to abstract.
anonymous wrote : I assume you are talking of a container like Tomcat? Or is there anything else we could use?
|
| Yeah I do suppose we would need the Registry to have similar Security features as the other services of the ESB. But we can think of them when the security features are worked out :-)).
Aye, I think "Service Security" is a bigger issue that needs to be solved for all services being plugged into the ESB. I'm not sure there's anything special about the registry in this regard.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966719#3966719
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966719
18 years, 1 month
[Design of JBoss ESB] - Re: Registry Design
by mugdho
anonymous wrote : How? I guess SOAP Interface will be the most useable.
SOAP sounds good. Haven't used it much though. But I guess its not tied to UDDI.
anonymous wrote : I'd wonder if we need to worry about this!! Who needs to make reg updates? Will reg updates need to be made by a running ESB or Services? Do we need it for the GA release?
How about the users trying to add a new service to be registered? We would need to provide a way for that I guess. Perhaps thru an admin console?
anonymous wrote :
| For the GA release (and possibly beyond), can we not rely on some form of container managed security (Authentication/Authorisation)?...
I assume you are talking of a container like Tomcat? Or is there anything else we could use?
Yeah I do suppose we would need the Registry to have similar Security features as the other services of the ESB. But we can think of them when the security features are worked out :-)).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966707#3966707
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966707
18 years, 1 month