AFAIK, You can't use the @EJB annotation outside of an actual bean or
class managed by the EJB framework (Tapestry is not). You need to bind
to the using a JNDI context - I think the Quickstart example has a good
example of using a Tapestry ASO (BeanLocator) for that.
Pavel Volkovitskiy wrote:
Annotations don't exist in JDK 1.4. You need to use JDK5 or stop using
annotations.
Ajit Raj wrote:
Hi,
I got an illegal character: \64 error for the following statement
@InjectMeta
^
and @Persist
^
etc when I switch from jdk1.5 to jdk1.4 to compile the project
As long as we can fix the
package foo.pages.bar;
class Bar {
}
turning into /bar/ and not finding the html page bug ;)
Howard Lewis Ship wrote:
That may not make it into the initial release of Tapestry; there are
so many other concerns that are more critical!
On 6/12/07, David Peterson
I'm working on two projects using T5 now. In my opinion its very usable,
just expect the occasional bug and rough edge at this point.
yes, on the one hand it's really good to have existing ajax components,
OTOH, if component creation is really simple (with adding stuff to
the header), it's
It seems the T5 asset javascript files (such as prototype,
scriptalicous) are not being cached by browsers (tested IE6 and FF).
Using Firebug and having the server on a slow (= cable modem upload)
connection shows this problem very well, with about 2-3s page delay in
transferring the .js
Went down this road recently.
You have a Layout component (call it what you want)
htmlbodysome static stuff
t:body/
/body
/html
and each page uses the layout;
t:layout
body body
/t:layout
if you want more flexibility, you can pass in other components as
parameters, and use t:delegate to
Not all of them are going to be well behaved web spiders. Exploit
scanners tend to hit specific URL suffixes to feed in their exploit code
(looking for vulnerable phpbb, phpnuke, etc), and they don't respond to
robots.txt ;)
It clogs up traditional Apache error logs as well.
I would
I'm using T5 to do some experimental testing, creating some mockup
applications to teach me more about the framework.
My question is, how do you best handle multi-part layouts?
For instance, a Layout can be composed of a Body and a Sidebar. The
Sidebar can be a component.
My current approach
AM, Yann Ramin wrote:
I'm using T5 to do some experimental testing, creating some mockup
applications to teach me more about the framework.
My question is, how do you best handle multi-part layouts?
For instance, a Layout can be composed of a Body and a Sidebar. The
Sidebar can be a component
Just figured out you can return the block in a render stage to get it to
render. Deceptively simple, but the docs (from my reading), didn't
mention it.
@BeforeRenderBody
Block doSidebar()
{
return _sidebar;
}
Yann Ramin wrote:
I got a good
10 matches
Mail list logo
