[T5.1] change style of client side validation

2009-07-31 Thread Michał Jedynak

Hello! 

Is there an easy way to change style of client side validation? 
I would like to have the same look as in server side (not a bubble), but I
don't want to turn it off (by setting ' clientValidation="false" ').

--
Michał
-- 
View this message in context: 
http://www.nabble.com/-T5.1--change-style-of-client-side-validation-tp24755039p24755039.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: Tapestry 5 with Spring Security - problem with unit tests.

2008-12-26 Thread Michał Jedynak

Thanks for the reply!

I came up with a similar solution:
I pass SecurityModel class from tapestry-spring-security to instance of
PageTester:

tester = new PageTester(appPackage, appName,
"src/main/webapp",SecurityModule.class);

and then I just create SecurityContext (the same way like in my first post)
and 
set it in SecurityContextHolder:

SecurityContextHolder.setContext(securityContext);

I don't create registry or use loadUserByUsername(...) method.

However, test() method from
nu.localhost.tapestry5.springsecurity.components.IfLoggedIn
throws NullPointerException during executing unit test, and I had to modify
it by adding (that's probably very sloppy ;-) ):

if (requestGlobals.getHTTPServletRequest()==null) {
if (((UserDetails)SecurityContextHolder.getContext()
.getAuthentication().getDetails()).getUsername()!=null) 
{
return true;
}
}


Did you handle it in a better way? (That's probably in yours handleIfLogIn() 
method ;-) )




