When is this new version of jetspeed 1.3a2 being released ? I wanted to play
with .xreg files. Should I download the latest source from cvs ?
Elham
> -----Original Message-----
> From: Paul Spencer [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 19, 2001 6:14 AM
> To: [EMAIL PROTECTED]
> Subject: Re: JetSpeed Registry question
>
>
> If the desire is to pass configurable information to the portlet,
> parameters may be the way to go. They have the following advantages:
> o No changes to current schema definitions
> o I believe they are supported by customize, i.e. the user can change
> the value.
> o No limit on number of parameters
> o Parameters can be added at will
>
> See the RSS in portlets.xreg for an example. Place your entries in
> local-portlets.xreg
>
> Hopefully one of the developers will comment on this.
>
> Paul Spencer
>
> Elham Chandler wrote:
> >
> > Hi,
> >
> > I'm new to jetspeed. I already have it installed and have added
> > portlets to connect to some applications/html that we've developed here.
> > All seems to be working well. I now need to do some customizations
> > which would mean I would need to extend the meta-info tag.
> >
> > I have a question about extending the meta-info section of the
> > jetspeed-config.jcfg such that it has some custom information
> > specific to our project. Can I extend the
> > java/org/apache/jetspeed/xml/api/jetspeedconfig/MetaInfoDescriptor.java
> > class such that I can add our own set of tags to read in and process ?
> > ie. subclass it. From looking at the code, it appears I can do this,
> > but I wanted to know if there is a precedence and if indeed
> > vendor specific information should go into the jetspeed-config.jcfg
> > file or not. If not, where should it be instead ?
> >
> > Would the stylesheet that is used for validation then have to change ?
> > ( I would think so).
> >
> > What other possible issue could one face with this change ?
> >
> > Any and all help would be appreciated.
> >
> > thanks,
> > Elham Chandler
> > Interwoven, Inc.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
