I'm using the bea, formerly m7 nitro tool.  I was a little worried it wouldn't like the format, but it appears to be just fine with it.

On 5/13/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:


On 5/13/06, Kevin Galligan < [EMAIL PROTECTED]> wrote:
Wild.  Thanks for the response.  I can honestly say I saw nothing like that in the docs I had come across, but my research tends to happen when I'm too tired to code, so I could've easily missed it.

I just tried it, and it certainly does pick it up, although I'm having some trouble with managed properties off the bean (but that's a different issue to explore).

As a general jsf question, I know some tools generated a backing bean per page behind the scenes.  The naming scheme here seems odd to me, but does it happen to match the backing beans generated with these types of tools?

Java Studio Creator uses basically the same algorithm, for pretty much the same reason (there needs to be a way to tie the JSP page and the corresponding backing bean source class), but here it's needed at design time as well as at runtime.  NetBeans lets you decide what the mapping is, by virtue of letting you type whatever you want for the binding expressions.  I don't know the innards of the other tools well enough to know whether they provide something similar.

Craig


Reply via email to