GWT + Model Meta data issue about slim3

[GoogleCodeExporter]

Sorry, I selected the issue as Defect by Mistake. Please read it as Issue to 
verify

Original comment by [email protected] on 19 Jan 2010 at 8:56

[GoogleCodeExporter]

Hi muneendra, thanks for your evaluation.

> The issues is GWT expects source files for Slim3 Meta classes as well, It
> is quite a big task for us to create dummy classes for every Meta class.
> otherwise, GWT don't compile model/entity classes.Because of this drawback
> we are in a position to go ahead with Slim3. We will face issues when
> entity model evolves into big.

You need to configure some settings before you use Slim3 on GWT.
Define GWTServiceServlet in web.xml as follows:

<servlet>
    <servlet-name>GWTServiceServlet</servlet-name>
    <servlet-class>org.slim3.gwt.server.rpc.GWTServiceServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
</servlet>

<servlet-mapping>
    <servlet-name>GWTServiceServlet</servlet-name>
    <url-pattern>*.s3gwt</url-pattern>
</servlet-mapping>

And define module file as follows:

<module>
    <inherits name="com.google.gwt.user.User" />
    <inherits name='org.slim3.gwt.emul.S3Emulation' />

    <source path="client" />
    <source path="shared" />
</module>

And execute gen-model task in build.xml.
A model will be created in <root>.shared.model package,
and a meta data of the model will be created in <root>.server.meta package.
So GWT does not include the meta data of the model in the source path.

Dummy classes for GWT are included in org.slim3.gwt.emul.S3Emulation.

Sorry for the poor document of Slim3 on GWT.
I am going to prepare the document as soon as possible.

Original comment by [email protected] on 23 Feb 2010 at 1:30

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

おはよう　Higayasuo-さん、

Thank you for the reply.

Yes, we found the solutions for all issues with GWT+Slim 3. We really 
appreciate all
your work. 

In our evaluation, we dropped out GWT idea. We are using Strut 2+ Slim 3 model
features. It really works like a gem.

However, we still have one issue with Slim3 is that we want to check-in meta 
classes
into repository, but annotation process deletes all files including subversion 
files
during rebuild due to changes to model/entity files. Hope we can find some 
solution
to this soon.

Between, Do you live in Tokyo :).  I am in Tokyo as well.

Original comment by [email protected] on 23 Feb 2010 at 1:50

[GoogleCodeExporter]

次のメッセージから日本語で書くために頑張ります。

Original comment by [email protected] on 23 Feb 2010 at 1:50

[GoogleCodeExporter]

Good morning muneendra,

> However, we still have one issue with Slim3 is that we want to check-in meta 
classes
> into repository, but annotation process deletes all files including 
subversion files
> during rebuild due to changes to model/entity files. Hope we can find some 
solution
> to this soon.

I don't recommend that you commit meta classes into repository,
because meta classes are created from sources of the models automatically
when compiling.

Original comment by [email protected] on 23 Feb 2010 at 2:23

[GoogleCodeExporter]

I am afraid this is not the case. 
Yes, Meta files are generated automatically during clean build. Clean build 
doesn't
happen all the time specially when working in Team.

For example, I modified the entity and checked-in into repository.
My team mate immediately checked-out(through eclipse plugin) only modified file 
and
he gets compilation error because he doesn't have meta file and annotation 
process
doesn't generate meta file.

I guess annotation process may generate meta file if eclipse is restarted but i 
am
yet to test this case   

Original comment by [email protected] on 23 Feb 2010 at 2:34

[GoogleCodeExporter]

Between, if you are short of committers to the code, probably i can contribute 
if you
are interested ;)

Original comment by [email protected] on 23 Feb 2010 at 2:37

[GoogleCodeExporter]

Don't worry.

When your team mate check out a model,
Eclipse will compile it and create the meta class.

For example, I check-in slim3-demo project into repository
and no one encounter such a compilation error.

Original comment by [email protected] on 23 Feb 2010 at 3:41

[GoogleCodeExporter]

Even i think it should be in that way but somehow it was not working for us. We 
were
too busy evaluating slim3 so we said we will look into this later. I will get 
back to
the issue soon and check your suggestions. Thank you for all your support.

We still need to evaluate Scalability and performance of Slim 3 data model 
compare to
JPA 

Original comment by [email protected] on 23 Feb 2010 at 3:46

[GoogleCodeExporter]

> if you are short of committers to the code, probably i can contribute if you
> are interested ;)

Thanks muneendra,
Welcome to Slim3 project. I added you into our project as committer.

Original comment by [email protected] on 23 Feb 2010 at 4:16

[GoogleCodeExporter]

Hai what is this ddd-WMS..

I can see entity model diagram with words like 
入荷、出荷,入庫、在庫、倉庫、棚　etc

Are you guys into Warehouse management.I am also into WMS domain. We do have 
our own
Java/JEE framework.What a coincidence..

Original comment by [email protected] on 23 Feb 2010 at 4:27

[GoogleCodeExporter]

Original comment by [email protected] on 9 Apr 2010 at 8:44

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

you said :
And execute gen-model task in build.xml.
A model will be created in <root>.shared.model package,
and a meta data of the model will be created in <root>.server.meta package.
So GWT does not include the meta data of the model in the source path.

but nothing  in <root>.server.meta, should i change the settings at java 
compiler -> 
annotation processing -> generated source directory ?

thanks

Original comment by asharlohmar on 10 Apr 2010 at 11:18

[GoogleCodeExporter]

I am writing "Getting Started with GWT".
http://sites.google.com/site/slim3appengine/getting-started-with-gwt
It is under construction, but will help you.

Original comment by [email protected] on 11 Apr 2010 at 3:03

• Changed state: Started
• Added labels: Version-1.0.2

[GoogleCodeExporter]

asharlohmar: What slim3 does is.It does not include the source files.Source 
files are
saved in separate folder (not under eclipse src folder) but compiled class 
files are
included in path.

you can change the source directory by chaining annotation processing settings 
as you
described.

I don't use Slim3 with GWT rather use with Struts2. If I am right, GWT need 
source
file as well to compile.

Original comment by [email protected] on 12 Apr 2010 at 1:29

[GoogleCodeExporter]

Original comment by [email protected] on 23 Apr 2010 at 7:37

• Changed state: Fixed