You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by mad7777 <ma...@runbox.com> on 2008/12/06 13:51:38 UTC
PageRenderSupport deprecated?
Hi again,
I recently upgraded an app from 5.0.11 to 5.0.17, and now it can no longer
find PageRenderSupport, which I was using to inject some javascript, like
this:
@Inject
@Path("scripts/injected.js")
private Asset injectedJsAsset;
@Inject
private PageRenderSupport pageRenderSupport;
void setupRender() {
pageRenderSupport.addScriptLink(injectedJsAsset);
}
This no longer compiles in 5.0.17, due to the fact that PageRenderSupport
seems to have disappeared.
What is the proper way to do this now?
Thanks in advance,
Marc
--
View this message in context: http://www.nabble.com/PageRenderSupport-deprecated--tp20869794p20869794.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: Beaneditform example with ManyToMany ManyToOne
Posted by Alejandro Scandroli <al...@gmail.com>.
Hi Toby
> Is there an example of using the Beaneditform for ManyToMany and ManyToOne associations?
> Is there a more simple solution with less code then what is described in "Adding New Property Editors" ?
>
Check Trails's main trunk. Check the "Recipe" example. It's still a
work in progress but you can see editors for ManyToMany and ManyToOne
in action.
> In theory there could be a Beaneditform that would automatically add all associated entities?
> Or what is the reason why associated objects are currently ignored?
>
I think that the main reason is that you'd need to process more
metadata than the metadata processed for "simple" properties, and that
that metadata is not fully available through annotations.
Even if it were available, is too much metadata to process it on the
fly (IMMO), so you would need to process it on bootstrap time and save
the processed info in custom "holders" to query them later.
Does it sounds familiar?
> Thanks!
>
> Toby
>
Saludos.
Alejandro.
--
Alejandro Scandroli - http://weblog.amneris.es/
Amneris: We build process-driven web applications.
http://www.amneris.es
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Cyclic relationships in Beaneditform
Posted by su...@gmx.de.
Would Beaneditform in combination with AppPropertyEditBlocks support cyclic relationships such as this one here:
public class Category
{
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Integer id;
private String name;
private Category parent;
...
}
?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Beaneditform example with ManyToMany ManyToOne
Posted by su...@gmx.de.
Is there an example of using the Beaneditform for ManyToMany and ManyToOne associations?
Is there a more simple solution with less code then what is described in "Adding New Property Editors" ?
In theory there could be a Beaneditform that would automatically add all associated entities?
Or what is the reason why associated objects are currently ignored?
Thanks!
Toby
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: PageRenderSupport deprecated?
Posted by Howard Lewis Ship <hl...@gmail.com>.
You could try reading the very detailed upgrade notes before spamming the list.
On Sat, Dec 6, 2008 at 4:56 AM, Martijn Brinkers <ma...@gmail.com> wrote:
> I think it has been renamed to RenderSupport
>
> Martijn Brinkers
>
> On Sat, 2008-12-06 at 04:51 -0800, mad7777 wrote:
>> Hi again,
>>
>> I recently upgraded an app from 5.0.11 to 5.0.17, and now it can no longer
>> find PageRenderSupport, which I was using to inject some javascript, like
>> this:
>>
>> @Inject
>> @Path("scripts/injected.js")
>> private Asset injectedJsAsset;
>>
>> @Inject
>> private PageRenderSupport pageRenderSupport;
>>
>> void setupRender() {
>> pageRenderSupport.addScriptLink(injectedJsAsset);
>> }
>>
>> This no longer compiles in 5.0.17, due to the fact that PageRenderSupport
>> seems to have disappeared.
>>
>> What is the proper way to do this now?
>>
>> Thanks in advance,
>> Marc
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: PageRenderSupport deprecated?
Posted by Martijn Brinkers <ma...@gmail.com>.
I think it has been renamed to RenderSupport
Martijn Brinkers
On Sat, 2008-12-06 at 04:51 -0800, mad7777 wrote:
> Hi again,
>
> I recently upgraded an app from 5.0.11 to 5.0.17, and now it can no longer
> find PageRenderSupport, which I was using to inject some javascript, like
> this:
>
> @Inject
> @Path("scripts/injected.js")
> private Asset injectedJsAsset;
>
> @Inject
> private PageRenderSupport pageRenderSupport;
>
> void setupRender() {
> pageRenderSupport.addScriptLink(injectedJsAsset);
> }
>
> This no longer compiles in 5.0.17, due to the fact that PageRenderSupport
> seems to have disappeared.
>
> What is the proper way to do this now?
>
> Thanks in advance,
> Marc
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org