Hi,
I am very interested on Prowler, I downloaded it (the compiled version), but
i didn't find any documentation
on how to set up it with jetspeed/cocoon.
For now I just added the jars to the class path,....
What have I to do then?
Thanks for any suggestions
Marco
-----Messaggio originale-----
Da: Gerd Mueller [mailto:[EMAIL PROTECTED]]
Inviato: Tuesday, November 07, 2000 4:29 PM
A: JetSpeed
Oggetto: Re: Portlet API
> Im looking over your configuration design and it reminds of something I've
> been meaning to research: Prowler.
> Is anyone familiar with it?
http://www.infozone-group.org/projects_main.html
>
> +-----------------------------------------------+
> | Portlet Customizer |
> +-----------------------------------------------+
> | Portlet Cust.Description Provider Interface |
> +-----------------+------+----------------------+
> | File Based Impl | or | Impl. using Database |
> +-----------------+ +----------------------+
> | |
> Customization Customization
> Descriptors in Descriptor Entries
> Portlet Registry XML File in a Database
>
> What I see in common is the abstraction from how the XML customization is
> stored as in your above diagram.
> I believe Prowler provides this abstraction under a transaction-controlled
> api.
>
> From reading the online docs, I would say Prowler is an xml-based content
> management system with some versioning and transaction support.
Thats correct. Prowler integrates different data sources (the resources),
e.g.
databases, ejb servers, mailboxes, etc., via the so-called adapters in an
XML based repository. An adapter is responsable to convert data coming from
a resource to XML and if possible back. From this point of view Prowler acts
as a content feeder for portlets.
But you may use Prowler to store the customization descriptors in a
transaction-safe
way. We've already thought about an integration of Jetspeed and Prowler.
We'd
like to use Jetspeed (+ Turbine) as the web-(portal)-frontend and store all
user-related information (that includes customization) within Prowler.
Once the 'Portlet Cust.Description Provider Interface' is defined, it should
be
easy to write a Prowler specific implementation.
> I could see how Jetspeed can use Prowler as a source
That would be really cool.
> for its content via the Prowler Java
> API and tag library. Transactions and versioning could be very valuable.
>
> I also need to disclaim: Ive just discovered Prowler a few days ago. I
> believe its open source but I really don't know much about it.
Prowler is completely open source - Apache-like license.
Best Regards,
Gerd
--
________________________________________________________________
Gerd Mueller [EMAIL PROTECTED]
SMB GmbH http://www.smb-tec.com
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
