Re: [trails-dev] Building code from cvs - Chris Nelson - net.java.dev.trails.dev

5 messages in net.java.dev.trails.devRe: [trails-dev] Building code from cvs

From	Sent On	Attachments
paul...@visi.com	Jun 10, 2005 12:55 pm
Chris Nelson	Jun 11, 2005 9:49 am
Paul Devine	Jun 19, 2005 11:20 am
Chris Nelson	Jun 19, 2005 3:13 pm
Rad Morka	Nov 15, 2005 6:22 am

Subject:	Re: [trails-dev] Building code from cvs
From:	Chris Nelson (cnel...@yahoo.com)
Date:	Jun 19, 2005 3:13:37 pm
List:	net.java.dev.trails.dev

Paul,

In your domain model you need to be sure to override isEquals. Both the first 2 problems can be attributed to this I think. I usually use the Apache commons EqualsBuilder. For the Tomcat thing, I have not seen that. What version of Tomcat? Does this appear in the log or on the screen?

--Chris

--- Paul Devine <paul...@visi.com> wrote:

Hi Chris

I converted my code over to the latest Trails code from CVS. I'm now using annotations for persistence. Plan to start taking a look at validations next. I kept some migration notes in and stumbling blocks i ran into. If people are interested in details I can post them here or blog them.

There are a couple of minor issues i'd appreciate help on. These may be my not understanding the default functioning on edit pages or current limitations in Trails? I'm not sure. -- property that is backed by a selection list does not seem to be defaulting to current value on display (for example in displaying an Album that is for Artist "Gorillaz" in the database, all the artists are shown as possible values for 'Artist' on the Album page, but Gorillaz is not the default selection to indicate that is the current value.) -- bi-directional one-to-many relationships from the many side do not appear to be displaying correctly to me (for example in displaying an Album that has tracks A and B, all tracks are shown in the "Available" panel rather than the "Selected" panel. I would expect the current tracks to be in the Selected panel.) -- a single run-time ERROR message is showing the very first time i hit an edit page after (re)starting Tomcat. Not yet sure what this means. It is: ERROR org.apache.tapestry.BaseComponentTemplateLoader - Template for component DefaultEdit/$ObjectForm.propertyTable.propertyEditor does not reference embedded component: idInsert.

Thanks -- Paul

----- Original Message ----- From: "Chris Nelson" <cnel...@yahoo.com> To: <paul...@visi.com>; <de...@trails.dev.java.net> Sent: Saturday, June 11, 2005 11:49 AM Subject: Re: [trails-dev] Building code from cvs

Paul,

First off, thanks for being an early adopter :) Sounds like you've found a few things I need to clean up. I checked into a new version of build.xml to call build-hibernate-config. Also, I removed the JAX_RPC dependency. Initially I was using their APT ant task, but then I found that ant had already made such a task and so I am using theirs. It will be part of Ant 1.7, but for now I need to install it so you need to be sure and have your ANT_HOME env variable set for the build to be able to do this. I just ran the all target and it worked.

Probably the best way to upgrade your project (if you don't have any custom pages) is to use the create-new-project and copy in your domain objects. If you have custom pages there may be some changes you need to make.

Let me know how it goes. Also, don't get too attached to the Appearance annotation, I'm about to do some refactoring. My thought is to separate into PropertyDescriptor and ClassDescriptor and have their attributes be the same as the interface properties.

Thanks,

Chris

--- paul...@visi.com wrote:

Hi all

I'm trying to build the "latest" code from cvs (actually a couple days old.)

Here's my `trail` so far (excuse the bad pun, it is Friday). I'm on jdk 1.5.0_02 and using the default ant target

1. build initially failed because it depended on jax-rpc which i didn't have. went and got jax-rpc, seemed to be the early access release of jax-rpc 2 that is needed for the annotation processing tool (?) pointed environment variable JAXRPC_HOME to the relevant install directory

2. build got further but failed on the `hibernatedoclet` with "Error parsing File ...\trails\test\org\....\Baz.java : Lexical error: .... It seemed to be complaining at the hibernate annotations encountered during doclet processing. But I'm not sure.

3. i modified the depends in the `all` target in build.xml to replace `hibernatedoclet` with `build-hiberante-config` 9and moved it after compile.) The former seemed to be generating mappings using the xdoclet for the source under test, the latter appeared to be doing so from annotations for the same files.

4. The full build now completes compile, unit tests, etc.

Did I do the right thing here? I am about to convert my code over from trails 0.6 to the latest trails, as amongst other things i want to get familiar with the annotations and make use of the textarea feature i recently read about. Anything else i'll need to watch out for in that conversion?

Thanks -- Paul Devine

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-...@trails.dev.java.net For additional commands, e-mail: dev-...@trails.dev.java.net

---------------------------------------------------------------------

To unsubscribe, e-mail: dev-...@trails.dev.java.net For additional commands, e-mail: dev-...@trails.dev.java.net

	Start a set with this search
	Include this search in one of my sets
	Exclude this search from one of my sets