[JBoss OSGi Development] - Cannot resolve dependency against unstarted bundle
by thomas.diesler@jboss.com
https://jira.jboss.org/jira/browse/JBOSGI-136
The VFSDeploymentClassLoaderPolicyModule creates the dependencies like this
| protected void createDependencies()
| {
| ControllerState classLoaderState = getClassLoaderState();
|
| List<Requirement> requirements = getRequirements();
| if (requirements != null)
| {
| requirementDependencies = new ArrayList<RequirementDependencyItem>();
| for (Requirement requirement : requirements)
| {
| RequirementDependencyItem item = new RequirementDependencyItem(this, requirement, classLoaderState);
| addIDependOn(item);
| requirementDependencies.add(item);
| }
| }
| }
|
The RequirementDependencyItem always initialized the the dependentState with ControllerState.INSTALLED
| public RequirementDependencyItem(Module module, Requirement requirement, ControllerState state)
| {
| super(module != null ? module.getContextName() : null, null, state, ControllerState.INSTALLED);
|
which ultimately leads to RequirementDependencyItem.resolve() not being able to find the dependent ControllerContext
| ControllerContext context = controller.getContext(iDependOn, getDependentState());
|
So it seems that RequirementDependencyItems can only resolve againt INSTALLED contexts.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252873#4252873
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252873
15 years, 4 months
[JBoss ESB Development] - Re: JBESB-2805 - Splitter EAI Pattern
by rferreir
Hi Tom,
Actually, the current implementation can route separated messages for the services, since every route-to request contain a smooks trans. The idea behind this is: You pass for the splitter a huge message (eg: An Complete Order), and the splitter process each smooks trans for this message, and the resulting messages (Eg: Separeted Items) are routed for the services.
Have said that, you can write custom smooks trans for each order of the message, which will cause the creation of separated messages for each service that waits for a item to be processed. Did you see the example that I've attached to the JIRA? It is a complete test scenario that does to different routings for the same message.
But let's talk about improvements. I've not work yeat with this FragmentRouter, I'm going to learn how it works and try to use in the implementation. Could you help in this class usage?
I've not found a description of this router in the programmers guide, I've only the source code. But it seems that I should instantiate a copy of this router for every routing that I'm planning to do, it's correct? If so, I've to pass a instance of a executionContext that wrapps a smooks transformed object.
Regards,
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252839#4252839
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4252839
15 years, 4 months