[GWT] [ERROR] Hint: Check that your module inherits 'com.google.gwt.core.Core'

2015-04-23 Thread Danish Khan
Hi all, 

I am upgrading to GWT 2.7.0 / Smartgwt 5, and I am seeing the following 
error when I try to build it through maven: 

[GWT][ERROR] Hint: Check that your module inherits 
'com.google.gwt.core.Core' either directly or indirectly (most often by 
inheriting module 'com.google.gwt.user.User')

Here is my gwt.xml. Please let me know if you have any suggestions to fix 
this error. 



 

 








  
  
  
  
  
  


-- 
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: SDM and client debugging with eclipse debugger?

2015-04-23 Thread kwmailswm
OK, thanks for the info! This clarifies the behaviour I described in my 
initial post.

On Wednesday, April 22, 2015 at 3:23:32 PM UTC+2, Jens wrote:
>
> With SDM your client side code only runs in the browser and you have to 
> set break points in the browser's dev tools. Launching the JVM in debug 
> mode does not give you anything for client side debugging.
>
> There is an Eclipse plugin called SDGB on Github that allows Eclipse to 
> connect to Chrome browser and then you can set break points in Eclipse (and 
> Eclipse synchronizes them with Chrome browser).
>
>
> -- 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: SDM and client debugging with eclipse debugger?

2015-04-23 Thread kwmailswm
Hello Ivan,

thanks for pointing me to this plugin. I've been stumbled upon it via 
youtube, didn't give it a try yet since I am pretty sure that I will have 
installation problems due to company security restrictions. However, I just 
so that sdbg also provides a zip version of the plugin :-) 

Regards
Kristian

On Wednesday, April 22, 2015 at 3:40:41 PM UTC+2, Ivan Markov wrote:
>
> Here's the web-page of the plugin: http://sdbg.github.io/ 
> 
> Drop me a note if you can't get it running.
>
>
> сряда, 22 април 2015 г., 16:23:32 UTC+3, Jens написа:
>>
>> With SDM your client side code only runs in the browser and you have to 
>> set break points in the browser's dev tools. Launching the JVM in debug 
>> mode does not give you anything for client side debugging.
>>
>> There is an Eclipse plugin called SDGB on Github that allows Eclipse to 
>> connect to Chrome browser and then you can set break points in Eclipse (and 
>> Eclipse synchronizes them with Chrome browser).
>>
>>
>> -- 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: SDM and client debugging with eclipse debugger?

2015-04-23 Thread kwmailswm
Independently from the reply from Jens and Ivan I'm curious to know why I 
do not see a sourcemaps entry in chrome developer section (as one can see 
in this video https://www.youtube.com/watch?v=p00K0BiiSGI&noredirect=1 
starting at 2 min 11 sec).  

Regards
Kristian

