You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by jlo_gestalt <jl...@gestalt-llc.com> on 2007/01/09 17:07:25 UTC
ServiceMix HTTP BC not working in OpenESB
I have finally installed the ServiceMix HTTP BC into OpenESB (Glassfish)
without any start up errors; most of which were classpath issues.
Now when I send an HTTP request to the HTTP BC I get the following
Exception:
javax.servlet.ServletException: Failed to process request:
javax.jbi.messaging.MessagingException: Operation name required to send
message exchange.
at
org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:79)
This is thrown by OpenESB's MessageExchangeProxy.validate() method who
throws this Exception when the
javax.jbi.messaging.MessageExchange.getOperation() returns null.
So it appears that ServiceMix doesn't require the operation to be set and
OpenESB does. Is this a compatibility issue? What can be done to resolve
this? Is this related to this
http://forum.java.sun.com/thread.jspa?forumID=512&threadID=734834 thread ?
--
View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8240728
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix HTTP BC not working in OpenESB
Posted by jlo_gestalt <jl...@gestalt-llc.com>.
Here is the thread to watch:
http://forum.java.sun.com/thread.jspa?threadID=5122900&tstart=0
http://forum.java.sun.com/thread.jspa?threadID=5122900&tstart=0
Thanks
--
View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8284383
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix HTTP BC not working in OpenESB
Posted by Guillaume Nodet <gn...@gmail.com>.
Yes, you should try to raise this problem on OpenESB forums.
I don't think this is required by the spec, so maybe change their
behavior ... I will follow the thread and join if needed.
On 1/11/07, jlo_gestalt <jl...@gestalt-llc.com> wrote:
>
> I made a change to AsyncBaseLifeCycle to log the exception and then log the
> message:
> catch (Exception e) {
> logger.error("Error processing exchange, exception is", e);
> logger.error("Error processing exchange" + exchange);
>
> This is probably a good idea to duplicate elsewhere.
>
> Anyways the HTTP Request gets to the HTTP BC and the HTTP BC sends the
> request to the EIP component. However when the EIP attempts to send the
> Message to our Component, guess what. Are good ol' buddy
> javax.jbi.messaging.MessagingException: Operation name required to send
> message exchange. EIP doesn't set the operation and consequenlty OpenESB
> throws an exception just like the HTTP BC did before I set the
> defaultOperation value.
>
> How can we fix this long term? Do we need to discuss with OpenESB and
> RonTenHove to overcome this?
> --
> View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8278082
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: ServiceMix HTTP BC not working in OpenESB
Posted by Guillaume Nodet <gn...@gmail.com>.
You can explicitely assign a WSDL on the eip endpoint by using
the wsdlResource attribute ...
On 1/12/07, jlo_gestalt <jl...@gestalt-llc.com> wrote:
>
> OK, I got farther, but now the EIPComponent doesn't forward the request to
> our JBI Component.
> Why is the EIPComponent not finding the service description. Is it because
> our JBI Component doesn't implement the getServiceDescription method (or it
> returns null). And ServiceMix doesn't require it and
> OpenESB does? This same ServiceAssembly works perfectly in ServiceMix 3.0.
> BTW RonTenHove got back to me and I plan on submitting a bug.
>
> Here is the output:
>
> org.apache.servicemix.http.processors.ConsumerProcessor|ClassName=org.apache.servicemix.http.processors.ConsumerProcessor;MethodName=process;_RequestID=c9f72300-7ca6-42f2-8be2-71882f2689ea;|Receiving
> HTTP request: POST /Encoding/HttpProxySaService/ HTTP/1.1
> Accept: */*
> Accept-Language: en-us
> Referer: file://C:\dev\current\nettoolkit\pingpong.ws\sample-IE-client.html
> UA-CPU: x86
> Accept-Encoding: gzip, deflate
> User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR
> 1.1.4322; .NET CLR 2.0.50727; InfoPath.1)
> Host: b-0648:8192
> Content-Length: 156
> Connection: keep-alive
> Cache-Control: no-cache
>
> org.apache.servicemix.eip.EIPComponent|ClassName=org.apache.servicemix.common.BaseComponent;MethodName=getServiceDescription;_RequestID=c9f72300-7ca6-42f2-8be2-71882f2689ea;|Querying
> service description for Endpoint Type: InternalEndpoint
> Owner: servicemix-eip Active: True
> Service:
> {http://nettoolkit.gestalt.com/pingpong/router}pingpong-encoding-router
> Endpoint: pingpong-encoding-router
> |#]
>
> org.apache.servicemix.eip.EIPComponent|ClassName=org.apache.servicemix.common.BaseComponent;MethodName=getServiceDescription;_RequestID=c9f72300-7ca6-42f2-8be2-71882f2689ea;|No
> description found for
> {http://nettoolkit.gestalt.com/pingpong/router}pingpong-encoding-router:pingpong-encoding-router|#]
>
> --
> View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8300043
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: ServiceMix HTTP BC not working in OpenESB
Posted by jlo_gestalt <jl...@gestalt-llc.com>.
OK, I got farther, but now the EIPComponent doesn't forward the request to
our JBI Component.
Why is the EIPComponent not finding the service description. Is it because
our JBI Component doesn't implement the getServiceDescription method (or it
returns null). And ServiceMix doesn't require it and
OpenESB does? This same ServiceAssembly works perfectly in ServiceMix 3.0.
BTW RonTenHove got back to me and I plan on submitting a bug.
Here is the output:
org.apache.servicemix.http.processors.ConsumerProcessor|ClassName=org.apache.servicemix.http.processors.ConsumerProcessor;MethodName=process;_RequestID=c9f72300-7ca6-42f2-8be2-71882f2689ea;|Receiving
HTTP request: POST /Encoding/HttpProxySaService/ HTTP/1.1
Accept: */*
Accept-Language: en-us
Referer: file://C:\dev\current\nettoolkit\pingpong.ws\sample-IE-client.html
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR
1.1.4322; .NET CLR 2.0.50727; InfoPath.1)
Host: b-0648:8192
Content-Length: 156
Connection: keep-alive
Cache-Control: no-cache
org.apache.servicemix.eip.EIPComponent|ClassName=org.apache.servicemix.common.BaseComponent;MethodName=getServiceDescription;_RequestID=c9f72300-7ca6-42f2-8be2-71882f2689ea;|Querying
service description for Endpoint Type: InternalEndpoint
Owner: servicemix-eip Active: True
Service:
{http://nettoolkit.gestalt.com/pingpong/router}pingpong-encoding-router
Endpoint: pingpong-encoding-router
|#]
org.apache.servicemix.eip.EIPComponent|ClassName=org.apache.servicemix.common.BaseComponent;MethodName=getServiceDescription;_RequestID=c9f72300-7ca6-42f2-8be2-71882f2689ea;|No
description found for
{http://nettoolkit.gestalt.com/pingpong/router}pingpong-encoding-router:pingpong-encoding-router|#]
--
View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8300043
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix HTTP BC not working in OpenESB
Posted by Guillaume Nodet <gn...@gmail.com>.
You should be able to set th operation name on the EIP component
as well.
<eip:target service="tns:service" operation="tns:operation" />
On 1/11/07, jlo_gestalt <jl...@gestalt-llc.com> wrote:
>
> I made a change to AsyncBaseLifeCycle to log the exception and then log the
> message:
> catch (Exception e) {
> logger.error("Error processing exchange, exception is", e);
> logger.error("Error processing exchange" + exchange);
>
> This is probably a good idea to duplicate elsewhere.
>
> Anyways the HTTP Request gets to the HTTP BC and the HTTP BC sends the
> request to the EIP component. However when the EIP attempts to send the
> Message to our Component, guess what. Are good ol' buddy
> javax.jbi.messaging.MessagingException: Operation name required to send
> message exchange. EIP doesn't set the operation and consequenlty OpenESB
> throws an exception just like the HTTP BC did before I set the
> defaultOperation value.
>
> How can we fix this long term? Do we need to discuss with OpenESB and
> RonTenHove to overcome this?
> --
> View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8278082
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: ServiceMix HTTP BC not working in OpenESB
Posted by jlo_gestalt <jl...@gestalt-llc.com>.
I made a change to AsyncBaseLifeCycle to log the exception and then log the
message:
catch (Exception e) {
logger.error("Error processing exchange, exception is", e);
logger.error("Error processing exchange" + exchange);
This is probably a good idea to duplicate elsewhere.
Anyways the HTTP Request gets to the HTTP BC and the HTTP BC sends the
request to the EIP component. However when the EIP attempts to send the
Message to our Component, guess what. Are good ol' buddy
javax.jbi.messaging.MessagingException: Operation name required to send
message exchange. EIP doesn't set the operation and consequenlty OpenESB
throws an exception just like the HTTP BC did before I set the
defaultOperation value.
How can we fix this long term? Do we need to discuss with OpenESB and
RonTenHove to overcome this?
--
View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8278082
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix HTTP BC not working in OpenESB
Posted by Guillaume Nodet <gn...@gmail.com>.
Yeah, i think you're right.
Btw the NPE thrown by OpenESB comes from the fact that there is
a null property on the jbi message.
On 1/10/07, jlo_gestalt <jl...@gestalt-llc.com> wrote:
>
> OK, I added a defaultOperation to the consumer endpoints and I got farther.
> Here is a short-term summary. I can give more detail later once I figure out
> how to improve logging in glassfish (it sucks btw).
> I get a NPE when the HTTP BC receives a Request (gut feeling though).
>
> Here is the stack trace:
> java.lang.NullPointerException
> at com.sun.jbi.messaging.MessageImpl.toString(MessageImpl.java:179)
> at
> com.sun.jbi.messaging.MessageExchangeImpl.toString(MessageExchangeImpl.java:478)
> at
> com.sun.jbi.messaging.MessageExchangeProxy.toString(MessageExchangeProxy.java:829)
> at java.lang.String.valueOf(String.java:2615)
> at java.lang.StringBuffer.append(StringBuffer.java:220)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchangeInTx(AsyncBaseLifeCycle.java:345)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle$2.run(AsyncBaseLifeCycle.java:250)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> at java.lang.Thread.run(Thread.java:595)
>
> This gives the appearance that OpenESB is the root cause, but it isn't. Its
> throwing the NPE after the ServiceMix class AsyncBaseLifeCycle receives an
> error and attempts to log the MessageExchange. At which the openesb
> toString() throws the NPE.
>
> This is where the root Exception is being thrown (from
> AsyncBaseLifeCycle.processExchangeInTx()):
> protected void processExchangeInTx(MessageExchange exchange, Transaction
> tx) {
> try {
> if (tx != null) {
> transactionManager.resume(tx);
> }
> processExchange(exchange); // root cause
> } catch (Exception e) {
> logger.error("Error processing exchange " + exchange, e); //
> causes NPE
>
> My guess is processExchange is throwing an Exception and the NPE is coming
> from the log.error in the catch clause.
>
> Let me know what you think. Like I said I plan on getting a better log to
> dig deeper.
>
> --
> View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8267501
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: ServiceMix HTTP BC not working in OpenESB
Posted by jlo_gestalt <jl...@gestalt-llc.com>.
OK, I added a defaultOperation to the consumer endpoints and I got farther.
Here is a short-term summary. I can give more detail later once I figure out
how to improve logging in glassfish (it sucks btw).
I get a NPE when the HTTP BC receives a Request (gut feeling though).
Here is the stack trace:
java.lang.NullPointerException
at com.sun.jbi.messaging.MessageImpl.toString(MessageImpl.java:179)
at
com.sun.jbi.messaging.MessageExchangeImpl.toString(MessageExchangeImpl.java:478)
at
com.sun.jbi.messaging.MessageExchangeProxy.toString(MessageExchangeProxy.java:829)
at java.lang.String.valueOf(String.java:2615)
at java.lang.StringBuffer.append(StringBuffer.java:220)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchangeInTx(AsyncBaseLifeCycle.java:345)
at
org.apache.servicemix.common.AsyncBaseLifeCycle$2.run(AsyncBaseLifeCycle.java:250)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
This gives the appearance that OpenESB is the root cause, but it isn't. Its
throwing the NPE after the ServiceMix class AsyncBaseLifeCycle receives an
error and attempts to log the MessageExchange. At which the openesb
toString() throws the NPE.
This is where the root Exception is being thrown (from
AsyncBaseLifeCycle.processExchangeInTx()):
protected void processExchangeInTx(MessageExchange exchange, Transaction
tx) {
try {
if (tx != null) {
transactionManager.resume(tx);
}
processExchange(exchange); // root cause
} catch (Exception e) {
logger.error("Error processing exchange " + exchange, e); //
causes NPE
My guess is processExchange is throwing an Exception and the NPE is coming
from the log.error in the catch clause.
Let me know what you think. Like I said I plan on getting a better log to
dig deeper.
--
View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8267501
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix HTTP BC not working in OpenESB
Posted by Guillaume Nodet <gn...@gmail.com>.
Ron is right about this one: this call can not work if the endpoint
doesn't have any WSDL description.
Each component is responsible for giving a valid description,
and ServiceMix does not enforce that.
Also, not that from version 3.1, servicemix supports WSDL 2
descriptions.
On 1/10/07, jlo_gestalt <jl...@gestalt-llc.com> wrote:
>
> Ok, I will try that fix and get back to you.
>
> Good point on OpenESB. It still concerns me thought because of this thread
> between you and RonTenHove:
> http://forum.java.sun.com/thread.jspa?forumID=512&threadID=734834
> http://forum.java.sun.com/thread.jspa?forumID=512&threadID=734834
> --
> View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8261345
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: ServiceMix HTTP BC not working in OpenESB
Posted by jlo_gestalt <jl...@gestalt-llc.com>.
Ok, I will try that fix and get back to you.
Good point on OpenESB. It still concerns me thought because of this thread
between you and RonTenHove:
http://forum.java.sun.com/thread.jspa?forumID=512&threadID=734834
http://forum.java.sun.com/thread.jspa?forumID=512&threadID=734834
--
View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8261345
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix HTTP BC not working in OpenESB
Posted by Guillaume Nodet <gn...@gmail.com>.
For non soap endpoints, you can try setting
the defaultOperation attribute on the endpoint.
This should fix your immediate problem.
However, I don't think this behavior is written
in the spec. Maybe OpenEsb is not liberal enough ;-)
On 1/10/07, jlo_gestalt <jl...@gestalt-llc.com> wrote:
>
> We use both SOAP endpoints and non-SOAP endpoints.
> In this particular test case it is not a SOAP endpoint.
>
> Yes I agreed this is a big problem for the other components. That is what
> makes this thread so important. The liberal implementation by ServiceMix of
> the JBI spec might cause the intent of "pluggable JBI Components." By
> reading the spec and supporting documents online you would think this is one
> of the most important features of JBI: the ability to take a component and
> install it in any JBI container. Much like the flexibility we have with web
> applications and being able to deploy a WAR, with minor modifications, in
> Tomcat, Weblogic, JBoss, etc.
>
> Looking forward to your response.
> --
> View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8260442
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: ServiceMix HTTP BC not working in OpenESB
Posted by jlo_gestalt <jl...@gestalt-llc.com>.
We use both SOAP endpoints and non-SOAP endpoints.
In this particular test case it is not a SOAP endpoint.
Yes I agreed this is a big problem for the other components. That is what
makes this thread so important. The liberal implementation by ServiceMix of
the JBI spec might cause the intent of "pluggable JBI Components." By
reading the spec and supporting documents online you would think this is one
of the most important features of JBI: the ability to take a component and
install it in any JBI container. Much like the flexibility we have with web
applications and being able to deploy a WAR, with minor modifications, in
Tomcat, Weblogic, JBoss, etc.
Looking forward to your response.
--
View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8260442
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix HTTP BC not working in OpenESB
Posted by Guillaume Nodet <gn...@gmail.com>.
Do you use a SOAP endpoint ?
In such a case, the operation should be se.
Anyway, this will certainly be a problem for other components, as
ServiceMix does not enforce an operation to be set.
On 1/9/07, jlo_gestalt <jl...@gestalt-llc.com> wrote:
>
> I have finally installed the ServiceMix HTTP BC into OpenESB (Glassfish)
> without any start up errors; most of which were classpath issues.
> Now when I send an HTTP request to the HTTP BC I get the following
> Exception:
> javax.servlet.ServletException: Failed to process request:
> javax.jbi.messaging.MessagingException: Operation name required to send
> message exchange.
> at
> org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:79)
>
>
> This is thrown by OpenESB's MessageExchangeProxy.validate() method who
> throws this Exception when the
> javax.jbi.messaging.MessageExchange.getOperation() returns null.
>
>
> So it appears that ServiceMix doesn't require the operation to be set and
> OpenESB does. Is this a compatibility issue? What can be done to resolve
> this? Is this related to this
> http://forum.java.sun.com/thread.jspa?forumID=512&threadID=734834 thread ?
> --
> View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8240728
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/
Re: ServiceMix HTTP BC not working in OpenESB
Posted by depstei2 <de...@umd.edu>.
I tried following the tutorial on how to get the servicemix components
working on open-esb,
I am just trying to expose an external web service locally, but I get this
error and no log:
Failed Execution of deployServiceAssembly: stockquote_sa.zip
Component: servicemix-http
Error: () org/apache/xbean/spring/context/SpringApplicationContext
Component: servicemix-http
Error: () could not deploy xbean service unit
Has anyone seen this? I am going to try the esb forums too.
jlo_gestalt wrote:
>
> I am installing the real HTTP BC component version 3.0 named:
> servicemix-http-3.0-incubating-installer.zip.
>
--
View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a13262673
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix HTTP BC not working in OpenESB
Posted by jlo_gestalt <jl...@gestalt-llc.com>.
I am installing the real HTTP BC component version 3.0 named:
servicemix-http-3.0-incubating-installer.zip.
--
View this message in context: http://www.nabble.com/ServiceMix-HTTP-BC-not-working-in-OpenESB-tf2947046s12049.html#a8258833
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: ServiceMix HTTP BC not working in OpenESB
Posted by Bruce Snyder <br...@gmail.com>.
On 1/9/07, jlo_gestalt <jl...@gestalt-llc.com> wrote:
>
> I have finally installed the ServiceMix HTTP BC into OpenESB (Glassfish)
> without any start up errors; most of which were classpath issues.
> Now when I send an HTTP request to the HTTP BC I get the following
> Exception:
> javax.servlet.ServletException: Failed to process request:
> javax.jbi.messaging.MessagingException: Operation name required to send
> message exchange.
> at
> org.apache.servicemix.http.HttpBridgeServlet.doPost(HttpBridgeServlet.java:79)
>
>
> This is thrown by OpenESB's MessageExchangeProxy.validate() method who
> throws this Exception when the
> javax.jbi.messaging.MessageExchange.getOperation() returns null.
>
>
> So it appears that ServiceMix doesn't require the operation to be set and
> OpenESB does. Is this a compatibility issue? What can be done to resolve
> this? Is this related to this
> http://forum.java.sun.com/thread.jspa?forumID=512&threadID=734834 thread ?
Are you deploying the old lightweight HTTP component
(http://servicemix.org/site/http.html) or the servicemix-http standard
JBI component (http://servicemix.org/site/servicemix-http.html)? The
old lightweight components are not JBI compliant so they cannot be
deployed to other JBI containers. However, the newer standard JBI
components (i.e., any component whose name is servicemix-*) are JBI
compliant and therefore can be deployed to any JBI container.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache Geronimo - http://geronimo.apache.org/
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Castor - http://castor.org/