I was mainly just wondering if that is the best way to do it. I don't use the direct="true" setting so it works fine. I was also wondering if the Tapestry ID and the HTML ID have
But then again , I don;t know , this is the best sugestion i could
come up with , if you guys know a better way of dooing what he needs
done , i'm sure he'll gladly listen :) And be sure i'd also be taking
notes
On 12/6/05, Cosmin Bucur <[EMAIL PROTECTED]> wrote:
> I guess if one needs to do such
I guess if one needs to do such a thing , one should make sure that
all requirements for this to work are met .
Other than that ... the only thing left that's wierd , is this
restriction that tapestry imposes of not calling the same instance of
a component twice in the page
On 12/6/05, Leonardo
Yes. That is what I mean. Any ajax response that contains a
textarea will fail on FF. It doesn't matter if the textarea was
rendered as a tapestry component or is just a standard HTML textarea.On 12/6/05, Cosmin Bucur <[EMAIL PROTECTED]
> wrote:yea static page works , i was getting concerned , s
Cosmin Bucur wrote:
I don't understand why the jwcid and the id have to match .
So tapestry won't render the page if your components have
subcomponents which end up having the same name ? that sux
Anywais , I never needed to do this , but I do have lists in my apps ,
and within the listable com
I don't understand why the jwcid and the id have to match .
So tapestry won't render the page if your components have
subcomponents which end up having the same name ? that sux
Anywais , I never needed to do this , but I do have lists in my apps ,
and within the listable components I make , the s
yea static page works , i was getting concerned , since i just
decidded to start developing for ff and give up msie .
looks like it's only when the page is loaded through an ajax response ...
On 12/6/05, Cosmin Bucur <[EMAIL PROTECTED]> wrote:
> are you saying that a static html page with a texta
are you saying that a static html page with a textarea in a form would
produce the same results in Firefox ?
that sounds ... disturbing
On 12/6/05, Tim Downey <[EMAIL PROTECTED]> wrote:
> That is what I have seen as well. If you simply use a plain, standard
> non-Tapestry using basic HTML and n
That works fine for the HTML ID, but how to get the jwcid to match? And more importantly, how to make them unique within the page? I've tried using ognl inside the jwcid attribute value before, but haven't had any luck.
What I have working now is
letting tapestry create the sub-component's T
That is what I have seen as well. If you simply use a plain,
standard non-Tapestry using basic HTML and no
_javascript_ you can reproduce the issue.
It's almost as if it is some sort of Firefox bug.On 12/6/05, Cosmin Bucur <[EMAIL PROTECTED]> wrote:
Ok so I had to do this mini app and I figure i
Ok so I had to do this mini app and I figure i'd give it a shot with
tacos and make it 100% ajax .
It all went ... relatively good and i have now finished 99.99 % of it
successfully . It helped me find 2 VERY anoying bugs however ( one of
them i'll talk about later in the tapestry ml a bit ) .
th
Won't it work if you give it a dynamic id value with ognl
id="ognl:myFirstId" ?
On 12/6/05, Michael Waluk <[EMAIL PROTECTED]> wrote:
> By giving it id="myDiv" you are explicitly naming it. If I did that inside
> my component, and used the component multiple times on the page you would
> get dupl
Aha! Thanks felix :) On 12/6/05, Felix Sun <[EMAIL PROTECTED]> wrote:
done! added AjaxStaleSession page to prevent doctype in ajax response.changed AjaxExceptionPresenter to let StaleSessionException use it too.make stale session check after response builder setup.
On 12/5/05, Jesse Kuhnert <[EMAI
By giving it id="myDiv" you are explicitly naming it. If I did that inside my component, and used the component multiple times on the page you would get duplicate IDs - and the 2nd instance wouldn't get updated with the results.
The real problem is when I place 2 instances of the same component
I'm doing it regularly.
first I don't use @Any into template but I define a component into my page/component
then I reference it as
updateComponents="ongl:{components.myDiv.id, otherId}"
I hope this may help.
Cheers,
kiumaOn 12/5/05, Cosmin Bucur <[EMAIL PROTECTED]> wrote:
the updateCompo
Leonardo Quijano Vincenzi wrote:
Dennis Fleurbaaij wrote:
Leo,
Agree on the Hibernate part, although it's kindof the de-facto
standard for database access I guess. And most people don't use Tacos
just-for-fun but will need to implement it in larger environments so
this might be a good idea.
Dennis Fleurbaaij wrote:
Leo,
Agree on the Hibernate part, although it's kindof the de-facto
standard for database access I guess. And most people don't use Tacos
just-for-fun but will need to implement it in larger environments so
this might be a good idea. On the other hand, if you strip th
Leo,
Agree on the Hibernate part, although it's kindof the de-facto standard
for database access I guess. And most people don't use Tacos
just-for-fun but will need to implement it in larger environments so
this might be a good idea. On the other hand, if you strip the
annotations it's just a
