mchytracek wrote:
When using attribute names on classes which begin with one lowercase
letter followed by a upercase letter generates a getter method. Spring seems to
use an other algorithm to generate the getter name it expects to be there.
(end of quote)
yeah, I strongly recommend agai
Hi Wouter
Seems it was my fault. When using attribute names on classes which
begin with one lowercase letter followed by a upercase letter generates a
getter method. Spring seems to use an other algorithm to generate the getter
name it expects to be there.
When modelling attribute names
I'm currently working on a similar issue:
are you saying you modeled a primitive boolean type attribute and the entity
has an isAttribute accessor which is not identified by the server ?
I have such cases in my entities and it's working fine, I use the same
configuration: Spring/Hibernate
Hallo Chad
You are right. JBoss 4.0.1 gave me a lot more information about the real Error
which seems to be that hibernate "Could not find a getter for in
class .".
As this is a boolean Type attribute there exist a getter "is" and a setter
"set...". No getter "get..." has bee
What version of Jboss are you using? 4.0.1sp1 seems to given more information
that 4.0.2 (if you're using 4.0.2).
--
Chad Brandon - [EMAIL PROTECTED]
http://www.andromda.org
_
Reply to the post : http://galaxy.andromda.org/forum/viewtopic.
Hi all
Since i added several classes in my project (uses Spring with
Hibernate) i get a EJBException (could not instantiate bean) after building
session factory. XMI exporting, code generation and compile is working without
errors.
Just for Info: If i drop some of the classes the log sh
Assum that there is a BaseObject with inheritance strategy of "subclass" and a
ConcretObject inherited from the BaseObject, and there is another object
OtherObject refenenced the ConcreteObject.
Then the SQL statements for these entities will be similar to the followings:
Create table BASE
Assum that there is a BaseObject with inheritance strategy of "interface" which
associate with a BaseObjectType (ManyToOne), and there are two subclasses
derived from the BaseObject, say ConcreteObject1 and ConcreteObject2
respectively. Then in the generated SQL statement, there are two
BASE_O
Hi,
I'm facing a strange problem with hibernate cartridge + postgresql :
I use the following code in a service method :
...
{
UserImpl user = new UserImpl();
user.setLogin(login);
user.setPassword(password);
user.setCreatedDate(new Date());
user.setLastLoginTim