On Wednesday, April 22, 2015 at 3:12:05 PM UTC+2, kwma...@gmail.com wrote:
>
> Hi all,
>
> I am new to Super Dev Mode in GWT and currently try to use SDM in 
> combination with Client Side Debugging, but it is not working (no break 
> point activation on client side code). My setup is the following:
>
> * IDE: Eclipse Luna Service Release 1 (4.4.1) with GWT Plugins 3.8.0
> * GWT project based on 2.7.0
> * Deployment to local JBOSS (Wildfly) via JBOSS Maven Plugin (mvn 
> wildfly:deploy)
> * Browser: Chrome 42
>
> The procedure is:
> * start the code server via maven --> mvn gwt:debug
> * Start a debug configuration in eclipse that connects to the (code 
> server?) debug port 8000 -> Debug connection successfully established
> * Compile and deploy project with maven -> mvn clean compile package 
> wildfly:deploy
> * Start the GWT-App in Chrome (URL pointing to GWT App running on local 
> JBOSS)
> * Turn "Dev Mode On" with previously created bookmarks -> Recompile Option 
> appears -> Click it --> Recompilation
> * Trigger Client-side functionality (e.g. click a button) that should 
> trigger a break point activation (e.g. in buttonClicked Handler) ==> NO 
> Break Point Halt in Eclispe Debugger :-(
>
> Any hints what could be wrong with my setup?
>
> Thanks
> Kristian
>

-- 
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: SDM and client debugging with eclipse debugger?

2015-04-23 Thread kwmailswm
Hi Ivan, 

in the meantime I was able to install the sdbg plugin and tried to use it 
according to video from the github readme page of the project. 

Difference was that I did start Codeserver via  Debug -> [GWT] Web 
Application (Super Dev Mode) and did not get a classnotfoundexception for 
the CodeServer. Also - since I have to use the target app server as runtime 
environment (e.g. JNDI-Lookup), I did provide the URL of the local JBOSS 
when creating a "Launch Chrome" Debug Configuration instead of the URL from 
the Development Mode View in Eclipse. 

Unfortunately I do get the same behaviour that the debugger does not halt 
at the break points in the client code. Should it work as expected also 
with local jboss as runtime instead of GWT-Plugin-internal JETTY Runtime?

Thanks
Kristian



On Thursday, April 23, 2015 at 9:10:01 AM UTC+2, kwma...@gmail.com wrote:
>
> OK, thanks for the info! This clarifies the behaviour I described in my 
> initial post.
>
> On Wednesday, April 22, 2015 at 3:23:32 PM UTC+2, Jens wrote:
>>
>> With SDM your client side code only runs in the browser and you have to 
>> set break points in the browser's dev tools. Launching the JVM in debug 
>> mode does not give you anything for client side debugging.
>>
>> There is an Eclipse plugin called SDGB on Github that allows Eclipse to 
>> connect to Chrome browser and then you can set break points in Eclipse (and 
>> Eclipse synchronizes them with Chrome browser).
>>
>>
>> -- 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: SafeHtmlCell column is not firing the handler onBrowserEvent

2015-04-23 Thread Raphael Garnier
SafeHtmlCell doesn't consume event. If you want to catch some event, you 
can't use it !

Here a sample of my TouchTextCell :

public class TouchTextCell extends AbstractSafeHtmlCell {
  public TouchTextCell() {
this(SimpleSafeHtmlRenderer.getInstance());
  }

  public TouchTextCell(SafeHtmlRenderer renderer) {
super(renderer, TouchBrowserEvents.TOUCHSTART, TouchBrowserEvents.
TOUCHMOVE, TouchBrowserEvents.TOUCHEND);
  }

  @Override
  public void onBrowserEvent(Context context, Element parent, String value, 
NativeEvent event, ValueUpdater valueUpdater) {
super.onBrowserEvent(context, parent, value, event, valueUpdater);
onEnterKeyDown(context, parent, value, event, valueUpdater);
  }
 
  @Override
  protected void onEnterKeyDown(Context context, Element parent, String 
value, NativeEvent event, ValueUpdater valueUpdater) {
if (valueUpdater != null) {
  valueUpdater.update(value);
}
  }

  @Override
  protected void render(Context context, SafeHtml value, SafeHtmlBuilder sb) 
{
if (value != null) {
  sb.append(value);
}
  }
}

Then use a ValueUpdater to do what you want.

Le jeudi 16 avril 2015 14:18:27 UTC+2, Abdul a écrit :
>
> In cell table column,i created a column of type SafeHtmlCell.Inside i 
> overridden the getvalue()and onBrowserEvent() Method. But when i click 
> the column its not firing the event.See the below
>
>  @Override
>  public SafeHtml getValue(final Object object) {
>  SafeHtmlBuilder sb = new SafeHtmlBuilder();
>  sb.appendHtmlConstant("");
>  sb.appendHtmlConstant(value);
>  sb.appendHtmlConstant("");
>  sb.appendHtmlConstant("");
>  return sb.toSafeHtml();
>   }
>
>@Override
> public void onBrowserEvent(Context context, Element elem,
> Object object, NativeEvent event) {
>if ("click".equals(event.getType())) {
>EventTarget eventTarget = event.getEventTarget();
> if (elem.isOrHasChild(Element.as(eventTarget))) {
> Element el = Element.as(eventTarget);
> if ("icon-pencil".equals(el.getClassName())) {
> Window.alert("Successfully clicked");
> }
> }
> }
> }
>
> How to solve this? Wether i need override render() Method as well?Any idea?
>
>

-- 
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: SDM and client debugging with eclipse debugger?

2015-04-23 Thread kwmailswm
Good news! I got it working now with the sdbg plugin - after restarting 
everything (eclipse, jboss, debug configs, sdm on) , the debugger pauses in 
the client code at the break points set :-)
Regards
Kristian



