You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Ajan Balakrishnan <AB...@ForestExpress.com> on 2001/10/18 01:05:44 UTC
Jetspeed URL redirection question
> I'm a newbie to jetspeed. My question is when the jetspeed shows it
> homepage the url shown is
> http://localhost:8080/jetspeed/portal/screen/Home or when i click the
> customize link it invokes
> http://localhost:8080/jetspeed/portal/screen/Customize url. Could
> anybody please tell me where these files are loadecated inside jetspeed
> directories or is it an alias name to some other directories.
>
> Thanks for the help in advance
> Ajan
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Jetspeed URL redirection question
Posted by Paul Spencer <pa...@mikon.com>.
Ajan,
You will not find the files, because they do not exist. Jetspeed
interprets the URL and determines what need to be returned to the
browser. I suggest you review Jetspeed's web site,
http://jakarta.apache.org/jetspeed
Also this message was CC: to the jetspeed-dev mailing list. Only post a
message to 1 mailing list. In this case the jetspeed-user was the
appropriate list.
Paul Spencer
Ajan Balakrishnan wrote:
>
> > I'm a newbie to jetspeed. My question is when the jetspeed shows it
> > homepage the url shown is
> > http://localhost:8080/jetspeed/portal/screen/Home or when i click the
> > customize link it invokes
> > http://localhost:8080/jetspeed/portal/screen/Customize url. Could
> > anybody please tell me where these files are loadecated inside jetspeed
> > directories or is it an alias name to some other directories.
> >
> > Thanks for the help in advance
> > Ajan
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-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
AW: Velocity / JSP / XML & XSLT : Why ???
Posted by Norman Schöneich <sc...@ecooperate.de>.
This sounds very interesting.
If I could help in some way, tell me !
-----Ursprüngliche Nachricht-----
Von: Santiago Gala [mailto:sgala@hisitech.com]
Gesendet: Freitag, 19. Oktober 2001 11:53
An: jetspeed-dev@jakarta.apache.org
Betreff: Re: Velocity / JSP / XML & XSLT : Why ???
Raphaël Luta wrote:
> Norman Schoneich wrote:
>
>> Jetspeed supports different template engines.
>> But in the moment, the default template layout engine is velocity and
>> it'is
>> the most supported engine by the jetspeed developers.
>> The previous default engine was jsp, but the support (or development
>> process) of the jsp layout seems to be stopped.
>> I can understand that some people prefer velocity. But every layout
>> engine
>> has it's own advantages and disadvanteges. I think Jetspeed
>> has to support multiple layout engines, but they must be handled
>> equally.
>>
>
>
> Agreed on the multiple support, as for the *equal* support it depends
> a all
> on finding people that make sure any given layout system is up to date
> with
> the engine features...
> I personnally use Velocity so this is the layout on which I'll work most.
>
>
>> What's about an XML & XSLT based approach ? Is it possible (or
>> better) to
>> render the portlets by the different controllers and then render the
>> result
>> with an XSLT file (the portlets use themself xml/xsl, which i use). I
>> like
>> this approach the most, because it' s based on open standards unlike
>> velocity.
>>
I work with a company that has developed a product based on Jetspeed
that does all rendering using a SAX event chain, using a
SAXXSLTtemplating system. If you notice the PortletAPI, there is a
provision for SAXPortlet, which are portlets that "write" content as a
chain of SAX events. This was agreed after discussing that "character
streaming" portlets (jsp,vm,...) are different from "event streaming"
portlets, and it would be hard to need parsing/serialization at every
point in the rendering loop.
We are making Jetspeed evolve so that it supports both byte-stream
portlets (be them java-class-portlets, jsp, vm,...), and
sax-event-stream portlets (be them XSLT based or generated). You are
welcome to help here. ;-)
>
>
> It's possible to use XML & XSLT but not necessarily very easy to manage:
> - if each portlet outputs a specific XML dialect/namespace, it's very
> difficult
> to write an engine that transfoms all these dialects into the target
> type
> without a complete foreknowledge of the supported XML dialects.
>
> - if each portlet outputs a standard media independent, layout
> oriented XML
> dialect (FO anybody ?) you can actually post-process the output
> correctly
We are aware of the problems that you are outlining. I think that FO is
too oriented to positioning to be useful here. I would prefer a more
abstract markup for the interface description, more like (parts of)
XHTML, so that it can be styled to several final markups, including
FO/pdf, Applets code, HTML (in several variants), text, Flash, ...
XSLT is very useful here as a transformation tool, but I agree that we
should look for a standard high level set of namespaces to describe how
output should look like.
>
> but you need to carefully select your intermediate layout language
> so that
> it's not to complex/costly to transform.
Yes. I think that XHTML Basic (http://www.w3.org/TR/xhtml-basic/) could
be a reasonable subset for portlet markup. It is expressive enough to
represent "paragraph" markup in abstract form, and basic form handling
capabilities. Complex display and styling can then be left to the PSML
rendering mechanism and the style sheets applied. What do you think?
>
>
> Also Velcoity is definitely an "open" format since its specification is
> publicly available and anybody can write an alternate implementation.
> It's just not recognized by an industry committe yet. But then if it fits
> your need better, who cares ?
>
I'm very happy with Velocity. I'm just starting to hack it, and I think
that Velocity with good tools is definitely going in the right
direction. I prefer it over jsp, even with taglibs. YMMV.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Velocity / JSP / XML & XSLT : Why ???
Posted by Santiago Gala <sg...@hisitech.com>.
Raphaël Luta wrote:
> Norman Schoneich wrote:
>
>> Jetspeed supports different template engines.
>> But in the moment, the default template layout engine is velocity and
>> it'is
>> the most supported engine by the jetspeed developers.
>> The previous default engine was jsp, but the support (or development
>> process) of the jsp layout seems to be stopped.
>> I can understand that some people prefer velocity. But every layout
>> engine
>> has it's own advantages and disadvanteges. I think Jetspeed
>> has to support multiple layout engines, but they must be handled
>> equally.
>>
>
>
> Agreed on the multiple support, as for the *equal* support it depends
> a all
> on finding people that make sure any given layout system is up to date
> with
> the engine features...
> I personnally use Velocity so this is the layout on which I'll work most.
>
>
>> What's about an XML & XSLT based approach ? Is it possible (or
>> better) to
>> render the portlets by the different controllers and then render the
>> result
>> with an XSLT file (the portlets use themself xml/xsl, which i use). I
>> like
>> this approach the most, because it' s based on open standards unlike
>> velocity.
>>
I work with a company that has developed a product based on Jetspeed
that does all rendering using a SAX event chain, using a
SAXXSLTtemplating system. If you notice the PortletAPI, there is a
provision for SAXPortlet, which are portlets that "write" content as a
chain of SAX events. This was agreed after discussing that "character
streaming" portlets (jsp,vm,...) are different from "event streaming"
portlets, and it would be hard to need parsing/serialization at every
point in the rendering loop.
We are making Jetspeed evolve so that it supports both byte-stream
portlets (be them java-class-portlets, jsp, vm,...), and
sax-event-stream portlets (be them XSLT based or generated). You are
welcome to help here. ;-)
>
>
> It's possible to use XML & XSLT but not necessarily very easy to manage:
> - if each portlet outputs a specific XML dialect/namespace, it's very
> difficult
> to write an engine that transfoms all these dialects into the target
> type
> without a complete foreknowledge of the supported XML dialects.
>
> - if each portlet outputs a standard media independent, layout
> oriented XML
> dialect (FO anybody ?) you can actually post-process the output
> correctly
We are aware of the problems that you are outlining. I think that FO is
too oriented to positioning to be useful here. I would prefer a more
abstract markup for the interface description, more like (parts of)
XHTML, so that it can be styled to several final markups, including
FO/pdf, Applets code, HTML (in several variants), text, Flash, ...
XSLT is very useful here as a transformation tool, but I agree that we
should look for a standard high level set of namespaces to describe how
output should look like.
>
> but you need to carefully select your intermediate layout language
> so that
> it's not to complex/costly to transform.
Yes. I think that XHTML Basic (http://www.w3.org/TR/xhtml-basic/) could
be a reasonable subset for portlet markup. It is expressive enough to
represent "paragraph" markup in abstract form, and basic form handling
capabilities. Complex display and styling can then be left to the PSML
rendering mechanism and the style sheets applied. What do you think?
>
>
> Also Velcoity is definitely an "open" format since its specification is
> publicly available and anybody can write an alternate implementation.
> It's just not recognized by an industry committe yet. But then if it fits
> your need better, who cares ?
>
I'm very happy with Velocity. I'm just starting to hack it, and I think
that Velocity with good tools is definitely going in the right
direction. I prefer it over jsp, even with taglibs. YMMV.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Velocity / JSP / XML & XSLT : Why ???
Posted by Paul Spencer <pa...@mikon.com>.
I have not seen this problem. Every time I have changed, and saved, the
JSP file, the updated page was displayed. Windows has a one minute
granularity on the file timestamp, so I make sure not to save the save
the file twice in the same minute.
Paul Spencer
Frans Thamura wrote:
>
> I get an experience that if you using JSP, tomcat will compile it, and if
> you change the JSP, the page will use old class from old JSP, this is
> wasting time.
>
> Velocity is JIT, compile in memory.
>
> Try it.
>
> Frans
>
> ----- Original Message -----
> From: "Raphaël Luta" <ra...@networks.groupvu.com>
> To: <je...@jakarta.apache.org>
> Sent: Friday, October 19, 2001 2:21 PM
> Subject: Re: Velocity / JSP / XML & XSLT : Why ???
>
> > Norman Schoneich wrote:
> >
> > > Jetspeed supports different template engines.
> > > But in the moment, the default template layout engine is velocity and
> it'is
> > > the most supported engine by the jetspeed developers.
> > > The previous default engine was jsp, but the support (or development
> > > process) of the jsp layout seems to be stopped.
> > > I can understand that some people prefer velocity. But every layout
> engine
> > > has it's own advantages and disadvanteges. I think Jetspeed
> > > has to support multiple layout engines, but they must be handled
> equally.
> > >
> >
> >
> > Agreed on the multiple support, as for the *equal* support it depends a
> all
> > on finding people that make sure any given layout system is up to date
> with
> > the engine features...
> > I personnally use Velocity so this is the layout on which I'll work most.
> >
> >
> > > What's about an XML & XSLT based approach ? Is it possible (or better)
> to
> > > render the portlets by the different controllers and then render the
> result
> > > with an XSLT file (the portlets use themself xml/xsl, which i use). I
> like
> > > this approach the most, because it' s based on open standards unlike
> > > velocity.
> > >
> >
> >
> > It's possible to use XML & XSLT but not necessarily very easy to manage:
> > - if each portlet outputs a specific XML dialect/namespace, it's very
> difficult
> > to write an engine that transfoms all these dialects into the target
> type
> > without a complete foreknowledge of the supported XML dialects.
> >
> > - if each portlet outputs a standard media independent, layout oriented
> XML
> >
> > dialect (FO anybody ?) you can actually post-process the output
> correctly
> >
> > but you need to carefully select your intermediate layout language so
> that
> >
> > it's not to complex/costly to transform.
> >
> >
> > Also Velcoity is definitely an "open" format since its specification is
> >
> > publicly available and anybody can write an alternate implementation.
> > It's just not recognized by an industry committe yet. But then if it fits
> > your need better, who cares ?
> >
> >
> > > norsch
> > >
> > > Norman Schoneich
> > >
> > > -----Ursprungliche Nachricht-----
> > > Von: Paul Spencer [mailto:paul@mikon.com]
> > > Gesendet: Donnerstag, 18. Oktober 2001 16:25
> > > An: jetspeed-dev@jakarta.apache.org
> > > Betreff: Re: Jetspeed URL redirection question
> > >
> > >
> > > Ajan,
> > > You will not find the files, because they do not exist. Jetspeed
> > > interprets the URL and determines what need to be returned to the
> > > browser. I suggest you review Jetspeed's web site,
> > > http://jakarta.apache.org/jetspeed
> > >
> > > Paul Spencer
> > >
> > > Ajan Balakrishnan wrote:
> > >
> > >>>I'm a newbie to jetspeed. My question is when the jetspeed shows it
> > >>>homepage the url shown is
> > >>>http://localhost:8080/jetspeed/portal/screen/Home or when i click the
> > >>>customize link it invokes
> > >>>http://localhost:8080/jetspeed/portal/screen/Customize url. Could
> > >>>anybody please tell me where these files are loadecated inside
> jetspeed
> > >>>directories or is it an alias name to some other directories.
> > >>>
> > >>>Thanks for the help in advance
> > >>>Ajan
> > >>>
> > >>>
> > >>>
> > >>---------------------------------------------------------------------
> > >>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> > >>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
> > >>
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
> > >
> > >
> >
> >
> >
> > --
> > --
> > Raphael Luta - raphael.luta@networks.groupvu.com
> > Vivendi Universal Networks - Paris
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Velocity / JSP / XML & XSLT : Why ???
Posted by Frans Thamura <ft...@yahoo.com>.
I get an experience that if you using JSP, tomcat will compile it, and if
you change the JSP, the page will use old class from old JSP, this is
wasting time.
Velocity is JIT, compile in memory.
Try it.
Frans
----- Original Message -----
From: "Raphaël Luta" <ra...@networks.groupvu.com>
To: <je...@jakarta.apache.org>
Sent: Friday, October 19, 2001 2:21 PM
Subject: Re: Velocity / JSP / XML & XSLT : Why ???
> Norman Schoneich wrote:
>
> > Jetspeed supports different template engines.
> > But in the moment, the default template layout engine is velocity and
it'is
> > the most supported engine by the jetspeed developers.
> > The previous default engine was jsp, but the support (or development
> > process) of the jsp layout seems to be stopped.
> > I can understand that some people prefer velocity. But every layout
engine
> > has it's own advantages and disadvanteges. I think Jetspeed
> > has to support multiple layout engines, but they must be handled
equally.
> >
>
>
> Agreed on the multiple support, as for the *equal* support it depends a
all
> on finding people that make sure any given layout system is up to date
with
> the engine features...
> I personnally use Velocity so this is the layout on which I'll work most.
>
>
> > What's about an XML & XSLT based approach ? Is it possible (or better)
to
> > render the portlets by the different controllers and then render the
result
> > with an XSLT file (the portlets use themself xml/xsl, which i use). I
like
> > this approach the most, because it' s based on open standards unlike
> > velocity.
> >
>
>
> It's possible to use XML & XSLT but not necessarily very easy to manage:
> - if each portlet outputs a specific XML dialect/namespace, it's very
difficult
> to write an engine that transfoms all these dialects into the target
type
> without a complete foreknowledge of the supported XML dialects.
>
> - if each portlet outputs a standard media independent, layout oriented
XML
>
> dialect (FO anybody ?) you can actually post-process the output
correctly
>
> but you need to carefully select your intermediate layout language so
that
>
> it's not to complex/costly to transform.
>
>
> Also Velcoity is definitely an "open" format since its specification is
>
> publicly available and anybody can write an alternate implementation.
> It's just not recognized by an industry committe yet. But then if it fits
> your need better, who cares ?
>
>
> > norsch
> >
> > Norman Schoneich
> >
> > -----Ursprungliche Nachricht-----
> > Von: Paul Spencer [mailto:paul@mikon.com]
> > Gesendet: Donnerstag, 18. Oktober 2001 16:25
> > An: jetspeed-dev@jakarta.apache.org
> > Betreff: Re: Jetspeed URL redirection question
> >
> >
> > Ajan,
> > You will not find the files, because they do not exist. Jetspeed
> > interprets the URL and determines what need to be returned to the
> > browser. I suggest you review Jetspeed's web site,
> > http://jakarta.apache.org/jetspeed
> >
> > Paul Spencer
> >
> > Ajan Balakrishnan wrote:
> >
> >>>I'm a newbie to jetspeed. My question is when the jetspeed shows it
> >>>homepage the url shown is
> >>>http://localhost:8080/jetspeed/portal/screen/Home or when i click the
> >>>customize link it invokes
> >>>http://localhost:8080/jetspeed/portal/screen/Customize url. Could
> >>>anybody please tell me where these files are loadecated inside
jetspeed
> >>>directories or is it an alias name to some other directories.
> >>>
> >>>Thanks for the help in advance
> >>>Ajan
> >>>
> >>>
> >>>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
> >
> >
>
>
>
> --
> --
> Raphael Luta - raphael.luta@networks.groupvu.com
> Vivendi Universal Networks - Paris
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Velocity / JSP / XML & XSLT : Why ???
Posted by Raphaël Luta <ra...@networks.groupvu.com>.
Norman Schoneich wrote:
> Jetspeed supports different template engines.
> But in the moment, the default template layout engine is velocity and it'is
> the most supported engine by the jetspeed developers.
> The previous default engine was jsp, but the support (or development
> process) of the jsp layout seems to be stopped.
> I can understand that some people prefer velocity. But every layout engine
> has it's own advantages and disadvanteges. I think Jetspeed
> has to support multiple layout engines, but they must be handled equally.
>
Agreed on the multiple support, as for the *equal* support it depends a all
on finding people that make sure any given layout system is up to date with
the engine features...
I personnally use Velocity so this is the layout on which I'll work most.
> What's about an XML & XSLT based approach ? Is it possible (or better) to
> render the portlets by the different controllers and then render the result
> with an XSLT file (the portlets use themself xml/xsl, which i use). I like
> this approach the most, because it' s based on open standards unlike
> velocity.
>
It's possible to use XML & XSLT but not necessarily very easy to manage:
- if each portlet outputs a specific XML dialect/namespace, it's very difficult
to write an engine that transfoms all these dialects into the target type
without a complete foreknowledge of the supported XML dialects.
- if each portlet outputs a standard media independent, layout oriented XML
dialect (FO anybody ?) you can actually post-process the output correctly
but you need to carefully select your intermediate layout language so that
it's not to complex/costly to transform.
Also Velcoity is definitely an "open" format since its specification is
publicly available and anybody can write an alternate implementation.
It's just not recognized by an industry committe yet. But then if it fits
your need better, who cares ?
> norsch
>
> Norman Schoneich
>
> -----Ursprungliche Nachricht-----
> Von: Paul Spencer [mailto:paul@mikon.com]
> Gesendet: Donnerstag, 18. Oktober 2001 16:25
> An: jetspeed-dev@jakarta.apache.org
> Betreff: Re: Jetspeed URL redirection question
>
>
> Ajan,
> You will not find the files, because they do not exist. Jetspeed
> interprets the URL and determines what need to be returned to the
> browser. I suggest you review Jetspeed's web site,
> http://jakarta.apache.org/jetspeed
>
> Paul Spencer
>
> Ajan Balakrishnan wrote:
>
>>>I'm a newbie to jetspeed. My question is when the jetspeed shows it
>>>homepage the url shown is
>>>http://localhost:8080/jetspeed/portal/screen/Home or when i click the
>>>customize link it invokes
>>>http://localhost:8080/jetspeed/portal/screen/Customize url. Could
>>>anybody please tell me where these files are loadecated inside jetspeed
>>>directories or is it an alias name to some other directories.
>>>
>>>Thanks for the help in advance
>>>Ajan
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>
--
--
Raphael Luta - raphael.luta@networks.groupvu.com
Vivendi Universal Networks - Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Velocity / JSP / XML & XSLT : Why ???
Posted by David Sean Taylor <da...@bluesunrise.com>.
>
> What's about an XML & XSLT based approach ? Is it possible (or better) to
> render the portlets by the different controllers and then render the
result
> with an XSLT file (the portlets use themself xml/xsl, which i use). I like
> this approach the most, because it' s based on open standards unlike
> velocity.
>
Try looking at Kevin Burton's new project. What you are describing sounds a
lot like reptile
http://reptile.openprivacy.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Velocity / JSP / XML & XSLT : Why ???
Posted by Paul Spencer <pa...@mikon.com>.
Norman Schoneich wrote:
>
> Jetspeed supports different template engines.
> But in the moment, the default template layout engine is velocity and it'is
> the most supported engine by the jetspeed developers.
> The previous default engine was jsp, but the support (or development
> process) of the jsp layout seems to be stopped.
This is not true. You can use JSP for layout. Only the default changed
from JSP
to Velocity.
> I can understand that some people prefer velocity. But every layout engine
> has it's own advantages and disadvanteges. I think Jetspeed
> has to support multiple layout engines, but they must be handled equally.
JSP and Velocity are equally supported.
>
> What's about an XML & XSLT based approach ? Is it possible (or better) to
> render the portlets by the different controllers and then render the result
> with an XSLT file (the portlets use themself xml/xsl, which i use). I like
> this approach the most, because it' s based on open standards unlike
> velocity.
>
Currently it is the portlets job to produce HTML. Although XML and XSL
are defined by
standards, thoes standards do not define how a tag is rendered.
> norsch
>
> Norman Schoneich
>
Paul Spencer
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Velocity / JSP / XML & XSLT : Why ???
Posted by Norman Schoneich <sc...@ecooperate.de>.
Jetspeed supports different template engines.
But in the moment, the default template layout engine is velocity and it'is
the most supported engine by the jetspeed developers.
The previous default engine was jsp, but the support (or development
process) of the jsp layout seems to be stopped.
I can understand that some people prefer velocity. But every layout engine
has it's own advantages and disadvanteges. I think Jetspeed
has to support multiple layout engines, but they must be handled equally.
What's about an XML & XSLT based approach ? Is it possible (or better) to
render the portlets by the different controllers and then render the result
with an XSLT file (the portlets use themself xml/xsl, which i use). I like
this approach the most, because it' s based on open standards unlike
velocity.
norsch
Norman Schoneich
-----Ursprungliche Nachricht-----
Von: Paul Spencer [mailto:paul@mikon.com]
Gesendet: Donnerstag, 18. Oktober 2001 16:25
An: jetspeed-dev@jakarta.apache.org
Betreff: Re: Jetspeed URL redirection question
Ajan,
You will not find the files, because they do not exist. Jetspeed
interprets the URL and determines what need to be returned to the
browser. I suggest you review Jetspeed's web site,
http://jakarta.apache.org/jetspeed
Paul Spencer
Ajan Balakrishnan wrote:
>
> > I'm a newbie to jetspeed. My question is when the jetspeed shows it
> > homepage the url shown is
> > http://localhost:8080/jetspeed/portal/screen/Home or when i click the
> > customize link it invokes
> > http://localhost:8080/jetspeed/portal/screen/Customize url. Could
> > anybody please tell me where these files are loadecated inside jetspeed
> > directories or is it an alias name to some other directories.
> >
> > Thanks for the help in advance
> > Ajan
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Jetspeed URL redirection question
Posted by Paul Spencer <pa...@mikon.com>.
Ajan,
You will not find the files, because they do not exist. Jetspeed
interprets the URL and determines what need to be returned to the
browser. I suggest you review Jetspeed's web site,
http://jakarta.apache.org/jetspeed
Paul Spencer
Ajan Balakrishnan wrote:
>
> > I'm a newbie to jetspeed. My question is when the jetspeed shows it
> > homepage the url shown is
> > http://localhost:8080/jetspeed/portal/screen/Home or when i click the
> > customize link it invokes
> > http://localhost:8080/jetspeed/portal/screen/Customize url. Could
> > anybody please tell me where these files are loadecated inside jetspeed
> > directories or is it an alias name to some other directories.
> >
> > Thanks for the help in advance
> > Ajan
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org