loosing seam initialization (in particular injection) when u

[cyberanto]

Env: Seam2.0.1.CR1/JBoss4.2.0/JBoss Development Studio/Windows XP

I am having a problem with Injection failing to work for components which are programmatically added to the context, e.g.

in the Action Class:

Contexts.getSessionContext().set("catalogModel", newCatalog);

the ModelClass:

@Scope(SESSION)
@Name("catalogModel")
public class CatalogModel {

@Logger private Log log;

@In(create=true)
private SkuDAO skuDao;

etc.
}

log and skuDao are null; Of course, the class has been created using new CatalogModel() ... I have tried to obtain the Objects by Context.get() and Components.instance(), to no avail. Had to new them into existence.

catalogModel and skuDao show up as Seam Components in the server log during startup and e.g. the correct catalogModel is available to the web application. (the object does get set into the Context).


Any hints, suggestions?

[pmuir]

You can't instantiate a Seam component using the new operator - you must use injection or Component.getInstance()

[cyberanto]

Thanks Pete, Component.getInstance() works.

I still have an issue where a (legacy) DAO is returning a list of e.g. CatalogModel and the user selects one. With JSF, it is easy to set the backing bean to a particular object. The equivalent method in Seam, Context.set(name, object) sets the object, but does not initialize it as a Seam component.

I have started to look at your source code, have not yet found the salient point where an object returned by the EntityManager is turned into a Seam Bean.

What am I missing?

[cyberanto]

Oh, I see you are doing Class.newInstance() in Home.createInstance() and this will initialize correctly.

Or you are using the EntityManager to return a properly initialized object ... as in the wiki example ... of course these objects get created new also before being populated