from:"ssg"

Re: Looks like ext-js issues migrating from GWT 1.7.0 to GWT 2.7.0. Need help.

2015-02-27 Thread ssg

Alain,
Thanks a lot for your response. 
Just making sure. Are you suggesting me to create Ext4j and upgrade my Ext 
JS libraries ?

Please let me know.

On Thursday, February 26, 2015 at 11:09:57 AM UTC-5, Alain wrote:

 If you are using GWT-Ext it wont work with a recent version of GWT/ Ext 
 JS. This is the reason why I created Ext4j: 
 http://opensource.ahome-it.com/#ext4j.
  
 Ext4j works with any version of Ext JS starting with version 4 and GWT 2.6+

 You can download Ext JS on the sencha's site.

 http://www.sencha.com/products/extjs/

 On 26 February 2015 at 16:43, ssg shiv...@gmail.com javascript: wrote:

 Thanks Jens. I have removed my 1st line with !DOCTYPE html as you 
 suggested.

 *Can you please tell me where I can get the upgraded version of 
 ext-all.js library to a version that is compatible with GWT 2.7.0 ?*
 I googled a got confused. Please let me know.

 Jens, Once again thanks a lot for your time and responses.

 On Wednesday, February 25, 2015 at 12:03:55 PM UTC-5, Jens wrote:



1. Application does not load initially as the IE Browser opens in 
IE 10 Compatability View Mode.

 Use !DOCTYPE html at the top of your html page that loads the app.

  


1. The application loads successfully once I change the Browser 
Mode to IE10. At this point if I CLICK on any items in the left 
 navigation 
panel I am getting the below errors and looks like OnClick() of GWT is 
 not 
working along with the ext-all.js issues.

 Here is the *ext-all.js* issues I see in Console of IE10 browser;


 Upgrade your ext-all.js library to a version that is compatible with GWT 
 2.7.


 -- J. 

  -- 
 You received this message because you are subscribed to the Google Groups 
 Google Web Toolkit group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to google-web-toolkit+unsubscr...@googlegroups.com javascript:.
 To post to this group, send email to google-we...@googlegroups.com 
 javascript:.
 Visit this group at http://groups.google.com/group/google-web-toolkit.
 For more options, visit https://groups.google.com/d/optout.




 -- 

 Alain Ekambi

 Co-Founder

 Ahomé Innovation Technologies

 http://www.ahome-it.com/ http://ahome-it.com/
  

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Looks like ext-js issues migrating from GWT 1.7.0 to GWT 2.7.0. Need help.

2015-02-26 Thread ssg

Thanks Thomas. I have removed my 1st line with !DOCTYPE html as you 
suggested and googled a bit about quirks mode vs standards mode.
Once again thanks a lot for your time and responses.

On Thursday, February 26, 2015 at 7:43:27 AM UTC-5, Thomas Broyer wrote:



 On Wednesday, February 25, 2015 at 8:51:28 PM UTC+1, ssg wrote:

 Jens,
 Thanks a lot for your response.
 The html page that loads the my app already has a code !DOCTYPE htmlyou 
 suggested.


 No, it has !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 
 Transitional//EN, not !DOCTYPE html

 (go google a bit about quirks mode vs standards mode)


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Looks like ext-js issues migrating from GWT 1.7.0 to GWT 2.7.0. Need help.

2015-02-26 Thread ssg

Thanks Jens. I have removed my 1st line with !DOCTYPE html as you 
suggested.

*Can you please tell me where I can get the upgraded version of ext-all.js 
library to a version that is compatible with GWT 2.7.0 ?*
I googled a got confused. Please let me know.

Jens, Once again thanks a lot for your time and responses.

On Wednesday, February 25, 2015 at 12:03:55 PM UTC-5, Jens wrote:



1. Application does not load initially as the IE Browser opens in IE 
10 Compatability View Mode.

 Use !DOCTYPE html at the top of your html page that loads the app.

  


1. The application loads successfully once I change the Browser Mode 
to IE10. At this point if I CLICK on any items in the left navigation 
 panel 
I am getting the below errors and looks like OnClick() of GWT is not 
working along with the ext-all.js issues.

 Here is the *ext-all.js* issues I see in Console of IE10 browser;


 Upgrade your ext-all.js library to a version that is compatible with GWT 
 2.7.


 -- J. 


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)

2015-02-25 Thread ssg

Juan,
Thanks for the reply. As I am new to GWT I do not understand the 
PROGRAM_ARGUMENTS values you mentioned here. Also I do not see a module[s] 
argument in your example. Based on my code provided earlier , Can you 
please help me rewrite PROGRAM_ARGUMENTS values using my code including 
the module[s] argument as well. 

Thanks in advance.

