Re: [Hypercontent-users] JSTL import

[tom t. <j_l...@ya...>]

Hi Alex,

Without making it too complicated, and also not having
many rules, I decided to have the following, Pls let
me know this leads to any unnecessary performance
issues when it comes to publishing.

Basicaly one xml-doctype and having two outputs, 


<xml-doctype create="manual" definition=""
label="Page" path="/**/*.xml" root="html">

<output basedir="/nostrip/" content-type="text/html">
<transform source="/config/skins/nostrip/common.xsl">
<with-param name="link-base" value="/nostrip"/>
</transform>
</output>


<output basedir="/strip/" content-type="text/html">
<transform source="/config/skins/strip/common2.xsl">
<with-param name="link-base" value="/strip"/>
</transform>
</output>
</xml-doctype>


Thanks


--- Alex Vigdor <al...@bi...> wrote:

> Actually it is not possible to prevent an output
> from getting  
> published by omitting the basedir - it defaults to
> "/".  So I would  
> recommend something similar to what Carl is
> recommending, e.g.
> 
> <xml-doctype definition="/dtd/common.dtd"
> label="Create a new page"  
> path="/**/*.xml" root="page">
>      <output basedir="/" content-type="text/html">
>          <include data="yes" metadata="no"
> source="/sitemap.xml"/>
>          <transform
> source="/config/xsl/base-tempalte.xsl"/>
>      </output>
> </xml-doctype>
> 
> <xml-doctype definition="/dtd/common.dtd"
> label="Create a new page  
> under business" path="/business/*.xml" root="page">
>       <output basedir="/" content-type="text/html">
>          <include data="yes" metadata="no"
> source="/sitemap.xml"/>
>          <transform
> source="/config/xsl/base-tempalte.xsl"/>
>      </output>
>       <output basedir="/stripped/"
> content-type="text/html">
>          <include data="yes" metadata="no"
> source="/sitemap.xml"/>
>          <transform
> source="/config/xsl/business-template.xsl"/>
>      </output>
> </xml-doctype>
> 
> 
> On Sep 6, 2007, at 6:38 AM, Carl P Barrow wrote:
> 
> > Hi,
> >
> > If I'm off the ball here please excuse me.  Would
> something like  
> > this not work?
> >
> > <xml-doctype definition="/dtd/common.dtd"
> label="Create a new page"  
> > path="/**/*.xml" root="page">
> >     <output basedir="/" content-type="text/html">
> >         <include data="yes" metadata="no"
> source="/sitemap.xml"/>
> >         <transform
> source="/config/xsl/base-tempalte.xsl">
> >             <with-filedate as="filedate"/>
> >             <with-baseurl as="baseurl"/>
> >         </transform>
> >     </output>
> > </xml-doctype>
> >
> > <xml-doctype definition="/dtd/business.dtd"
> label="Create a new  
> > under business" path="/business/*.xml"
> root="page">
> >      <output basedir="/" content-type="text/html">
> >         <include data="yes" metadata="no"
> source="/sitemap.xml"/>
> >         <transform
> source="/config/xsl/business-template.xsl">
> >             <with-filedate as="filedate"/>
> >             <with-baseurl as="baseurl"/>
> >         </transform>
> >     </output>
> > </xml-doctype>
> >
> > The only problem I can see here is that you would
> get the stripped  
> > out view in HyperContent for business. I haven't
> tried this and  
> > Alex will probably have a view, but you might be
> able to add  
> > another out put to the business doc-type without a
> basedir so it  
> > won't actually publish it to anywhere an you will
> still get a  
> > visual view.
> >
> > <output content-type="text/html">
> >         <include data="yes" metadata="no"
> source="/sitemap.xml"/>
> >         <transform
> source="/config/xsl/base-template.xsl">
> >             <with-filedate as="filedate"/>
> >             <with-baseurl as="baseurl"/>
> >         </transform>
> > </output>
> >
> > Thanks
> > Carl
> >
> > *************************************
> >
> > Carl Barrow
> > Systems Integrator
> > e-Services
> > The University of Hull
> > Cottingham Road
> > Hull
> > HU6 7RX
> > Ext. 6838
> >
> > *************************************
> >
> >
> >
> >
> > -----Original Message-----
> > From:
> hyp...@li... on
> behalf of  
> > tom tom
> > Sent: Thu 9/6/2007 05:31
> > To: Alex Vigdor; hypercontent List
> > Subject: Re: [Hypercontent-users] JSTL import
> >
> > Hi Alex,
> >
> > With regards to publishing extra output, Cant we
> have
> > a different output works on a different path
> inside
> > same xml-doctype instead of based on one path
> > attribute. For. main path is the toplevel one but
> > others overiding them.
> >
> >
> > I can put all the business text(not the static
> > content) inside a toplevel folder called business.
> For
> > the second output(strip content) can't we only
> based
> > on the business folder, For this should I have to
> > declare an another doctype? I want to have the
> current
> > preview reflect the styles for both the content.
> >
> > If I put it in a differently, I would like
> everything
> > to be processed with styles but only business
> folder
> > contents to be published with stripping. If I can
> > achieve this am atleast saving something.
> >
> > Let me know your thoughts as well.
> >
> > Thanks,
> >
> >
> >
> >
> >
> > --- Alex Vigdor <al...@bi...> wrote:
> >
> > > Hi,
> > >       For the portlet, I wrote a special wrapper
> stage
> > > that uses regular
> > > expressions to strip certain elements and
> rewrite
> > > links.  This is why
> > > I suggested you consider using regular
> expressions
> > > within your JSP.
> > >
> > > Another possibility is you can define a "css"
> > > resource-directory with
> > > publish="false"; you can reference it as a CSS
> > > import with a relative
> > > path, so it will render while you're in HC, but
> > > won't find the CSS
> > > once published.
> > >
> > > It is not possible at this time to publish
> something
> > > that is
> > > different from what you preview; the portlet for
> > > example doesn't use
> > > static publishing at all, it uses a special
> modal
> > > template to
> > > dynamically rewrite content on demand.
> > >
> > > As for publishing extra outputs, I'm not sure
> why
> > > you would prefer a
> > > different approach - this is one of the core
> > > strengths of HC, and
> > > we're only talking about a few extra KB per
> file.
> > > Unless the pages
> > > are very expensive to render, it also should not
> > > have a significant
> 
=== message truncated ===>
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? 
> Stop.
> Now Search log events and configuration files using
> AJAX and a browser.
> Download your FREE copy of Splunk now >> 
http://get.splunk.com/>
_______________________________________________
> Hypercontent-users mailing list
> Hyp...@li...
>
https://lists.sourceforge.net/lists/listinfo/hypercontent-users
> 



       
____________________________________________________________________________________
Sick sense of humor? Visit Yahoo! TV's 
Comedy with an Edge to see what's on, when. 
http://tv.yahoo.com/collections/222