Integration with Axis ( http://ws.apache.org/axis/ ) into the same web
context as Magnolia is very easy. Once Magnolia has access to Axis,
creating a web service from which your portlet type application can
access data is very simple. I have implemented this on two occasions
now, and both times have been very pleased with the results.
Since the magnolia context has access to all the repository information,
making calls to the repository is done with the standard Magnolia API.
As a web service, you have the ability to pass data both into and out of
the magnolia repository.
Your remote application simply then makes a call to the web-service
context in the magnolia instance, for example:
http://my.host.com/magnoliaPublic/webservices/topArticles
The registered servlet that Axis is serving will produce a WSDL and all
needed information for interacting with the repository and displaying
the resulting data.
Cheers,
-Travis
Theodore Nguyen-Cao wrote:
Hey,
Has anyone had experience with pulling Magnolia content into a different
application context?
Since Magnolia lives in its own application context, what I would like
to do is pull in Magnolia content (HTML, CSS, images, js, flash, etc.)
into a separate application context to serve up in snippets.
Essentially, what I'm looking for is a portlet-like solution that isn't
dependent on full-blown portlet integration. Initial thinking is to use
c:import tags or maybe using SiteMesh. Anyone have cooler ideas? :)
Thanks in advance,
Theo
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
