I found out how to solve these problems.
For the first problem, that is because the password field requires one more
attribute to be set in the .page configuration file. The textField needs to the
property of hidden set to be true to enable the start sign on the screen.
<component id="password" type="TextField">
<binding name="value" value="ognl:password"/>
<binding name="hidden" value="true"/>
</component>
For the second problem, reportedly that in jboss the ejb3 does not require
users to bind the jndi naming rule, however, it seems not so. You still need to
set the jboss.xml file to bind the jndi name.
the jboss.xml file content may look like below:
<?xml version="1.0" encoding="UTF-8"?>
http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd";>
<jboss>
<enterprise-beans>
<session>
<ejb-name>SessBean</ejb-name>
<jndi-name>SessBean/remote</jndi-name>
</session>
</enterprise-beans>
</jboss>
----- Original Message ----
My first questions is, according to the document, I am able to disable
tapestry cache in order to see the change made during testing my web
project. So I set the the attribute
"-Dorg.apache.tapestry.disable-caching=true" in run.sh which shows
...
I found the cache still exists because the first page (Home.html)
originally I set the password field to type = "text"; then change it to type
= "password". Unfortunately, the the html source of generated page
still shows type = "text", resulting in the password filed still displays
characters that user types. What part I might miss in order to disable
the cache.
My second question is - when connecting to stateless session bean,
jboss always issues error "javax.naming.NameNotFoundException: LoginService
not bound". LoginService is a Stateless session, which implements
Remote and Local interface, as follow:
___________________________________________________________
Want ideas for reducing your carbon footprint? Visit Yahoo! For Good
http://uk.promotions.yahoo.com/forgood/environment.html
