In theory, the data URL approach sounds perfect.
But in reality we'd be swapping this:
scriptalert('hello');/script
For this:
script src=data:text/javascript;charset=utf-8,alert('hello'); /
As you mentioned, it's likely that at least on browser won't support this
(I'm looking at you IE!).
Hi, I need to write a service where jobs can be added and should
executed after a given delay. After execution they are finished, so
periodical execution is not required. I prefer to user the
ScheduledExecutorService for this task.
The question is now, how do I use my @Inject objects in the
Ticking certainly, however my dreadful js tells me that whatever whacky
functions I've made can be parameterised-in-a-template to be received by a
t5 component.
Extract their name (interface like) or some other more integrated language
binding thing..
Linking them within tapestry and it sounds
It's easy to say it should be cached until you realize that the
application could be running in a cluster. At that point, you need to have
that cached data available across all servers in the cluster ... that means
you need to store it in the HttpSession, which is exactly the opposite
approach
I agree; this is an ugly hack to satisfy the arbitrary CSP requirement.
On Thu, Feb 6, 2014 at 5:20 AM, Lance Java lance.j...@googlemail.comwrote:
In theory, the data URL approach sounds perfect.
But in reality we'd be swapping this:
scriptalert('hello');/script
For this:
script
Hi, I need to write a service where jobs can be added and should
executed after a given delay. After execution they are finished, so
periodical execution is not required. I prefer to user the
ScheduledExecutorService for this task.
The question is now, how do I use my @Inject objects in the
I agree the data url sounds interesting but is not really practical for a
general purpose public site. I do think this might be interesting though
t:script cachePolicy=never require=jquery t:id=hello
alert(hello ${user});
\t:script
That becomes something like:
script
You can try anjlab-tapestry-quartz from here:
https://github.com/anjlab/anjlab-tapestry-commons/tree/master/anjlab-tapestry-quartz
On Thu, Feb 6, 2014 at 2:46 PM, Matthias matthias.eich...@uni-jena.dewrote:
Hi, I need to write a service where jobs can be added and should executed
after a
Hi, is there anyone on the list that could shed some light on the problem
I'm having?
Thanks,
Ryan
On Fri, Jan 31, 2014 at 10:41 AM, Ryan rnidef...@gmail.com wrote:
Hoping I can still get some help with Tapestry 4 on this mailing list - I
know its old but unfortunately I'm stuck with it and
On Thu, 06 Feb 2014 14:55:33 -0200, Ryan rnidef...@gmail.com wrote:
Hi, is there anyone on the list that could shed some light on the problem
I'm having?
The only hint I can give you is this: don't use the Map directly. Create a
class to represent the pairs you put into the MapString,
Thanks Dmitry, works perfect :).
On 06.02.2014 16:11, Dmitry Gusev wrote:
You can try anjlab-tapestry-quartz from here:
https://github.com/anjlab/anjlab-tapestry-commons/tree/master/anjlab-tapestry-quartz
On Thu, Feb 6, 2014 at 2:46 PM, Matthias matthias.eich...@uni-jena.dewrote:
Hi, I
hi all, how can I transform the next example from inheritance design to
composition design ?
ParentComponent.tml:
container xmlns:t=http://tapestry.apache.org/schema/tapestry_5_3.xsd;
xmlns:p=tapestry:parameter
t:content=text/html; charset=utf-8
this is parent componentbr/
On Thu, 06 Feb 2014 16:05:04 -0200, iberck ibe...@gmail.com wrote:
hi all,
Hi!
how can I transform the next example from inheritance design to
composition design ?
You don't even need to have two different components to have a component
which can have a part of its template replaced:
Thank you for your answer Thiago.
I have to create multiple c1,c2,c3,c4,c5,c6,c7,c8,c9 child components of
parentcomponent so I prefer to put the logic inside each component and then
decide which component use with a separate component:
ComponentCase.tml:
t:delegate to=block/
t:block id=c1
On Thu, 06 Feb 2014 18:57:24 -0200, iberck ibe...@gmail.com wrote:
Thank you for your answer Thiago.
;)
I have to create multiple c1,c2,c3,c4,c5,c6,c7,c8,c9 child components of
parentcomponent so I prefer to put the logic inside each component and
then decide which component use with a
What's annoying is that if Tapestry created some HTML5 elements for this
purpose; say require and init; it would pass the CSP even though it
would be exactly as hackable as having the inline script. Meanwhile, if
there's a man in the middle, having an inline script is no different than
having an
16 matches
Mail list logo
