hypercontent-users

[Hypercontent-users] Editor stripping tags

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

[Hypercontent-users] Important code update improves long-term HC maintenance

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

Hi everyone,
	I have just checked a change into CVS that should remove a long-term  
HC server maintenance issue that everyone seems to run across  
periodically - that is a piling up of stale files in the bootstrap  
directory ".server-public-keys" which can lead to a general slow-down  
of most operations.

Please patch your servers with this update from CVS at your earliest  
convenience: the updated code is in the class

org.hypercontent.server.SecureStore

I would encourage you, of course, to deploy the update in a test  
environment first to make sure there are no unintended consequences!   
Especially make sure to test FTP/SFTP publishing that prompts the  
user for a username/password.  Should you discover any issues, please  
let me know.  I observed no problems in my own environment.

Note: this is NOT an urgent fix, but it is an important one for your  
long term stability and happiness!

-Alex


FAQ:

What is .server-public-keys?
	This directory is used to store encrypted flat-file databases that  
can be used to share data securely between active instances of  
HyperContent.  For example, if you have 2 or more HC instances  
running and start a publish job to an FTP server, the public key file  
is used to encrypt the FTP password into the instance secure DB so  
each instance has access to the password without leaving it  
vulnerable to discovery.  Each running HC instance holds the private  
key that can decrypt the password in memory, and a new key pair is  
created upon each restart.
	Even if you are running only a single instance, these files are  
still loaded and used, so don't think you'll be immune to the problem!

What causes the files to pile up here?
	During a normal shutdown, an instance of HC will delete its own  
public key and DB files from this directory.  However, if for any  
reason the shutdown is not graceful (e.g. kill -9, hard crash, etc),  
the files are left behind.  Over the course of 6 months to a year  
enough of these might accumulate to slow things down.

What is the solution?
	Until now, the only solution was to periodically manually check  
the .server-public-keys directory and remove any obviously stale  
files.  The new, automatic solution to this problem is for each  
instance to register a heartbeat by updating the last mod date of its  
public key every 5 minutes - if another instance detects that a key  
file has not been touched in 10 minutes, it will delete that key file  
and its associated db.  Thus HC is now self-maintaining in this  
regard.  In the unlikely event that an instance is still running but  
fails to update the last mod in time (e.g. if it temporarily loses  
network or SAN connectivity), and its key and DB are deleted by  
another instance, it will create itself a new key pair and db when it  
goes to register its heartbeat.

Re: [Hypercontent-users] Strip text from content on render

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

Carl,

You might try using a mode to avoid the overlapping scope of those  
attribute templates, e.g.

  <xsl:apply-templates select="/cms:wrapper/cms:source/page/bodytext/ 
@title" mode="title"/>

and wherever you declare the template

<xsl:template match="@title" mode="title">

Or if you're only stripping border="0" out of elements from a WYSIWYG  
editor, you could try adding a mode to Adam's template

  <xsl:template match="@*" mode="html">
         <!--Copy attribute if it's not border-->
         <xsl:if test="name() != 'border'">
         <xsl:copy />
             </xsl:if>
     </xsl:template>

I'm not sure if that will work with your XSL, though, depends if  
you're using the same boilerplate templates I'm used to!

Alex

On Sep 13, 2007, at 11:34 AM, Carl P Barrow wrote:

