Aye aye;
To add to Ian's response, the module definition files do three things:
A) When you inherit any module.gwt.xml {say, com.example.util.A}, you
add access to all the source in that modules package, as if you used:
import com.example.util.*; Note, this causes ALL static code calls in
the p
Hi,
It does what it is told! (The big advantage and the big disadvantage of
computers :-))
One of the big disadvantages of the application creators so far is that they
call everything the same and you can't work out some of the stranger
relationships.
If the GWT named things better, a lot of con
Thanks for reply, it worked. I could call service layer of module A
without loading the entry point class. I would appreciate if you could
help me understand how does it works, for example my application name
is "Test" so I have Test.gwt.xml in com.user.sim.test package. I
create another file exac
Aye, use deferred binding to override any direct references to the
code you want to include.
Be careful of static fields that are auto initialized, and static code
blocks, as you CANNOT override these. Even if you never access the
static object, GWT must inc
If you want to use the module A separatly you can create a C module
with the EntryPoint from A.
On May 13, 2:24 am, Ian Bambury wrote:
> Have a module (*.gwt.xml) file for A that doesn't define an entry point and
> inherit that in the module file for B
> Ian
>
> http://examples.roughian.com
>
>
Have a module (*.gwt.xml) file for A that doesn't define an entry point and
inherit that in the module file for B
Ian
http://examples.roughian.com
2009/5/13 sim123
>
> I have two GWT modules A and B and where B is inheriting A. When I run
> B application, GWT tries to load B.java and then A.ja
I have two GWT modules A and B and where B is inheriting A. When I run
B application, GWT tries to load B.java and then A.java. I don't want
to load A.java. B uses A but it has it's own API, is there any way to
prevent loading of A via B, as I can not make any changes in A.
Thanks for all the hel
