[seam-dev] Seam 2.1.1.CR1 release testing status

[Dan Allen]

I don't think an issue was created. I'll try to investigate in a bit.
I'm pretty sure this likely a configuration issue (not an issue in the
libraries).

-Dan

On Fri, Dec 5, 2008 at 2:08 PM, Jay Balunas <jbalunas at redhat.com> wrote:
> Hi Dan,
>
> Was a jira ever created for this issue?  I searched but I did not want to
> put in a duplicate.
>
> Also is this a seam issue or htools, or both ;-)
>
> I'l still seeing it in 2.1.1.CR2.
>
> -Jay
>
>
> On Nov 20, 2008, at 9:35 PM, Dan Allen wrote:
>
>> On Thu, Nov 20, 2008 at 5:44 PM, Max Rydahl Andersen
>> <max.andersen at redhat.com> wrote:
>>>
>>> Dan, you should fix this in htools instead ;)
>>
>> I think it should be both places. Getting past the "seam setup" is.
>> just about populating the build.properties file. Here, we are just
>> saying "oh, you probably meant uppercase, just to be correct about
>> it". It makes the user aware of the requirement of the JDBC driver.
>> But then, if a lowercase schema name is fed into htools, then we
>> should uppercase it there to make it more intelligent.
>>
>> -Dan
>>
>>>
>>> /max
>>>
>>>> Yes, this is a new feature to uppercase oracle schema names (since
>>>> oracle schema names must be uppercased). But we are running against
>>>> mysql, so why is it being uppercased? What database is being used?
>>>>
>>>> Please provide me with the build.properties being used to generate the
>>>> project. Also, verify that it is MySQL that seam-gen is running
>>>> against. Whatever my settings are don't cause this problem, so I need
>>>> to reproduce it.
>>>>
>>>> -Dan
>>>>
>>>> On Thu, Nov 20, 2008 at 2:29 PM, Jay Balunas <jbalunas at redhat.com>
>>>> wrote:
>>>>>
>>>>> Hi Dan,
>>>>>
>>>>> Jozef sent you email with the exception we was seeing I have attached
>>>>> it
>>>>> below.
>>>>>
>>>>>
>>>>>> [testng] ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] Unsuccessful:
>>>>>> create table seam.Person (username varchar(10) not null, address
>>>>>> varchar(600) not null, birthdate date, name varchar(100) not null,
>>>>>> primary
>>>>>> key (username), unique (username))
>>>>>> [testng] ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] invalid
>>>>>> schema
>>>>>> name: SEAM in statement [create table seam.Person]
>>>>>> [testng] ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] Unsuccessful:
>>>>>> create table seam.Vehicle (registration varchar(8) not null, state
>>>>>> varchar(2) not null, make varchar(50) not null, model varchar(50) not
>>>>>> null,
>>>>>> year integer not null, ownerUsername varchar(10), primary key
>>>>>> (registration,
>>>>>> state))
>>>>>> [testng] ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] invalid
>>>>>> schema
>>>>>> name: SEAM in statement [create table seam.Vehicle]
>>>>>> [testng] ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] Unsuccessful:
>>>>>> alter table seam.Vehicle add constraint FK779C270C2C1BBB19 foreignkey
>>>>>> (ownerUsername) references seam.Person
>>>>>> [testng] ERROR [org.hibernate.tool.hbm2ddl.SchemaExport] invalid
>>>>>> schema
>>>>>> name: SEAM in statement [alter table seam.Vehicle]
>>>>>> I am not sure why hibernate is trying to do something with the DDL at
>>>>>> all.
>>>>>> In project setup  I've chosen that my tables are already at database
>>>>>> and
>>>>>> I
>>>>>> do not want then to be recreated each time.
>>>>>
>>>>> I do get it now. Datasource used for tests is not the same as default.
>>>>> But
>>>>> the question why creating tables fail remains.
>>>>>
>>>>> Dan, have you
>>>>>>
>>>>>> seen this before?
>>>>>> This happens in both EAR and WAR project. To reproduce create new
>>>>>> project,
>>>>>> generate entities, create new action and form and run tests. Note that
>>>>>> these
>>>>>> errors do not affect test results.
>>>>>
>>>>> \
>>>>> On Nov 20, 2008, at 1:03 PM, Dan Allen wrote:
>>>>>
>>>>>>> Seam-gen -  there are errors being displayed when the tests are
>>>>>>> running
>>>>>>> in
>>>>>>> seam-gen generated projects however tests pass.
>>>>>>
>>>>>> What is the error? I am playing with seam-gen a bunch right now, so I
>>>>>> can check it out.
>>>>>>
>>>>>> -Dan
>>>>>>
>>>>>> --
>>>>>> Dan Allen
>>>>>> Software consultant | Author of Seam in Action
>>>>>>
>>>>>> http://mojavelinux.com
>>>>>> http://mojavelinux.com/seaminaction
>>>>>>
>>>>>> NOTE: While I make a strong effort to keep up with my email on a daily
>>>>>> basis, personal or other work matters can sometimes keep me away
>>>>>> from my email. If you contact me, but don't hear back for more than a
>>>>>> week,
>>>>>> it is very likely that I am excessively backlogged or the message was
>>>>>> caught in the spam filters.  Please don't hesitate to resend a message
>>>>>> if
>>>>>> you feel that it did not reach my attention.
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> /max
>>>
>>
>>
>>
>> --
>> Dan Allen
>> Software consultant | Author of Seam in Action
>>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>>
>> NOTE: While I make a strong effort to keep up with my email on a daily
>> basis, personal or other work matters can sometimes keep me away
>> from my email. If you contact me, but don't hear back for more than a
>> week,
>> it is very likely that I am excessively backlogged or the message was
>> caught in the spam filters.  Please don't hesitate to resend a message if
>> you feel that it did not reach my attention.
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>



-- 
Dan Allen
Software consultant | Author of Seam in Action

http://mojavelinux.com
http://mojavelinux.com/seaminaction

NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.