David Joseph
asked on
Errors in deployment of webservice on JBoss Fuse using OSGi bundle
I am stuck with the following problem:
What I am trying to achieve:
1. Create a application that generates webservices on the fly
2. Deploy these as individual services in JBoss Fuse.
Package these as OSGi bundle to deploy in JBoss Fuse server, using Apache CXF framework (This uses Apache Felix)
3. Call these Web Services
a. Individually
b. Aggregate / Combine output from multiple web services, create a new web service and deploy this in JBoss Fuse
The issue I'm, facing:
I get the following errors and warnings during deployment of 3 b, i.e. the new web service:
Errors
org.apache.felix.scr.impl.
org.apache.felix.framework
Warnings
org.apache.felix.framework
org.apache.felix.framework
I have posted this on stackoverflow, jboss developer forums and raised issues in redhat but no responses on this query.
Please find summary of files attached
1. Blueprint :- The blueprint container is a dependency injection framework that simplifies interaction with the OSGi container. In particular, the blueprint container supports a configuration-based approach to using the OSGi service registry—for example, providing standard XML elements to import and export OSGi services.
2. Features :- It Enables to deploy multiple bundles in a single step ,which automatically aggregates related bundles at deployment time, without requiring any additional configuration.
features.xml
StaticMethodChainingRest.java
blueprint.xml
What I am trying to achieve:
1. Create a application that generates webservices on the fly
2. Deploy these as individual services in JBoss Fuse.
Package these as OSGi bundle to deploy in JBoss Fuse server, using Apache CXF framework (This uses Apache Felix)
3. Call these Web Services
a. Individually
b. Aggregate / Combine output from multiple web services, create a new web service and deploy this in JBoss Fuse
The issue I'm, facing:
I get the following errors and warnings during deployment of 3 b, i.e. the new web service:
Errors
org.apache.felix.scr.impl.
org.apache.felix.framework
Warnings
org.apache.felix.framework
org.apache.felix.framework
I have posted this on stackoverflow, jboss developer forums and raised issues in redhat but no responses on this query.
Please find summary of files attached
1. Blueprint :- The blueprint container is a dependency injection framework that simplifies interaction with the OSGi container. In particular, the blueprint container supports a configuration-based approach to using the OSGi service registry—for example, providing standard XML elements to import and export OSGi services.
2. Features :- It Enables to deploy multiple bundles in a single step ,which automatically aggregates related bundles at deployment time, without requiring any additional configuration.
features.xml
StaticMethodChainingRest.java
blueprint.xml
ASKER
Dear Mr. David Favor,
I have attached some files for more insight.
Please find summary of files attached
1. Blueprint :- The blueprint container is a dependency injection framework that simplifies interaction with the OSGi container. In particular, the blueprint container supports a configuration-based approach to using the OSGi service registry—for example, providing standard XML elements to import and export OSGi services.
2. Features :- It Enables to deploy multiple bundles in a single step ,which automatically aggregates related bundles at deployment time, without requiring any additional configuration.
I have attached some files for more insight.
Please find summary of files attached
1. Blueprint :- The blueprint container is a dependency injection framework that simplifies interaction with the OSGi container. In particular, the blueprint container supports a configuration-based approach to using the OSGi service registry—for example, providing standard XML elements to import and export OSGi services.
2. Features :- It Enables to deploy multiple bundles in a single step ,which automatically aggregates related bundles at deployment time, without requiring any additional configuration.
To clarify. This all makes sense to you, as you designed + implemented your code.
For someone else to get their head around this + provide assistance, will likely require a large time investment + access to your system.
This is likely better handled as a paid engagement, for someone to go through this process + provide you with a fix.
For someone else to get their head around this + provide assistance, will likely require a large time investment + access to your system.
This is likely better handled as a paid engagement, for someone to go through this process + provide you with a fix.
I get the following errors and warnings
What you have posted above is not the actual errors/warnings but parts of the stack trace that come after the actual error/warning, i.e. they are of no use, at least on their own like that.
If you look up from whatever logs you found the above stack trace lines in, then you should find something more interesting, usually something accompanied by the term "Exception".
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
For someone to answer your question, they'd likely require an entire copy of your code, then time to learn your code, then time to do problem resolution.
My guess is the fix will be simple + to determine the fix may take many hours.
Likely a developer working on this system will be the best person to fix the problem.
To do this, you'll require adding checks to every step of your deployment process to verify each step worked + then bail out at first sign of trouble. This will show you the point in your deployment process where problem occurs.