won´t you have a separate servlet mapping/binding in web.xml? Things
then are in their own "namespace".
Why do you think screens are not used anymore?
But may be I misunderstood, whats your intent...
Best regards, Georg
Von: Szűcs Attila <[email protected]>
An: "[email protected]" <[email protected]>,
Datum: 21.01.2013 09:59
Betreff: Vaadin with Turbine
Hi,
has anyone tried to integrate Vaadin into a Turbine (2.3.2) application?
What are the advantages / disadvantages?
I am concerned in particular about accessing the Session object (I have
some infos stored in the session including the logged user, current
locale etc.).... will the Action classes be useful anymore or I have to
write listeners for each button (like for save I had a doSave method in
the corresponding Action, now I will have a separate class for the save
action)?
Does it mess up the whole Screen, Action logic of Turbine? As far as I
have seen Screens will not be used anymore, maybe the Actions can be
kept ...
I would like to use Vaadin for some new pages and keep Velocity (1.6)
for the already existing parts.
Any insight is welcome!
Thanks,
Atti
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
