(Note the odd version number of 0.0.2030 to help make it obvious that you shouldn't use it for anything important.)
For milestone builds like this, please understand that there are still known problems, and it is use-at-your-own-risk. It *definitely* isn't ready for production use. For example, this milestone build is missing release notes, and it doesn't include the developer guide documentation. So, you should expect some trial and error getting everything to work.
Are your expectations low enough yet? Well, I also have some good news about what's included in this milestone:
- The Java 1.5 syntax is fully supported, including generics, enums, nice "for" loops, autoboxing, static imports, annotations, and so on - Support for generics in RPC (no more @gwt.typeArgs!) - The ability to subclass JavaScriptObject<http://code.google.com/p/google-web-toolkit/wiki/JavaScriptObjectRede...>for very straightforward JavaScript interop - Standards mode is now supported by the UI library (though there may be a few remaining bugs)
- GWT 1.5 requires Java 5 or later - The compiler output now goes into a subdirectory (e.g. ".../std" or ".../xs", depending on your linker settings<http://code.google.com/p/google-web-toolkit/wiki/LinkerDesign> ) - To encourage people to start using annotations and generics instead of the javadoc metadata, you'll see warnings about uses of old-style metadata such as @gwt.typeArgs; it is intentionally annoying :-) - The benchmark classes have moved into a separate package; should be easily fixable using your IDE's auto-import fixup - As a performance improvement, widgets now often call DOM.sinkEvents() lazily, when listeners are actually added rather than in the constructor. Sometimes, widget subclasses implicitly depend on the set of events sunk in the superclass' constructor. Consequently, if you are overriding onBrowserEvent() in a widget subclass and certain events mysteriously stop firing, you should explicitly call DOM.sinkEvents() in your subclass constructor for the events you depend on (don't worry, sinking an event more than once has no effect). If the preceding sentences made no sense at all to you, then you shouldn't be affected.
> (Note the odd version number of 0.0.2030 to help make it obvious that you
> shouldn't use it for anything important.)
> For milestone builds like this, please understand that there are still known
> problems, and it is use-at-your-own-risk. It *definitely* isn't ready for
> production use. For example, this milestone build is missing release notes,
> and it doesn't include the developer guide documentation. So, you should
> expect some trial and error getting everything to work.
> Are your expectations low enough yet? Well, I also have some good news about
> what's included in this milestone:
> - The Java 1.5 syntax is fully supported, including generics, enums,
> nice "for" loops, autoboxing, static imports, annotations, and so on
> - Support for generics in RPC (no more @gwt.typeArgs!)
> - The ability to subclass
> JavaScriptObject<http://code.google.com/p/google-web-toolkit/wiki/JavaScriptObjectRede...>for
> very straightforward JavaScript interop
> - Standards mode is now supported by the UI library (though there may
> be a few remaining bugs)
> - GWT 1.5 requires Java 5 or later
> - The compiler output now goes into a subdirectory (e.g. ".../std" or
> ".../xs", depending on your linker
> settings<http://code.google.com/p/google-web-toolkit/wiki/LinkerDesign>
> )
> - To encourage people to start using annotations and generics instead
> of the javadoc metadata, you'll see warnings about uses of old-style
> metadata such as @gwt.typeArgs; it is intentionally annoying :-)
> - The benchmark classes have moved into a separate package; should be
> easily fixable using your IDE's auto-import fixup
> - As a performance improvement, widgets now often call DOM.sinkEvents()
> lazily, when listeners are actually added rather than in the constructor.
> Sometimes, widget subclasses implicitly depend on the set of events sunk in
> the superclass' constructor. Consequently, if you are overriding
> onBrowserEvent() in a widget subclass and certain events mysteriously stop
> firing, you should explicitly call DOM.sinkEvents() in your subclass
> constructor for the events you depend on (don't worry, sinking an event more
> than once has no effect). If the preceding sentences made no sense at all to
> you, then you shouldn't be affected.
> (Note the odd version number of 0.0.2030 to help make it obvious that you
> shouldn't use it for anything important.)
> For milestone builds like this, please understand that there are still known
> problems, and it is use-at-your-own-risk. It *definitely* isn't ready for
> production use. For example, this milestone build is missing release notes,
> and it doesn't include the developer guide documentation. So, you should
> expect some trial and error getting everything to work.
> Are your expectations low enough yet? Well, I also have some good news about
> what's included in this milestone:
> - The Java 1.5 syntax is fully supported, including generics, enums,
> nice "for" loops, autoboxing, static imports, annotations, and so on
> - Support for generics in RPC (no more @gwt.typeArgs!)
> - The ability to subclass
> JavaScriptObject<http://code.google.com/p/google-web-toolkit/wiki/JavaScriptObjectRede...>for
> very straightforward JavaScript interop
> - Standards mode is now supported by the UI library (though there may
> be a few remaining bugs)
> - GWT 1.5 requires Java 5 or later
> - The compiler output now goes into a subdirectory (e.g. ".../std" or
> ".../xs", depending on your linker
> settings<http://code.google.com/p/google-web-toolkit/wiki/LinkerDesign>
> )
> - To encourage people to start using annotations and generics instead
> of the javadoc metadata, you'll see warnings about uses of old-style
> metadata such as @gwt.typeArgs; it is intentionally annoying :-)
> - The benchmark classes have moved into a separate package; should be
> easily fixable using your IDE's auto-import fixup
> - As a performance improvement, widgets now often call DOM.sinkEvents()
> lazily, when listeners are actually added rather than in the constructor.
> Sometimes, widget subclasses implicitly depend on the set of events sunk in
> the superclass' constructor. Consequently, if you are overriding
> onBrowserEvent() in a widget subclass and certain events mysteriously stop
> firing, you should explicitly call DOM.sinkEvents() in your subclass
> constructor for the events you depend on (don't worry, sinking an event more
> than once has no effect). If the preceding sentences made no sense at all to
> you, then you shouldn't be affected.
great work. A note though: You are only supporting JDK1.5.
We are busy making our production ready software using GWT
and since our customers can NOT upgrade tot 1.5 yet, is this
going to be an issue ?
I know that 1.4 is EOL at the end of this year, but we'll still have
customers
running the old VM (so <1.5). (Think about their AppServers, some of
the customer
are still running IBM Websphere 5.1 or 6.0, which are not JDK 1.5
platforms
yet and trust me, upgrading their VM's is a lot of work (for them)).
What would be the solution on this ? Can I use the GWT1.5 binaries
with a 1.4 VM (for example if I use RetroTranslator).
> > (Note the odd version number of 0.0.2030 to help make it obvious that you
> > shouldn't use it for anything important.)
> > For milestone builds like this, please understand that there are still known
> > problems, and it is use-at-your-own-risk. It *definitely* isn't ready for
> > production use. For example, this milestone build is missing release notes,
> > and it doesn't include the developer guide documentation. So, you should
> > expect some trial and error getting everything to work.
> > Are your expectations low enough yet? Well, I also have some good news about
> > what's included in this milestone:
> > - The Java 1.5 syntax is fully supported, including generics, enums,
> > nice "for" loops, autoboxing, static imports, annotations, and so on
> > - Support for generics in RPC (no more @gwt.typeArgs!)
> > - The ability to subclass
> > JavaScriptObject<http://code.google.com/p/google-web-toolkit/wiki/JavaScriptObjectRede...>for
> > very straightforward JavaScript interop
> > - Standards mode is now supported by the UI library (though there may
> > be a few remaining bugs)
> > - GWT 1.5 requires Java 5 or later
> > - The compiler output now goes into a subdirectory (e.g. ".../std" or
> > ".../xs", depending on your linker
> > settings<http://code.google.com/p/google-web-toolkit/wiki/LinkerDesign>
> > )
> > - To encourage people to start using annotations and generics instead
> > of the javadoc metadata, you'll see warnings about uses of old-style
> > metadata such as @gwt.typeArgs; it is intentionally annoying :-)
> > - The benchmark classes have moved into a separate package; should be
> > easily fixable using your IDE's auto-import fixup
> > - As a performance improvement, widgets now often call DOM.sinkEvents()
> > lazily, when listeners are actually added rather than in the constructor.
> > Sometimes, widget subclasses implicitly depend on the set of events sunk in
> > the superclass' constructor. Consequently, if you are overriding
> > onBrowserEvent() in a widget subclass and certain events mysteriously stop
> > firing, you should explicitly call DOM.sinkEvents() in your subclass
> > constructor for the events you depend on (don't worry, sinking an event more
> > than once has no effect). If the preceding sentences made no sense at all to
> > you, then you shouldn't be affected.
There are still some unresolved (some serious) bugs, like #1741, which
possibly makes contents of your HTMLPanel go fishing.
So, don't switch your test platform just yet...
You could use Java 5 to compile the client and whatever you want on
the server-side. You could, for example, instruct the Java 5 compiler
to output Java <1.4-compliant class files. Or, you could refrain from
Java 5 language features in your RPC and compile the server code using
Java <1.4 compiler. Or, implement the server-side independently from
the client, but this way you may have to come up with your own RPC
framework or use JSON.
Lots of options and you still can use Java 5 to develop the client.
Yegor
On Mar 7, 5:57 am, Rockster <rjan...@gmail.com> wrote:
> great work. A note though: You are only supporting JDK1.5.
> We are busy making our production ready software using GWT
> and since our customers can NOT upgrade tot 1.5 yet, is this
> going to be an issue ?
> I know that 1.4 is EOL at the end of this year, but we'll still have
> customers
> running the old VM (so <1.5). (Think about their AppServers, some of
> the customer
> are still running IBM Websphere 5.1 or 6.0, which are not JDK 1.5
> platforms
> yet and trust me, upgrading their VM's is a lot of work (for them)).
> What would be the solution on this ? Can I use the GWT1.5 binaries
> with a 1.4 VM (for example if I use RetroTranslator).
> > On Mar 6, 11:48 am, "Bruce Johnson" <br...@google.com> wrote:
> > > Hi everybody,
> > > GWT 1.5 isn't finished yet, but it is starting to get close. I'm happy to
> > > report that the first milestone build of GWT 1.5 is now available:
> > > (Note the odd version number of 0.0.2030 to help make it obvious that you
> > > shouldn't use it for anything important.)
> > > For milestone builds like this, please understand that there are still known
> > > problems, and it is use-at-your-own-risk. It *definitely* isn't ready for
> > > production use. For example, this milestone build is missing release notes,
> > > and it doesn't include the developer guide documentation. So, you should
> > > expect some trial and error getting everything to work.
> > > Are your expectations low enough yet? Well, I also have some good news about
> > > what's included in this milestone:
> > > - The Java 1.5 syntax is fully supported, including generics, enums,
> > > nice "for" loops, autoboxing, static imports, annotations, and so on
> > > - Support for generics in RPC (no more @gwt.typeArgs!)
> > > - The ability to subclass
> > > JavaScriptObject<http://code.google.com/p/google-web-toolkit/wiki/JavaScriptObjectRede...>for
> > > very straightforward JavaScript interop
> > > - Standards mode is now supported by the UI library (though there may
> > > be a few remaining bugs)
> > > - GWT 1.5 requires Java 5 or later
> > > - The compiler output now goes into a subdirectory (e.g. ".../std" or
> > > ".../xs", depending on your linker
> > > settings<http://code.google.com/p/google-web-toolkit/wiki/LinkerDesign>
> > > )
> > > - To encourage people to start using annotations and generics instead
> > > of the javadoc metadata, you'll see warnings about uses of old-style
> > > metadata such as @gwt.typeArgs; it is intentionally annoying :-)
> > > - The benchmark classes have moved into a separate package; should be
> > > easily fixable using your IDE's auto-import fixup
> > > - As a performance improvement, widgets now often call DOM.sinkEvents()
> > > lazily, when listeners are actually added rather than in the constructor.
> > > Sometimes, widget subclasses implicitly depend on the set of events sunk in
> > > the superclass' constructor. Consequently, if you are overriding
> > > onBrowserEvent() in a widget subclass and certain events mysteriously stop
> > > firing, you should explicitly call DOM.sinkEvents() in your subclass
> > > constructor for the events you depend on (don't worry, sinking an event more
> > > than once has no effect). If the preceding sentences made no sense at all to
> > > you, then you shouldn't be affected.
> (Note the odd version number of 0.0.2030 to help make it obvious that you
> shouldn't use it for anything important.)
> For milestone builds like this, please understand that there are still known
> problems, and it is use-at-your-own-risk. It *definitely* isn't ready for
> production use. For example, this milestone build is missing release notes,
> and it doesn't include the developer guide documentation. So, you should
> expect some trial and error getting everything to work.
> Are your expectations low enough yet? Well, I also have some good news about
> what's included in this milestone:
> - The Java 1.5 syntax is fully supported, including generics, enums,
> nice "for" loops, autoboxing, static imports, annotations, and so on
> - Support for generics in RPC (no more @gwt.typeArgs!)
> - The ability to subclass
> JavaScriptObject<http://code.google.com/p/google-web-toolkit/wiki/JavaScriptObjectRede...>for
> very straightforward JavaScript interop
> - Standards mode is now supported by the UI library (though there may
> be a few remaining bugs)
> - GWT 1.5 requires Java 5 or later
> - The compiler output now goes into a subdirectory (e.g. ".../std" or
> ".../xs", depending on your linker
> settings<http://code.google.com/p/google-web-toolkit/wiki/LinkerDesign>
> )
> - To encourage people to start using annotations and generics instead
> of the javadoc metadata, you'll see warnings about uses of old-style
> metadata such as @gwt.typeArgs; it is intentionally annoying :-)
> - The benchmark classes have moved into a separate package; should be
> easily fixable using your IDE's auto-import fixup
> - As a performance improvement, widgets now often call DOM.sinkEvents()
> lazily, when listeners are actually added rather than in the constructor.
> Sometimes, widget subclasses implicitly depend on the set of events sunk in
> the superclass' constructor. Consequently, if you are overriding
> onBrowserEvent() in a widget subclass and certain events mysteriously stop
> firing, you should explicitly call DOM.sinkEvents() in your subclass
> constructor for the events you depend on (don't worry, sinking an event more
> than once has no effect). If the preceding sentences made no sense at all to
> you, then you shouldn't be affected.
On Fri, Mar 7, 2008 at 11:41 AM, Jeremy Cohen <jeremy.h.co...@gmail.com> wrote:
> Hi, > Is OOPHM available already? If not, is there a target date / timeframe > for this functionality.
OOPHM won't be in GWT 1.5, but we are making solid progress on it in parallel to finalizing 1.5. The post-1.5 development cycle that would include OOPHM is likely to be a lot shorter than the one we're starting to wrap up now. Those Java 5 tweaks took a while.
> On Fri, Mar 7, 2008 at 11:41 AM, Jeremy Cohen <jeremy.h.co...@gmail.com>
> wrote:
> > Hi,
> > Is OOPHM available already? If not, is there a target date / timeframe
> > for this functionality.
> OOPHM won't be in GWT 1.5, but we are making solid progress on it in
> parallel to finalizing 1.5. The post-1.5 development cycle that would
> include OOPHM is likely to be a lot shorter than the one we're starting to
> wrap up now. Those Java 5 tweaks took a while.
> On Mar 7, 9:54 am, "Bruce Johnson" <br...@google.com> wrote:
> > On Fri, Mar 7, 2008 at 11:41 AM, Jeremy Cohen <jeremy.h.co...@gmail.com>
> > wrote:
> > > Hi,
> > > Is OOPHM available already? If not, is there a target date / timeframe
> > > for this functionality.
> > OOPHM won't be in GWT 1.5, but we are making solid progress on it in
> > parallel to finalizing 1.5. The post-1.5 development cycle that would
> > include OOPHM is likely to be a lot shorter than the one we're starting to
> > wrap up now. Those Java 5 tweaks took a while.
OOPHM is Out-of-process Hosted Mode. I think one goal of OOPHM is to allow choice of browser during development (so, for example, Windows users could probably use Firefox for hosted mode as well as IE), it will also allow the use of more up-to-date browsers (1.4's hosted mode runs Mozilla 1.7.something on Linux), and it will allow you to use whatever browser add-ons you like, such as the DOM Inspector, Flash, etc.
I'd add to the list of things that may trip you up
- HTMLPanels no longer allow the same ID to be used more than once on
a page, if your application relied on this, you will need to rethink
your approach
Congrats on the milestone release though, very exciting! Just between
you and me we are using one of the trunk builds in a production
environment, but since that's considered bad practice you didn't hear
it from me :)
Rusty
On Mar 8, 3:48 pm, "Ian Petersen" <ispet...@gmail.com> wrote:
> OOPHM is Out-of-process Hosted Mode. I think one goal of OOPHM is to
> allow choice of browser during development (so, for example, Windows
> users could probably use Firefox for hosted mode as well as IE), it
> will also allow the use of more up-to-date browsers (1.4's hosted mode
> runs Mozilla 1.7.something on Linux), and it will allow you to use
> whatever browser add-ons you like, such as the DOM Inspector, Flash,
> etc.
Congratulations for this first step to GWT 1.5. I migrated to this
version in my project because the use of Java 5 is important for me. I
had some problems that I solved. Here is my solutions. Hoping it will
help someone.
1/ under linux ubuntu 7.10 the GWT shell crashes with the following
JVM error message :
An unexpected error has been detected by HotSpot Virtual Machine:
Java VM: Java HotSpot(TM) Client VM (1.5.0_06-b05 mixed mode, sharing)
# Problematic frame:
# C [libmozz.so+0x78dc] inflate_blocks_reset+0x2c
I solved this problem by using a more recent JVM (1.5.0_15).
2/ The compiler output is now in the new 'std' subdirectory. I am not
sure what I must include into my .war archive (J2EE application).
Currently I include the content of the 'std' directory.
3/ I had blank screen on my web page. I found that the script gwt.js
is not more generated by the gwt compiler. So in my main html page I
replaced it by xxx.nocache.js (xxx is the fully qualified name
corresponding to the .gwt.xml). Is it normal ?
I found also the GWT ext javascript must be placed in the <body> of
the html page instead of in the <meta> area.
Here is an extract of my html page :
<body>
<!-- gwt javascript -->
<script language="javascript"
src="com.raisepartner.prism.PRISM.nocache.js"></script>
<!-- gwtext javascript -->
<script type="text/javascript" src="ext/adapter/yui/yui-
utilities.js"></script>
<script type="text/javascript" src="ext/adapter/yui/ext-yui-
adapter.js"></script>
<script type="text/javascript" src="ext/ext-all.js"></script>
<!-- history support -->
<iframe id="__gwt_historyFrame" style="width:0;height:0;border:
0"></iframe>
</body>
Finally my application works fine with GWT 1.5 (milestone 1) and GWT
EXT 0.9.3
Do you have a road map of the next milestone for the GWT 1.5 version ?
I am waiting for the OOPHM too in order to use firebug (helpful for
css edition) and to switch to other navigators.
Regards,
Seb
On 8 mar, 11:32, rusty <rustysh...@gmail.com> wrote:
> I'd add to the list of things that may trip you up
> - HTMLPanels no longer allow the same ID to be used more than once on
> a page, if your application relied on this, you will need to rethink
> your approach
> Congrats on the milestone release though, very exciting! Just between
> you and me we are using one of the trunk builds in a production
> environment, but since that's considered bad practice you didn't hear
> it from me :)
> Rusty
> On Mar 8, 3:48 pm, "Ian Petersen" <ispet...@gmail.com> wrote:
> > OOPHM is Out-of-process Hosted Mode. I think one goal of OOPHM is to
> > allow choice of browser during development (so, for example, Windows
> > users could probably use Firefox for hosted mode as well as IE), it
> > will also allow the use of more up-to-date browsers (1.4's hosted mode
> > runs Mozilla 1.7.something on Linux), and it will allow you to use
> > whatever browser add-ons you like, such as the DOM Inspector, Flash,
> > etc.
On Sat, Mar 8, 2008 at 3:43 PM, Sebastien <chassa...@gmail.com> wrote: > 2/ The compiler output is now in the new 'std' subdirectory. I am not > sure what I must include into my .war archive (J2EE application). > Currently I include the content of the 'std' directory.
That's exactly the right thing to do. We'll be adding other types of linkers in the future, and you'll pick which set of output you want depending on your target deployment environment. For example, if you want a compiled module that can be included cross-site, your output will go into the "xs" subdirectory. When the Gadget linker is ready, you'll take the contents of the "gadget" subdir, and so on.
I can transfer entity(ejb3 persistence) into GWT Client by step :
1. download the GWT 1.5 Milestone 1
2. download javax.persistence.* with class and source from sun web,
add Persistence.gwt.xml in package javax, such as :
<module>
<inherits name="com.google.gwt.user.User"/>
<source path="client"/>
<source path="persistence"/>
</module>
then jar named ejb3_persistence4gwt.jar
3. In my GWT Project , include ejb3_persistence4gwt.jar
4. In my GWT Project ,create GWT Module for your Business
(com.mycompany.project.Test),
add <inherits name="javax.Persistence"/> in the Test.gwt.xml
5. create entity, such as :
package com.mycompany.project.client;
public class Customer implements Serializable{
private static final long serialVersionUID = 1L;
private String name ;
private int age;
public Customer(){
}
@Column
public String getName() {
return name;
}
public void setName(String name) {
this.name = name;
}
public int getAge() {
return age;
}
public void setAge(int age) {
this.age = age;
}
@Override
public String toString(){
return "name:"+getName()+ ",age:"+getAge();
}
}
oh , the Customer can use by GWT Widget. run is ok.
but GWT Development Shell Window log error , such as:
Errors in 'jar:file:/D:/workspaceBase/lib_src/ejb3-
persistenceAndSrc.jar!/javax/persistence/Persistence.java'
Line 50: The import java.net cannot be resolved
Line 51: The import java.util.regex cannot be resolved
......
/**
* This field is a Set that must always contain Strings.
* @gwt.typeArgs <xxxx.web.core.model.SelectItem>
*/
private List selectList = new ArrayList();
be instead of
/**
* This field is a Set that must always contain Strings.
*/
private List<SelectItem> selectList = new ArrayList<SelectItem>();
but , you should add jdk1.5.
On 3月9日, 下午10时14分, Toki <sed.n...@gmail.com> wrote:
Do you plan to support generic (Java 5) in the AsyncCallback
interface ?
By this way we could specifiy the parameter type of the
onSuccess(Object) method :
> Do you plan to support generic (Java 5) in the AsyncCallback > interface ? > By this way we could specifiy the parameter type of the > onSuccess(Object) method :
I'm new to GWT. Since our code is running Java 1.5 and the project
has some lead time on it I just pulled the 1.5 milestone.
I configured the project using projectCreator, applicationCreator, and
i18Creator. A soon as I started instantiating constant objects via
GWT.create() I got error messages.
Turns out the above sequence doesn't add <inherits
name="com.google.gwt.i18n.I18N"/> to the <module> tag in the
[project].gwt.xml file that is generated. I found the fix on:
> I can transfer entity(ejb3 persistence) into GWT Client by step :
> 1. download the GWT 1.5 Milestone 1
> 2. download javax.persistence.* with class and source from sun web,
> add Persistence.gwt.xml in package javax, such as :
> <module>
> <inherits name="com.google.gwt.user.User"/>
> <source path="client"/>
> <source path="persistence"/>
> </module>
> then jar named ejb3_persistence4gwt.jar
> 3. In my GWT Project , include ejb3_persistence4gwt.jar
> 4. In my GWT Project ,create GWT Module for your Business
> (com.mycompany.project.Test),
> add <inherits name="javax.Persistence"/> in the Test.gwt.xml
> 5. create entity, such as :
> package com.mycompany.project.client;
> oh , the Customer can use by GWT Widget. run is ok.
> but GWT Development Shell Window log error , such as:
> Errors in 'jar:file:/D:/workspaceBase/lib_src/ejb3-
> persistenceAndSrc.jar!/javax/persistence/Persistence.java'
> Line 50: The import java.net cannot be resolved
> Line 51: The import java.util.regex cannot be resolved
> ......
The type parameter of AsyncCallback must match the argument type for
onSuccess. In this case, your type parameter appears to be List<Type>,
so you'd write something like new AsyncCallback<List<Type>>() { public
void onSuccess(List<Type> result) {...}}
On Mar 15, 5:34 am, Chris Marshall <ch...@campsbayterrace.com> wrote:
I just ported a complete Hibernate/JPA application (the hibernate4gwt
sample application, which is available for download) and
unfortunately, the example from aibo is too simple to be exhaustive.
In fact, you still cannot send EJB3 beans to the GWT client side in a
real world application. For the reasons mentioned here (http://
www.dotnetguru2.org/bmarchesson/index.php?p=786&more=1&c=1&tb=1&pb=1),
sending collections, SQL dates or lazy loaded associations still
fails.
I will probably write a more complete article on EJB3 and GWT
integration, but the good news is there is only a few work to make
hibernate4gwt work with the GWT 1.5 first milestone (in fact, it
already works on my laptop, and I will problably publish it as a
"milestone" release this week), and using it, you will not need
Java1.4 DTO anymore.
> Can someone please comment on aibo's way of integrating ejb3 entities?
> I'd like to know if this is feasible and what are the cons and pros?
> Thanks.
> > I can transfer entity(ejb3 persistence) into GWT Client by step :
> > 1. download the GWT 1.5 Milestone 1
> > 2. download javax.persistence.* with class and source from sun web,
> > add Persistence.gwt.xml in package javax, such as :
> > <module>
> > <inherits name="com.google.gwt.user.User"/>
> > <source path="client"/>
> > <source path="persistence"/>
> > </module>
> > then jar named ejb3_persistence4gwt.jar
> > 3. In my GWT Project , include ejb3_persistence4gwt.jar
> > 4. In my GWT Project ,create GWT Module for your Business
> > (com.mycompany.project.Test),
> > add <inherits name="javax.Persistence"/> in the Test.gwt.xml
> > 5. create entity, such as :
> > package com.mycompany.project.client;
> > oh , the Customer can use by GWT Widget. run is ok.
> > but GWT Development Shell Window log error , such as:
> > Errors in 'jar:file:/D:/workspaceBase/lib_src/ejb3-
> > persistenceAndSrc.jar!/javax/persistence/Persistence.java'
> > Line 50: The import java.net cannot be resolved
> > Line 51: The import java.util.regex cannot be resolved
> > ......
