As I recall, it had something to do with the IoC having an issue
identifying symbol injection with String value types without
additional information.
Kalle
On Sun, Oct 17, 2010 at 10:41 PM, Alessio Gambi wrote:
> Hi,
>
> I solved this by adding the @Inject annotation. BTW, why something @Symbol
Hi,
I solved this by adding the @Inject annotation. BTW, why something
@Symbol annotation is used without the @Inject and other time they are
coupled ?
Thanks.
-- Alessio
On Oct 18, 2010, at 7:30 AM, Alessio Gambi wrote:
Hi,
I am using Tapestry 5.0.1.5 and I have problem with using Symb
Hi,
I am using Tapestry 5.0.1.5 and I have problem with using Symbols.
In a service, I need the version of tapestry currently run, so I
injected the TAPESTRY_VERSION symbol in the service constructor (see
the code below)
public class MyComponentEventResultProcessor implements
ComponentEv
Hello Everyone
I just want to ask if this is the best practice for saving an add cart
function. Using SSO.
Need comments...
My code
Page Class
private List item;
@SessionState
@Property
private UserSession usersession;
private boolean usersessionExists;
Object onActivate
A long time ago (tapestry-acegi days maybe), I saw a post about using log4j
filtering configured in a log4j.xml file - it is not available in a
properties file configuration. If log4j is your underlying logging
mechanism, check into filtering options.
On Wed, Oct 13, 2010 at 9:29 PM, iberck wrot
JumpStart is the BEST Tapestry Documentation...
http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/javascript/zonewithoutyellowfade
http://jumpstart.doublenegative.com.au:8080/jumpstart/examples/javascript/zonewithoutyellowfade
Good Luck...
--
View this message in context:
http:/
For your specific use case, displaying the server time on the page, would
you not be better off to initialize a value to the current server time upon
initial page display, and then use a JS widget to increment/refresh the time
field on the client side? This would save a lot of unnecessary network
On Sun, 17 Oct 2010 10:07:44 -0200, Muhammad Mohsen
wrote:
I'm sorry I'm just trying to understand more about tapestry. So you'll be
using services because they are either global or request scoped, correct?
Yes, except for one nitpick: Tapestry doesn't provide a true request
scope, provid
I'm sorry I'm just trying to understand more about tapestry. So you'll be
using services because they are either global or request scoped, correct ?
I didn't quit understand the @Retain annotation by the way that's why I was
searching for old posts about it to see what have people been saying.
On