Win a copy of Kotlin in Action this week in the Kotlin forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

examples using SEAM + pojo + Tomcat  RSS feed

 
Anthony Sykes
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am a newbie to seam and I am looking for examples showing how to use SEAM with POJO. The vast majority of examples I found thus far deal with EJB3 and SEAM. Also, I am using Eclipse version 3.3.2. I really need something kind of end to end, how to take a jsf based project without seam and turn it into a seam project. I found one good example but I became confused when I saw ejb items in it. I am trying to avoid using an application server, jboss or weblogic, for example.
 
Anthony Sykes
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
maybe I should re-phrase the question, does anyone have experience with SEAM and POJO?
 
Bauke Scholtz
Ranch Hand
Posts: 2458
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"POJO" is a very general term.

What exactly is the functional requirement? Why do you want Seam while you don't want EJB3?
 
Anthony Sykes
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I created something that functions similar to JPA. JPA did not seem very stored procedure friendly plus I am not a big application server fan. I basically want to use POJO's with the tool I created in order to move data from the client to the server and back again. Is this possible?
 
Bauke Scholtz
Ranch Hand
Posts: 2458
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Anthony Sykes wrote:I created something that functions similar to JPA.
Uh OK.
JPA did not seem very stored procedure friendly
It is also not designed for that. But you certainly can run SP´s with JPA.
plus I am not a big application server fan.
Uh, how would you run a webapplication otherwise?
I basically want to use POJO's with the tool I created in order to move data from the client to the server and back again.
Again, "POJO" is a too general term. Also "POJO's with the tool I created" makes no sense to me. Please be specific. At least "move data" makes me think that you´re just talking about data transfer objects (DTO's)? Also, how to transfer data between client and server fully depends on the protocol which you´re using. Is it HTTP? Is it just a website? You want to pass Java Objects between client and server? Why? In case of a website you need to convert them to String and vice versa anyway. A HTML page is nothing less or more than one big String.
 
Anthony Sykes
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In a nutshell, I would like to use seam without jpa and without hibernate. I already have a JPA-like library and would like to use this instead of jpa or hibernate. So, for example, in a given Action class I need to somehow replace the "EntityManager" with the class I already have for that purpose. Would it be that simple or is there more going on behind the scenes that would prevent me from doing this?

Bauke Scholtz wrote:
Anthony Sykes wrote:I created something that functions similar to JPA.
Uh OK.
JPA did not seem very stored procedure friendly
It is also not designed for that. But you certainly can run SP´s with JPA.
plus I am not a big application server fan.
Uh, how would you run a webapplication otherwise?
I basically want to use POJO's with the tool I created in order to move data from the client to the server and back again.
Again, "POJO" is a too general term. Also "POJO's with the tool I created" makes no sense to me. Please be specific. At least "move data" makes me think that you´re just talking about data transfer objects (DTO's)? Also, how to transfer data between client and server fully depends on the protocol which you´re using. Is it HTTP? Is it just a website? You want to pass Java Objects between client and server? Why? In case of a website you need to convert them to String and vice versa anyway. A HTML page is nothing less or more than one big String.
 
Bauke Scholtz
Ranch Hand
Posts: 2458
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Anthony Sykes wrote:In a nutshell, I would like to use seam without jpa and without hibernate.
Well, this roughly left behind just a Sun JSF Mojarra 1.2 implementation with the RichFaces component library.
 
Anthony Sykes
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
what is mojarra 1.2, is this a version of seam? Are you saying is is not possible to effectively use SEAM without jpa or hibernate?

Bauke Scholtz wrote:
Anthony Sykes wrote:In a nutshell, I would like to use seam without jpa and without hibernate.
Well, this roughly left behind just a Sun JSF Mojarra 1.2 implementation with the RichFaces component library.
 
Bauke Scholtz
Ranch Hand
Posts: 2458
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mojarra is the Sun Reference Implementation of JSF 1.2 API. You can download it here: http://javaserverfaces.dev.java.net
Alternatively you could also use MyFaces, but as far as I know that isn´t been used in Seam.

Seam is nothing less or more than a buzzword for some existing API´s gobbled together. Exactly as Ajax is.
 
Anthony Sykes
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From reading up on seam, I believe that it fills alot of gaps that seem to exist in jsf, so I definitely want to use it. However, I'm just looking for a way to use it without jpa or hibernate. For example, suppose I wanted to use an alternate approach for "persisting" data when an action is fired. An action that saves user information when a button is clicked. Currently, as far as I have gathered from the small number of examples I have found, An action class would have an EntityManager instance variable with an annotation tied to it. When the user performs the action, the EntityManager has the task of persisting the data. It seems like it should be easy to replace the EntityManager with another approach. Lets say, for example I am a glutton for punishment and wanted to use JDBC and CallableStatement in place of JPA or hibernate. Would I still be able to do that or are JPA and hibernate my only two options? Additionally, how close are seam and JPA tied together?

Bauke Scholtz wrote:Mojarra is the Sun Reference Implementation of JSF 1.2 API. You can download it here: http://javaserverfaces.dev.java.net
Alternatively you could also use MyFaces, but as far as I know that isn´t been used in Seam.

Seam is nothing less or more than a buzzword for some existing API´s gobbled together. Exactly as Ajax is.
 
Bauke Scholtz
Ranch Hand
Posts: 2458
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
From reading up on seam, I believe that it fills alot of gaps that seem to exist in jsf, so I definitely want to use it.

Don´t you forgot RichFaces? It is the JSF component library as used in Seam.

You are still too general. For instance, what gaps are you talking about?
 
Anthony Sykes
Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I actually want to use RichFaces/Ajax4JSF with SEAM. Just to name one thing, I like how you can pass parameters into actions from a jsf page. Not to mention the conversation states. It has alot of features I really like. I just want the flexibility I mentioned with the JDBC and CallableStatement example I mentioned earlier.


Bauke Scholtz wrote:
From reading up on seam, I believe that it fills alot of gaps that seem to exist in jsf, so I definitely want to use it.

Don´t you forgot RichFaces? It is the JSF component library as used in Seam.

You are still too general. For instance, what gaps are you talking about?
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!