Messages posted by: Stephan Albers

robokaso wrote:Could you share a short howto run the nightly snapshots with Grails 1.2?

The nightly build has been working with Grails 1.2 for the last couple of weeks (application and plugin).

Unluckily the "final" tickets for GrailsFlow 1.0 took longer than expected and for every 2 tickets we closed, we opened one new ticket with minor requests or bugs.

Now, we plan to release GrailsFlow 1.0 latest in the next two weeks and the demo application and plugin will be based on Grails 1.2.2.

We also have a development plan for 1.1 which includes compatibility with Grails 1.3.

Is the demo application supposed to be compatible with Grails 1.1.1 already?

We have made the changes for Grails 1.2 and they have been available in the nightly build for the last couple of weeks. The application that is installed on the demo server is still running the old release.

I will doublecheck with Grails 1.2.2 before we do the final release of GrailsFlow 1.0.

For GrailsFlow 1.1 we plan to compatible with Grails 1.3, which should come out in April/May.

We are improving the documentation for the 1.0 release. We have added more "how to's" for the most important problems and questions.

I hope this is helpful for everybody.

We have made the changes for Grails 1.2. The nightly build is working with Grails 1.2 for the last couple of weeks.

I will doublecheck with Grails 1.2.2 before we do the final release of GrailsFlow 1.0.

Dale wrote:Did you ever consider the possibility of keeping each domain object in its own table? Right now it just adds more column to the master "content" table to cover all possible fields for all domain classes. Maybe the content table could just store the versions and types, and point to the tables (probably through the code and reflection). I'm sure there are a lot of challenges with this approach (searching content for one?), but am wondering if you tried it?

Yes, we are thinking about it. The single table gets too many columns over time. The "table per class" mapping becomes problematic, because many queries get very ugly; often each sub class gets queried with an outer join (because of the reference to the parent class). So we might either put the parent reference into an independent table or we define the mapping for hibernate manually (which gives us additional mapping styles, that might be better for Weceem).

Whatever we do, this needs to be decided before 1.0 because we want the domain model to be stable by then.

Dale wrote:I've got a lot more questions. I'm trying to figure out how it works and how it will work with what I'm trying to do. Some of the documentation is out of date, some of it documents things not yet implemented (some tags). In general I'm looking at the source...

Yes, there is "room for improvement"

Dale wrote:A lot of my questions are about best practices for introducing your own domain objects, and providing the most efficient ways to edit them. (I want a Destination content type, for example, which will allow you to pick from a dropdown of destination types, like country,state,region,theme, city). Those types are loaded at startup through a private plugin which uses XML over HTTP to get the data from a different grails app on a different server, and then creates them as objects in a memory cache. How to get something like that to populate the dropdown in the editor view would be of interest to me. Not sure how to explain the questions I have.

Weceem can be used like any other Grails plugin, so you can define you own domain objects in your application or in your other plugins.

If you want your domain objects to be edited in the Weceem content editor, then you have to subclass the Weceem content class. However we currently don't have support for dropdown fields that get populated via a XML over http call. Please create a JIRA ticket (http://jira.jcatalog.com/), if you want that feature in the Weceem editor.

Dale wrote:Also, I'd be willing to help Weceem grow if needed....

That would be great. Documentation, bug reports, source code.. every help is appreciated.

Stephan

Anonymous wrote:I'm considering using weceem for a small project, and I would like to know what your release roadmap looks like with regard to the grails 1.2 status (see: http://old.nabble.com/Grails-1.2-Release-Status-Update-td26197771.html).

Will there be a corresponding weceem release for 1.2 RC1/final? In the mean time what grails/weceem release/codebase is recommended to use?

Yes, we will soon have a Weceem Release for Grails 1.2 RC1, please see:

http://forums.jcatalog.com/forums/posts/list/127.page

Stephan

Franklin Samir Dattein wrote:it is stated in the documentation page that Weceem is only supported by Grails RC-M2. However, this version is not even available in the Grails web-site for download.
Could I use RC-M4 with no problems?

Hello Franklin,

originally, we had several problems with the 1.2 betas, but we have now tested Weceem with Grails 1.2 RC1 and everything seems to work fine. We want to release 0.8 before christmas and will make sure, that it works with the latest version of Grails 1.2.

Stephan

Steve wrote:We're looking for speakers for the Sacramento Groovy User's Group:

http://groups.google.com/group/sacgru

Please let me know if you are interested!

Thanks for the invitation, however most of the team is currently located in Europe, so it would not be easy for us to make it. Scott Burch is located in Canada, so maybe it would be possible for him.

I would love to hear if there are any Weceem users in California.

Stephan

rochb wrote:With the release of the AppEngine GORM Plugin http://grails.org/blog/limcheekin/AppEngine+GORM+Plugin+Released, is there any chance that Weceem will be ported to GAE?

Yes, I think that this bring GAE a lot closer.
Marc Palmer was at the Groovy & Grails eXchange 2009 that was in London last week and some people where talking about Weceem on the GAE, so there might be other, who also want to try it out.

However we are currently working on 0.8 and that is all about Grails 1.2 final, Node level security, performance/caching and bugs. The release after 0.8 we will focus on the blog and wiki functionality and we won't have time for GAE before that is done.

Stephan

demo wrote:What about some docs on Grailsflow?

Hello,

we have prepared an improved documentation for the 1.0 release. We have a basic users guide that describes the application and a developers guide with a couple of "how to's". The docs are currently in local files and we will integrate them in the GrailsFlow website.

Stephan

(Message from SteveBoyd; moved into an independent thread)

I'm in the process of trying to integrate GrailsFlow into my existing application. I was looking for the plugin so that I can install it. Any help would be great.

The plugin and the GrailsFlow application are available from the download page
http://www.grailsflow.org/downloads

The plugin can be installed using the regular Grails mechanisms. The process is described in
http://www.grailsflow.org/installation/plugin

roy wrote:http://www.weceem.org

Im getting a server error.

Thanks for letting us know. We know about the intermittent problem. Permgen is getting used up by template GSPs not being cached, so the server comes down.

The ticket is: http://jira.jcatalog.com/browse/WCM-315

A new plugin release soon will fix this. For now we are restarting the server every couple of days automatically.

Anonymous wrote:Now grails released 1.2-M4, it is very stable now. From 1.2-M2 which Weceem began to upgrade, there are many bug fixed.

Does the team have any plan to upgrade GrailsFlow to Grails 1.2? I want to use it in my running project.

Yes, GrailsFlow 1.0 will be compatible with Grails 1.2.

See http://forums.jcatalog.com/forums/posts/list/37.page for more details about the release.

Anonymous wrote:Any update for the GrailsFlow 1.0-final released date?

We only have 6 tickets left, that need to be implemented so the development is nearly done. We are currently waiting for Grails 1.2 to come out, because we want to make sure, that we are compatible with that release. We are currently testing with Grails 1.2-RC1 to make sure, that there are no bad surprises when the final Grails version is available.

From October to November 2009, we had massive problems with spam in our forums. Therefore, we did not answer the forum questions for a couple of weeks. Sorry for that.

We deleted and cleaned up the forums, but our hope, that this would reduce the spamming activity was wrong. In fact the number of spam posts increased to nearly 10.000 before we finally gave up.

We now:
- require registration, so you cannot post anonymously anymore
- we moderate all threads and all forum messages.

We try to review and approve the forum messages on a daily basis, however depending on our other activities, it sometimes may take longer. I hope that this is in the interest of all users and that this will improve the quality of the forums.

Stephan Albers for the Forum Team of
GrailsFlow, Weceem and XSLfast