On Thursday, April 23, 2015 at 12:13:04 PM UTC+2, kwma...@gmail.com wrote:
>
> Hi Ivan, 
>
> in the meantime I was able to install the sdbg plugin and tried to use it 
> according to video from the github readme page of the project. 
>
> Difference was that I did start Codeserver via  Debug -> [GWT] Web 
> Application (Super Dev Mode) and did not get a classnotfoundexception for 
> the CodeServer. Also - since I have to use the target app server as runtime 
> environment (e.g. JNDI-Lookup), I did provide the URL of the local JBOSS 
> when creating a "Launch Chrome" Debug Configuration instead of the URL from 
> the Development Mode View in Eclipse. 
>
> Unfortunately I do get the same behaviour that the debugger does not halt 
> at the break points in the client code. Should it work as expected also 
> with local jboss as runtime instead of GWT-Plugin-internal JETTY Runtime?
>
> Thanks
> Kristian
>
>
>
> On Thursday, April 23, 2015 at 9:10:01 AM UTC+2, kwma...@gmail.com wrote:
>>
>> OK, thanks for the info! This clarifies the behaviour I described in my 
>> initial post.
>>
>> On Wednesday, April 22, 2015 at 3:23:32 PM UTC+2, Jens wrote:
>>>
>>> With SDM your client side code only runs in the browser and you have to 
>>> set break points in the browser's dev tools. Launching the JVM in debug 
>>> mode does not give you anything for client side debugging.
>>>
>>> There is an Eclipse plugin called SDGB on Github that allows Eclipse to 
>>> connect to Chrome browser and then you can set break points in Eclipse (and 
>>> Eclipse synchronizes them with Chrome browser).
>>>
>>>
>>> -- 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: SDM and client debugging with eclipse debugger?

2015-04-23 Thread Ivan Markov
Hi,

SDBG *no longer *provides a ZIP version of the plugin (as noted on the 
Releases page).
I hope you managed to install from the P2 site. If you used some of the old 
ZIP releases, you shouldn't as they are really old in the meantime.

Perhaps you can use the approach outlined here: 
https://groups.google.com/forum/#!topic/sdbg/qvkr4WJvpm0


четвъртък, 23 април 2015 г., 15:33:49 UTC+3, kwma...@gmail.com написа:
>
> Good news! I got it working now with the sdbg plugin - after restarting 
> everything (eclipse, jboss, debug configs, sdm on) , the debugger pauses in 
> the client code at the break points set :-)
> Regards
> Kristian
>
>
>
> On Thursday, April 23, 2015 at 12:13:04 PM UTC+2, kwma...@gmail.com wrote:
>>
>> Hi Ivan, 
>>
>> in the meantime I was able to install the sdbg plugin and tried to use it 
>> according to video from the github readme page of the project. 
>>
>> Difference was that I did start Codeserver via  Debug -> [GWT] Web 
>> Application (Super Dev Mode) and did not get a classnotfoundexception for 
>> the CodeServer. Also - since I have to use the target app server as runtime 
>> environment (e.g. JNDI-Lookup), I did provide the URL of the local JBOSS 
>> when creating a "Launch Chrome" Debug Configuration instead of the URL from 
>> the Development Mode View in Eclipse. 
>>
>> Unfortunately I do get the same behaviour that the debugger does not halt 
>> at the break points in the client code. Should it work as expected also 
>> with local jboss as runtime instead of GWT-Plugin-internal JETTY Runtime?
>>
>> Thanks
>> Kristian
>>
>>
>>
>> On Thursday, April 23, 2015 at 9:10:01 AM UTC+2, kwma...@gmail.com wrote:
>>>
>>> OK, thanks for the info! This clarifies the behaviour I described in my 
>>> initial post.
>>>
>>> On Wednesday, April 22, 2015 at 3:23:32 PM UTC+2, Jens wrote:

 With SDM your client side code only runs in the browser and you have to 
 set break points in the browser's dev tools. Launching the JVM in debug 
 mode does not give you anything for client side debugging.

 There is an Eclipse plugin called SDGB on Github that allows Eclipse to 
 connect to Chrome browser and then you can set break points in Eclipse 
 (and 
 Eclipse synchronizes them with Chrome browser).


 -- 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.


JsInterop code seems to compile out @JsExport code in GWT 2.8.0

2015-04-23 Thread Alex W
If I run the codeserver my jsinterop code runs fine. I can open the chrome 
inspector and instantiate @JsExported java objects.

But if I do a mvn clean compile gwt:compile package I can't see my exported 
symbols in my code. They seem to be compiled out. 
I tried this with: true on both true 
and false. No help. Has anyone else experienced this, or able to provide 
advice on how to fix?

Thanks
-Alex



-- 
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.