hi Russel,
we didn't use Spring WebFlow. We did everything using
Tapestry IOC. Flow starts and ends are marked using own
annotations added to actionMethods.
g,
kris
Russell Brown [EMAIL PROTECTED]
16.09.2008 17:24
Bitte antworten an
Tapestry users users@tapestry.apache.org
An
Tapestry
Greetings!
I'm migrating a I18N enabled Tap3 application to Tap5. The current
application is using a custom implementation of BaseEngine class (overriding
createComponentStringsSource method to use my provided
IComponentMessagesSource) to use internationalized resources form a
database. The
Hi all,
I am doing a evaluation on Tapestry, I am very new to Tapestry as well as Java and
its frameworks.
I came across a problem when I try to use the PageTester. I wrote a very simple test
case like the one in
http://tapestry.apache.org/tapestry5/guide/unit-testing-pages.html.
I put
Hello,
maybe this is a bit off-topic, but I will give it a shot here.
If one web application is developed in JSP and the other in Tapestry 5 and
both of them are deployed into a single instance of Resin/Tomcat, what is
the best way to share some common very large objects (~200MB)? Only in
memory
Hi,
This will be a very interesting topic, I'd like to see how TDD can be used
in the development of T5 pages, my experience with T5 page tester isn't so
successful, now I try to do everything in the services as it is a easy place
to test.
angelo
akochnev wrote:
Let's keep this
From the T5 documentation:
When a sub-class overrides an render phase method of a base class, the method
is only invoked once, along with any other base class methods. The subclass can
change the implementation of the base class method via an override, but can't
change the timing of when that
Thanks Robin.
I've put up a wiki page explaining how someone can secure a T5
application using spring security and LDAP.
http://wiki.apache.org/tapestry/Tapestry5HowToSecureWithSpringAndLDAP
Robin Helgelin wrote:
Hi,
Thanks to Michael Gerzabek I've been able to put together a new
version of
Hi all,
I haven't got around to using PageTester yet, but I started using Easymock for
my IoC services recently... Its quite amazing how you can create a full blown
IoC service with all dependencies satisfied so easily, it just works since
service proxies are all interfaces in Tapestry.
Hi Alex,
Testing pages as POJOs is quite simple. You can roll your own very,
very, very simple service injector and inject EasyMock services into the
pojo. I have done it using reflection. So I have a class that takes the
page instance being tested in the constructor (and the test class too)
and
Hi Peter,
How have you done this? When I try to use Tapestry to Build my EasyMock
services the resultant proxies are rejected by EasyMock as not being EasyMock
proxies...
Cheers
Russell
-Original Message-
From: Peter Stavrinides [mailto:[EMAIL PROTECTED]
Sent: 17 September 2008 11:47
Hi Russel,
Very interesting! possible to have a very simple sample project that get us
started? thanks.
Angelo
Russell Brown-6 wrote:
Hi Alex,
Testing pages as POJOs is quite simple. You can roll your own very,
very, very simple service injector and inject EasyMock services into the
Hi,
Please search the list. This has already been answered.
Cheers,
Serge
Ovidiu Hurducas-2 wrote:
Greetings!
I'm migrating a I18N enabled Tap3 application to Tap5. The current
application is using a custom implementation of BaseEngine class
(overriding
createComponentStringsSource
Hi,
I started documenting this for the migration from T4 to T5.
Please refer to the following project:
http://code.google.com/p/tapestry5-appfuse/
The code is updated. However, I haven't had a chance to update the steps
recently, but this is on my todo list.
/Serge
Matt Doran-3 wrote:
Hi
Hi Russell
I am not sure exactly what you mean that you couldn't build Tapestry Easymock
services, but let me explain what I am doing:
I am running a Maven setup, so if my tapestry services are in:
scr.main.java.web.services the relevant tests are in
scr.test.java.web.services. They are
Hi Peter,
Thanks for that. That is just normal EasyMock testing isn't it? I don't see
where tapestry comes into that at all? You are creating the instances of all
the classes and you are creating the instance of the class under test aren't
you? Where is the PageTester and Tapestry IoC and all
Russell,
this is just speculation, as I haven't tried this on my own, but it seems
to me that you'll have to do the EasyMock setup training inside your test
module, e.g. :
@SubModule( { MyAppModule.class })
MyAppTestModule
public static MyService buildMyService () {
MyService
Hi Russell,
Now I see what you mean, like I said though I haven't used PageTester yet.
I only use Easymock to test my IoC services that implement Tapestry interfaces,
you appear to have an unsatisfied class dependency... just a shot in the dark,
but have you tried the EasyMock Class
-Ursprüngliche Nachricht-
Von: Kristian Marinkovic [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 16. September 2008 15:19
An: Tapestry users
Betreff: Re: T5: ApplicationStateObject is misleading
I'm no native speaker but ApplicationStateObject is quite fine for
me... it
ApplicationStateObject is a misnomer, it also got me when I started T5, what it
really is, is a session scoped object (1 per user, per session), by default
Tapestry services that use the @Inject annotation are singletons (1 per
application) as apposed to the @ApplicationState annotation
Alex,
Yeah. I think that the approach you outline may well work but is
unworkable (if you know what I mean). I hold out for some way of
stripping the proxy from my mock service (using reflection to fire the
Object Creators create method and using the un proxied mock).
The problem with training
Exactly. To everyone who thinks @ApplicationState is not a misleading
term, I would ask you to think back to when you started with T5. Are
you sure you didn't think @ApplicationState meant application-wide
scope? When I see @ApplicationState today I still do a momentary
double-take
Hi Kit,
On Wed, Sep 17, 2008 at 01:19, Kit Yeung [EMAIL PROTECTED] wrote:
I am doing a evaluation on Tapestry, I am very new to Tapestry as well as
Java and its frameworks.
Don't you think you're taking on slightly more than you can handle? If
you're really that new to Java, its frameworks,
@Scope does, indeed, make more sense than @Persist and
@ApplicationStateObject. I wouldn't mind that change, but is it feasible
at this point in Tapestry 5's development cycle?
-Filip
On 2008-09-17 17:36, Geoff Callender wrote:
Exactly. To everyone who thinks @ApplicationState is not a
Hi,
While debugging with Tapestry5, I noticed one not-so-nice issue. But
first, a bit of background.
I usually configure my logging framework (log4j) to log all statements
for my application at debug level during development. E.g. all log
records logged to com.mycompany.myapp logging
On Wed, Sep 17, 2008 at 09:03, Filip S. Adamsen [EMAIL PROTECTED] wrote:
@Scope does, indeed, make more sense than @Persist and
@ApplicationStateObject. I wouldn't mind that change, but is it feasible at
this point in Tapestry 5's development cycle?
Sure, just deprecate @Persist and
Right. I done it. I'll write a wiki post about it this evening.
In short, only services with an interface are wrapped in the
ObjectCreator proxy. I just use reflection to grab the ObjectCreator
field from the proxy and fire its create method and use the resultant
service.
Sweet
Russell
Hi,
Yes, you can just inject Request and PersistentLocale.
-Filip
Ulrich Stärk skrev:
In order to have localized Translators, Howard suggested to override the
default TranslatorSource service and add my own Translators to it. If I
want to have localized Translators I have to take into
There are still dozens of Tapestry services that will need to be
changed/rewritten, though. I'm not against this, just saying it's a huge
change at this point - the way I see it, anyway.
-Filip
On 2008-09-17 18:12, Hilco Wijbenga wrote:
On Wed, Sep 17, 2008 at 09:03, Filip S. Adamsen [EMAIL
There is some logic to what is proposed by Geoff, so it at least merits
consideration and exploration.
I could see problems arising in the area of uniqueness. We know there's only
one ASO of a specific class in a T5 app. That's a nice simplification. It
gets fuzzy moving to conversations, and
Hugo,
I was thinking that it would have been nice if the instructions for both
tapestry-acegi and tapestry-spring-security were available on the wiki. I
guess the idea is that a whole bunch of people out there still use acegi
(and haven't migrated to spring security).
Nice work !
Cheers,
You're probably right. I had first written the same document but for
tapestry-acegi but then changed it to tapestry-spring-security.
I'll create a new page with the tapestry-acegi version.
Alex Kotchnev wrote:
Hugo,
I was thinking that it would have been nice if the instructions for both
I'm looking for ways to create tiled, multi-panel page layouts. An example
is the new Yahoo Mail. It has several panels, some with scroll bars,
separated by draggable dividers. Together, they fill the browser window,
growing and shrinking if I resize it. I poked around the various T5
By my original post I didn't want to say that current implementation of ASO
objects and persistent page properties is illogical or utterly wrong. I
understand that it has its internal logic and historical genesis. I just
wanted to point out few issues I came across when I was implementing
Tapestry
33 matches
Mail list logo
