Jsf form without entity component

[luuzz]

Hello,
Is it possible to use a session bean component property to map a jsf form without having to use an entity bean component ?
I tried it but it doesn't work.

[delphi'sghost]

It is possible.

Maybe you haven't defined the getters and setters on the interface for the session bean. If you post any error messages or results you get along with any code, that might help.

Any properties on the session bean are read and written to just like any other property is handled in JSF.

[luuzz]

I'm gonna try this, indeed i didn't put the getters on the interface.
Yhanks a lot.

[luuzz]

It's working great but i don't understand why i have to expose the setters and getters in the bean interface...
Thanks

[wschwendt]

"luuzz" wrote:
It's working great but i don't understand why i have to expose the setters and getters in the bean interface...
Thanks

if my understanding is correct, you have to the declare getters and setters in the so-called "business interface" of your EJBs because with the EJB(3) architecture you're never accessing EJB bean instances directly. Technically, when a EJBean is called, a container-generated proxy/stub object is called which in turn delegates to the EJB instance. These container-generated proxy/stub objects implement the same methods as declared in the business interface of your EJB, that's why you need to define a business interface.

[wschwendt]

correction, it should read:

if my understanding is correct, you have to declare the getters and setters in the so-called "business interface" of your EJBs because with the EJB(3) architecture you're never accessing EJB bean instances directly. Technically, when an EJBean is called, ...

[luuzz]

Ok I understand now.
Do you think it's a good idea to do it like this ?
Isn't it better to do the form mapping through a pojo component and use bijection in the session bean ?
Another question, using stateful session beans, should we still expose the getters and setters in the interface ?

[matt.drees]

Why wouldn't you want to expose getters/setters in the interface?

[luuzz]

usually sesion beans only imlement business methods ....

[azalea]

Now session beans can be backing beans in Seam application,
and usually backing beans have getters/setters.