> Adam,
>
> The did work, but it stopped the bellow working, not sure why. Any  
> ideas?
>
>     <xsl:template name="bodytitle">
>         <xsl:apply-templates select="/cms:wrapper/cms:source/page/ 
> bodytext/@title"/>
>     </xsl:template>
>
>
> <xsl:choose>
>      <xsl:when test="($sourceItem/@location='/index.xml')"></xsl:when>
>            <xsl:otherwise>
>               <h1>
>                 <xsl:call-template name="bodytitle"/>
>               </h1>
>             </xsl:otherwise>
> </xsl:choose>
>
> Thanks
> Carl
>
> *************************************
>
> Carl Barrow
> Systems Integrator
> e-Services
> The University of Hull
> Cottingham Road
> Hull
> HU6 7RX
> Ext. 6838
>
> *************************************
>
>
>
>
> -----Original Message-----
> From: Adam Carl [mailto:ac...@co...]
> Sent: Thu 9/13/2007 14:51
> To: Carl P Barrow; hyp...@li...
> Subject: Re: [Hypercontent-users] Strip text from content on render
>
> Carl,
>
> Something like this should ignore any border attributes.
>
>  <xsl:template match="@*">
>         <!--Copy attribute if it's not border-->
>         <xsl:if test="name() != 'border'">
>         <xsl:copy />
>             </xsl:if>
>     </xsl:template>
>
> Adam
>
>
> On 9/13/07 7:25 AM, "Carl P Barrow" <C.P...@hu...> wrote:
>
> > All,
> >
> > Does anyone know of a good/easy way to strip out certain text  
> from the content
> > on render. They want to strip out all instances of border=0 from  
> the content,
> > which can't be done in reality but I thought it might be possible  
> in XSL.
> >
> > Cheers
> > Carl
> >
> > *************************************
> >
> > Carl Barrow
> > Systems Integrator
> > e-Services
> > The University of Hull
> > Cottingham Road
> > Hull
> > HU6 7RX
> > Ext. 6838
> >
> > *************************************
> >
> >
> >
> >
> >  
> ********************************************************************** 
> ********
> > ***********
> > 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: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio 2005.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> >
> > _______________________________________________
> > 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: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ 
> _______________________________________________
> Hypercontent-users mailing list
> Hyp...@li...
> https://lists.sourceforge.net/lists/listinfo/hypercontent-users

Re: [Hypercontent-users] Resolving conflicting permissions inherited from groups

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

Hi,
	The only factor in resolving conflicting but equally specific  
permissions applied to different ancestor groups of a user is depth.   
If the user belongs directly to group A, and also belongs to group C  
that is a subgroup of group B, a permission applied to group A takes  
precedence over one applied to group B for that user because the  
depth of the user from A is less than from B.  If you have  
conflicting permissions on A and C, however, the result is arbitrary,  
as the user is at equal depth from each -  I believe the first  
permission declared in permissions.xml may end up taking precedence,  
but I wouldn't guarantee it!
	So if you want the permissions applied to group:approvers to take  
precedence, create a subgroup of group:authors, e.g. "group:casual- 
authors", and move the user there from group:authors.  This weakens  
the association between the user and the group:authors by increasing  
depth.  The inverse holds true - if you want group:author permissions  
to take precedence for that user, you would place them in subgroup of  
group:approvers, e.g. "group:casual-approvers".
	Keep in mind that group depth is only evaluated after the  
permissions with the most specific targets have been selected, so a  
permission on "/config/**/*.*" always takes precedence over a  
permission on "/**/*.*" regardless of the depth of the user in  
relation to the groups to which those permissions are applied.

Alex

On Sep 10, 2007, at 9:25 PM, tom tom wrote:

> Hi Alex,
>
> How the permissions get overidden, for e.g.
>
> If I give persmission to build as an 'Author' and deny
> the permissions to build as an 'Approver' and if
> someone is a author and approver, what will happen,
> will the author permissions get overidden by approver
> rights.
>
> Can you explain, how does this permission model works
> with respect to the groups
>
>
> Thanks
>
>
>
>
> --- Alex Vigdor <al...@bi...> wrote:
>
>> The permissions approach should work - it works for
>> me!  Make sure to
>> test as a user who is not in group:admin and also
>> not in the
>> publisher group.
>>
>> Alex
>>
>> On Sep 3, 2007, at 8:03 PM, tom tom wrote:
>>
>>> Hi,
>>>
>>> If there is a business requirement to remove the
>> build
>>> and build All links from the workflow screen for
>>> approvers what is the best way to do, I thought we
>> can
>>> do it via permissions.xml as follows but it still
>>> shows the links, is there any declarative way to
>> do
>>> this?
>>>
>>> <permission activity="build" denied="true"
>>> principal="group:approvers" target="/**/"/>
>>> <permission activity="build" denied="true"
>>> principal="group:approvers" target="/**/*.*"/>
>>>
>>> Thanks,
>>>
>>>
>>>
>>>
>>
> ______________________________________________________________________
>>
>>> ______________
>>> Moody friends. Drama queens. Your life? Nope! -
>> their life, your
>>> story. Play Sims Stories at Yahoo! Games.
>>> http://sims.yahoo.com/
>>>
>>
>>
>>
> ---------------------------------------------------------------------- 
> ---
>> 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
>>
>
>
>
>
> ______________________________________________________________________ 
> ______________
> Need a vacation? Get great deals
> to amazing places on Yahoo! Travel.
> http://travel.yahoo.com/
>

Re: [Hypercontent-users] Strip text from content on render

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

Re: [Hypercontent-users] How to use vcard editor xith HC2 ?

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

See this page for some background:

http://hypercontent.sourceforge.net/docs/manual/develop/vcard.html

Since VCard info is stored as metadata, you can enable the VCard  
editor for any xml-doc, xml-doctype or resource-directory by  
configuring custom editors

http://hypercontent.sourceforge.net/docs/manual/develop/editors.html

e.g.

<xml-doctype ...
	<editor key="vcard"/>
	<editor key="xml"/>
	<editor key="spellcheck"/>

-Alex


On Sep 13, 2007, at 10:51 AM, Jose H. REMY wrote:

> Hi,
>
> How to use vcard editor xith HC2 ?
>
> Jose H. REMY
> ---------------------
> BP 46 - 74200 THONON FRANCE
>
>
>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Hypercontent-users mailing list
> Hyp...@li...
> https://lists.sourceforge.net/lists/listinfo/hypercontent-users
>

[Hypercontent-users] How to use vcard editor xith HC2 ?

[Jose H. R. <Jos...@SE...>]

Hi,

How to use vcard editor xith HC2 ?

Jose H. REMY
---------------------
BP 46 - 74200 THONON FRANCE

Re: [Hypercontent-users] Strip text from content on render

[Adam C. <ac...@co...>]

Carl,

Something like this should ignore any border attributes.

 <xsl:template match="@*">
        <!--Copy attribute if it's not border-->
        <xsl:if test="name() != 'border'">
        <xsl:copy />
            </xsl:if>
    </xsl:template>

Adam


On 9/13/07 7:25 AM, "Carl P Barrow" <C.P...@hu...> wrote:

> All,
> 
> Does anyone know of a good/easy way to strip out certain text from the content
> on render. They want to strip out all instances of border=0 from the content,
> which can't be done in reality but I thought it might be possible in XSL.
> 
> Cheers
> Carl
> 
> *************************************
> 
> Carl Barrow
> Systems Integrator
> e-Services
> The University of Hull
> Cottingham Road
> Hull
> HU6 7RX
> Ext. 6838
> 
> *************************************
> 
> 
> 
> 
> ******************************************************************************
> ***********
> 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: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> _______________________________________________
> Hypercontent-users mailing list
> Hyp...@li...
> https://lists.sourceforge.net/lists/listinfo/hypercontent-users

[Hypercontent-users] Strip text from content on render

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

Re: [Hypercontent-users] XHMTL Output

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

Re: [Hypercontent-users] XHMTL Output

[Adam C. <ac...@co...>]

Something like this should work.

<xsl:output method="html"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN" indent="no"/>

Adam



On 9/12/07 11:27 AM, "Carl P Barrow" <C.P...@hu...> wrote:

> Hi Alex,
> 
> I am outputting XHTML
> 
> <xsl:output method="xhtml" indent="no" doctype-public="-//W3C//DTD XHTML 1.0
> Transitional//EN"
>         
> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"/>
> 
> This seems to be XHTML strict.  Which is having problems in some browsers
> since it isn't fully supported. Is there a way that I can transform as XHTML
> transitional?
> 
> For example <a name="a"></a>  in the content is transformed at <a name="a"/>
> which is IE 7 courses problems.
> 
> Cheers
> Carl
> 
> *************************************
> 
> Carl Barrow
> Systems Integrator
> e-Services
> The University of Hull
> Cottingham Road
> Hull
> HU6 7RX
> Ext. 6838
> 
> *************************************
> 
> 
> 
> 
> ******************************************************************************
> ***********
> 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: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> _______________________________________________
> Hypercontent-users mailing list
> Hyp...@li...
> https://lists.sourceforge.net/lists/listinfo/hypercontent-users

[Hypercontent-users] XHMTL Output

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

[Hypercontent-users] xmlns=" "

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

Re: [Hypercontent-users] Remove build link

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

Hi Alex,

How the permissions get overidden, for e.g.

If I give persmission to build as an 'Author' and deny
the permissions to build as an 'Approver' and if
someone is a author and approver, what will happen,
will the author permissions get overidden by approver
rights.

Can you explain, how does this permission model works
with respect to the groups


Thanks




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

> The permissions approach should work - it works for
> me!  Make sure to  
> test as a user who is not in group:admin and also
> not in the  
> publisher group.
> 
> Alex
> 
> On Sep 3, 2007, at 8:03 PM, tom tom wrote:
> 
> > Hi,
> >
> > If there is a business requirement to remove the
> build
> > and build All links from the workflow screen for
> > approvers what is the best way to do, I thought we
> can
> > do it via permissions.xml as follows but it still
> > shows the links, is there any declarative way to
> do
> > this?
> >
> > <permission activity="build" denied="true"
> > principal="group:approvers" target="/**/"/>
> > <permission activity="build" denied="true"
> > principal="group:approvers" target="/**/*.*"/>
> >
> > Thanks,
> >
> >
> >
> >
>
______________________________________________________________________
> 
> > ______________
> > Moody friends. Drama queens. Your life? Nope! -
> their life, your  
> > story. Play Sims Stories at Yahoo! Games.
> > http://sims.yahoo.com/
> >
> 
> 
>
-------------------------------------------------------------------------
> 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
> 



       
____________________________________________________________________________________
Need a vacation? Get great deals
to amazing places on Yahoo! Travel.
http://travel.yahoo.com/

Re: [Hypercontent-users] JSTL import

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

Thanks,

I will proceed on that,


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

> That should work fine!  HC is very optimized for
> producing multiple  
> outputs - the page XML is only parsed once, for
> example, for both  
> transformations.  So you should not see any
> noticeable performance  
> impact.
> 
> Alex
> 
> On Sep 6, 2007, at 10:46 PM, tom tom wrote:
> 
> > 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.
> 
=== message truncated ===



      ____________________________________________________________________________________
Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/ 

[Hypercontent-users] non XHTML Output

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

Re: [Hypercontent-users] JSTL import

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

That should work fine!  HC is very optimized for producing multiple  
outputs - the page XML is only parsed once, for example, for both  
transformations.  So you should not see any noticeable performance  
impact.

Alex

On Sep 6, 2007, at 10:46 PM, tom tom wrote:

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

Re: [Hypercontent-users] JSTL import

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

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

Re: [Hypercontent-users] JSTL import

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

Re: [Hypercontent-users] JSTL import

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

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

Re: [Hypercontent-users] JSTL import

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

Re: [Hypercontent-users] JSTL import

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

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

Re: [Hypercontent-users] JSTL import

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

Re: [Hypercontent-users] Displaying list

[Carl P B. <C.P...@hu...>]

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************