Re: [T5] Colons in element ids?

2008-04-22 Thread Jason Lea
or you could try looking at the css spec... 
http://www.w3.org/TR/CSS21/syndata.html#escaped-characters

and use the escape character \  :)

example:

html
head
style type=text/css
   #foo\:bar { color: red;}
/style
/head
body
p id=foo:barfubar/p
/body
/html

Julian Wood wrote:

5.0.12-SNAP

If I make a form and put a form label combo in it:

form t:type=Form
  div
   label t:type=Label t:for=username /
   input t:type=TextField t:id=username type=text  
maxlength=15/

  /div
/form

It is rendered out like this:

label for=username id=username:labelUsername:/label
input id=username maxlength=15 name=username type=text

How can I target the the label id with a css rule?

#username:label {
color: red;
}

is illegal - well it is a pseudo-class, like a:hover. I realize there  
are other ways to get around this - my point is shouldn't tapestry be  
using something other than a colon in the identifier?


J

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  


--
Jason Lea



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: T5: Multiple clicks causing NPE

2008-01-08 Thread jason lea
Hi,

We get this error quite often with Java 1.5, we asked about it in the
mailing list back in August.  We found the error doesn't occur in Java 1.6.
We usually see a stack trace with a NPE when doing getSession() or
getCookies().

Here is what I wrote last time:

We are getting an intermittent NullPointerException in Tapestry 5.0.5.  We
are running on Java 1.5.
It seems that the RequestGlobals has a null Request when the call to
getCookies is made (or that RequestGlobals is null).  We cannot get the
error to occur every time so testing is tricky, sometimes it occurs on the
first request after the webapp starts with subsequent requests good for a
few minutes before it occurs again.  Other times it starts fine and pressing
F5 100 times might make it occur.

Our thought at the moment is that a ThreadLocal bug (
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6550283 ) might be
causing the RequestGlobals to initially be correctly initialised and stored
in ThreadLocal but later on with more items being added this bug means
further down the track, a new RequestGlobals is added with null values.



-- 
Jason Lea


T5 Intermittent NPE

2007-08-26 Thread jason lea
)
at org.apache.catalina.core.StandardWrapperValve.invoke(
StandardWrapperValve.java:230)
at org.apache.catalina.core.StandardContextValve.invoke(
StandardContextValve.java:175)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(
AuthenticatorBase.java:433)
at org.apache.catalina.core.StandardHostValve.invoke(
StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(
ErrorReportValve.java:104)
at org.apache.catalina.core.StandardEngineValve.invoke(
StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(
CoyoteAdapter.java:261)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
Http11Protocol.java:581)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java
:447)
at java.lang.Thread.run(Thread.java:613)




-- 
Jason Lea


Re: T5: File input component

2007-06-01 Thread Jason Lea

In this thread a file upload component is mentioned:
http://www.nabble.com/T5-Upload-component--tf3373673.html#a9849252

and the download from here:
https://issues.apache.org/jira/browse/TAPESTRY-1354


Joshua Jackson wrote:

Dear all,

Does anybody know where is the component or what is the name for the
component for file input in T5? I've been searching through under the
package org.apache.tapestry.corelib.components but could not find it?
Have I missed on something?

Currently I'm using version 5.0.4. Perhaps it is already available in
the snapshot version?

Thanks in advance :)

  


--
Jason Lea



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: T5 application wide message catalog

2007-05-24 Thread jason lea

Oh cool.

In the meantime I have just created a GenericPage.java that my other pages
will extend and put all my global messages into GenericPage.properties as
the message catalog inheritance seems to be working.

On 5/23/07, SergeEby [EMAIL PROTECTED] wrote:



Hi,

I believe this is now available in 5.0.5-SNAPSHOT.

/Serge


Jason Lea wrote:

 I'm using Tapestry 5.0.4 and have some localized fields getting messages
 from message catalog for the page working correctly, but I cannot get an
 application wide message catalog to work

 In the page Target.html:
   input type=submit t:type=Any value=message:button.next
/

 (have also tried input type=submit t:type=Any value=message:
 button.next/ )

 In web.xml:
   filter
   filter-nameapp/filter-name
   filter-classorg.apache.tapestry.TapestryFilter
 /filter-class
   /filter

 So from what I have read about the global message catalog coming from
the
 name of the filter, I should put a file here
 WEB-INF/app.properties:
   button.next=Next

 But this gives me the message on my button:  [[missing key: button.next
]]
 I have put button.next into Target.properties and it found it.
 Target.properties was sitting in the same folder as Target.java.

 So have I called it the wrong name or put it in the wrong place?

 Thanks for any help,

 --
 Jason Lea



--
View this message in context:
http://www.nabble.com/T5-application-wide-message-catalog-tf3801451.html#a10756715
Sent from the Tapestry - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Jason Lea


T5 application wide message catalog

2007-05-22 Thread jason lea

I'm using Tapestry 5.0.4 and have some localized fields getting messages
from message catalog for the page working correctly, but I cannot get an
application wide message catalog to work

In the page Target.html:
 input type=submit t:type=Any value=message:button.next/

(have also tried input type=submit t:type=Any value=message:
button.next/ )

In web.xml:
 filter
 filter-nameapp/filter-name
 filter-classorg.apache.tapestry.TapestryFilter
/filter-class
 /filter

So from what I have read about the global message catalog coming from the
name of the filter, I should put a file here
WEB-INF/app.properties:
 button.next=Next

But this gives me the message on my button:  [[missing key: button.next]]
I have put button.next into Target.properties and it found it.
Target.properties was sitting in the same folder as Target.java.

So have I called it the wrong name or put it in the wrong place?

Thanks for any help,

--
Jason Lea


T5 5.0.4 loop and checkbox

2007-05-21 Thread jason lea

Hi,

I am new to Tapestry and have started a project where we want to use
Tapestry 5.

My question is about how I can use the  loop and checkbox with my code.

I will have a few objects to play with like User and Category.  User has a
Set of Category objects.  Category just holds an id and string that is
really a message key (for localization).

So on say the Category.html page we want to show a list of categories with a
checkbox next to each one that the user can check.
When the user submits the form we want to stuff the checked Category objects
into the User's Set.

So my Category.html might have something like
t:form
tr t:type=loop source=myList value=rowitem
   tdinput t:type=checkbox t:id=myCategory t:value=rowitem.checked
/${rowitem.label}/td
/tr
input type=submit /
/t:form

Are those attributes right?
Can anyone point me in the right direction for what the Category.java should
have in it?

I think I have managed to get the rowitem.label appearing with a simple list
eg

@persist
private List myList = new ArrayList();
public List getMyList();
public void setMyList(List _myList);

(I have it populated in the constructor as an example)

What where do the values of checkbox go?  Is it some sort of indexed
property?

getMyCategory()
setMyCategory(what type goes here?)

any hints (or complete examples ;) ) would be welcome

--
Jason Lea