cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frans Thamura <j...@intercitra.com>
Subject Re: [CimandeUpgrade] strange xsp:attribute handling -> ?????
Date Mon, 21 Apr 2003 13:27:41 GMT
yah smiliar. thanks, so i have to wait for the patch..

mm keep working with this, hopefully i can finish it, the new, and search is finish.. and
next step is result, and drop table, and generate table.. 

I love if my script run on top of Cocoon 2, and hopefully the cocoon 2 is stable enough to
handle my script. several time crash in cocoon 1.. 

Thanks Jeorg

Frans



At 01:31 PM 4/21/2003 +0200, you wrote:
>Hello Frans,
>
>there is a bug known about xsp:attribute (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15841).
Does it apply to your problem?
>
>Regards,
>
>Joerg
>
>Frans Thamura wrote:
>>I am upgrading my project from Cocoon 1 to Cocoon 2,
>>I have a worked xsp:logic using Cocoon 1 (run well in my client website, and production),
and in Cocoon 2, there is a *strange behavior*, if I put a new xml tag together with an xsp:attribute,
the xsp:attribute is not add an element to the tag where the position of the pointer, but
to the new tag
>>Cocoon 2, have a silly behavior. how can?
>>this is the logic:
>>*Cocoon 1, i can put the xsp:logic together.
>>*<xsl:template name="contentmanager">
>><xsl:copy><xsp:logic>
>>sGA_USER=(String)session.getAttribute("GA_USER");
>>if (sGA_USER!=null) {
>> <xsp:attribute name="session">login</xsp:attribute>
>>  <information>
>>        <statusset title="Login Session" param="Activated."/>
>></information>
>>} else { // session time out...
>><xsp:attribute name="session">logout</xsp:attribute>
>>} // END of session time out
>></xsp:logic>
>></xsl:copy>                                     
>></xsl:template>
>>*Cocoon 2, I have to split 2 xsl:logic
>>*<xsl:template name="contentmanager">
>><xsl:copy>
>><xsp:logic>
>>sGA_USER=(String)session.getAttribute("GA_USER");
>>if (sGA_USER!=null) {
>> <xsp:attribute name="session">login</xsp:attribute>
>>                                                
>>} else {
>><xsp:attribute name="session">logout</xsp:attribute>
>></xsp:logic>
>><xsp:logic>     
>>if (sGA_USER!=null) {
>><information>
>>        <statusset title="Login Session" param="Activated."/>
>></information>
>>} else { // session time out...
>>} // END of session time out
>></xsp:logic>
>></xsl:copy>                                     
>></xsl:template>
>>I cannot use Cocoon 1 step, because cocoon engine will put the session attribute in
the information tag, and put the information tag as a root. that is silly..BUGS I think?
>>if I run the Cocoon 1 step in Cocoon 2 engine there will be an out put like this
>><information session="login">
>>        <statusset title="Login Session" param="Activated."/>
>></information>
>><contentmanager >
>></contentmanager>
>>
>>but the result that I want is
>>as an attribute of contentmanager tag;
>><contentmanager session="login">
>>        <statusset title="Login Session" param="Activated."/>
>></contentmanager>
>>
>>*Comment plz..
>>
>>*Frans
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
>For additional commands, e-mail: cocoon-users-help@xml.apache.org
>

Ikutan dong ke jug-indonesia@yahoogroups.com, biar bisa diskusi Java.

Kita buat Java User Group Indonesia. 

cara subscribe, jug-indonesia-subscribe@yahoogroups.com

Topik Java Open Source .

Frans Thamura
Intercitra Innovation Center
Inspiring the Uninspired
http://www.intercitra.com

HP: +62 - 855 - 7888 - 699

Guerilla will help everyone exchange information and develop value to stakeholder.  
Mime
View raw message