Specifing the pattern for source path

[Asif Rajwani]

Is there anyway to tell the source tag to pickup the selected set of
files, instead of picking up everything in the package and subpacakge.

<source path="dataaccess/VO*"/> or <source path="dataaccess/abc.java/
>

We have business modules in different packages with well define
interfaces. Input to all the methods in the interface is POJO and
output is also POJO. We would like to use these POJO on client side as
well. These POJO resides in the same package as the business logic. if
we try to set the source path in *.gwt.xml to business module package
it fails, as there are classes there which could not be converted.

Putting all these classes in different package really would not make
sense in our case. If this capability is not available, is there any
plan to add it. Is there any easy workaround in the mean time.

[Peter Blazejewicz]

hi,

the "public" tag does not suport ant-like filesets, etc:
http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.DeveloperGuide.Fundamentals.html#Modules

try to define different project in Eclipse (just sample) and import it
to main project path, If I remember well we can defin exlusion/
inclusion pattern that way between projects (i.e without export
jar.s),

regards,
Peter

[Asif Rajwani]

Peter,

Thanks for the suggestion. I will try it out.

I am sure lot of developer's would like to have this feature, is there
any plan to add this feature?, any other ideas how to deal with it.

On Feb 6, 4:05 pm, Peter Blazejewicz <peter.blazejew...@gmail.com>
wrote:
> hi,
>
> the "public" tag does not suport ant-like filesets, etc:http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.De...

>
> try to define different project in Eclipse (just sample) and import it
> to main project path, If I remember well we can defin exlusion/
> inclusion pattern that way between projects (i.e without export
> jar.s),
>
> regards,
> Peter
>
> On Feb 6, 4:20 pm, Asif Rajwani <asif_rajw...@yahoo.com> wrote:
>
>
>
> > Is there anyway to tell the source tag to pickup the selected set of
> > files, instead of picking up everything in the package and subpacakge.
>
> >  <source path="dataaccess/VO*"/> or <source path="dataaccess/abc.java/
>
> > We have business modules in different packages with well define
> > interfaces. Input to all the methods in the interface is POJO and
> > output is also POJO. We would like to use these POJO on client side as
> > well. These POJO resides in the same package as the business logic. if
> > we try to set the source path in *.gwt.xml to business module package
> > it fails, as there are classes there which could not be converted.
>
> > Putting all these classes in different package really would not make
> > sense in our case. If this capability is not available, is there any

> > plan to add it. Is there any easy workaround in the mean time.- Hide quoted text -
>
> - Show quoted text -

[Miguel Méndez]

Please see issue 2003 to see if addresses your needs.

[gregor]

Hi Asif,

I had exactly the same issue. I came up with a short term solution by
moving GWT exportable domain classes down a level to artificial
packages . e.g.

com.foo.app.domain.module
com.foo.app.domain.module.gwt

and reference the latter in app.gwt.xml source path statement. I do
not like this at all, and I called these packages "gwt" because they
had no other purpose and I couldn't think of anything else to call
them (apart from something longer involving "gwt!).

I was wondering if the GWT compiler could reasonably use an extra
attribute or tag in the source tag similar to ant FileSet to screen
out non-compatible domain classes within packages. e.g.

<source path="com.foo.app.domain.module">
<fileset includes="*POJO.java"/>
</source>

or

<source path="com.foo.app.domain.module" includes="*POJO.java">

regards
gregor






On Feb 7, 1:11 pm, "Miguel Méndez" <mmen...@google.com> wrote:
> Please see issue
> 2003<http://code.google.com/p/google-web-toolkit/issues/detail?id=2003>to

> see if addresses your needs.
>

> --
> Miguel

[Asif Rajwani]

gregor,

Thanks for the suggestion, it would work. I agree that, it is not very
clean, but may be better than duplicating the classes.

It will require changing about 15 packages on our end and all the
calling code would need to be refactored, plus we will have all the
convertable POJO in one package (gwt) and those which cannot be
converted in different package, very artifical structure.

Can somebody from GWT team tell us if there is good reason to not have
this capability, or it is just the matter of priority.

> > Miguel- Hide quoted text -

[Asif Rajwani]

Miguel,

It will work, as public paths allow the pattern based filtering. Could
you please tell us when it will be released, is there any way to
increase the priority by voting etc.

I think issue is well define in this thread, if you need any more
information please let me know.

On Feb 7, 8:11 am, "Miguel Méndez" <mmen...@google.com> wrote:
> Please see issue

> 2003<http://code.google.com/p/google-web-toolkit/issues/detail?id=2003>to

> see if addresses your needs.
>

> --
> Miguel- Hide quoted text -

[Miguel Méndez]

The issue is marked as FixedNotReleased.  It will be included in the next version of GWT.

[Asif Rajwani]

Miguel,

Thanks for the quick response, it will be big help.

On Feb 7, 3:07 pm, "Miguel Méndez" <mmen...@google.com> wrote:
> The issue is marked as FixedNotReleased.  It will be included in the next
> version of GWT.
>