Re: [Hypercontent-users] JSTL import

[Alex V. <al...@bi...>]

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
>
>