You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Ron <mp...@vollbio.de> on 2005/03/02 13:09:58 UTC
accessing component private asset
In my .jwc I have:
<private-asset name="js" resource-path="script.js"/>
in my components class, I access the asset:
IAsset script = getAsset("js");
but I get null.
The script.js is on the same directory as the .jwc inside a library on
the classpath.
How do I access the private asset?
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How the tapestry specific tags like are interpreted by the browser
Posted by Ryan Owens <ry...@infoether.com>.
> *The Browser gets to see them only when your web-designer is working on
> yout page.*
>
> so at that time did the browser ignores those things ??
Those things never get to the browser. The Tapestry servlet processes
the .html files as templates, and returns html to the browser with no
jwcid attributes.
Each Tapestry components is rendered differently so consult the
Component docs for more on them individually.
Hope that helps,
Ryan Owens
>
> ----- Original Message ----- From: "ron" <ro...@gmx.net>
> To: "Tapestry users" <ta...@jakarta.apache.org>
> Sent: Wednesday, March 02, 2005 6:15 PM
> Subject: Re: How the tapestry specific tags like <jwcid> are
> interpreted by the browser
>
>
>> ציטוט Siva VP:
>>
>>> hi
>>>
>>> How the tapestry specific tags like <jwcid> are interpreted by the
>>> browser
>>
>> jwcid is an attribute and not a tag
>>
>>>
>>> did browsers understand those tags ?? surely no i think
>>
>> The Browser gets to see them only when your web-designer is working
>> on yout page.
>>
>>>
>>> then what is the mechanism behind that how they are interpreted
>>
>> Tapestry interprets thos Tags on the server side and replaces them
>> *before* sending the page to the client's browser.
>>
>>>
>>> Thanks & Regards,
>>> Siva,
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:
>>> tapestry-user-help@jakarta.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How the tapestry specific tags like are interpreted by
the browser
Posted by ron <ro...@gmx.net>.
ציטוט Siva VP:
> Thank u for your reply
>
> *The Browser gets to see them only when your web-designer is working on
> yout page.*
>
> so at that time did the browser ignores those things ??
Yes, thats (only) one of Tapestry advanteges, the browser ignores them.
You can really design the pages and use them as Templates in the same time.
>
> ----- Original Message ----- From: "ron" <ro...@gmx.net>
> To: "Tapestry users" <ta...@jakarta.apache.org>
> Sent: Wednesday, March 02, 2005 6:15 PM
> Subject: Re: How the tapestry specific tags like <jwcid> are
> interpreted by the browser
>
>
>> ציטוט Siva VP:
>>
>>> hi
>>>
>>> How the tapestry specific tags like <jwcid> are interpreted by the
>>> browser
>>
>>
>> jwcid is an attribute and not a tag
>>
>>>
>>> did browsers understand those tags ?? surely no i think
>>
>>
>> The Browser gets to see them only when your web-designer is working
>> on yout page.
>>
>>>
>>> then what is the mechanism behind that how they are interpreted
>>
>>
>> Tapestry interprets thos Tags on the server side and replaces them
>> *before* sending the page to the client's browser.
>>
>>>
>>> Thanks & Regards,
>>> Siva,
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How the tapestry specific tags like are interpreted by the browser
Posted by Siva VP <si...@synergy-infotech.com>.
Thank u for your reply
*The Browser gets to see them only when your web-designer is working on
yout page.*
so at that time did the browser ignores those things ??
----- Original Message -----
From: "ron" <ro...@gmx.net>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Wednesday, March 02, 2005 6:15 PM
Subject: Re: How the tapestry specific tags like <jwcid> are interpreted by
the browser
> ציטוט Siva VP:
>
>> hi
>>
>> How the tapestry specific tags like <jwcid> are interpreted by the
>> browser
>
> jwcid is an attribute and not a tag
>
>>
>> did browsers understand those tags ?? surely no i think
>
> The Browser gets to see them only when your web-designer is working on
> yout page.
>
>>
>> then what is the mechanism behind that how they are interpreted
>
> Tapestry interprets thos Tags on the server side and replaces them
> *before* sending the page to the client's browser.
>
>>
>> Thanks & Regards,
>> Siva,
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How the tapestry specific tags like are interpreted by
the browser
Posted by ron <ro...@gmx.net>.
ציטוט Siva VP:
> hi
>
> How the tapestry specific tags like <jwcid> are interpreted by the browser
jwcid is an attribute and not a tag
>
> did browsers understand those tags ?? surely no i think
The Browser gets to see them only when your web-designer is working on
yout page.
>
> then what is the mechanism behind that how they are interpreted
Tapestry interprets thos Tags on the server side and replaces them
*before* sending the page to the client's browser.
>
> Thanks & Regards,
> Siva,
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How the tapestry specific tags like are interpreted by the browser
Posted by Sunil <su...@hotmail.com>.
Tapestry is a framework built on java servlet API. Browser definately dont
understand those tags.
Whne u try to access the page of a deployed application of the browser for
example if u want to access
home page u will say something like ..
http://localhost:8080/demo/app?service=page/Home
so ur servelet will handle this request and get the .page file for this page
and instantiate the class specified
after that it will start rendering the html and send the response. At the
time of rendering it will replace all
tags havin jwcid tag with some dynamik stuff.
i suggest u to go thru this beutiful presentation.
http://www.ociweb.com/javasig/knowledgebase/2004-12/TapestryPresentation.pdf
this is very useful for those who are new to tapestry.
Sunil
----- Original Message -----
From: "Siva VP" <si...@synergy-infotech.com>
To: "Tapestry users" <ta...@jakarta.apache.org>
Sent: Wednesday, March 02, 2005 6:01 PM
Subject: How the tapestry specific tags like <jwcid> are interpreted by the
browser
> hi
>
> How the tapestry specific tags like <jwcid> are interpreted by the browser
>
> did browsers understand those tags ?? surely no i think
>
> then what is the mechanism behind that how they are interpreted
>
> Thanks & Regards,
> Siva,
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How the tapestry specific tags like are interpreted by
the browser
Posted by "t.n.a." <tn...@sharanet.org>.
Siva VP wrote:
> hi
>
> How the tapestry specific tags like <jwcid> are interpreted by the
> browser
>
> did browsers understand those tags ?? surely no i think
>
> then what is the mechanism behind that how they are interpreted
As far as I know, the .html files containing elements with "jwcid"
parameters are just templates i.e. tapestry uses them to generate DHTML
which, as you can see for yourself, contains no jwcid parameters.
During the design phase, the templates can be viewed in a browser and
the browser ignores the jwcid parameters.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: How the tapestry specific tags like are interpreted by the browser
Posted by Markus Eberle <ma...@tngtech.com>.
Hi,
there is no tag "jwcid". It is an attribute. Most browser ignore
unknown/non-html attributes when rendering a page.
These Tapestry attributes are interpreted on the server-side.
Cheers,
Markus
> hi
>
> How the tapestry specific tags like <jwcid> are interpreted by the browser
>
> did browsers understand those tags ?? surely no i think
>
> then what is the mechanism behind that how they are interpreted
>
> Thanks & Regards,
> Siva,
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
How the tapestry specific tags like are interpreted by the browser
Posted by Siva VP <si...@synergy-infotech.com>.
hi
How the tapestry specific tags like <jwcid> are interpreted by the browser
did browsers understand those tags ?? surely no i think
then what is the mechanism behind that how they are interpreted
Thanks & Regards,
Siva,
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: accessing component private asset
Posted by ron <ro...@gmx.net>.
OK - The NullPointerException is coming from the body reference and not
from the Asset, which is actually being referenced...
Sorry...
ציטוט Ron:
> In my .jwc I have:
> <private-asset name="js" resource-path="script.js"/>
>
> in my components class, I access the asset:
>
> IAsset script = getAsset("js");
>
> but I get null.
>
> The script.js is on the same directory as the .jwc inside a library on
> the classpath.
>
> How do I access the private asset?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org