How did you disable schema validation in seam?
Is this a documented feature? Presumably this instruction to relax
schema-validation will filter down to the orm (hibernate) layer.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4033695#4033695
Reply to the post
Does tha mean you'd use
hibernate.hbm2ddl.auto=create
the first time round (if you wanted your schema generated for you based on
annotations on your entity beans) and then set
hibernate.hbm2ddl.auto=false ?
View the original post :
I came across a similar Exception with the 1.2.0Patch1 release (I haven't tried
this on 1.2.1 yet).
In short, some fields in my tables were deliberately of type char (rather than
varchar) to test out seam-gen and even though the entity beans were reveng'ed
by seam-gen, the expected type for
I manually coded my MoleculeHome (rather than create it by config in
components.xml) so it can suck out the Atom object (and the Compound) from the
context and get the id from the Atom object for use in the overridden persist.
I am not sure if this is a reasonable practice in seam but it seems
Is there a layman's (but accurate and clear) description of what entity
converters are for and how to use them.
I read everything google threw at me (search string: seam convertEntity)
including
http://wiki.jboss.org/wiki/Wiki.jsp?page=SeamEntityConverter
but am none the more certain about the
I get the following Exception when I run a project created by seam-gen.
1 - Do I need to do something to add this missing resource? Is it related to
browser cache ?
2 - How do I switch-off icefaces (code-geneartion) so my pages use simple
(x)html rendering (ie no javascript)?
23:34:02,406
In a seam gen generated app, I guess the ID field is included on the
create/edit eg Atom.Edit.xhtml pages, even if in the database the key (ID_)
is marked as auto-generated, because the jdbc meta-data may not be available to
help hibernate reveng this detail.
When I manually remove the ID input
I was just adding an atom to a molecule and trying to save.
When I refresh the page, the Exception stopped, so it's probably related to
FireFox caching stuff with stale ids (?)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4033491#4033491
Reply to the post :
OK, so the catbean.categories in
| h:selectOneMenu value=#{search.category}
| converter=#{catbean.converter}
| f:selectItem itemLabel=Any
itemValue=#{catbean.nullCategory} /
| f:selectItems
petemuir
That is precisely the sort of nudge we needed. I hope to have some more
feedback soon. If we can get something up and running, I'll post it here but
you can expect some more naive questions first.
I think we have a bit more of a learning curve to climb than we expected but I
think
I will be trying exactly that with 1.2.1, hopefully later this afternoon (UK).
I didn't get very far with the version current at the weekend and the forum has
not given much feedback (except for the very helpful quilleashm) yet.
I will post my findings but I am not quite optimistic at this
Thanks for your input.
Did you read the original post carefully - there's no need to answer unless you
know, or want to know, a bit about SEAM and have some advice/ideas/questions on
the topic and the issues it will raise.
View the original post :
Is there a suggested workaround? Is there a fix coming?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4031500#4031500
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031500
___
If you have a spare moment, could you please give a specific example of how I
can do as you suggest using SEAM and, in particular, seam-gen?
On Michael Yuan's website there is a link to a video where in a 5 min he
generates an app with seam-gen (via Eclipse). The intro text on the site says
The prupose of this post is to save future, new SEAM users hours if not days.
Given what SEAM is and what it is capable of, the solution for someone with
some relevant knowledge will probably take less time than it took to write
this. In theory, a solution will take only a few minutes to
Thanks Gavin.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4031394#4031394
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4031394
___
jboss-user mailing list
I have used seam-gen's generate-entities on a simple schema I knocked up (using
HSQLDB), whilst I learn the basics of SEAM, with a view to prototype a system
that will run against a legacy database.
There is a many-to-many relationship between 2 tables A (the auto-generated PK
is ID_) and B
I run the script below to generate some simple tables and insert a bit of data.
I use seam-gen to create my project settings and then generate a project (m2m)
and the entities.
I use the generated ant script to deploy.
I open the browser at the m2m home page.
I click on the A List menu and see my
javax.faces.el.PropertyNotFoundException: Bean:
q.BHome$$EnhancerByCGLIB$$fe5689a5, property: bId
I appreciate the detailed response, thanks Mike.
I have tried that and it certainly gets me past the deployment stage.
Now I can go to the B List and to the A List pages and Search works but,
when
It's probaby on BHome (that's where the code generation created it).
| public class BHome extends EntityHomeB {
|
| public void setBId(Long id) {
| setId(id);
| }
| ...
|
The exception says
Bean: q.BHome$$EnhancerByCGLIB$$fe5689a5, property: bId
View
Thanks monkeyden. As I wrote, I have been trying various combinations of the
things you mention while I try to learn how to develop a Seam application,
about JBoss and Hibernate.
The idea is to have 2 separate databases; one to store the dvdstore business
data only (my dvdstore hsqldb
That's done the trick, thanks.
So if I understand correctly,
1 - In the dvdstore app, hibernate.cfg.xml effects only jBPM. It has no impact
on how the entity beans are persisted.
2 - jboss-beans.xml is not relevant at all for the dvdstore example (I've
deleted it with no apparent side-effects).
Having used seam-gen to create my beans from an existing schema, on deploying
the ear, I got messages along the lines of
Wrong column type: PROJECT, expected: varchar(3).
So I guessed Seam (or Hibernate) is having trouble mapping back the beans to
the schema so I changed all the CHAR fields to
Could you please give a simple example of config required to run the dvd store
example in a way that jBPM uses a separate database (ie NOT the orders
database)?
I have tried several combinations of multiple persistence-units +
@PersistenceUnit and also leveraging the components.xml file (as
24 matches
Mail list logo
