[JBoss ESB Development] - How to architect a ESB project?
by jbossEsbDev
Hello,
I'm new to JbossEsb and am having trouble figuring out how to design my software in terms of JbossEsb .esb archive, actions etc. I'm hoping that if I explain my problem space, someone can point me in the right direction.
Problem:
------------
1) I need to expose an JAXWS endpoint as the entry point (it will be a oneway call)
2) I need to process xml messages
3) I need to turn them into POJOs
4) I need to then call JAXWS external web services to do the business logic on the POJOs
5) I need to call REST external web service to do business logic on the POJOs
6) I need to then call another JAXWS external web service with the results of the business logic
My questions include:
1) Should all this be in one .esb archive as one service with lots of actions?
2) Should each external web service be it's own service inside it's own .esb archive. They would then somehow be called from the main .esb archive as deployment dependencies?
Any other suggestions or advice would be greatly be appreciated on a good design.
Thank You.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265304#4265304
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4265304
16 years, 4 months
[JBoss Tools Development] - Re: Integrate with XText/JET/Xpand: Drop Freemarker as gener
by luxspes
"max.andersen(a)jboss.com" wrote : Does it run from ant without massive dependencies and overhead ? If not, then no.
|
Not sure...
anonymous wrote :
| And are you willing to migrate all our templates to JET or Xpand ?
|
Maybe, I know them pretty well (having done extensive modifications to them) , but I am not sure I will have the free time :'(
anonymous wrote :
| Stuff like this does not happen without someone with the time to do it. Plus the fixes we got waiting in freemarker component did not work when I applied them last (too many changes in one patch).
|
I did not implemented those, I have not experience in that kind of programming (that is why I like the idea of using Xtext: that work is already being done by someone else with interest in creating the ultimate code generation tool)
anonymous wrote :
| Care to make them smaller so we can apply them ?
|
If I had implemented them, or had the level of knowledge required, I would try... :'(. But that is precisely the point, nobody seems to care-about/have-spare-time for improving support for Freemarker in Eclipse: Why not leave that job to a team of people that actually have the creation of such a tool as their main goal?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265300#4265300
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4265300
16 years, 4 months
[JBoss Microcontainer Development] - Re: Testing Deployers with new Reflect + ClassPool
by flavia.rainone@jboss.com
"flavia.rainone(a)jboss.com" wrote : I'll continue investigating. Once I have all this sorted out, I'll commit the full version of those tests.
The cause of the failure is that the cleanup of classpools is not being performed. At the moment RegisterModuleCallback.removeModule is invoked, the classloader in the module is already null:
logger.debug("Removing module " + module);
| ClassLoader classLoader = ClassLoading.getClassLoaderForModule(module);
| ClassPoolRepository.getInstance().unregisterClassLoader(classLoader);
| domainRegistry.cleanupLoader(classLoader);
| registeredModules.remove(module);
| unregisteredModules.remove(module);
I can use the maps in domainRegistry in order to get to the classloader and "fix" this. However, those maps use WeakReference and I can never be sure whether the class loader is gc'ed at the moment I try to use those maps. If it is gc'ed, the associated ClassPool won't be cleaned up.
To workaround this scenario, I can see three options here:
1. replace the CL weak reference by a hard reference. That will garantee that we can do the right cleanup. This has a downside because weak references are safe against memory leaks. But we will always get rid of the hard reference on removeModule, and this method must always be called or otherwise the classpools won't work.
2. add checks in strategic points of the code. Those checks will look for the classpools associated with a null CL, performing a clean up of those (there is already a method for doing this in ScopedClassPoolRepository). IMO, this has the disadvantage that we are trying to cover ourselves from a ClassPool cleanup that failed, when in reality we should be fixing the cleanup itself instead of trying to cover the failure in other points of the code.
3. create an extra map in DomainRegistry that maps Modules to ClassPools. The downside of this option is that it kind of breaks the current design, because we use:
ClassPool javassist.scopedpool.ScopedClassPoolRepository.registerClassLoader(ClassLoader cl) to create a ClassPool, and we use:
void javassist.scopedpool.ScopedClassPoolRepository.unregisterClassLoader(ClassLoader cl) to clean it up. So we would have to create an unregister method that receives the module as a paramter and add this method to org.jboss.classpool.spi.ClassPoolRepository (subclass of ScopedCPRepository).
Which way should I go? My vote is for the first option.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4265288#4265288
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4265288
16 years, 4 months