hello all,
Currently i am working with GWT. I need to convert the
uploaded file into byte array using Servlet . i have done that coding, when
i run the code in loacal machine i am getting the request type
as HttpServletRequest. when i run the code using JBoss 4.2 i am getting
Hi, I have been dealing with a problem which seems to me not having a clean
solution.
I have declared a SuggestBox in uibinder:
g:SuggestBox ui:field=suggestBox height=32px
width=550px/g:SuggestBox
Then, I can populate the already provided SuggestBox on the View:
Use
@UiField(provided = true)
SuggestBox box;
and then instantiate the SuggestBox before you call initWidget() in your
constructor.
-- 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
yes, thanks Jens, (provided = true) made the difference in the solution 2
above.
It works now
:-)
--
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
Sorry this has taken a while to respond, but I just tested again with your
recommendation and it didn't help. I agree that I think it's related to
the logging, but I'm not sure what to do. To make things worse, as I said,
it is consistent between linux and mac builds. Here's what I have in my
Dear all,
We are using GWT as our main front end technology.
We are using Bamboo as our Build Server GIT as our source code management
Tool.
Our application is very huge and divided into different modules. But still
the compilation on local developer machine with 4 GB RAM takes lot of time.
Hi,
Why *table *layout is used in GWT?Why not *div *layout?
--
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
Well this still does not solve the problem!
As a workaround you can try using:
https://gist.github.com/jnehlmeier/cddbc476fd330b1d4999
I use the master branch of GWT but I think it should also work with GWT
2.7. In Chrome I get clickable stack traces that point to the source mapped
Java
Forgot to mention: to get clickable, source mapped stack traces you need
Chrome 40 beta.
-- J.
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I am using GWT-PhoneGap with my iPhone 5. This means that I have to use
Safari as dev console.
Am Montag, 8. Dezember 2014 15:45:35 UTC+1 schrieb Jens:
Well this still does not solve the problem!
As a workaround you can try using:
https://gist.github.com/jnehlmeier/cddbc476fd330b1d4999
You need to get the underlying Javascript exception trace, not the GWT
Exception.getStackTrace(). I guess no one has been testing or
updating StackTraceDeobfuscator on the server. We added code IIRC to
preserve the original underlying JS Error object in GWT, but probably
no one paid attention to
I tested the exception handler (
https://gist.github.com/jnehlmeier/cddbc476fd330b1d4999)
This is what I did:
logger.log(Level.SEVERE, RuntimeException, new RuntimeException(2 +
2 = 5));
GWT.log(RuntimeException, new RuntimeException(2 + 2 = 5));
And my output is still obfuscated:
So the short answer is, you need to turn on GWT logging, and use the
Remote stack trace deobfuscator stuff. That means the -aux output in
the SDM directory needs to be seen by your deobfuscation servlet.
Maybe https://code.google.com/p/google-web-toolkit/issues/detail?id=7693
should be
I tested the exception handler (
https://gist.github.com/jnehlmeier/cddbc476fd330b1d4999
https://www.google.com/url?q=https%3A%2F%2Fgist.github.com%2Fjnehlmeier%2Fcddbc476fd330b1d4999sa=Dsntz=1usg=AFQjCNEOfKPnULYklipp_37ayc-cynaGTg
)
This is what I did:
logger.log(Level.SEVERE,
I use it like this:
GWT.setUncaughtExceptionHandler(new SuperDevModeUncaughtExceptionHandler());
Am Montag, 8. Dezember 2014 18:29:58 UTC+1 schrieb Jens:
I tested the exception handler (
https://gist.github.com/jnehlmeier/cddbc476fd330b1d4999
I use it like this:
GWT.setUncaughtExceptionHandler(new SuperDevModeUncaughtExceptionHandler
());
Then just throw an exception somewhere in your app that you do not catch
yourself. The handler does not fix your java.util.logging.Logger or
GWT.log() calls.
But as you are using Safari you
The stack traces that are logged as escaped exceptions (with missing
causes) and the ones that are logged by Logger (without inheriting
c.g.gwt.logging) will be deobfuscated by Chrome dev tools (if haven't
already fixed in Dev channel).
Being said that, I don't understand why you are not seeing
I use GWT-PhoneGap on an iPhone5 and Super Dev Mode. SDM works file. I use
the Safari console for logging.
It would be great if you could provide an example of how
StackTraceDeobfuscation worked. I see there is a lack in the documentation.
Michael
Am Montag, 8. Dezember 2014 21:28:56 UTC+1
The stack traces that are logged as escaped exceptions (with missing
causes) and the ones that are logged by Logger (without inheriting
c.g.gwt.logging) will be deobfuscated by Chrome dev tools (if haven't
already fixed in Dev channel).
Being said that, I don't understand why you are not
On Mon, Dec 8, 2014 at 1:00 PM, confile michael.gorsk...@googlemail.com
wrote:
I use GWT-PhoneGap on an iPhone5 and Super Dev Mode. SDM works file. I use
the Safari console for logging.
The problem is you shouldn't be seeing obfuscated method names in GWT 2.7
SDM as incremental compiler uses
On Mon, Dec 8, 2014 at 1:11 PM, Jens jens.nehlme...@gmail.com wrote:
The stack traces that are logged as escaped exceptions (with missing
causes) and the ones that are logged by Logger (without inheriting
c.g.gwt.logging) will be deobfuscated by Chrome dev tools (if haven't
already fixed in
2.) There seem to be a bug in LogImpl.gwt.xml because Logger output does
not appear in SuperDevMode if you do not inherit Logging.gwt.xml. At least
I wasn't able to make it work in a small app of mine (maybe the
superdevmode property is always off in incremental mode?)
This is
Thanks, I'll look into the issues.
On Mon, Dec 8, 2014 at 3:03 PM, Jens jens.nehlme...@gmail.com wrote:
2.) There seem to be a bug in LogImpl.gwt.xml because Logger output does
not appear in SuperDevMode if you do not inherit Logging.gwt.xml. At least
I wasn't able to make it work in a small
He said he's not using Chrome, he's using Safari, which I don't think
respects the displayName feature. We can't rely on cross-browser
debugging supporting a client-side Chrome proprietary feature. IDEs
and SDM need to support source-map/symbolmap based log deobfuscation.
On Mon, Dec 8, 2014 at
We are using pretty naming in 2.7 so even using Safari he should get
non-obfuscated names by default. If I'm not missing anything; if he is
getting obfuscated names either he is using trunk (not 2.7) or incremental
is not enabled.
On Mon, Dec 8, 2014 at 3:45 PM, 'Ray Cromwell' via GWT
BTW, displayName, even though is not standard, is not Chrome proprietary.
Firebug supports it. Supposedly Safari should be supporting it as well:
https://bugs.webkit.org/show_bug.cgi?id=25171
If it is not fixed by next release, we should provide at least an opt-out
for incremental name
Hi,
Why *table *layout is used in GWT?Why not *div *layout?Please give some
suggestion?
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Hi,
Why *table *layout is used in GWT?Why not *div *layout?
--
You received this message because you are subscribed to the Google Groups GWT
Contributors group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I use the latest trunk and also SDM with incremental compile. @Goktug could
you please provide a sample project where obfuscation works which has the
correct configuration?
Am Dienstag, 9. Dezember 2014 02:11:31 UTC+1 schrieb Goktug Gokdogan:
We are using pretty naming in 2.7 so even using
29 matches
Mail list logo
