hi,
i'm currently trying out the tapestry 5.3 new tree component and after
searched through and study the demo from :-
http://jumpstart.doublenegative.com.au/jumpstart/examples/component/treebrowse
i realized its a recursive tree which i'm not very good at. such that i
think there must be an eas
I write a string translator like this:
public class EditorTranslator extends AbstractTranslator {
public KindEditorTranslator() {
super("editor", String.class, "editor-format-exception");
}
public String parseClient(Field field, String clientValue, String
m
That's interesting. I did not know you could bind an abstract class instead
of an interface.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/tapestry-security-0-4-3-released-tp5574027p5576063.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
--
On Sun, Mar 18, 2012 at 3:41 PM, trsvax wrote:
> I guess I've just gotten in the habit of making everything a service with an
> Interface. Class reloading without a restart is pretty handy, but in this
Of course, you can make it a service, you just don't need to. If you
nevertheless do, you need
My advice... "Roll-your-own" can be okay for simple cases, but
home-grown security implementations, even for such "simple" cases, can
have subtle security vulnerabilities that a well-tested library like
Tapestry-security probably won't. And many "simple" cases evolve into
complex ones over time, so
Hi
On Mar 19, 2012, at 6:50 AM, Paul Stanton wrote:
> Hi group,
>
> Is it recommended to use a security module such as tynamo's tapestry-security
> when all you require is username/password authentication to a couple of pages?
>
If the project is going to stay at "a couple of pages of authent
Hi group,
Is it recommended to use a security module such as tynamo's
tapestry-security when all you require is username/password
authentication to a couple of pages?
Is there a simpler add-on module?
Is 'roll-your-own' a generally accepted practice for a simple
implementation?
Discuss...
I guess I've just gotten in the habit of making everything a service with an
Interface. Class reloading without a restart is pretty handy, but in this
case you are correct the following is the way to go:
public static void contributeWebSecurityManager(Configuration
configuration, UserDAO userDAO)
On Sun, Mar 18, 2012 at 2:43 PM, trsvax wrote:
> I see what the problem is although now I not sure why it works at all. I have
> this in my AppModule
> binder.bind(Realm.class, UserRealm.class);
> public static void contributeWebSecurityManager(Configuration
> configuration, Realm userRealm) {
>
I see what the problem is although now I not sure why it works at all. I have
this in my AppModule
binder.bind(Realm.class, UserRealm.class);
and
public static void contributeWebSecurityManager(Configuration
configuration, Realm userRealm) {
configuration.add(userRealm);
}
but
Hello,
I am using tapestry 5.3.2 with JBoss 7, and I'm having some problems
when using a JBoss datasource with JPA.
My datasource configuration:
(...)
My persistence.xml configuration:
org.hibernate.ejb.HibernatePersistence
Thanks... Man I feel stupid now.. I was using Spring 2.5.6 instead of the
newest version. Once I changed it to use the correct version 3.1.0.RELEASE
everything started working perfectly.
Thanks for your help.
-
--
Don't Forget to Rate
--
View this message in context:
http://tapestry.1045711
Tried 0.4.1 and I have the same problem. I'll see if I can track it down and
report back.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/tapestry-security-0-4-3-released-tp5574027p5575350.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
On Sun, Mar 18, 2012 at 6:56 AM, trsvax wrote:
> Thanks for the update but when I upgraded from 0.4.0 I can authenticate but
> my roles quit working. When I run the app in debug mode it appears
> protected AuthorizationInfo doGetAuthorizationInfo(PrincipalCollection
> principals)
> in my UserRealm
Thanks for the update but when I upgraded from 0.4.0 I can authenticate but
my roles quit working. When I run the app in debug mode it appears
protected AuthorizationInfo doGetAuthorizationInfo(PrincipalCollection
principals)
in my UserRealm is not called. It does get called in 0.4.0. My UserRe
On Sun, 18 Mar 2012 04:37:23 -0300, ksrijith wrote:
Hi,
Hi!
I'm currently building a solution using Tapestry and Spring
What Tapestry and Spring versions? As far as I recall, Tapestry 5.3.2
works with Spring 3.1.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and
Hi,
I'm currently building a solution using Tapestry and Spring and I'm facing
an issue once the war is build and deployed. On deploying the war file i'm
getting the following error:
I'm aware that this issue comes due to the antlr version differences.
Currently Tapestry uses antlr 2.7.6/7 but sp
17 matches
Mail list logo