That pom shouldn't be there, I deleted it from trunk.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121549#4121549
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4121549
___
The pom.xml has this in it:
| version@seam.version@/version
|
The 2.0.0GA version does not have a pom.xml in the dvdstore examples dir.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121400#4121400
Reply to the post :
I just downloaded: JBoss Seam 2.0 - 2.0.1.CR1
Ran the maven command from the dvd examples directory - didn't change anything
except the root build.properties to point to my JBoss AS home dir.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121389#4121389
Hi
This line is quite informative:
| Downloading:
http://repo1.maven.org/maven2/org/jboss/seam/parent/@seam.version@/[EMAIL
PROTECTED]@.pom
|
Looks like the seam version is wrong somehow, instead of a proper version
string it is @seam-version@.
If you defined this parent dependency
Thanks for your reply, Pete.
So if I wanted to make Seam manage the entity, I could remove the home entity
(which extends EntityHome and gives you persist, delete, edit, etc), annotate
the entity with @Name and then reference the entity in a xhtml file using
| #{EntityName.propertyName}
|
It's not if you don't want the entity to be a Seam component. You can use a
Seam component like EntityHome to manage the entity instead.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121034#4121034
Reply to the post :
I personally would much prefer the EntityHome approach to annotating entities.
I the aim is to not have to write entityHome.instance.property, then just add a
factory to components.xml
factory name=entityName value=#{entityHome.instance} /
Why? I think the lifecycle is much clearer like this,
THANK YOU!!!
I've been confused with all the different ways of working with Seam and you
answered so many of my questions in just these few posts. I'll look into
working more with the EntityHome.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121046#4121046
Thanks for the advice. I will try that, I never thought of that since
seam-setup asks for the folder every time and has not indicated anything like
Resetting your input with default folder 'C:\Applications\...'.
View the original post :
I think you need to fix the location of your jboss home in the seam gen
build.properties file. It thinks that C:\Applications\... is where JBoss is
installed.
In the mean time you can copy your ear and ds.xml from C:\Applications\... to
your JBoss deploy directory.
View the original post :
At first glance I can see one wrong thing, your entity component name is
LoginAccount, so if you want to biject it, you should declare it as follows:
| @In @Out
| public LoginAccount LoginAccount;
|
or
| @In(value=#{LoginAccount}) @Out(value=#{LoginAccount})
| public
Well, I think I can spot at least 3 errors to begin with:
(1) The value bindings should be #{account==null}, #{account.realName}, etc, OR
you need to get rid of the @Out annotation, and add a getAccount() method.
(2) @Name(LoginAccount) should be @Name(loginAccount), names are supposed
to be
hmmm I noticed that, but I intentionally didn't want to give the instance
the same name as the entity. What if I wanted to deal with 2 LoginAccounts in
my conversation?
I know the user registration is not a good example where I might want to have 2
instances of the same entity class, but
Typo in the second option I mentioned, it should be:
|@In(value=#{LoginAccount})
| @Out(value=#{LoginAccount})
| public LoginAccount account;
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4053648#4053648
Reply to the post :
anonymous wrote : hmmm I noticed that, but I intentionally didn't want to
give the instance the same name as the entity. What if I wanted to deal with 2
LoginAccounts in my conversation?
|
| I know the user registration is not a good example where I might want to
have 2 instances of
(In my experience of helping thousands of people learn Hibernate and Seam,
early frustration is always a result of trying to do too much at once, and
ignoring the resources - docs, examples - that already exist.)
View the original post :
Hello Gavin,
thanks for your response and I can understand your frustration about dealing
with people that are a bit too enthusiastic at start. It's just that no 2
developers write the same HelloWorld application. And since Seam looked easy to
me, I tried to do HelloWorld + 10%. Reading a lot
17 matches
Mail list logo
