I'm just getting started with Sling/Felix; so I'm probably not in sync with the overall strategy. But my planned approach is to deploy Sling as a webapp in a normal j2ee server (or as a peer application). I don't see how Sling can effectively replace a j2ee server.
This is why I don't understand the benefit of getting the ActiveMQ web console working in Sling. My ActiveMQ brokers/console would be deployed as a peer and any ActiveMQ bundle would be related to message handling. Is it for better access to the console? Or, that standalone is preferred? Just curious if I'm off base with my thinking. -Robert On Fri, Oct 23, 2009 at 9:27 AM, Carl F. Hall <[email protected]>wrote: > > AFAIK, Felix HttpService doesn't support legacy WAR > > files. > > This seems OK to me, but let me know if you forsee this as a problem > > for > > some reason. > > I may be in the minority here but I'm working diligently to get the > ActiveMQ web console (j2ee webapp) to work in Sling. For me to continue > using this console, I would need WAR support. >
