Yeah, we realized that chrome debugger and SDBG are the same, but it's a different world when your debug session is like a desktop application, you don't notice it's a Web application.
I checked the video how to separate the projects but unfortunately we cannot move to maven.
We are very happy that GWT is not going to die. GWT is a miracle, in compare to other JS libraries.
Thanks for your response and time.
... and for development: it is wise to separate your GWT UI project from your server part:
- Separate the Maven modules: one for server and one for client GWT UI, don't mixed both modules.
- Develop both modules independently, mock your server to be able to make a fast turn around time for your UI development.
- Take the result of your client module which are HTML, CSS, JS and put it on the server module to have it deployed.
So if you are doing this, you could just use the Jetty server which are standard in GWT libs and later you put your result on your "real server" which could be Tomcat or whatever...I have some examples which use the mechanism above. But for this you should move to Maven: https://github.com/gwtboot/domino-rest-enum-dateIMHO no other way, you need Maven 😉Hope this helps.--shahra...@gmail.com schrieb am Montag, 31. August 2020 um 03:25:08 UTC+2:Thanks Thomas for your prompt response, I loaded the old project and added the old jars one by one and after apache commons it started working, I mean it stopped using the gwt-dev.jar libraries.Now I'm able to load the application with1) Eclipse plugin, using the integrated Server jetty-9.2.z-SNAPSHOT,2) AdoptOpenJdk Java 83) GWT 2.94) SDBG debugger stops at breakpoints, it's interesting that it shows the real variable names like the old times legacy Dev Mode however, it doesn't show the function names :-(is there any solution for that because we don't want to use the chrome debugger.Oh my Goodness, GWT 2.9 compiler is extremely serious and much faster. We need to add null checks in lots of places because NullPointerException was not a problem for 2.7it could internally handle it but 2.9 is killing us. It was a great success that we reached this point. The next step is DB migration to oracle 19c.I would appreciate a solution for SDBG. Another question is how to find and manipulate the CodeServer parameters, we are thinking about replacing Jetty with Tomcat for development.I appreciate it in advance.Shahram...On Fri, Aug 28, 2020 at 7:35 AM Thomas Broyer <t.br...@gmail.com> wrote:That one's "easy": don't use the embedded Jetty of DevMode; run your own servlet container instead, along with either DevMode in -noserver mode, or CodeServer.--
On Thursday, August 27, 2020 at 8:30:45 PM UTC+2, Shahram Zadeh wrote:after a long time and hard work we were able to make it work up to the successful compilation, now there is a conflict between the integrated apache xerces in gwt-dev.jar and java 8.is there any way to force the GWT in dev mode not to use tools in the gwt-dev.jar?any help would be greatly appreciated.org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfigurationjava.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration cannot be cast to org.apache.xerces.xni.parser.XMLParserConfigurationat org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)at org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.<init>(Unknown Source)at org.apache.xerces.jaxp.SAXParserImpl.<init>(Unknown Source)at org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown Source)at com.sun.xml.internal.bind.v2.runtime.unmarshaller.UnmarshallerImpl.getXMLReader(UnmarshallerImpl.java:144)at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:157)at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:162)at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:171)at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:189)at com.soflytics.rguroo.server.util.ServerUtility.readGUIComponents(ServerUtility.java:175)On Saturday, August 8, 2020 at 7:11:54 AM UTC-7 frank.h...@web.de wrote:Use this to generate a multi module artifact:shahra...@gmail.com schrieb am Freitag, 7. August 2020 um 18:23:52 UTC+2:is there any documentation for how to set it up, we are not maven oriented. I appreciate a link or document...GWT Eclipse plugin is not maintained anymore... So to use the newest one you could move to pure Maven or Gradle... I only use Maven sofar and it works well...shahra...@gmail.com schrieb am Dienstag, 28. Juli 2020 um 00:11:58 UTC+2:We have a huge GWT project (GWT 2.7, JDK 1.7, Eclipse) everything works perfect. We are planning to upgrade to Java 11 and GWT 2.9 which has been recently released. However Java 1.7 is retiring and getting obsolete we have to move on and upgrade. Since last week we are trying to create a development environment like the existing one but there is no success. I was wondering whether anyone out there is struggling with the same issue, any hint, solution or hacking the eclipse plugin would be greatly appreciated.
Eclipse plugin comes with GWT (2.7 and 2.8.1)
--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/l_E1Y8XKg7k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/c9461274-510c-4661-8a73-28ad39fc35ecn%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/l_E1Y8XKg7k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/177cdccf-afc9-4f61-a82a-3eec44074bd9o%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/l_E1Y8XKg7k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/8839a771-01b9-4bc0-b2da-2a03e8edb9f2n%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CAGcWJ-cpq4b4kJoQLKBJkNXEoiOttKTSFA2uTAp4hVUyvZsigQ%40mail.gmail.com.
No comments:
Post a Comment