[Design of JBoss ESB] - Registry Design
by mugdho
Like Mark had mentioned, the Beta release did not give much of an insight to the registry design. So now we need to start looking into that.
The idea initially was to have a standalone custom regsitry that can be deployed on multiple machines to prevent single point of failure.
Moreover the registry should be independent of a specific implementation like UDDI.
Now based on the JBossWS project we decided to initially design with jUDDI and later move on to our custom regsirty. Now the problem with jUDDI is that it is WS based, so we would need to have an application server where we deployed the registry. This is something that we had planned to avoid since the registry should be essentially stand alone.
I have been going thru the jUDDI code and I came to realise that along with builiding our custom listener for the requests, we may need to plugins for the aspects of security and authentication.
For starters however we can get the current Code bound with jUDDI.
Please let me know your thoughts on this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965754#3965754
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965754
19 years, 7 months
[Design the new POJO MicroContainer] - Re: Bean instantiate order with contextual injection
by alesj
Another issue:
| <bean name="testObject5" class="org.jboss.test.kernel.inject.support.PropertyInjectTestObject">
| <property name="map">
| <map>
| <entry >
| <key>test</key>
| <value class="org.jboss.test.kernel.inject.support.TesterInterface"><inject/></value>
| </entry>
| </map>
| </property>
| </bean>
|
| public Class getType(MetaDataVisitor visitor, MetaDataVisitorNode previous) throws Throwable
| {
| // where did I come from ... key or value
| for(MetaDataVisitorNode key : keySet())
| {
| if (previous.equals(key) && keyType != null)
| {
| return getClass(visitor, keyType);
| }
| }
| for(MetaDataVisitorNode v : values())
| {
| if (previous.equals(v) && valueType != null)
| {
| return getClass(visitor, valueType);
| }
| }
| return super.getType(visitor, this);
| }
|
|
But the thing is that MD values seem to get cloned ... so we never actually get equality.
In that Constructor factory + inject problem we should probably set dependency item's whenRequired to earlier state ... will that do it?
Ok, off to the sea. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965725#3965725
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965725
19 years, 7 months
[Design of JBoss jBPM] - Re: console build scripts
by tom.baeyens@jboss.com
aha. i found the build script again :-) it was in the jpdl/suite sub project.
currently my idea is the following:
* create a separate package for the jboss configuration updates. the idea is that you could take any default installation (of a given jboss version), then unzip the jbpm configuration package over the existing configuration and you would have jbpm installed. such package would only include what has to be overwritten and added in a default jboss configuration in order to deploy the jbpm service archive into it. we could create a zip file per jboss version.
* move the create.jboss.configuration from the suite to console subproject
* try and get the ant tasks to run from the project rather then having to deploy the jbpm jar to the ant lib directory
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3965707#3965707
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3965707
19 years, 7 months