Raphael Luta wrote:
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: Monday, December 18, 2000 12:37 AM
> To: JetSpeed
> Subject: Re: minor problems in release_1_3a1-branch
>
>
> David Sean Taylor wrote:
> >
> > > > 3) I'm not sure of the state of the profiler, which is correct?
> > > (The second one works, but the distribution has files
> > > > of the first form)
> > > >
> > > > C:\TOMCAT\WEBAPPS\jetspeed/WEB-INF/psml/demo/homeHTML.psml
> > > > or:
> > > >
> C:\TOMCAT\WEBAPPS\jetspeed\WEB-INF\psml\user\userid\html\default.psml
> >
> > The new profiler is disabled in Home.java.
> > Im really not sure what /demo/homeHTML.psml is used for. Its
> not part of the
> > new profiler.
> > In order to get the new profiler completely working, it needs to be
> > integrated with the new customizer and new persistence service.
> >
> > It wouldn't be that difficult, except that the customizer and
> persistence
> > service don't have any concept of 'named-page' resources other than the
> > default, nor does it support 'group' or 'role' resources. So I
> need to come
> > with a way of passing that information around, since with the
> profiler its
> > in the request URL. So the problem is how does the customizer know which
> > page, group or role resource it is working on. The security service will
> > have the same problem. By using the MultiDeviceProfler, there
> are alot of
> > assumptions about two pages per user: one for html and one for wml.
> > Decoupling will not be that trivial.
> >
> > Even so, I'd still like to give it a try (with everyone's +1 of course)
> >
>
> So what you say is that it's quite risky to do it in a hurry because
> the customizer and persistence system have some hard-wired
> dependencies on
> the MultiDeviceProfiler (which is bad) ?
>
> If this is the case, I'm -1 for integration in 1.3a1, if we keep
> the release
> date for this week, unless you can work quickly and closely with
> someone from
> the IBM to fix this.
>
Im continuing work on this on will send a status by tomorrow evening.
So far its not so risky, its just a matter of doing it right and abstracting
and decoupling everything.
I will have a better idea of the risks by then. If its too late for 1.3a1
then so be it...
> In any case, I want to freeze the code at least 24 hours before
> releasing to
> make sure no big bug is introduced in the release so that leaves
> very little
> time for working on the profiler integration.
>
> > Raphael, I can't believe how much stuff you have committed this weekend!
> >
> > Could you please send me an email summarizing what you've committed and
> > changed, and specifically what areas I need to add or modify
> documentation.
>
> Nothing realy major, most of what I've done is described in the
> TODO-RELEASE
> document.
> The only important modification is:
> I moved out some portlets of the main source tree in the /modules
> directory
> We'll need to provide some build instructions for these.
>
> --
> Rapha�l Luta - [EMAIL PROTECTED]
> Vivendi Universal Networks - Services Manager / Paris
>
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
