On Sun, 21 Apr 2013 19:23:27 -0300, Bob Harner wrote:
Yes, this is such a common mistake that the error probably should be much
clearer.
I'd even suggest some configuration symbol (default value true) which
treats expansions in parameter values as template errors. (By the way, I'm
back. :
I'm still not having any success :-/ I've followed all your instructions
plus attempted in both Tomcat6 and 7.
I just want to verify this is the correct spot for resource-ref and that
it's written correctly.
http://java.sun.com/dtd/web-app_2_3.dtd";>
rolemanager Tapestry 5 Application
I don't have anything related to this datasource in
TOMCAT_HOME/conf/context.xml
nor in TOMCAT_HOME/conf/server.xml
Note that context file name will be ROOT.xml only if you deploy to root
context,
that is your application url will be http://localhost:8080/
If you deploy to custom context, then co
Well I thought I was using ROOT.xml, but it was overwritten during
deployment. "I created the file manually on the server", I guess the
question is where should I be creating ROOT.xml? should this be done in
app? After manually creating it, I still have the same error.
What I had after manually cr
I don't use tapestry-hibernate, I use tapestry-jpa with Hibernate as JPA
implementation.
persistence.xml -- is a JPA specific file, I don't think you need it for
tapestry-hibernate.
Looking at your exception:
> javax.naming.NameNotFoundException: Name [jdbc/rolemanager] is not bound
in
this Conte
Thanks Dmitry, it sounds like we are at the tail end of this issue. :) My
only question left is in regards to your persistence.xml file. I use
tapestry-hibernate, however I do not have a persistence.xml file present in
my app. I'm not really sure what it's purpose is, but without it and
changing my
Check all the items in the troubleshooting section at the bottom of
http://tapestry.apache.org/class-reloading.html
On Apr 29, 2013 8:58 AM, "George Christman" wrote:
> Have you checked to ensure your not running in production mode?
>
>
> On Mon, Apr 29, 2013 at 6:56 AM, Alberto Fernández >wrote
It's fine in the sidebar, you just need to understand the limitations of
trying to hack tapestry to function outside of the normal request /
response flow.
CometD requires that the HttpSession is created before the push occurs.
Perhaps you could initialize your httpsession scoped list in the setup
I think i may need to step away from the idea of puttingit in the sidebar.
since that is the reason for all the problems.
I get following error at some times
I thin it is becous the Onchat function doesn't know where that session is?
part of the onchat function that is called:
Block onChat(Ch
Hmm... Your use case is really needing the entire server spec in your push
event innit? It seems as if you are generating links in your push event's
block, correct?
Unfortunately, FakeHttpServletResponse does not have an implementation for
encodeURL which is required by AbstractLink to generate li
The session works! but now i'm left over with this problem.
org.apache.tapestry5.internal.services.RenderQueueException
Render queue error in
BeginRender[ticketing/EmployerTicketCreate:layout.chatside.eventlink]:
encodeURL
activeComponents
ticketing/EmployerTicketCreate:layout.chatsid
11 matches
Mail list logo
