You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Stefan Wagner <wa...@ixtern.de> on 2001/05/17 18:16:43 UTC
*.xreg files
Hi!
Can someone explain the new *.xreg files in the conf directory?
Thanks
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: *.xreg files
Posted by Raphaël Luta <ra...@networks.groupvu.com>.
Stefan Wagner wrote:
>
> Am Samstag, 19. Mai 2001 11:45 schrieben Sie:
>
> > > But why do all my own portlets display "No title set"? I (think I) did
> > > set it in the Registry. I tried both, the jcfg and the portlet.xreg file.
> > >
> > > Can someone help me out?
> >
> > send me your porlet defintion in xreg and I'll check if I can reproduce
> > this.
>
> Sorry! Forget it!
>
> I just tried it in the jcfg file. That isn't supported anymore, isn't it?
>
No, it won't be used anymore in 1.3a2.
--
Raphael Luta - raphael.luta@networks.groupvu.com
Vivendi Universal Networks - Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: *.xreg files
Posted by Stefan Wagner <wa...@ixtern.de>.
Am Samstag, 19. Mai 2001 11:45 schrieben Sie:
> > But why do all my own portlets display "No title set"? I (think I) did
> > set it in the Registry. I tried both, the jcfg and the portlet.xreg file.
> >
> > Can someone help me out?
>
> send me your porlet defintion in xreg and I'll check if I can reproduce
> this.
Sorry! Forget it!
I just tried it in the jcfg file. That isn't supported anymore, isn't it?
> --
> Raphaël Luta - luta.raphael@networks.vivendi.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: *.xreg files
Posted by ra...@networks.groupvu.com.
Stefan Wagner wrote:
>
> Am Donnerstag, 17. Mai 2001 21:35 schrieben Sie:
> > Stefan Wagner wrote:
> > > Hi!
> > >
> > > Can someone explain the new *.xreg files in the conf directory?
> >
> > They are used by the new registry service that will replace the registry
> > manager service in 1.3a2.
> >
> > They completely replace the old jcfg config file keeping the same syntax
> > (OK, there's one syntax exception).
> >
> > The goal of this move is to enable easier portlet deployment since they can
> > be bundled with a default *.xreg file that will be automatically picked up
> > by Jetspeed at runtime. This move will be completed in 1.3a3 when the
> > registry will also recognize the new PAR files defined in the new Portlet
> > API.
>
> Okay. I think that's great!
>
> > Another implication of this move is that the FeedDaemon now serializes and
> > save the portlet definitions it creates for the RSS entries so this should
> > give a better visibility on the syndication process.
> >
> > Finally, the Registry API has been completed so that you can
> > programmatically manipulate the Registry and serialize the state on disk.
>
> All right. I think I got this, too.
>
> But why do all my own portlets display "No title set"? I (think I) did set it
> in the Registry. I tried both, the jcfg and the portlet.xreg file.
>
> Can someone help me out?
>
send me your porlet defintion in xreg and I'll check if I can reproduce this.
--
Raphaël Luta - luta.raphael@networks.vivendi.net
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: *.xreg files
Posted by Stefan Wagner <wa...@ixtern.de>.
Am Donnerstag, 17. Mai 2001 21:35 schrieben Sie:
> Stefan Wagner wrote:
> > Hi!
> >
> > Can someone explain the new *.xreg files in the conf directory?
>
> They are used by the new registry service that will replace the registry
> manager service in 1.3a2.
>
> They completely replace the old jcfg config file keeping the same syntax
> (OK, there's one syntax exception).
>
> The goal of this move is to enable easier portlet deployment since they can
> be bundled with a default *.xreg file that will be automatically picked up
> by Jetspeed at runtime. This move will be completed in 1.3a3 when the
> registry will also recognize the new PAR files defined in the new Portlet
> API.
Okay. I think that's great!
> Another implication of this move is that the FeedDaemon now serializes and
> save the portlet definitions it creates for the RSS entries so this should
> give a better visibility on the syndication process.
>
> Finally, the Registry API has been completed so that you can
> programmatically manipulate the Registry and serialize the state on disk.
All right. I think I got this, too.
But why do all my own portlets display "No title set"? I (think I) did set it
in the Registry. I tried both, the jcfg and the portlet.xreg file.
Can someone help me out?
Ciao
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: *.xreg files
Posted by ra...@networks.groupvu.com.
Stefan Wagner wrote:
>
> Hi!
>
> Can someone explain the new *.xreg files in the conf directory?
>
They are used by the new registry service that will replace the registry manager
service in 1.3a2.
They completely replace the old jcfg config file keeping the same syntax
(OK, there's one syntax exception).
The goal of this move is to enable easier portlet deployment since they can be bundled
with a default *.xreg file that will be automatically picked up by Jetspeed at runtime.
This move will be completed in 1.3a3 when the registry will also recognize the new PAR
files defined in the new Portlet API.
Another implication of this move is that the FeedDaemon now serializes and save the
portlet definitions it creates for the RSS entries so this should give a better visibility
on the syndication process.
Finally, the Registry API has been completed so that you can programmatically manipulate
the Registry and serialize the state on disk.
--
Raphaël Luta - luta.raphael@networks.vivendi.net
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org