t yet).
>
> On Fri, Dec 16, 2016 at 5:12 AM, Andrus Adamchik
> wrote:
>
>>> I haven't found yet a situation in which I wanted something
>>> like that.
>>> I've see people creating a MyServiceSource service, for example,
>>> which th
M, Thiago H. de Paula Figueiredo
> wrote:
>
> Hi!
>
> On Tue, Dec 13, 2016 at 5:31 AM, Andrus Adamchik
> wrote:
>
>> From what I gather Tapestry 5.4 still does not support parameterized
>> service injection?
>
>
> It does not. I haven't found y
jectService("s1")
> private MyService s1;
>
> @InjectService("s2")
> private MyService s2;
>
>
>
> On 13 Dec 2016 7:31 a.m., "Andrus Adamchik" wrote:
>
>> From what I gather Tapestry 5.4 still does not support parameterized
>> servic
From what I gather Tapestry 5.4 still does not support parameterized service
injection? E.g. in the following example both s1 and s2 will map to the same DI
key of the bare class:
@Inject
private MyService s1;
@Inject
private MyService s2;
I am running Tapestry on a Bootique.io stack w
with Bootique: http://bootique.io/docs/0/getting-started/
3. Tapestry module with instructions: https://github.com/nhl/bootique-tapestry
4. Recent Bootique conference presentation:
https://www.youtube.com/watch?v=o6kSEG4v3VE
Andrus
---
Andrus Adamchik
@andrus_a | @ApacheCa
Exactly. I can envision a lot of pissed of users (myself included). PR disaster
and people walking away from the framework is probably what will happen.
The voluntary registration idea floated in this thread is much more honest. Not
sure how to implement it in the context of Tapestry though.
An
Hi folks,
While I am generally happy with the clean default package structure of
a tapestry app, I am running into a snag with the coding style we've
been using with T4 and got quite used to. Each service package looks
something like this:
/services/s1/IService (service interface)
/servi
ice) {
return new MySiteService(dataService);
}
}
A different order of service loading or a typo in the old build method
name... Hard to say now.
Andrus
On Apr 2, 2010, at 4:52 PM, Andrus Adamchik wrote:
Ok, not very specific, but I found what you are referring to.
Unfortunat
org/tapestry5.1/tapestry-ioc/cookbook/override.html
On Fri, Apr 2, 2010 at 3:58 AM, Andrus Adamchik > wrote:
Hi guys,
having a bit of trouble overriding my services with T5.2 (build
from a few
days ago ... can't use 5.1 due to some bugs that got fixed in 5.2).
I have
AppModule and a
Hi guys,
having a bit of trouble overriding my services with T5.2 (build from a
few days ago ... can't use 5.1 due to some bugs that got fixed in
5.2). I have AppModule and a submodule:
@SubModule( { ServicesModule.class })
public class AppModule {
public static void bind(ServiceBi
The question was about Tapestry 4. And the answer I guess is to throw
a PageRedirectException.
Andrus
On Oct 29, 2009, at 4:12 PM, Ulrich Stärk wrote:
http://tapestry.apache.org/tapestry5.1/guide/pagenav.html
Am 29.10.2009 14:54 schrieb asianCoolz:
public void pageValidate(PageEvent event)
I am an open source developer myself and I *love* when the users submit
patches that work or at least create intelligent Jira's :-)
But that's not the point here. Even though there is an OGNL-11 bug report,
this is not a bug. This is a new "feature" of Tapestry 4.1. No matter was
else was said i
loop in a try/catch that
would switch to a generic algorithm on the first ClassCastException?
Andrus
Andrus Adamchik wrote:
>
> Hi Jesse,
>
> Thanks for clarification. I guess we won't be doing the upgrade :-)
>
> Andrus
>
>
>
> Jessek wrote:
>>
&g
is used.
>
> In Summary: Find a way to have a common interface for these object
> properties or don't plan on upgrading anytime soon...
>
> On 8/15/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
>>
>> Thanks for the suggestion. I tried the latest ognl build
Thanks for the suggestion. I tried the latest ognl build, but the problem is
still there (and in addition I get a bunch of OGNL stack traces in other
places).
Ok, I guess I can't use 4.1.x just yet :-/
Andrus
On 8/14/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
>
> I foun
eyond 2.6.7.
I wonder if you had a chance to look into this issue?
Thanks
Andrus Adamchik
Jessek wrote:
>
> Thanks, I've re-opened the bug and will take a look.
>
> On 7/10/07, Damien Uern <[EMAIL PROTECTED]> wrote:
>>
>> Hello,
>>
>> I
Hi Jesse,
Thanks for your reply. I'll try bumping up MaxPermSize value - this
is one parameter that can possibly cause the crashes I am observing
(Xms/Xmx are sufficiently high already).
Although I was still hoping there is a way to warm up the stack to
fill in the page cache before the a
Analyzing more thread dumps, I found that PageLoader is not the only
contention point, but still Tapestry service stack warmup is the
bottleneck. Any ideas?
Andrus
On Apr 24, 2007, at 5:00 PM, Andrus Adamchik wrote:
Maybe that's a FAQ that I overlooked somehow, but a google s
Maybe that's a FAQ that I overlooked somehow, but a google search
wasn't helpful in solving the problem below...
I have a busy application running on Tapestry 4.0.2 / Jetty 6 / JDK
1.5. On startup the JVM would sometimes crash overwhelmed with
requests. If it survives for the first 1-2 minu
19 matches
Mail list logo