Mark Horn-2 wrote:
> 
> We also use spring-security and ran into some issues as well.  What we
> ended up doing was adding something like this to the JUnit #setUp
> method
> 
>/* (non-Javadoc)
> * @see junit.framework.TestCase#setUp()
> */
>protected void setUp() throws Exception {
>super.setUp();
> 
>_tester = new PageTester(_ROOT_PACKAGE_NAME, _APP_MODULE,
>PageTester.DEFAULT_CONTEXT_PATH, TestHarnessModule.class);
> 
>_encoder = _tester.getService(ContextPathEncoder.class);
> 
>Registry registry = _tester.getRegistry();
>registry.performRegistryStartup();
> 
>UserDetailsService userDetailsSvc =
> _tester.getService(UserDetailsService.class);
>UserDetails ud = userDetailsSvc.loadUserByUsername(someuser);
> 
>handleIfLogIn();
> 
>SecurityContext context = new SecurityContextImpl();
>Authentication currentUser = new
> UsernamePasswordAuthenticationToken(ud.getUsername(),
>somepassword);
>context.setAuthentication(currentUser);
>SecurityContextHolder.setContext(context);
>}
> 
> Hope that helps.. and if anyone has a better solution please let me know.
> 
> -Mark
> 
> PS (sorry for the double post, but wanted to make sure my comment was
> attached to the appropriate thread)
> 
> On Mon, Dec 22, 2008 at 10:28 AM, SergeEby  wrote:
>>
>> Hi,
>>
>> This seems to be related to this thread:
>> http://www.nabble.com/PageLinkTarget%2C-where-did-it-go--to21022001.html#a21022001
>>
>> /Serge
>>
>>
>> Michał Jedynak wrote:
>>>
>>> Hi there,
>>>
>>> I've integrated spring security to my sample tapestry5 application
>>> (I'm using version 5.0.18) based on tapestry-spring-security
>>> (http://www.localhost.nu/java/tapestry-spring-security), but now my
>>> unit tests that use PageTester don't work, because there is no
>>> Authentication object in SecurityContext.
>>>
>>> I thought about creating SecurityContext, something like:
>>>
>>> SecurityContext securityContext = new SecurityContextImpl();
>>> User user = new User();
>>> user.setId(1L);
>>> user.setUsername("user");
>>> user.setPassword("password");
>>> UsernamePasswordAuthenticationToken token =
>>> new UsernamePasswordAuthenticationToken(
>>>   user.getUsername(), user.getPassword(), user.getAuthorities());
>>> token.setDetails(user);
>>> securityContext.setAuthentication(token);
>>>
>>> and adding it to the rendered page through PageTester, as it is
>>> described in
>>> http://tapestry.apache.org/tapestry5/guide/unit-testing-pages.html:
>>>
>>> PageTester tester = new PageTester(appPackage, appName,
>>> "src/main/webapp");
>>> Object[] context = new Object[]{ "abc", 123 };
>>> Document doc = tester.invoke(new ComponentInvocation(new
>>> PageLinkTarget("MyPage"), context));
>>>
>>> However this doesn't work, ComponentInvocation is an interface and I
>>> don't know how to initialize properly ComponentInvocationImpl.
>>> Anyone care to help?
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Michał Jedynak
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Tapestry-5-with-Spring-Security---problem-with-unit-tests.-tp21126486p21129652.html
>> Sent from the Tapestry - User mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>
> 
> 
q
-- 
View this message in context: 
http://www.nabble.com/Tapestry-5-with-Spring-Security---problem-with-unit-tests.-tp21126486p21176964.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: PageLinkTarget, where did it go?

2008-12-22 Thread Michał Jedynak

I have a similar issue:
http://www.nabble.com/Tapestry-5-with-Spring-Security---problem-with-unit-tests.-td21126486.html.
 
The problem is not about PageLinkTarget -> PageRenderTarget, but about the
way to properly initialize ComponentInvocationImpl.



nille hammer wrote:
> 
> 
> Hi Mark,
> first I have to admit I am not familliar with Tapestry´s testing
> mechanisms so this information is based on browsing through the javadocs
> rather than experience. I think this is the class you are looking for:
> http://tapestry.apache.org/tapestry5/apidocs/org/apache/tapestry5/internal/services/PageRenderTarget.html
> Hope that helps, cheers nillehammer
> 
> - original Nachricht 
> 
> Betreff: PageLinkTarget, where did it go?
> Gesendet: Mo, 15. Dez 2008
> Von: Mark Horn
> 
>> I am in the process of updating our application from Tapestry version
>> 5.0.15 to 5.0.18 and it looks like PageLinkTarget has disappeared.  We
>> have been following the Unit testing as outlined
>> http://tapestry.apache.org/tapestry5/guide/unit-testing-pages.html
>> which uses the PageLinkTarget when testing a page with a context.  I
>> looked around and can't find the class or any documentation on what
>> its replacement is.
>> 
>> Any help is greatly appreciated.
>> 
>> Thanks,
>> Mark
>> 
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>> 
>> 
> 
> --- original Nachricht Ende 
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/PageLinkTarget%2C-where-did-it-go--tp21022001p21134364.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Tapestry 5 with Spring Security - problem with unit tests.

2008-12-22 Thread Michał Jedynak
Hi there,

I've integrated spring security to my sample tapestry5 application
(I'm using version 5.0.18) based on tapestry-spring-security
(http://www.localhost.nu/java/tapestry-spring-security), but now my
unit tests that use PageTester don't work, because there is no
Authentication object in SecurityContext.

I thought about creating SecurityContext, something like:

SecurityContext securityContext = new SecurityContextImpl();
User user = new User();
user.setId(1L);
user.setUsername("user");
user.setPassword("password");
UsernamePasswordAuthenticationToken token =
new UsernamePasswordAuthenticationToken(
user.getUsername(), user.getPassword(), user.getAuthorities());
token.setDetails(user);
securityContext.setAuthentication(token);

and adding it to the rendered page through PageTester, as it is
described in http://tapestry.apache.org/tapestry5/guide/unit-testing-pages.html:

PageTester tester = new PageTester(appPackage, appName, "src/main/webapp");
Object[] context = new Object[]{ "abc", 123 };
Document doc = tester.invoke(new ComponentInvocation(new
PageLinkTarget("MyPage"), context));

However this doesn't work, ComponentInvocation is an interface and I
don't know how to initialize properly ComponentInvocationImpl.
Anyone care to help?





-- 
Michał Jedynak