There is currently a bug in servicemix-http which
forbig the use of servicemix-http as managed, when
not using the HttpSpringComponent (see [1]).
Feel free to provide a patch to the existing JIRA [2]

[1] 
http://www.nabble.com/WAR-deployment-of-servicemix-http-tf2258443.html#a6265559
[2] http://issues.apache.org/activemq/browse/SM-578

On 9/18/06, vijaymasina <[EMAIL PROTECTED]> wrote:

I was not able to get this working. We have similar requirment to provide
multiple http endpoints using servicemix . I am getting "The component is
not an instance of HttpSpringComponent" message. Please provide a solution
for this problem.



jpuro wrote:
>
> Using the JBoss deployer, is it possible to achieve the following
> situation with a web application.
>
> 1)  Deploy a web application under the following context /MyWebApp.  So to
> reach this web application you would navigate to
> http://localhost:8080/MyWebApp.
>
> 2)  Deploy a service assembly that has a service unit in it which uses the
> http endpoint with "managed=true" set.  Typically this means that the
> endpoint will reuse the servlet's web context if this was deployed in a
> full blown .war file.  However, I'd like it to reuse the web context
> already created in the above step (MyWebApp).  There is one more
> requirement, instead of it just hijacking the MyWebApp web context, I
> would like it to add its own path onto the URL.  So in order to actually
> access this http endpoint you would type in
> http://localhost:8080/MyWebApp/httpEndpoint1.
>
> 3)  Down the road I would like to deploy other service assemblies that
> re-use the same MyWebApp web context, but as in the above situation I
> would like them to redefine their own sub path.  So the end result of
> let's say 4 different service assembly deployments would be:
>
> http://localhost:8080/MyWebApp/httpEndpoint1
>
> http://localhost:8080/MyWebApp/httpEndpoint2
>
> http://localhost:8080/MyWebApp/httpEndpoint3
>
> http://localhost:8080/MyWebApp/httpEndpoint4
>
> As you can see what I am trying to achieve is the ability to deploy a
> single .War file and have various service units/service assemblies (which
> are independent of each other) hijack the web context of the originally
> deployed web application.  I do not want to have to deploy a new web
> application per each new sub path I need to create.
>
> -Jeff
>

--
View this message in context: 
http://www.nabble.com/Http-endpoints-and-the-managed-attribute-tf2197708.html#a6371800
Sent from the ServiceMix - User mailing list archive at Nabble.com.




--
Cheers,
Guillaume Nodet

Reply via email to