Hello! Thanks for the replies. I forgot to subscribe to the list so I will
link the previous mails Problem with converting to myfaces (custom
components) <http://markmail.org/message/nlhq5ceuufwcc7cn>
To clarify these are indeed custom components built from scratch. Similar
level to Richfaces 3.3.3 in complexity but home brewed completely so
there's a lot of code.
Leo, you are completely right about why our code breaks - it is adapted
only to mojarra. I am a fan of the myfaces project (that's why i'm working
on the switch) and I have no change requests.
I was just hoping for some advice on how to solve it.
Must I branch the logic in the code?
if (myfaces) {
}
else {
}
As I said it was a big mistake not testing with myfaces when the components
was built and I am just looking for the best way to clean up the mess :-)
Anyways I am very thankful for the project and fui it is my obvious first
choice. I am even willing to spend weeks on these components if need be.
Best regards / Karl
2013/2/14 Karl Kildén <karl.kil...@gmail.com>
> Hello!
>
>
> We have decided to upgrade to myfaces. Problem: We have about 30 or so in
> house components and a lot of things stopped working. Here's a concrete
> problem we would really appreciate some help with:
>
> we use onDoubleClick on our datatable and our js function receives:
>
> tr#tableRow:inbox:supplierInvoicesTable:0:0.odd <-- Mojarra
> tr#tableRow:inbox:supplierInvoicesTable:0.odd <-- Myfaces
>
> Now the number is the row, no Idea why mojarra puts another number in
> there but our code is adapted to it. Any idea why there's a difference? We
> of course needs our own components to a) work and b) be vendor independent.
>
> Obviously a mistake to never test it with myfaces during development.
> Further autogenerated ids, I sadly suspect that people have hardcoded in
> generated ids in the components from mojarra - I assume those will break as
> well?
>
>
> Right now it goes like "it feels quicker wow" but.... Nothing works :-)
>
>
> best regards / Karl
>
