Re: [Hypercontent-users] JSTL import
Brought to you by:
alexvigdor
Menu
▾
▴
Re: [Hypercontent-users] JSTL import
|
From: Alex V. <al...@bi...> - 2007-09-06 13:33:26
|
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
> > impact on publishing performance.
> >
> > Alex
> >
> > On Sep 4, 2007, at 9:49 PM, tom tom wrote:
> >
> > > Hi Alex,
> > >
> > > I do not want to publish/process contents
> > > unnecessarily, I would like to create a seperate
> > > project for this, it makes sense as well because
> > it is
> > > only for business text.
> > >
> > > But let me know the following
> > >
> > > Is your xsls written for portlet samples strip off
> > the
> > > contents,
> > >
> > > How can we have the styles incooperated within the
> > HC
> > > so that while editing they can see the effect.
> > > Where should I incooperate my Styles within HC.
> > > Currently I did put my styles in the common.xsl,
> > but
> > > currently I did not want to strip off those while
> > > publising or building.
> > >
> > >
> > > Thanks,
> > >
> > >
> > > --- Alex Vigdor <al...@bi...> wrote:
> > >
> > >> Hi,
> > >> I see two approaches - using HC you could set up
> > a
> > >> separate output
> > >> with just the markup you want; put the one with
> > >> styles first so it
> > >> will be the default preview output, but import
> > the
> > >> stripped down
> > >> markup output into the JSTL. If you set up your
> > xsl
> > >> templates
> > >> appropriately you can reuse as much of the body
> > >> formatting you want
> > >> to retain for the import. The only side effect
> > is
> > >> that both versions
> > >> would be published, though you only need one. The
> > >> alternative would
> > >> be to use another taglib to transform the output
> > >> within the JSP, e.g.
> > >>
> > >>
> > >
> >
> http://jakarta.apache.org/taglibs/doc/regexp-doc/intro.html
> > >>
> > >> Alex
> > >>
> > >> On Sep 4, 2007, at 2:42 AM, tom tom wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> We finish one lot of work, which is static text,
> > >> we
> > >>> had a staging area and used uPortal CWebProxy,
> > it
> > >>> worked perfectly.
> > >>>
> > >>>
> > >>> We got some business text within our jsp pages,
> > we
> > >>> want to take those out and consider as jstl
> > >> c:import,
> > >>> so that business users can edit similar to the
> > >> static
> > >>> file approach we did. This also should get
> > >> published
> > >>> to a staging area.
> > >>>
> > >>> In the previous approach we had the CSS styles
> > in
> > >> the
> > >>> published contents but with no issue, reason is
> > >>> CWebProxy filter those out without any problem.
> > >>>
> > >>> for JSTL import, how can we see the effect of
> > >> styles
> > >>> within HC and take those out (infact require the
> > >>> contents of the body tag). Is there any already
> > >>> written xsl which serves this purpose, The key
> > >> thing
> > >>> is users should be able to see the effect of
> > >> styles
> > >>> within the HC and moment we build or publish it
> > >> should
> > >>> take off the styles from the tranformed content
> > >> and
> > >>> should publish to a staging area.
> > >>>
> > >>>
> > >>>
> > >>> Thanks
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >
> >
> ______________________________________________________________________
> > >>
> > >>> ______________
> > >>> Shape Yahoo! in your own image. Join our
> > Network
> > >> Research Panel
> > >>> today!
> > >>
> > >
> >
> http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
> > >>>
> > >>>
> > >>
> > >>
> > >>
> > >
> >
> ----------------------------------------------------------------------
> >
> > > ---
> > >> 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
> > >>
> > >
> > >
> > >
> > >
> > >
> >
> ______________________________________________________________________
> >
> > > ______________
> > > Shape Yahoo! in your own image. Join our Network
> > Research Panel
> > > today!
> >
> http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
> > >
> > >
> >
> >
> >
> ----------------------------------------------------------------------
> ---
> > This SF.net email is sponsored by: Splunk Inc.
> >
> === message truncated ===
>
>
>
>
> ______________________________________________________________________
> ______________
> Sick sense of humor? Visit Yahoo! TV's
> Comedy with an Edge to see what's on, when.
> http://tv.yahoo.com/collections/222
>
> ----------------------------------------------------------------------
> ---
> 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
>
>
>
>
> **********************************************************************
> *******************
> To view the terms under which this email is distributed, please go
> to http://www.hull.ac.uk/legal/email_disclaimer.html
> **********************************************************************
> *******************---------------------------------------------------
> ----------------------
> 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
|
