Using Seam without any database dependencies

[serkan.s.eskici.online.nl]

Hi.

I've tried to use Seam without any dependencies on JPA/EJB/Hibernate/JTA/.. and so on, because I don't have any backend that depends on a database or any other storage, but for so far I was not able to make this work.

In our system we only have to make Webservice calls, that retrieve pojos or send data back to the backend that takes care for the CRUD on the database and ldap.

However, what seems to work is Hibernate Validations on Seam components without @Entity marked on the pojos. This is great, since I can use these validations on my JSF page.

I was wondering if someone knows whether Seam can be set up without any database dependency at all.

The reason why I want to use Seam is, because of its additions on JSF like the conversation scope, page navigation and other things in general like security, bijection, reporting support and so on.

[mail.micke]

What exactly do you mean with database dependencies? That you don't want any of the jars?

You can find more information about Seam's dependencies in the documentation

[serkan.s.eskici.online.nl]

Mikael Andersson wrote on Dec 19, 2008 14:27:


What exactly do you mean with database dependencies? That you don't want any of the jars?

You can find more information about Seam's dependencies in the documentation

Well, basically I want to start Seam without JPA, Hibernate, transaction managment and so on. It seems that Seam (core or some other parts) is highly coupled to JPA or any other non-JPA API's.

It always expects to have some entitymanager to be available.

And since I don't need Entity beans or persistence, I want to disable this functionality.

[mail.micke]

No no

Seam doesn't require any of that stuff.

Myself I'm using it without JPA/EntityManagers. Using it purely for its other awesome features.

Likewise all my backing beans are POJOs.

When I started I had some issues with exceptions being thrown due to no transactions being available or something similar (long time ago).

Adding this solved it(using 2.0.1.GA so might be different with latest):

     <core:init debug="true" transaction-management-enabled="false"/>
     <transaction:no-transaction/>

[serkan.s.eskici.online.nl]

This is exactly what I wanted to know.

I had the same problems while starting it up and some transactions errors showing up and other stuff.

So I guess that I don't need the jars for persistency anymore in my package ?

Im gonna test this in Seam 2.1 and let you guys now.

Btw, I assume that I can't use Hibernate Search on my Pojos anymore ? (Hibernate Validation does work on non-entity beans).