ChenilleKit IE Rendering
I am using the components in ChenillKit/T5Components extensively in my app, but I am running into some issues with how they are rendered in IE vs Firefox. As is usually the case, the components looks great in Firefox. But often struggle in IE. In fact, while using IE6 even the demo doesn't render correctly. I am most concerned with the rendering of the window components. It looks like the bluelighting and mac_os_x styles are having problems. In addition, it seems like the loading of the window page is lagging in IE. I am not sure what is causing that. I have also noticed that IE seems to calculate the size of hidden divs differently that firefox does. This makes for some strange behavior with different components "jumping" across the screen during some actions. I know that the cross browswer functionality is a huge hurdle to get over, but was wondering if anyone else has run into this problems and/or had a work around for getting these components working consistently between firefox and ie. -- View this message in context: http://www.nabble.com/ChenilleKit-IE-Rendering-tp24113647p24113647.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [T5] Request Management
Okay, so I tried contributing a MasterDispatcher. I contributed it with an order of after:PageRender, however it doesn't seem to be getting called. It seems that PageRenderDispatcher is interrupting the pipeline, so contributing a dispatcher after:PageRender isn't possible. Anyone know of a work around for this since? The PageRenderDispatcher is internal to T5 and I would like to keep my hands out of it. :) -- View this message in context: http://www.nabble.com/-T5--Request-Management-tp21253367p21254525.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
[T5] Request Management
I am running into a problem trying to determine when a conversation starts and more specifically ends with Tapestry. I understand that Tapestry issues some redirects or creates a new request(s) for the render cycle. Is there a way to determine when a conversation is completed and the page has been rendered? Right now, I have a Servlet Filter that puts an attribute into the HttpSession. I want to clean that attribute up when the conversation is over and tapestry is done with all of its requests/redirects/rendering. I have looked at contributing a requestHandler but it seems to be called on both the action and render requests. I looked at contributing a Master Dispatcher, but I don't think that is what I want to do, so I didn't pursue it too far. Any ideas? -- View this message in context: http://www.nabble.com/-T5--Request-Management-tp21253367p21253367.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [T5] Nested Zones
Well, I thought I would post a note about what I did to actually get this to work. I think that this still seems like a work around and that tapestry should make the dealings of its generated internal ids more transparent. Also, I didn't come up with this on my own, so thank Fanf for pointing me in this direction. The first thing I did was in my component I injected the RenderSupport object. This object has a method allocateClientId that I called on the zone during the setup render. This method returns the client id of the zone which I put into a persistent property on the component. In the template, I gave the zone both a t:id="zoneName" and an id="prop:zoneId". All of the components that needed to reference the zone used zone="prop:zoneId". These seems to work for the most part, but I don't think it is very clear on how to do it. Hope this helps somone else that might need it. -- View this message in context: http://www.nabble.com/-T5--Nested-Zones-tp21060828p21115259.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: [T5] Nested Zones
I have been thinking about this problem a little further and I don't think that adding a static id on the zone is going to work. The problem that I have is that this Zone lives inside a component. This component could be used multiple times and that would break the uniqueness of the id of the zone. Does tapestry have the concept of scope? This seems like it would solve the potential problem of partial updates and changing ids. If the Zone is changing then the changes within that zone's scope should be able to handle the updated references. Does that make sense? Is something like this possible with the current code-base (T5.0.18)? -- View this message in context: http://www.nabble.com/-T5--Nested-Zones-tp21060828p21073771.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
[T5] Nested Zones
I know that this topic has come up a number or times in the past but I am still struggling to get it to work. I am trying to update a nested zone and I get the Javascript message: "Unable to localte Ajax Zone '...' for dynamic update". In several posts, and JIRA Cases, the solution has been to bind the zone's id parameter. I am not sure how this is done exactly. I have used: @Component(id="zoneName") private Zone _zoneName; , but that doesn't seem to be doing the trick. Can someone tell me how to bind the id parameter of the zone in the component class so that Tapestry will leave it alone during a partial ajax update? Thanks! -- View this message in context: http://www.nabble.com/-T5--Nested-Zones-tp21060828p21060828.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: T5 - Authentication filter
Otho did you ever find a solution to the the Class Cast Exception when using
the @ApplicationState annotation? I have read and reread the docs and it
seems like my code should work. I am basically just trying to create an ASO
with the default persistence strategy and constructor. So I am not sure I
understand why I am getting the class cast exception.
-BGregory
Otho wrote:
>
> Hi all!
> Was there a solution to this really strange ClassCastException already?
>
> I have the same problem in the following circumstances:
>
> public class Search extends BaseComponent
> {
> @Component
> private Form simpleSearch;
>
> @ApplicationState
> private SimpleSearchString simpleSearchString;
>
> private String searchTerm; // wil be populated by the form;
>
> /* Form Handler */
>
> String onSuccess()
> {
> if (searchTerm == null)
> return null;
>
>
>getSimpleSearchString().setSearchTerm(searchTerm);
> return "ExtendedSearch";
> }
>
> public SimpleSearchString getSimpleSearchString()
> {
> return simpleSearchString;
> }
>
> This line gives the following stacktrace
>
> java.lang.ClassCastException myapp.state.SimpleSearchString cannot be cast
> to myapp.state.SimpleSearchString
> Stack trace
>
>- myapp.components.search.Search._$read_simpleSearchString(Search.java
>)
>- myapp.components.search.Search.getSimpleSearchString(Search.java:79)
>- myapp.components.search.Search.onSuccess(Search.java:53)
>- myapp.components.search.Search.handleComponentEvent(Search.java)
>
>
> This happens regardless of if I access simpleSearchString directly or with
> the getter.
> Any idead what causes this somewhat puzzling behaviour?
>
> Regards,
> Otho
>
--
View this message in context:
http://www.nabble.com/T5---Authentication-filter-tf3726392.html#a11607946
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
