Uh OK.Anthony Sykes wrote:I created something that functions similar to JPA.
It is also not designed for that. But you certainly can run SP´s with JPA.JPA did not seem very stored procedure friendly
Uh, how would you run a webapplication otherwise?plus I am not a big application server fan.
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.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.
Bauke Scholtz wrote:
Uh OK.Anthony Sykes wrote:I created something that functions similar to JPA.
It is also not designed for that. But you certainly can run SP´s with JPA.JPA did not seem very stored procedure friendly
Uh, how would you run a webapplication otherwise?plus I am not a big application server fan.
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.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.
Well, this roughly left behind just a Sun JSF Mojarra 1.2 implementation with the RichFaces component library.Anthony Sykes wrote:In a nutshell, I would like to use seam without jpa and without hibernate.
Bauke Scholtz wrote:
Well, this roughly left behind just a Sun JSF Mojarra 1.2 implementation with the RichFaces component library.Anthony Sykes wrote:In a nutshell, I would like to use seam without jpa and without hibernate.
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.
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.
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?
Consider Paul's rocket mass heater. |