I was a complete newbie in January, so have recently followed the path you're
on. I think seam-gen's main benefit is just providing a project structure and
correct packaging of a seam app. The generation stuff was useful for my first
test page, but I haven't used it since. It's much better to
I tried creating a "without J2EE5" application directly based in the register
application... but... just failed... and couldn't find any posts (with answers)
of problems similar to the ones I had...
I also didn't like the fact that all examples share the same huge ant file
(makes it hard to unde
yeah, seam-gen caters for the majority by providing ee5 ootb. i'm not quite
sure *what* a "transient POJOs to persistent POJOS to J2EE5 tutorial" is... the
tutorial really builds up from basics!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043010#4043010
Hi!
well a "transient POJOs to persistent POJOs to J2EE5 tutorial" would be:
-First, transient POJOs: show me what can be done in
SEAM without JPA or Hibernate. (a really simple in memory POJOs example with 1
page first, and then 2 or three) ¿this part needs the microcontainer?
-Second, persiste
Perhaps, between each of the 3 steps of the tutorial, to show, the difference
between more or less integration with J2EE, the tutorial should try to use SEAM
"wrong" (trying to do something that can only be done with SEAM tutorial level
3, in tutorial level 1, and showing how to do it right)
Vi
anonymous wrote : the tutorial should try to use SEAM "wrong"
As a writer I can tell you that this is a very difficult approach. You should
not show readers something that doesn't work, the risk that part of it is
memorized is high. You can use that technique sometimes, but I don't think it's
a
Yes... I can see what you mean... but... then... how can we really learn "what
can, and can't be done in Seam on each level?" I mean... errors are going to
happen... and I have always loved tutorials with a troubleshooting are that
says "if you are seeing error, is because you are trying to
I really think you are coming from this upside down - Seam is *simplest* to run
in an EE5 container - and, obviously, JBoss AS is the most tested - using the
microcontainer or EEJB3 is *more complex*. Seam was built for EE5 environments
- elsewhere we provide code to make it more like an EE5 en
I agree... Seam is simplest to use in an EE5 container... perhpas my problem is
that I am used to other frameworks on which you learn the other way around:
1) How to do it without EE5
2) How to do it with EE5
I guess all this comes from the fact that I would love to use Seam over OC4J...
but fr
"fperedo" wrote : Hi!
| -First, transient POJOs: show me what can be done in
| SEAM without JPA or Hibernate. (a really simple in memory POJOs example
with 1 page first, and then 2 or three) ¿this part needs the microcontainer?
No, though one does get included in the Seam-PDF example. You can
10 matches
Mail list logo