On Tuesday, February 24, 2015 at 5:17:02 PM UTC-5, Juan Pablo Gardella 
wrote:

 Sure.  (working for GWT 2.7)

 stringAttribute key=org.eclipse.jdt.launching.MAIN_TYPE 
 value=com.google.gwt.dev.DevMode/
 stringAttribute key=org.eclipse.jdt.launching.PROGRAM_ARGUMENTS 
 value=-remoteUI quot;${gwt_remote_ui_server_port}:${unique_id}quot; 
 -codeServerPort 9997 -port auto -superDevMode -logLevel INFO 
 com.foo.SismuEntryPoint/


 On 24 February 2015 at 17:47, ssg shiv...@gmail.com javascript: wrote:

 Yes I agree that the error is self explanatory. I was expecting an 
 example code using this argument. Can you please provide me an example ?

 Thanks a lot in advance.

 On Tuesday, February 24, 2015 at 2:46:21 PM UTC-5, Juan Pablo Gardella 
 wrote:

 The error is self described: Missing required argument 'module[s]. 
 You have to add the module(s)

 On 24 February 2015 at 16:33, ssg shiv...@gmail.com wrote:

 Thanks Thomas. I tried your suggestion as below.
 *stringAttribute key=org.eclipse.jdt.launching.PROGRAM_ARGUMENTS 
 value=-war www -startupUrl mmsea/app.jsp -noserver -port 9080/*

 I am getting the following error now;

 Missing required argument 'module[s]'
 Google Web Toolkit 2.7.0
 DevMode [-[no]startServer] [-port port-number | auto] [-whitelist 
 whitelist-string] [-blacklist blacklist-string] [-logdir directory] 
 [-logLevel level] [-gen dir] [-bindAddress host-name-or-address] 
 [-codeServerPort port-number | auto] [-[no]superDevMode] [-server 
 servletContainerLauncher[:args]] [-startupUrl url] [-war dir] [-deploy 
 dir] [-extra dir] [-modulePathPrefix ] [-workDir dir] 
 [-XmethodNameDisplayMode NONE | ONLY_METHOD_NAME | ABBREVIATED | FULL] 
 [-sourceLevel [auto, 1.6, 1.7]] [-XjsInteropMode [NONE, JS, CLOSURE]] 
 [-[no]incremental] module[s] 

 where 
   -[no]startServer Starts a servlet container serving the 
 directory specified by the -war flag. (defaults to OFF)
   -portSpecifies the TCP port for the embedded web 
 server (defaults to )
   -whitelist   Allows the user to browse URLs that match 
 the specified regexes (comma or space separated)
   -blacklist   Prevents the user browsing URLs that match 
 the specified regexes (comma or space separated)
   -logdir  Logs to a file in the given directory, as 
 well as graphically
   -logLevelThe level of logging detail: ERROR, WARN, 
 INFO, TRACE, DEBUG, SPAM, or ALL
   -gen Debugging: causes normally-transient 
 generated types to be saved in the specified directory
   -bindAddress Specifies the bind address for the code 
 server and web server (defaults to 127.0.0.1)
   -codeServerPort  Specifies the TCP port for the code server 
 (defaults to 9997 for classic Dev Mode or 9876 for Super Dev Mode)
   -[no]superDevModeRuns Super Dev Mode instead of classic 
 Development Mode. (defaults to ON)
   -server  Specify a different embedded web server to 
 run (must implement ServletContainerLauncher)
   -startupUrl  Automatically launches the specified URL
   -war The directory into which deployable output 
 files will be written (defaults to 'war')
   -deploy  The directory into which deployable but not 
 servable output files will be written (defaults to 'WEB-INF/deploy' under 
 the -war directory/jar, and may be the same as the -extra directory/jar)
   -extra   The directory into which extra files, not 
 intended for deployment, will be written
   -modulePathPrefixThe subdirectory inside the war dir where 
 DevMode will create module directories. (defaults empty for top level)
   -workDir The compiler's working directory for 
 internal use (must be writeable; defaults to a system temp dir)
   -XmethodNameDisplayMode  Emit extra information allow chrome dev 
 tools to display Java identifiers in many places instead of JavaScript 
 functions.
   -sourceLevel Specifies Java source level (defaults to 
 auto:1.6)
   -XjsInteropMode  Specifies JsInterop mode, either NONE, JS, 
 or CLOSURE (defaults to NONE)
   -[no]incremental Compiles faster by reusing data from the 
 previous compile. (defaults to ON)
 and 
   module[s]Specifies the name(s) of the module(s) to 
 host

 Please let me know.
 Thanks a lot in advance.

 On Tuesday, February 24, 2015 at 12:10:06 PM UTC-5, Thomas Broyer wrote:



 On Tuesday, February 24, 2015 at 4:53:34 PM UTC+1, ssg wrote:

 Jens,

 Below is the message I am getting. Not sure which one to use or how

Looks like ext-js issues migrating from GWT 1.7.0 to GWT 2.7.0. Need help.

2015-02-25 Thread ssg

Running my application using localhost.
When I open my application in IE using GWT 2.7.0, I have the following 
issues;


   1. Application does not load initially as the IE Browser opens in IE 10 
   Compatability View Mode.
   2. The application loads successfully once I change the Browser Mode to 
   IE10. At this point if I CLICK on any items in the left navigation panel I 
   am getting the below errors and looks like OnClick() of GWT is not working 
   along with the ext-all.js issues.

Here is the *ext-all.js* issues I see in Console of IE10 browser;

SCRIPT5007: Unable to get property 'ui' of undefined or null reference 
ext-all.js, line 100 character 1914
SCRIPT5007: Unable to get property 'ui' of undefined or null reference 
t-all.js, line 100 character 1954
SCRIPT5007: Unable to get property 'ui' of undefined or null reference 
ext-all.js, line 100 character 1954
SCRIPT5007: Unable to get property 'ui' of undefined or null reference 

*Can someone please help me resolve these issues so that I can successfully 
migrate from GWT 1.7.0 to GWT 2.7.0 ?*

*Below is the screenshot of the IE10 browser Console;*

*Thanks a lot in advance.*





-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Looks like ext-js issues migrating from GWT 1.7.0 to GWT 2.7.0. Need help.

2015-02-25 Thread ssg

Jens,
Thanks a lot for your response.
The html page that loads the my app already has a code !DOCTYPE htmlyou 
suggested. Below is the copy of the html code that loads my app. *Please 
check and let me know any corrections.*

!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
html
  head
meta http-equiv=content-type content=text/html; charset=UTF-8
!--CSS for loading message at application Startup--
style type=text/css
#loading {
position: absolute;
left: 45%;
top: 40%;
padding: 2px;
z-index: 20001;
height: auto;
border: 1px solid #ccc;
}
#loading a {
color: #225588;
}

#loading .loading-indicator {
background: white;
color: #444;
font: bold 13px tahoma, arial, helvetica;
padding: 10px;
margin: 0;
height: auto;
}

#loading-msg {
font: normal 10px arial, tahoma, sans-serif;
}
/style
link type=text/css rel=stylesheet href=Mmsea.css
titleMMSEA/title
  /head
  body
iframe src=javascript:'' id=__gwt_historyFrame tabIndex='-1' 
style=position:absolute;width:0;height:0;border:0/iframe
!--add loading indicator while the app is being loaded--
div id=loading
div class=loading-indicator
img 
src=js/ext/resources/images/default/shared/large-loading.gif width=32 
height=32

 style=margin-right:8px;float:left;vertical-align:top;/Mmseabr/
span id=loading-msgLoading styles and images.../span
/div
/div

!--include the Ext CSS, and use the gray theme--
!--link rel=stylesheet type=text/css 
href=Mmsea/js/ext/resources/css/ext-all.css/--
link rel=stylesheet href=js/ext/resources/css/ext-all.css /
link id=theme rel=stylesheet type=text/css 
href=themes/silverCherry/css/xtheme-silverCherry.css/
script 
type=text/javascriptdocument.getElementById('loading-msg').innerHTML = 
'Loading Core API...';/script

!--include the Ext Core API--
script type=text/javascript 
src=js/ext/adapter/ext/ext-base.js/script
 
!--include Ext --
script 
type=text/javascriptdocument.getElementById('loading-msg').innerHTML = 
'Loading UI Components...';/script
script type=text/javascript src=js/ext/ext-all.js/script

!--include the application JS--
script 
type=text/javascriptdocument.getElementById('loading-msg').innerHTML = 
'Initializing...';/script
script type=text/javascript language=javascript 
src=com.acg.mmsea.gwt.Mmsea.nocache.js/script
!--hide loading message--
script type=text/javascriptExt.get('loading').fadeOut({remove: true, 
duration:.25});/script

  /body
/html


*Please let me know.*


On Wednesday, February 25, 2015 at 12:03:55 PM UTC-5, Jens wrote:



1. Application does not load initially as the IE Browser opens in IE 
10 Compatability View Mode.

 Use !DOCTYPE html at the top of your html page that loads the app.

  


1. The application loads successfully once I change the Browser Mode 
to IE10. At this point if I CLICK on any items in the left navigation 
 panel 
I am getting the below errors and looks like OnClick() of GWT is not 
working along with the ext-all.js issues.

 Here is the *ext-all.js* issues I see in Console of IE10 browser;


 Upgrade your ext-all.js library to a version that is compatible with GWT 
 2.7.


 -- J. 


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)

2015-02-24 Thread ssg

Yes I agree that the error is self explanatory. I was expecting an example 
code using this argument. Can you please provide me an example ?

Thanks a lot in advance.

On Tuesday, February 24, 2015 at 2:46:21 PM UTC-5, Juan Pablo Gardella 
wrote:

 The error is self described: Missing required argument 'module[s]. You 
 have to add the module(s)

 On 24 February 2015 at 16:33, ssg shiv...@gmail.com javascript: wrote:

 Thanks Thomas. I tried your suggestion as below.
 *stringAttribute key=org.eclipse.jdt.launching.PROGRAM_ARGUMENTS 
 value=-war www -startupUrl mmsea/app.jsp -noserver -port 9080/*

 I am getting the following error now;

 Missing required argument 'module[s]'
 Google Web Toolkit 2.7.0
 DevMode [-[no]startServer] [-port port-number | auto] [-whitelist 
 whitelist-string] [-blacklist blacklist-string] [-logdir directory] 
 [-logLevel level] [-gen dir] [-bindAddress host-name-or-address] 
 [-codeServerPort port-number | auto] [-[no]superDevMode] [-server 
 servletContainerLauncher[:args]] [-startupUrl url] [-war dir] [-deploy dir] 
 [-extra dir] [-modulePathPrefix ] [-workDir dir] [-XmethodNameDisplayMode 
 NONE | ONLY_METHOD_NAME | ABBREVIATED | FULL] [-sourceLevel [auto, 1.6, 
 1.7]] [-XjsInteropMode [NONE, JS, CLOSURE]] [-[no]incremental] module[s] 

 where 
   -[no]startServer Starts a servlet container serving the 
 directory specified by the -war flag. (defaults to OFF)
   -portSpecifies the TCP port for the embedded web 
 server (defaults to )
   -whitelist   Allows the user to browse URLs that match the 
 specified regexes (comma or space separated)
   -blacklist   Prevents the user browsing URLs that match the 
 specified regexes (comma or space separated)
   -logdir  Logs to a file in the given directory, as well 
 as graphically
   -logLevelThe level of logging detail: ERROR, WARN, 
 INFO, TRACE, DEBUG, SPAM, or ALL
   -gen Debugging: causes normally-transient generated 
 types to be saved in the specified directory
   -bindAddress Specifies the bind address for the code server 
 and web server (defaults to 127.0.0.1)
   -codeServerPort  Specifies the TCP port for the code server 
 (defaults to 9997 for classic Dev Mode or 9876 for Super Dev Mode)
   -[no]superDevModeRuns Super Dev Mode instead of classic 
 Development Mode. (defaults to ON)
   -server  Specify a different embedded web server to run 
 (must implement ServletContainerLauncher)
   -startupUrl  Automatically launches the specified URL
   -war The directory into which deployable output 
 files will be written (defaults to 'war')
   -deploy  The directory into which deployable but not 
 servable output files will be written (defaults to 'WEB-INF/deploy' under 
 the -war directory/jar, and may be the same as the -extra directory/jar)
   -extra   The directory into which extra files, not 
 intended for deployment, will be written
   -modulePathPrefixThe subdirectory inside the war dir where 
 DevMode will create module directories. (defaults empty for top level)
   -workDir The compiler's working directory for internal 
 use (must be writeable; defaults to a system temp dir)
   -XmethodNameDisplayMode  Emit extra information allow chrome dev tools 
 to display Java identifiers in many places instead of JavaScript functions.
   -sourceLevel Specifies Java source level (defaults to 
 auto:1.6)
   -XjsInteropMode  Specifies JsInterop mode, either NONE, JS, or 
 CLOSURE (defaults to NONE)
   -[no]incremental Compiles faster by reusing data from the 
 previous compile. (defaults to ON)
 and 
   module[s]Specifies the name(s) of the module(s) to host

 Please let me know.
 Thanks a lot in advance.

 On Tuesday, February 24, 2015 at 12:10:06 PM UTC-5, Thomas Broyer wrote:



 On Tuesday, February 24, 2015 at 4:53:34 PM UTC+1, ssg wrote:

 Jens,

 Below is the message I am getting. Not sure which one to use or how to 
 use. 

 Unknown argument: -out
 Google Web Toolkit 2.7.0
 DevMode [-[no]startServer] [-port port-number | auto] [-whitelist 
 whitelist-string] [-blacklist blacklist-string] [-logdir directory] 
 [-logLevel level] [-gen dir] [-bindAddress host-name-or-address] 
 [-codeServerPort port-number | auto] [-[no]superDevMode] [-server 
 servletContainerLauncher[:args]] [-startupUrl url] [-war dir] [-deploy 
 dir] [-extra dir] [-modulePathPrefix ] [-workDir dir] 
 [-XmethodNameDisplayMode NONE | ONLY_METHOD_NAME | ABBREVIATED | FULL] 
 [-sourceLevel [auto, 1.6, 1.7]] [-XjsInteropMode [NONE, JS, CLOSURE]] 
 [-[no]incremental] module[s] 

 where 
   -[no]startServer Starts a servlet container serving the 
 directory specified by the -war flag. (defaults to ON)
   -portSpecifies the TCP port for the embedded web 
 server

Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)

2015-02-24 Thread ssg

Thanks Jens. I still have the 2nd error Unknown argument: -out

How can I rewrite the 2nd line in red text above for GWT 2.7.0. Copying the 
line here again.



*stringAttribute key=org.eclipse.jdt.launching.PROGRAM_ARGUMENTS 
value=-out www mmsea/app.jsp#10;-noserver#10;-port 9080/*Please let me 
know. Thanks.


On Tuesday, February 24, 2015 at 9:52:24 AM UTC-5, Jens wrote:

 Instead of GWTShell use com.google.gwt.dev.DevMode

 -- J.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

launchConfiguration issue for GWT 2.7.0 (New to GWT)

2015-02-24 Thread ssg

I am migrating from GWT 1.7.0 to GWT 2.7.0

My GWT 1.7.0 launch configuration ( from MmseaApp.launch file)

?xml version=1.0 encoding=UTF-8 standalone=no?
launchConfiguration type=org.eclipse.jdt.launching.localJavaApplication
listAttribute key=org.eclipse.debug.core.MAPPED_RESOURCE_PATHS
listEntry value=/MmseaApp/
/listAttribute
listAttribute key=org.eclipse.debug.core.MAPPED_RESOURCE_TYPES
listEntry value=4/
/listAttribute
booleanAttribute key=org.eclipse.debug.core.appendEnvironmentVariables 
value=true/
listAttribute key=org.eclipse.jdt.launching.CLASSPATH
listEntry value=lt;?xml version=quot;1.0quot; 
encoding=quot;UTF-8quot;?gt;#13;#10;lt;runtimeClasspathEntry 
containerPath=quot;org.eclipse.jdt.launching.JRE_CONTAINERquot; 
javaProject=quot;MmseaAppquot; path=quot;1quot; 
type=quot;4quot;/gt;#13;#10;/
listEntry value=lt;?xml version=quot;1.0quot; 
encoding=quot;UTF-8quot;?gt;#13;#10;lt;runtimeClasspathEntry 
internalArchive=quot;/MmseaApp/srcquot; path=quot;3quot; 
type=quot;2quot;/gt;#13;#10;/
listEntry value=lt;?xml version=quot;1.0quot; 
encoding=quot;UTF-8quot;?gt;#13;#10;lt;runtimeClasspathEntry 
id=quot;org.eclipse.jdt.launching.classpathentry.defaultClasspathquot;gt;#13;#10;lt;memento
 
project=quot;MmseaAppquot;/gt;#13;#10;lt;/runtimeClasspathEntrygt;#13;#10;/
listEntry value=lt;?xml version=quot;1.0quot; 
encoding=quot;UTF-8quot;?gt;#13;#10;lt;runtimeClasspathEntry 
externalArchive=quot;C:/gwt 
1.7.0/gwt-windows-1.7.0/gwt-dev-windows.jarquot; path=quot;3quot; 
type=quot;2quot;/gt;#13;#10;/
/listAttribute
booleanAttribute key=org.eclipse.jdt.launching.DEFAULT_CLASSPATH 
value=false/


*stringAttribute key=org.eclipse.jdt.launching.MAIN_TYPE 
value=com.google.gwt.dev.GWTShell/stringAttribute 
key=org.eclipse.jdt.launching.PROGRAM_ARGUMENTS value=-out www 
mmsea/app.jsp#10;-noserver#10;-port 9080/*

stringAttribute key=org.eclipse.jdt.launching.PROJECT_ATTR 
value=MmseaApp/
stringAttribute key=org.eclipse.jdt.launching.VM_ARGUMENTS 
value=-Xmx256M/
/launchConfiguration

*I need help in rewriting/changing the above 2 lines in red text for 
migrating to GWT 2.7.0 ;*


*Below are the errors I am getting;*
   
   1. Exception in thread main java.lang.NoClassDefFoundError: 
   com.google.gwt.dev.GWTShell
   Caused by: java.lang.ClassNotFoundException: com.google.gwt.dev.GWTShell
   at java.net.URLClassLoader.findClass(URLClassLoader.java:423)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:660)
   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:346)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:626)
   2. Unknown argument: -out

Looks like 'com.google.gwt.dev.GWTShell' is deprecated. What is the 
replacement code for this in GWT 2.7.0 ?

Any help would be greatly appreciated.

Thanks a lot in advance.



-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)

2015-02-24 Thread ssg

Jens,

Below is the message I am getting. Not sure which one to use or how to use. 

Unknown argument: -out
Google Web Toolkit 2.7.0
DevMode [-[no]startServer] [-port port-number | auto] [-whitelist 
whitelist-string] [-blacklist blacklist-string] [-logdir directory] 
[-logLevel level] [-gen dir] [-bindAddress host-name-or-address] 
[-codeServerPort port-number | auto] [-[no]superDevMode] [-server 
servletContainerLauncher[:args]] [-startupUrl url] [-war dir] [-deploy dir] 
[-extra dir] [-modulePathPrefix ] [-workDir dir] [-XmethodNameDisplayMode 
NONE | ONLY_METHOD_NAME | ABBREVIATED | FULL] [-sourceLevel [auto, 1.6, 
1.7]] [-XjsInteropMode [NONE, JS, CLOSURE]] [-[no]incremental] module[s] 

where 
  -[no]startServer Starts a servlet container serving the directory 
specified by the -war flag. (defaults to ON)
  -portSpecifies the TCP port for the embedded web 
server (defaults to )
  -whitelist   Allows the user to browse URLs that match the 
specified regexes (comma or space separated)
  -blacklist   Prevents the user browsing URLs that match the 
specified regexes (comma or space separated)
  -logdir  Logs to a file in the given directory, as well 
as graphically
  -logLevelThe level of logging detail: ERROR, WARN, INFO, 
TRACE, DEBUG, SPAM, or ALL
  -gen Debugging: causes normally-transient generated 
types to be saved in the specified directory
  -bindAddress Specifies the bind address for the code server 
and web server (defaults to 127.0.0.1)
  -codeServerPort  Specifies the TCP port for the code server 
(defaults to 9997 for classic Dev Mode or 9876 for Super Dev Mode)
  -[no]superDevModeRuns Super Dev Mode instead of classic 
Development Mode. (defaults to ON)
  -server  Specify a different embedded web server to run 
(must implement ServletContainerLauncher)
  -startupUrl  Automatically launches the specified URL
  -war The directory into which deployable output files 
will be written (defaults to 'war')
  -deploy  The directory into which deployable but not 
servable output files will be written (defaults to 'WEB-INF/deploy' under 
the -war directory/jar, and may be the same as the -extra directory/jar)
  -extra   The directory into which extra files, not 
intended for deployment, will be written
  -modulePathPrefixThe subdirectory inside the war dir where 
DevMode will create module directories. (defaults empty for top level)
  -workDir The compiler's working directory for internal 
use (must be writeable; defaults to a system temp dir)
  -XmethodNameDisplayMode  Emit extra information allow chrome dev tools to 
display Java identifiers in many places instead of JavaScript functions.
  -sourceLevel Specifies Java source level (defaults to 
auto:1.6)
  -XjsInteropMode  Specifies JsInterop mode, either NONE, JS, or 
CLOSURE (defaults to NONE)
  -[no]incremental Compiles faster by reusing data from the 
previous compile. (defaults to ON)
and 
  module[s]Specifies the name(s) of the module(s) to host


*Can you please help me in rewriting this line based on the above 
suggestions ?*
*stringAttribute key=org.eclipse.jdt.launching.PROGRAM_ARGUMENTS 
value=-out www mmsea/app.jsp#10;-noserver#10;-port 9080/*

Thanks a lot.

On Tuesday, February 24, 2015 at 10:39:30 AM UTC-5, Jens wrote:


 Thanks Jens. I still have the 2nd error Unknown argument: -out

  
 The DevMode class should show you all valid arguments and the description 
 should tell you which one to choose as a replacement. I don't know anything 
 about GWT 1.7, but I assume DevMode -war is probably the same as GWTShell 
 -out.

 -- J.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)

2015-02-24 Thread ssg

Thanks Thomas. I tried your suggestion as below.
*stringAttribute key=org.eclipse.jdt.launching.PROGRAM_ARGUMENTS 
value=-war www -startupUrl mmsea/app.jsp -noserver -port 9080/*

I am getting the following error now;

Missing required argument 'module[s]'
Google Web Toolkit 2.7.0
DevMode [-[no]startServer] [-port port-number | auto] [-whitelist 
whitelist-string] [-blacklist blacklist-string] [-logdir directory] 
[-logLevel level] [-gen dir] [-bindAddress host-name-or-address] 
[-codeServerPort port-number | auto] [-[no]superDevMode] [-server 
servletContainerLauncher[:args]] [-startupUrl url] [-war dir] [-deploy dir] 
[-extra dir] [-modulePathPrefix ] [-workDir dir] [-XmethodNameDisplayMode 
NONE | ONLY_METHOD_NAME | ABBREVIATED | FULL] [-sourceLevel [auto, 1.6, 
1.7]] [-XjsInteropMode [NONE, JS, CLOSURE]] [-[no]incremental] module[s] 

where 
  -[no]startServer Starts a servlet container serving the directory 
specified by the -war flag. (defaults to OFF)
  -portSpecifies the TCP port for the embedded web 
server (defaults to )
  -whitelist   Allows the user to browse URLs that match the 
specified regexes (comma or space separated)
  -blacklist   Prevents the user browsing URLs that match the 
specified regexes (comma or space separated)
  -logdir  Logs to a file in the given directory, as well 
as graphically
  -logLevelThe level of logging detail: ERROR, WARN, INFO, 
TRACE, DEBUG, SPAM, or ALL
  -gen Debugging: causes normally-transient generated 
types to be saved in the specified directory
  -bindAddress Specifies the bind address for the code server 
and web server (defaults to 127.0.0.1)
  -codeServerPort  Specifies the TCP port for the code server 
(defaults to 9997 for classic Dev Mode or 9876 for Super Dev Mode)
  -[no]superDevModeRuns Super Dev Mode instead of classic 
Development Mode. (defaults to ON)
  -server  Specify a different embedded web server to run 
(must implement ServletContainerLauncher)
  -startupUrl  Automatically launches the specified URL
  -war The directory into which deployable output files 
will be written (defaults to 'war')
  -deploy  The directory into which deployable but not 
servable output files will be written (defaults to 'WEB-INF/deploy' under 
the -war directory/jar, and may be the same as the -extra directory/jar)
  -extra   The directory into which extra files, not 
intended for deployment, will be written
  -modulePathPrefixThe subdirectory inside the war dir where 
DevMode will create module directories. (defaults empty for top level)
  -workDir The compiler's working directory for internal 
use (must be writeable; defaults to a system temp dir)
  -XmethodNameDisplayMode  Emit extra information allow chrome dev tools to 
display Java identifiers in many places instead of JavaScript functions.
  -sourceLevel Specifies Java source level (defaults to 
auto:1.6)
  -XjsInteropMode  Specifies JsInterop mode, either NONE, JS, or 
CLOSURE (defaults to NONE)
  -[no]incremental Compiles faster by reusing data from the 
previous compile. (defaults to ON)
and 
  module[s]Specifies the name(s) of the module(s) to host

Please let me know.
Thanks a lot in advance.

On Tuesday, February 24, 2015 at 12:10:06 PM UTC-5, Thomas Broyer wrote:



 On Tuesday, February 24, 2015 at 4:53:34 PM UTC+1, ssg wrote:

 Jens,

 Below is the message I am getting. Not sure which one to use or how to 
 use. 

 Unknown argument: -out
 Google Web Toolkit 2.7.0
 DevMode [-[no]startServer] [-port port-number | auto] [-whitelist 
 whitelist-string] [-blacklist blacklist-string] [-logdir directory] 
 [-logLevel level] [-gen dir] [-bindAddress host-name-or-address] 
 [-codeServerPort port-number | auto] [-[no]superDevMode] [-server 
 servletContainerLauncher[:args]] [-startupUrl url] [-war dir] [-deploy dir] 
 [-extra dir] [-modulePathPrefix ] [-workDir dir] [-XmethodNameDisplayMode 
 NONE | ONLY_METHOD_NAME | ABBREVIATED | FULL] [-sourceLevel [auto, 1.6, 
 1.7]] [-XjsInteropMode [NONE, JS, CLOSURE]] [-[no]incremental] module[s] 

 where 
   -[no]startServer Starts a servlet container serving the 
 directory specified by the -war flag. (defaults to ON)
   -portSpecifies the TCP port for the embedded web 
 server (defaults to )
   -whitelist   Allows the user to browse URLs that match the 
 specified regexes (comma or space separated)
   -blacklist   Prevents the user browsing URLs that match the 
 specified regexes (comma or space separated)
   -logdir  Logs to a file in the given directory, as well 
 as graphically
   -logLevelThe level of logging detail: ERROR, WARN, 
 INFO, TRACE, DEBUG, SPAM, or ALL
   -gen

Re: What is the path of the Host HTML page that loads our GWT app ? (new to GWT)

2015-02-18 Thread ssg

Thanks Jens.

On Wednesday, February 18, 2015 at 2:55:14 PM UTC-5, Jens wrote:


1. XxxApp/src/com/acg/xxx/gwt/public

 Seems like the best bet because all public resources are copied to the 
 GWT compilation output folder automatically.


 -- J.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: What is the path of the Host HTML page that loads our GWT app ? (new to GWT)

2015-02-18 Thread ssg

Thanks Thomas.

On Wednesday, February 18, 2015 at 3:46:07 PM UTC-5, Thomas Broyer wrote:

 The one(s) that loads the *.nocache.js script.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

DeferredCommand Deprecated. Need help.

2015-02-18 Thread ssg

I am migrating from GWT 1.7.0 to GWT 2.7.0

Below is the code from GW 1.7.0

   * DeferredCommand*.addPause();
*DeferredCommand*.addCommand(new Command() {

@Override
public void execute() {
panel.getEl().unmask();
}
});

Since the *DeferredCommand *is deprecated*, *what is the equivalent code in 
GWT 2.7.0 for the following lines
* DeferredCommand*.addPause(); 
 
*DeferredCommand*.addCommand(new Command() {

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

What is the path of the Host HTML page that loads our GWT app ? (new to GWT)

2015-02-18 Thread ssg

I have to add ext-js script tags in the Host HTML page that loads my GWT 
app. I am migrating this application (Xxx) from GWT 1.7.0 to GWT 2.7.0.

script src=js/ext/adapter/ext/ext-base.js/script and 
script src=js/ext/ext-all.js/script

My application has Xxx.html pages in 4 different locations; (Xxx is my 
application name); 

*which one of the following is the right place to add ext-js script tags ?*
   
   1. XxxApp/build/com.acg.xxx.gwt.Xxx
   2. XxxApp/src/com/acg/xxx/gwt/public
   3. XxxApp/war/com.acg.xxx.gwt.Xxx
   4. XxxApp/WebContent


Can someone please help me?

Thank you in advance.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Error migrating to GWT 2.7.0 (script tags in the gwt.xml files)

2015-01-29 Thread ssg

Thomas,
Thanks a lot very much for your response. 

On Wednesday, January 28, 2015 at 4:45:17 AM UTC-5, Thomas Broyer wrote:



 On Tuesday, January 27, 2015 at 6:20:53 PM UTC+1, ssg wrote:

  Hi All,
 I am getting the following error while running ANT Build.xml; Please help 
 me in correcting the following.

 *[java]   [ERROR] The Cross-Site-Iframe linker does not support 
 script tags in the gwt.xml files, but the gwt.xml file (or the gwt.xml 
 files which it includes) contains the following script tags: *

 * [**java**] js/ext/adapter/ext/ext-base.js*

 * [**java**] js/ext/ext-all.js*
 * [java] In order for your application to run correctly, you will 
 need to include these tags in your host page directly. In order to avoid 
 this error, you will need to remove the script tags from the gwt.xml file, 
 or add this property to the gwt.xml file: set-configuration-property 
 name='xsiframe.failIfScriptTag' value='FALSE'/*

 Based on the above message, 
 *STEP 1:*
   How do I include these tags in the host page? WHERE is the host page 
 and WHAT all tags I have to include in the host page ?



 The host page is the HTML page that loads your GWT app: 
 http://www.gwtproject.org/doc/latest/DevGuideOrganizingProjects.html#DevGuideHostPage
 So you'll have to put script 
 src=js/ext/adapter/ext/ext-base.js/script and script 
 src=js/ext/ext-all.js/script in there (adapt the paths as necessary).
  



 *STEP 2:*
  I have added *set-configuration-property 
 name='xsiframe.failIfScriptTag' value='FALSE'/ *to my gwt.xml file. 


 I'd have rather removed the script elements from the gwt.xml, but indeed 
 that works too…
  


 *Below is my gwt.xml code;*

 ?xml version=1.0 encoding=UTF-8?
 !--!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 
 1.7.0//EN 
 http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd
 --
 !DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 
 2.7.0//EN http://www.gwtproject.org/doctype/2.7.0/gwt-module.dtd;
 module
 inherits name=com.google.gwt.user.User /
 inherits name='com.google.gwt.json.JSON' /
 !-- Inherit the GWTEXT stuff.--
 stylesheet src=js/ext/resources/css/ext-all.css /


 I'd also move that to the host page: link rel=stylesheet 
 href=js/ext/resources/css/ext-all.css /



-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Error migrating to GWT 2.7.0 (script tags in the gwt.xml files)

2015-01-29 Thread ssg

Jim,
Thanks a lot very much for your response.

On Tuesday, January 27, 2015 at 12:40:19 PM UTC-5, Jim Douglas wrote:

 Yeah, this was a hassle for me too.  This is the breaking change in 2.7.0:

 https://code.google.com/p/google-web-toolkit/issues/detail?id=8578

 I did a few things to bridge the gap from 2.6.1 to 2.7.0.

 (1) Add this to the project.gwt.xml to not crash on those script tags:

   set-configuration-property name='xsiframe.failIfScriptTag' 
 value='FALSE'/

 (2) Add this to my GWT client entry point (details will vary depending on 
 your specific .js files):

 @Override

 public void onModuleLoad()

 {

 if (Browser.isJQueryLoaded()) // GWT 2.6.1 script tags are 
 supported

 {

 if (!Browser.isTouch())

 Browser.setTooltips(BUISupport.initJQueryTooltip());

 }

 else // GWT 2.7.0+; we need to load external script files.

 {

 ListString injectList = new ArrayListString();

 injectList.add(html2canvas.min.js);

 injectList.add(jquery-1.11.1.min.js);

 injectList.add(jquery-ui.min.js);

 inject(injectList);

 }
 ...

 public static native boolean isJQueryLoaded()

 /*-{

 return (typeof $wnd.jQuery != 'undefined');

 }-*/;

 private void inject(final ListString p_jsList)

 {

 final String js =

 GWT.getModuleBaseForStaticFiles() + p_jsList.remove(0);


 ScriptInjector.fromUrl(js).setCallback(new CallbackVoid, 
 Exception()

 {

 @Override

 public void onFailure(Exception e)

 {

 Log.log(inject  + js +  failure  + e);

 }


 @Override

 public void onSuccess(Void ok)

 {

 if (!p_jsList.isEmpty())

 inject(p_jsList);

 else if (!Browser.isTouch())

 Browser.setTooltips(BUISupport.initJQueryTooltip());

 }

 }).setWindow(ScriptInjector.TOP_WINDOW).inject();

 }

 On Tuesday, January 27, 2015 at 9:20:53 AM UTC-8, ssg wrote:

  Hi All,
 I am getting the following error while running ANT Build.xml; Please help 
 me in correcting the following.

 *[java]   [ERROR] The Cross-Site-Iframe linker does not support 
 script tags in the gwt.xml files, but the gwt.xml file (or the gwt.xml 
 files which it includes) contains the following script tags: *

 * [**java**] js/ext/adapter/ext/ext-base.js*

 * [**java**] js/ext/ext-all.js*
 * [java] In order for your application to run correctly, you will 
 need to include these tags in your host page directly. In order to avoid 
 this error, you will need to remove the script tags from the gwt.xml file, 
 or add this property to the gwt.xml file: set-configuration-property 
 name='xsiframe.failIfScriptTag' value='FALSE'/*

 Based on the above message, 
 *STEP 1:*
   How do I include these tags in the host page? WHERE is the host page 
 and WHAT all tags I have to include in the host page ?

 *STEP 2:*
  I have added *set-configuration-property 
 name='xsiframe.failIfScriptTag' value='FALSE'/ *to my gwt.xml file. 

 *Below is my gwt.xml code;*

 ?xml version=1.0 encoding=UTF-8?
 !--!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 
 1.7.0//EN 
 http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd
 --
 !DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 
 2.7.0//EN http://www.gwtproject.org/doctype/2.7.0/gwt-module.dtd;
 module
 inherits name=com.google.gwt.user.User /
 inherits name='com.google.gwt.json.JSON' /
 !-- Inherit the GWTEXT stuff.--
 stylesheet src=js/ext/resources/css/ext-all.css /

 set-configuration-property name='xsiframe.failIfScriptTag' 
 value='FALSE'/

 script src=js/ext/adapter/ext/ext-base.js /
 script src=js/ext/ext-all.js /
 inherits name=com.gwtext.GwtExt /
 inherits name=com.gwtextux.GwtExtUx /

 !-- RPC service servlet declarations --
 servlet path=/appname.rpc 
 class=com.acg.mmsea.server.service.AppnameServiceImpl /
 servlet path=/codeDecode.rpc
 
 class=com.acg.appname.server.service.AppnameCodesDecodeServiceImpl /

 !-- Specify the app entry point class. --
 entry-point class='com.acg.appname.gwt.client.Appname' /
 /module

 Thanks a lot in advance.




-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Error migrating to GWT 2.7.0 (script tags in the gwt.xml files)

2015-01-27 Thread ssg

 Hi All,
I am getting the following error while running ANT Build.xml; Please help 
me in correcting the following.

*[java]   [ERROR] The Cross-Site-Iframe linker does not support 
script tags in the gwt.xml files, but the gwt.xml file (or the gwt.xml 
files which it includes) contains the following script tags: *

* [**java**] js/ext/adapter/ext/ext-base.js*

* [**java**] js/ext/ext-all.js*
* [java] In order for your application to run correctly, you will need 
to include these tags in your host page directly. In order to avoid this 
error, you will need to remove the script tags from the gwt.xml file, or 
add this property to the gwt.xml file: set-configuration-property 
name='xsiframe.failIfScriptTag' value='FALSE'/*

Based on the above message, 
*STEP 1:*
  How do I include these tags in the host page? WHERE is the host page and 
WHAT all tags I have to include in the host page ?

*STEP 2:*
 I have added *set-configuration-property name='xsiframe.failIfScriptTag' 
value='FALSE'/ *to my gwt.xml file. 

*Below is my gwt.xml code;*

?xml version=1.0 encoding=UTF-8?
!--!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 
1.7.0//EN 
http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd;--
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 2.7.0//EN 
http://www.gwtproject.org/doctype/2.7.0/gwt-module.dtd;
module
inherits name=com.google.gwt.user.User /
inherits name='com.google.gwt.json.JSON' /
!-- Inherit the GWTEXT stuff.--
stylesheet src=js/ext/resources/css/ext-all.css /

set-configuration-property name='xsiframe.failIfScriptTag' 
value='FALSE'/

script src=js/ext/adapter/ext/ext-base.js /
script src=js/ext/ext-all.js /
inherits name=com.gwtext.GwtExt /
inherits name=com.gwtextux.GwtExtUx /

!-- RPC service servlet declarations --
servlet path=/appname.rpc 
class=com.acg.mmsea.server.service.AppnameServiceImpl /
servlet path=/codeDecode.rpc

class=com.acg.appname.server.service.AppnameCodesDecodeServiceImpl /

!-- Specify the app entry point class. --
entry-point class='com.acg.appname.gwt.client.Appname' /
/module

Thanks a lot in advance.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Errors migrating to GWT 2.7.0 . Can someone please help me ?

2015-01-21 Thread ssg

] at 
com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)
 [java] at com.google.gwt.dev.Compiler.main(Compiler.java:127)
 *[java] Caused by: java.io.InvalidClassException: 
com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
classdesc serialVersionUID = -2407201776821563037, local class 
serialVersionUID = 4713379764594032837*
 [java] at 
java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:619)
 [java] at 
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1606)
 [java] at 
java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1501)
 [java] at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1755)
 [java] at 
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1334)
 [java] at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1976)
 [java] at 
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1900)
 [java] at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1782)
 [java] at 
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1334)
 [java] at 
java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1976)
 [java] at 
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1900)
 [java] at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1782)
 [java] at 
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1334)
 [java] at 
java.io.ObjectInputStream.readObject(ObjectInputStream.java:353)
 [java] at java.util.ArrayList.readObject(ArrayList.java:731)
 [java] at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown 
Source)
 [java] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 [java] at java.lang.reflect.Method.invoke(Method.java:600)
 [java] at 
java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1028)
 [java] at 
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1878)
 [java] at 
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1782)
 [java] at 
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1334)
 [java] at 
java.io.ObjectInputStream.readObject(ObjectInputStream.java:353)
 [java] at 
com.google.gwt.dev.jjs.ast.JDeclaredType.readMembers(JDeclaredType.java:412)
 [java] at 
com.google.gwt.dev.jjs.ast.JProgram.deserializeTypes(JProgram.java:229)
 [java] at 
com.google.gwt.dev.javac.CompilationUnit.getTypes(CompilationUnit.java:381)
 [java] ... 32 more

BUILD FAILED
C:\APPNAME WrkSpc\AppnameApp\build.xml:64: Java returned: 1
Endof
 
ERROR


On Friday, January 16, 2015 at 12:12:14 PM UTC-5, Thomas Broyer wrote:



 On Friday, January 16, 2015 at 6:02:18 PM UTC+1, ssg wrote:

 Thomas, Thanks a lot for your response.
 I am using JDK1.6. I am also new to GWT.

 1) Can you please help me how  where to add *-Dgwt.usearchives=false* ?


 In your Ant build, where you call the GWT Compiler, add a sysproperty 
 key=gwt.usearchives value=false / to your java task.
  

 2) Are you suggesting me to use GWT 2.8 instead of 2.7 now?


 No!
 (GWT 2.8 will require Java 7+ anyway)


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Errors migrating to GWT 2.7.0 . Can someone please help me ?

2015-01-16 Thread ssg

Thomas, Thanks a lot for your response.
I am using JDK1.6. I am also new to GWT.

1) Can you please help me how  where to add *-Dgwt.usearchives=false* ?
2) Are you suggesting me to use GWT 2.8 instead of 2.7 now?

Thanks in advance.

On Friday, January 16, 2015 at 4:15:32 AM UTC-5, Thomas Broyer wrote:

 What JDK are you using? If you're not using OpenJDK or Oracle's JDK (e.g. 
 IBM JDK), then add -Dgwt.usearchives=false.

 Note: GWT 2.8 will remove the gwtar (which are serialized precompilation 
 state) so it should hopefully work out of the box with any JDK.

 On Thursday, January 15, 2015 at 9:42:51 PM UTC+1, ssg wrote:

 I am getting the following error while performing Ant Build.
 *Can someone please help me ?*

 Compiling module com.acg.mmsea.gwt.Appname
  [java][WARN] Unable to read: 
 jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/core/Core.gwtar. 
 Skipping: java.io.InvalidClassException: 
 com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
 classdesc serialVersionUID = -2407201776821563037, local class 
 serialVersionUID = 4713379764594032837
  [java][WARN] Unable to read: 
 jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/user/User.gwtar. 
 Skipping: java.io.InvalidClassException: 
 com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
 classdesc serialVersionUID = -2407201776821563037, local class 
 serialVersionUID = 4713379764594032837
  [java][WARN] Unable to read: 
 jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/user/UI.gwtar. 
 Skipping: java.io.InvalidClassException: 
 com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
 classdesc serialVersionUID = -2407201776821563037, local class 
 serialVersionUID = 4713379764594032837
  [java][WARN] Unable to read: 
 jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/user/DOM.gwtar. 
 Skipping: java.io.InvalidClassException: 
 com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
 classdesc serialVersionUID = -2407201776821563037, local class 
 serialVersionUID = 4713379764594032837
  [java][WARN] Unable to read: 
 jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/user/RemoteService.gwtar.
  
 Skipping: java.io.InvalidClassException: 
 com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
 classdesc serialVersionUID = -2407201776821563037, local class 
 serialVersionUID = 4713379764594032837
  [java][WARN] Unable to read: 
 jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/xml/XML.gwtar. 
 Skipping: java.io.InvalidClassException: 
 com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
 classdesc serialVersionUID = -2407201776821563037, local class 
 serialVersionUID = 4713379764594032837
  [java]Ignored 2 units with compilation errors in first pass.

 [ERROR] Unexpected internal compiler error
  [java] java.lang.RuntimeException: Unexpected IOException on 
 in-memory stream
  [java] at 
 com.google.gwt.dev.javac.CompilationUnit.getTypes(CompilationUnit.java:383)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.java:999)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:1595)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.java:1010)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:1595)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.java:1010)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:1595)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.java:1010)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:1595)
  [java] at 
 com.google.gwt.dev.jjs.impl.UnifyAst.addRootTypes(UnifyAst.java:733)
  [java] at 
 com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1291)
  [java] at 
 com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.constructJavaAst

Errors migrating to GWT 2.7.0 . Can someone please help me ?

2015-01-15 Thread ssg

I am getting the following error while performing Ant Build.
*Can someone please help me ?*

Compiling module com.acg.mmsea.gwt.Appname
 [java][WARN] Unable to read: 
jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/core/Core.gwtar. 
Skipping: java.io.InvalidClassException: 
com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
classdesc serialVersionUID = -2407201776821563037, local class 
serialVersionUID = 4713379764594032837
 [java][WARN] Unable to read: 
jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/user/User.gwtar. 
Skipping: java.io.InvalidClassException: 
com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
classdesc serialVersionUID = -2407201776821563037, local class 
serialVersionUID = 4713379764594032837
 [java][WARN] Unable to read: 
jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/user/UI.gwtar. 
Skipping: java.io.InvalidClassException: 
com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
classdesc serialVersionUID = -2407201776821563037, local class 
serialVersionUID = 4713379764594032837
 [java][WARN] Unable to read: 
jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/user/DOM.gwtar. 
Skipping: java.io.InvalidClassException: 
com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
classdesc serialVersionUID = -2407201776821563037, local class 
serialVersionUID = 4713379764594032837
 [java][WARN] Unable to read: 
jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/user/RemoteService.gwtar. 
Skipping: java.io.InvalidClassException: 
com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
classdesc serialVersionUID = -2407201776821563037, local class 
serialVersionUID = 4713379764594032837
 [java][WARN] Unable to read: 
jar:file:/C:/gwt-2.7.0/gwt-user.jar!/com/google/gwt/xml/XML.gwtar. 
Skipping: java.io.InvalidClassException: 
com.google.gwt.dev.jjs.SourceOrigin$1; local class incompatible: stream 
classdesc serialVersionUID = -2407201776821563037, local class 
serialVersionUID = 4713379764594032837
 [java]Ignored 2 units with compilation errors in first pass.

[ERROR] Unexpected internal compiler error
 [java] java.lang.RuntimeException: Unexpected IOException on in-memory 
stream
 [java] at 
com.google.gwt.dev.javac.CompilationUnit.getTypes(CompilationUnit.java:383)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.java:999)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:1595)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.java:1010)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:1595)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.java:1010)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:1595)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1653)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.translate(UnifyAst.java:1645)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.resolveType(UnifyAst.java:1552)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.assimilateSourceUnit(UnifyAst.java:1010)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.internalFindType(UnifyAst.java:1595)
 [java] at 
com.google.gwt.dev.jjs.impl.UnifyAst.addRootTypes(UnifyAst.java:733)
 [java] at 
com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.unifyJavaAst(JavaToJavaScriptCompiler.java:1291)
 [java] at 
com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.constructJavaAst(JavaToJavaScriptCompiler.java:1038)
 [java] at 
com.google.gwt.dev.jjs.JavaToJavaScriptCompiler$Precompiler.precompile(JavaToJavaScriptCompiler.java:954)
 [java] at 
com.google.gwt.dev.jjs.MonolithicJavaToJavaScriptCompiler.precompile(MonolithicJavaToJavaScriptCompiler.java:303)
 [java] at 
com.google.gwt.dev.jjs.JavaScriptCompiler.precompile(JavaScriptCompiler.java:38)
 [java] at 
com.google.gwt.dev.Precompile.precompile(Precompile.java:286)
 [java] at 
com.google.gwt.dev.Precompile.precompile(Precompile.java:229)
 [java] at 
com.google.gwt.dev.Precompile.precompile(Precompile.java:145)
 [java] at com.google.gwt.dev.Compiler.run(Compiler.java:206)
 [java] at

Re: (New to GWT) Need advise in migrating current app from GWT 1.7.0

2014-12-18 Thread ssg

Fabien, gwt1.7.0 does not support higher IE browsers. To support IE 10 and 
above browsers we have to upgrade gwt. Hope I clarified your question. Can 
you please answer my earlier questions?

On Wednesday, December 17, 2014 6:39:05 PM UTC-5, Fabien Dumay wrote:

 Hi, 

 My question will maybe seem to you stupid, but why do you need upgrade to 
 GWT 2.7? 
 The GWT of your project has never been updated for over 5 years. 
 Then suddenly you need to do it by your self! without even know GWT! 
 To really enjoy GWT 2.7 , you should rewrite almost all your project. 

 So finally, the question why do you need to do it? is a real question. 

 Anyway, very good luck for whatever you will do… 



-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: (New to GWT) Need advise in migrating current app from GWT 1.7.0

2014-12-18 Thread ssg

Jens,
Extremely sorry for multiple postings of same questions. Reason for this is
I did not find my earlier postings. A BIG thank you for answering my
questions. I will start working towards implementing your suggestions. I
will get back to you soon. Thanks a lot once again.

On Wednesday, December 17, 2014 5:55:23 PM UTC-5, Jens wrote:

As I am new to GWT development, I have done the following based on
current App gwt1.7.0
1) I have downloaded standalone GWT SDK 2.7.0
2) Current build.xml file using HostedMode as follows
target name=hosted depends=javac description=Run hosted mode
java failonerror=true fork=true
classname=com.google.gwt.dev.HostedMode
*Should I change the above lines to SuperDevMode ? *

HostedMode does not exist anymore, so yes you would need to replace it. I
guess your best bet is to execute webAppCreator of GWT 2.7.0 SDK and create
a new sample project with it. Then compare the build.xml file of the sample
project with the one of your app and make changes as needed.

3) Current App gwt 1.7.0 is using some GWT jar files under directory
\WebContent\WEB-INF\lib. I have replaced these gwt jars (gwt-user,
get-servlet,gwt-servlet-deps) with the latest 2.7.0 jars.
This directory also has jdom, jettison-1.0.1, json, gwtext
gwtextux jars. *Do I have to replace all these with the latest jars or
only the gwtext gwtextux jars ?*

In WebContent/WEB-INF/lib should never ever contain gwt-user.jar /
gwt-dev.jar. Both jars are only used during development and compilation to
JavaScript. Only gwt-servlet.jar / gwt-servlet-deps.jar need to be deployed
on server side (if you use GWT-RPC).
It also seems strange that other GWT libraries (gwtext / gwtextux) are in
WEB-INF/lib since you usually don't need GWT libraries on the server. But I
don't know these libraries so maybe they contain server side classes as
well.

I found gwtext-2.0.5 at http://gwt-ext.com/download/. *Is this the latest
and the right one for migrating to gwt 2.7.0 ?*
I found gwtextux.jar at http://www.java2s.com/Code/Jar/CatalogJar.htm

No idea if all your libraries are compatible to GWT 2.7, you need to check
that on your own.

In the above code I have modified/changed the first line *FROM *
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit
1.7.0//EN
http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd;

* TO*
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit
2.7.0//EN
https://gwt.googlesource.com/gwt/+/2.7.0/distro-source/core/src/gwt-module.dtd

*Is this modification correct?*

Replace

https://gwt.googlesource.com/gwt/+/2.7.0/distro-source/core/src/gwt-module.dtd

with

http://www.gwtproject.org/doctype/2.7.0/gwt-module.dtd

*Is there anymore changes I need to do in this x.gwt.xml file ?*

The script tags in your *.gwt.xml file will cause a compile error in GWT
2.7 because by default GWT 2.7 uses a new linker that does not support
these script tags. You need to include these scripts directly into your
host page or use the class ScriptInjector + ClientBundle/TextResource to
inject them when your app starts.

-- J.

--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

(New to GWT) Need advise in migrating current app from GWT 1.7.0

2014-12-17 Thread ssg

Hi all,
I am new to GWT. Need your input. Current app is using GWT 1.7.0

Is it better to migrate to gwt2.6.1 because it will be much smoother with 
less hurdles than migrating to gwt2.7.0 since I am new to gwt ?
(OR)
Is it better to migrate to gwt2.7.0 even though I am new to gwt and the 
hurdles I face in migrating will be same as gwt2.6.1 ?

Any help would be greatly appreciated.

Thank you.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: (New to GWT) Need advise in migrating current app from GWT 1.7.0

2014-12-17 Thread ssg

Thanks a lot Jens.
As I am new to GWT development, I have done the following based on
current App gwt1.7.0
1) I have downloaded standalone GWT SDK 2.7.0
2) Current build.xml file using HostedMode as follows
target name=hosted depends=javac description=Run hosted mode
java failonerror=true fork=true
classname=com.google.gwt.dev.HostedMode
*Should I change the above lines to SuperDevMode ? *

3) Current App gwt 1.7.0 is using some GWT jar files under directory
\WebContent\WEB-INF\lib. I have replaced these gwt jars (gwt-user,
get-servlet,gwt-servlet-deps) with the latest 2.7.0 jars.
This directory also has jdom, jettison-1.0.1, json, gwtext gwtextux
jars. *Do I have to replace all these with the latest jars or only the
gwtext gwtextux jars ?*

I found gwtext-2.0.5 at http://gwt-ext.com/download/. *Is this the latest
and the right one for migrating to gwt 2.7.0 ?*
I found gwtextux.jar at http://www.java2s.com/Code/Jar/CatalogJar.htm

4) My current x.gwt.xml file code
?xml version=1.0 encoding=UTF-8?
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 1.7.0//EN
http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd;
module
inherits name=com.google.gwt.user.User /
inherits name='com.google.gwt.json.JSON' /
!-- Inherit the GWTEXT stuff.--
stylesheet src=js/ext/resources/css/ext-all.css /
script src=js/ext/adapter/ext/ext-base.js /
script src=js/ext/ext-all.js /
inherits name=com.gwtext.GwtExt /
inherits name=com.gwtextux.GwtExtUx /

!-- RPC service servlet declarations --
servlet path=/x.rpc
class=com.acg.mmsea.server.service.XServiceImpl /
servlet path=/codeDecode.rpc
class=com.acg.x.server.service.XCodesDecodeServiceImpl /

!-- Specify the app entry point class. --
entry-point class='com.acg.x.gwt.client.X' /

/module

In the above code I have modified/changed the first line *FROM *
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 1.7.0//EN
http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd;

* TO*
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 2.7.0//EN
https://gwt.googlesource.com/gwt/+/2.7.0/distro-source/core/src/gwt-module.dtd;
*Is this modification correct?*
*Is there anymore changes I need to do in this x.gwt.xml file ?*

Thanks a lot in advance for your time.

On Wednesday, December 17, 2014 12:34:49 PM UTC-5, Jens wrote:

Upgrading from 1.7 will probably mean quite some work anyways.

So I would go with 2.7 because it has a much faster SuperDevMode which is
important because up-to-date Chrome/FireFox/Opera/Safari do not support
classic GWT DevMode anymore.

The only really important difference between 2.6.1 and 2.7 (beside bug
fixes and SuperDevMode improvements) is that 2.7 does not support Internet
Explorer 6 / 7 and Opera = 12 anymore. If you need to support these
browsers then you can not use 2.7.0.

-- J.

Re: (New to GWT) Need advise in migrating current app from GWT 1.7.0

2014-12-17 Thread ssg

Thanks a lot for the previous response. Can someone please answer my
questions below.
As I am new to GWT development, I have done the following based on
current App gwt1.7.0
1) I have downloaded standalone GWT SDK 2.7.0
2) Current build.xml file using HostedMode as follows
target name=hosted depends=javac description=Run hosted mode
java failonerror=true fork=true classname=com.google.gwt.dev.
HostedMode
*Should I change the above lines to SuperDevMode ? *

3) Current App gwt 1.7.0 is using some GWT jar files under directory
\WebContent\WEB-INF\lib. I have replaced these gwt jars (gwt-user,
get-servlet,gwt-servlet-deps) with the latest 2.7.0 jars.
This directory also has jdom, jettison-1.0.1, json, gwtext gwtextux
jars. *Do I have to replace all these with the latest jars or only the
gwtext gwtextux jars ?*

I found gwtext-2.0.5 at http://gwt-ext.com/download/. *Is this the latest
and the right one for migrating to gwt 2.7.0 ?*
I found gwtextux.jar at http://www.java2s.com/Code/Jar/CatalogJar.htm

module
inherits name=com.google.gwt.user.User /
inherits name='com.google.gwt.json.JSON' /
!-- Inherit the GWTEXT stuff.--
stylesheet src=js/ext/resources/css/ext-all.css /
script src=js/ext/adapter/ext/ext-base.js /
script src=js/ext/ext-all.js /
inherits name=com.gwtext.GwtExt /
inherits name=com.gwtextux.GwtExtUx /

!-- RPC service servlet declarations --
servlet path=/x.rpc
class=com.acg.mmsea.server.service.XServiceImpl /
servlet path=/codeDecode.rpc
class=com.acg.x.server.service.XCodesDecodeServiceImpl /

!-- Specify the app entry point class. --
entry-point class='com.acg.x.gwt.client.X' /

/module

In the above code I have modified/changed the first line *FROM *
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 1.7.0//EN
http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd;

* TO*
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 2.7.0//EN
https://gwt.googlesource.com/gwt/+/2.7.0/distro-source/core/src/gwt-module.dtd

*Is this modification correct?*
*Is there anymore changes I need to do in this x.gwt.xml file ?*

Thanks a lot in advance for your time.

On Wednesday, December 17, 2014 9:48:36 AM UTC-5, ssg wrote:

Hi all,
I am new to GWT. Need your input. Current app is using GWT 1.7.0

Is it better to migrate to gwt2.6.1 because it will be much smoother with
less hurdles than migrating to gwt2.7.0 since I am new to gwt ?
(OR)
Is it better to migrate to gwt2.7.0 even though I am new to gwt and the
hurdles I face in migrating will be same as gwt2.6.1 ?

Any help would be greatly appreciated.

Thank you.

Need help migrating from gwt 1.7.0 to gwt 2.7.0

2014-12-17 Thread ssg

Can someone please answer my question (bold black) below?
As I am new to GWT  development, I have done the following based on 
current App gwt1.7.0
1) I have downloaded standalone GWT SDK 2.7.0
2) Current build.xml file using HostedMode as follows
target name=hosted depends=javac description=Run hosted mode
java failonerror=true fork=true classname=com.google.gwt.dev.
HostedMode
*Should I change the above lines to  SuperDevMode ?   *

3) Current App gwt 1.7.0 is using some GWT jar files under directory 
\WebContent\WEB-INF\lib. I have replaced these gwt jars (gwt-user, 
get-servlet,gwt-servlet-deps) with the latest 2.7.0 jars. 
 This directory also has jdom, jettison-1.0.1, json, gwtext  gwtextux 
jars. *Do I have to replace all these with the latest jars or only the 
gwtext  gwtextux jars ?*

I found gwtext-2.0.5 at http://gwt-ext.com/download/. *Is this the latest 
and the right one for migrating to gwt 2.7.0 ?*
I found gwtextux.jar at http://www.java2s.com/Code/Jar/CatalogJar.htm

4) My current x.gwt.xml file code
 ?xml version=1.0 encoding=UTF-8?
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 1.7.0//EN 
http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd

module
inherits name=com.google.gwt.user.User /
inherits name='com.google.gwt.json.JSON' /
!-- Inherit the GWTEXT stuff.--
stylesheet src=js/ext/resources/css/ext-all.css /
script src=js/ext/adapter/ext/ext-base.js /
script src=js/ext/ext-all.js /
inherits name=com.gwtext.GwtExt /
inherits name=com.gwtextux.GwtExtUx /

!-- RPC service servlet declarations --
servlet path=/x.rpc 
class=com.acg.mmsea.server.service.XServiceImpl /
servlet path=/codeDecode.rpc
class=com.acg.x.server.service.XCodesDecodeServiceImpl /

!-- Specify the app entry point class. --
entry-point class='com.acg.x.gwt.client.X' /

/module

In the above code I  have modified/changed the first line *FROM *
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 1.7.0//EN 
http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd;
  

* TO*
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 2.7.0//EN 
https://gwt.googlesource.com/gwt/+/2.7.0/distro-source/core/src/gwt-module.dtd

*Is this modification correct?*
*Is there anymore changes I need to do in this x.gwt.xml file ?*

Thanks a lot in advance for your time.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Which recent GWT version is the most stable version to migrate to?

2014-12-11 Thread ssg

Hi everyone,
I am new to GWT. Currently my App is using GWT 1.7.0. I am planning on 
migrating this App to a latest stable version of GWT. 
Can someone please suggest me asap?

Thanks a lot in advance.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Which recent GWT version is the most stable version to migrate to?

2014-12-11 Thread ssg

Jens, I know GWT2.7.0 is the latest version. Is it the most stable version?

On Thursday, December 11, 2014 10:11:32 AM UTC-5, Jens wrote:

 GWT 2.7.0 is the latest version: http://www.gwtproject.org/versions.html

 -- J.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Question about GWT 2.6.1

2014-07-11 Thread ssg

Thanks to earlier response from Jens (a member of this forum) .

Does GWT 2.6.1 work with browser IE 10 or hihger browser?
Does GWT 2.6.1 has backward compatability with browser IE 10 Compatability 
View, IE 9, IE 8 ?

Currently I am using GWT 1.7.0 and my application is NOT working with 
browser IE 10. 
Will migrating to latest version GWT 2.6.1 RESOLVE my issue?

Once again, thanks for any help regarding this.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT 1.7.0 is not working with browser IE 10 or above.

2014-07-10 Thread ssg

Good morning everyone,
I am currently using GWT 1.7.0. It was working fine in earlier versions of 
browser IE 10 Compatibility View, IE 9, IE 8.
Our company moved to Windows 7 with browser IE 10. My application is NOT 
working in IE 10 or higher?

Should I migrate to latest versions of GWT.? If yes, Which version of GWT 
should I migrate my application to? 
I am currently using GWT 1.7.0, Spring.
Any help regarding this would be greatly appreciated.

Thanks a lot in advance!

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Looks like ext-js issues migrating from GWT 1.7.0 to GWT 2.7.0. Need help.

Re: Looks like ext-js issues migrating from GWT 1.7.0 to GWT 2.7.0. Need help.

Re: Looks like ext-js issues migrating from GWT 1.7.0 to GWT 2.7.0. Need help.

Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)

Looks like ext-js issues migrating from GWT 1.7.0 to GWT 2.7.0. Need help.

Re: Looks like ext-js issues migrating from GWT 1.7.0 to GWT 2.7.0. Need help.

Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)

Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)

launchConfiguration issue for GWT 2.7.0 (New to GWT)

Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)

Re: launchConfiguration issue for GWT 2.7.0 (New to GWT)

Re: What is the path of the Host HTML page that loads our GWT app ? (new to GWT)

Re: What is the path of the Host HTML page that loads our GWT app ? (new to GWT)

DeferredCommand Deprecated. Need help.

What is the path of the Host HTML page that loads our GWT app ? (new to GWT)

Re: Error migrating to GWT 2.7.0 (script tags in the gwt.xml files)

Re: Error migrating to GWT 2.7.0 (script tags in the gwt.xml files)

Error migrating to GWT 2.7.0 (script tags in the gwt.xml files)

Re: Errors migrating to GWT 2.7.0 . Can someone please help me ?

Re: Errors migrating to GWT 2.7.0 . Can someone please help me ?

Errors migrating to GWT 2.7.0 . Can someone please help me ?

Re: (New to GWT) Need advise in migrating current app from GWT 1.7.0

Re: (New to GWT) Need advise in migrating current app from GWT 1.7.0

(New to GWT) Need advise in migrating current app from GWT 1.7.0

Re: (New to GWT) Need advise in migrating current app from GWT 1.7.0

Re: (New to GWT) Need advise in migrating current app from GWT 1.7.0

Need help migrating from gwt 1.7.0 to gwt 2.7.0

Which recent GWT version is the most stable version to migrate to?

Re: Which recent GWT version is the most stable version to migrate to?

Question about GWT 2.6.1

GWT 1.7.0 is not working with browser IE 10 or above.

31 matches

Site Navigation

Mail list logo

Footer information