[Trinidad 1.0.3] backward compatibility

[Andrew Richards <An...@focus-solutions.co.uk>]

Hello all.

Can anyone tell me if Trinidad 1.0.3 is backward compatible with Trinidad 1.0.1? I have a reasonably complex legacy JSF application which I have tried porting to 1.0.3 for a number of reasons. Unfortunately the application fails miserably. Just taking a quick glance I can see MenuModel, PanelAccordian, TreeTable etc etc all fail in my application?

Are there any major configuration changes I need to make to port to Trinidad 1.0.3 ? Currently all I have done is changed the dependency in my maven pom.

Many thanks

Andy

RE: [Trinidad 1.0.3] backward compatibility

[Andrew Richards <An...@focus-solutions.co.uk>]

Ok I agree my description was rather vague; however I thought I may have missed something obvious. All of the components are on complex pages so I will have to pull the pages apart to provide test cases. I tested the three failing components in 1.0.2 & 1.0.3 as follows...

A pages are Apache Tiled and using IE 7

Trinidad 1.0.2

PanelAccordian -  does not expand
java: No stack trace
javascript:'console' is undefined

Complex panelPage -  fails completely, no tiling, some Trinidad menuItems
java: No stack trace
javascript: '_tURL' is undefined

treeTable: does not expand
java: No stack trace
javascript: 'console' is undefined

Trinidad 1.0.3

PanelAccordian -  does not expand
java: (If i try and expand more than once) WARNING: Event org.apache.myfaces.trinidad.event.DisclosureEvent[phaseId=INVOKE_
APPLICATION 5,component=CoreShowDetailItem[UINodeFacesBean, id=_id6],expanded=true] was delivered to a showDetail already in that disclosure state.
javascript: No exception

Complex panelPage -  fails completely, no tiling, some Trinidad menuItems
java: No stack trace
javascript: '_tURL' is undefined

treeTable: does not expand
java: No stack trace
javascript: No exception

I think I have seen some of the 1.0.2 javascript issues previously on the forum so I will investigate and try and provide simple test cases.

Thanks,

Andy

-----Original Message-----
From: Adam Winer [mailto:awiner@gmail.com]
Sent: 09 October 2007 22:47
To: MyFaces Discussion
Subject: Re: [Trinidad 1.0.3] backward compatibility

Yeah, we really could use info on whether it was 1.0.2 or 1.0.3
that causes the problems. And, since obviously we wouldn't
have released anything if the whole thing was broken, it's important
to make some attempt to say exactly what is failing and how, and
to provide a minimal testcase of something that does not work.

-- Adam


On 10/9/07, Simon Lessard <si...@gmail.com> wrote:
> Hello Andrew,
>
> It should be backward compatible, yes. However there was some big changes
> from 1.0.1 to 1.0.2, true AJAX PPR mainly. Do you get any exception stack
> trace or is it just the components refusing to work? Also, what happen if
> you use 1.0.2?
>
>
> Regards,
>
> ~ Simon
>
>
> On 10/9/07, Andrew Richards
> <Andrew.Richards@focus-solutions.co.uk >
> wrote:
> > Hello all.
> >
> > Can anyone tell me if Trinidad 1.0.3 is backward compatible with Trinidad
> 1.0.1? I have a reasonably complex legacy JSF application which I have tried
> porting to 1.0.3 for a number of reasons. Unfortunately the application
> fails miserably. Just taking a quick glance I can see MenuModel,
> PanelAccordian, TreeTable etc etc all fail in my application?
> >
> > Are there any major configuration changes I need to make to port to
> Trinidad 1.0.3 ? Currently all I have done is changed the dependency in my
> maven pom.
> >
> > Many thanks
> >
> > Andy
> >
>
>

Re: [Trinidad 1.0.3] backward compatibility

[Adam Winer <aw...@gmail.com>]

Yeah, we really could use info on whether it was 1.0.2 or 1.0.3
that causes the problems. And, since obviously we wouldn't
have released anything if the whole thing was broken, it's important
to make some attempt to say exactly what is failing and how, and
to provide a minimal testcase of something that does not work.

-- Adam


On 10/9/07, Simon Lessard <si...@gmail.com> wrote:
> Hello Andrew,
>
> It should be backward compatible, yes. However there was some big changes
> from 1.0.1 to 1.0.2, true AJAX PPR mainly. Do you get any exception stack
> trace or is it just the components refusing to work? Also, what happen if
> you use 1.0.2?
>
>
> Regards,
>
> ~ Simon
>
>
> On 10/9/07, Andrew Richards
> <Andrew.Richards@focus-solutions.co.uk >
> wrote:
> > Hello all.
> >
> > Can anyone tell me if Trinidad 1.0.3 is backward compatible with Trinidad
> 1.0.1? I have a reasonably complex legacy JSF application which I have tried
> porting to 1.0.3 for a number of reasons. Unfortunately the application
> fails miserably. Just taking a quick glance I can see MenuModel,
> PanelAccordian, TreeTable etc etc all fail in my application?
> >
> > Are there any major configuration changes I need to make to port to
> Trinidad 1.0.3 ? Currently all I have done is changed the dependency in my
> maven pom.
> >
> > Many thanks
> >
> > Andy
> >
>
>

Re: [Trinidad 1.0.3] backward compatibility

[Simon Lessard <si...@gmail.com>]

Hello Andrew,

It should be backward compatible, yes. However there was some big changes
from 1.0.1 to 1.0.2, true AJAX PPR mainly. Do you get any exception stack
trace or is it just the components refusing to work? Also, what happen if
you use 1.0.2?


Regards,

~ Simon

On 10/9/07, Andrew Richards <An...@focus-solutions.co.uk> wrote:
>
> Hello all.
>
> Can anyone tell me if Trinidad 1.0.3 is backward compatible with Trinidad
> 1.0.1? I have a reasonably complex legacy JSF application which I have
> tried porting to 1.0.3 for a number of reasons. Unfortunately the
> application fails miserably. Just taking a quick glance I can see MenuModel,
> PanelAccordian, TreeTable etc etc all fail in my application?
>
> Are there any major configuration changes I need to make to port to
> Trinidad 1.0.3 ? Currently all I have done is changed the dependency in my
> maven pom.
>
> Many thanks
>
> Andy
>