You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Rafa Pérez <ra...@gmail.com> on 2007/10/24 10:03:32 UTC
[Trinidad] Problems with dialogs
Hi all,
My scenario:
MyFaces 1.1.5
Trinidad 1.0.3
Seam 1.2.1
I am trying to migrate our application from ADF to Trinidad. Besides
the API changes, it's been a smooth change except for the dialogs. I
have been googling and found some discussions about problems with
dialogs and mappings, and changed our web.xml according to that
emails.
But I am still facing several problems. The dialog's window raises but
does not show anything. If I look the source code for the generated
frame, I find that the problem seems to be that the application is not
translating the jsp code into HTML.
Any hints appreciated. Thanks in advance,
- - Rafa
Re: [Trinidad] Problems with dialogs
Posted by Rafa Pérez <ra...@gmail.com>.
Hi all,
the problem was... mine. Sorry for the noise. Filter mappings by
extension were not the problem, as you pointed. I forgot to translate
the jsp form adf to trinidad...
Thanks for all,
- - Rafa
On 10/24/07, Rafa Pérez <ra...@gmail.com> wrote:
> No, neither logging warnings or errors. I have deployed the
> application to JBoss AS 4.0.4 and to Oracle OC4J 10.1.3.1 and I am
> facing this problem in both application servers. It is quite weird, I
> have been following the cycle of the request and all seems to be in
> order. The launchDialog method of the CoreRenderKit is called and the
> createView is called either. Do not know if there is any problem with
> Seam when it takes the control after Trinidad's processing of the
> request, but the same dialog was working perfectly with ADF.
>
> Could you tell me what else could I do to find the problem? Is the
> jsp's code translated into HTML by Trinidad or by Seam?
>
> Thanks for your help,
>
> - - Rafa
>
> On 10/24/07, Matthias Wessendorf <ma...@apache.org> wrote:
> > Hi,
> >
> > The mapping this is only present in myfaces 1.2.x.
> > I am using 1.0.3 and myfaces 1.1.5 with facelets. Works
> >
> > You've Seam inside your stack, never really used Seam.
> >
> > Do you notice some logging statements, like warnings ?
> >
> > Greetings,
> > M
> >
> > On 10/24/07, Rafa Pérez <ra...@gmail.com> wrote:
> > > Hi all,
> > >
> > > My scenario:
> > >
> > > MyFaces 1.1.5
> > > Trinidad 1.0.3
> > > Seam 1.2.1
> > >
> > > I am trying to migrate our application from ADF to Trinidad. Besides
> > > the API changes, it's been a smooth change except for the dialogs. I
> > > have been googling and found some discussions about problems with
> > > dialogs and mappings, and changed our web.xml according to that
> > > emails.
> > >
> > > But I am still facing several problems. The dialog's window raises but
> > > does not show anything. If I look the source code for the generated
> > > frame, I find that the problem seems to be that the application is not
> > > translating the jsp code into HTML.
> > >
> > > Any hints appreciated. Thanks in advance,
> > >
> > > - - Rafa
> > >
> >
> >
> > --
> > Matthias Wessendorf
> >
> > further stuff:
> > blog: http://matthiaswessendorf.wordpress.com/
> > mail: matzew-at-apache-dot-org
> >
>
Re: [Trinidad] Problems with dialogs
Posted by Rafa Pérez <ra...@gmail.com>.
No, neither logging warnings or errors. I have deployed the
application to JBoss AS 4.0.4 and to Oracle OC4J 10.1.3.1 and I am
facing this problem in both application servers. It is quite weird, I
have been following the cycle of the request and all seems to be in
order. The launchDialog method of the CoreRenderKit is called and the
createView is called either. Do not know if there is any problem with
Seam when it takes the control after Trinidad's processing of the
request, but the same dialog was working perfectly with ADF.
Could you tell me what else could I do to find the problem? Is the
jsp's code translated into HTML by Trinidad or by Seam?
Thanks for your help,
- - Rafa
On 10/24/07, Matthias Wessendorf <ma...@apache.org> wrote:
> Hi,
>
> The mapping this is only present in myfaces 1.2.x.
> I am using 1.0.3 and myfaces 1.1.5 with facelets. Works
>
> You've Seam inside your stack, never really used Seam.
>
> Do you notice some logging statements, like warnings ?
>
> Greetings,
> M
>
> On 10/24/07, Rafa Pérez <ra...@gmail.com> wrote:
> > Hi all,
> >
> > My scenario:
> >
> > MyFaces 1.1.5
> > Trinidad 1.0.3
> > Seam 1.2.1
> >
> > I am trying to migrate our application from ADF to Trinidad. Besides
> > the API changes, it's been a smooth change except for the dialogs. I
> > have been googling and found some discussions about problems with
> > dialogs and mappings, and changed our web.xml according to that
> > emails.
> >
> > But I am still facing several problems. The dialog's window raises but
> > does not show anything. If I look the source code for the generated
> > frame, I find that the problem seems to be that the application is not
> > translating the jsp code into HTML.
> >
> > Any hints appreciated. Thanks in advance,
> >
> > - - Rafa
> >
>
>
> --
> Matthias Wessendorf
>
> further stuff:
> blog: http://matthiaswessendorf.wordpress.com/
> mail: matzew-at-apache-dot-org
>
Re: [Trinidad] Problems with dialogs
Posted by Matthias Wessendorf <ma...@apache.org>.
Hi,
The mapping this is only present in myfaces 1.2.x.
I am using 1.0.3 and myfaces 1.1.5 with facelets. Works
You've Seam inside your stack, never really used Seam.
Do you notice some logging statements, like warnings ?
Greetings,
M
On 10/24/07, Rafa Pérez <ra...@gmail.com> wrote:
> Hi all,
>
> My scenario:
>
> MyFaces 1.1.5
> Trinidad 1.0.3
> Seam 1.2.1
>
> I am trying to migrate our application from ADF to Trinidad. Besides
> the API changes, it's been a smooth change except for the dialogs. I
> have been googling and found some discussions about problems with
> dialogs and mappings, and changed our web.xml according to that
> emails.
>
> But I am still facing several problems. The dialog's window raises but
> does not show anything. If I look the source code for the generated
> frame, I find that the problem seems to be that the application is not
> translating the jsp code into HTML.
>
> Any hints appreciated. Thanks in advance,
>
> - - Rafa
>
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org