Thanks again Thomas.
net.ltgt.gwt.maven
gwt-maven-plugin
com.mycompany.mywebapp.App
mywebapp
${project.build.directory}/${project.build.finalName}/WEB-INF/deploy
On Tuesday 27 February 2024 at 4:06:12 am UTC+11 Thomas Broyer
On Monday, February 26, 2024 at 11:56:45 AM UTC+1 ma...@craig-mitchell.com
wrote:
Thanks Thomas, now working great!
For anyone coming from the Eclipse GWT plugin, you can do this to keep it
consistant with how it used to work:
In your client pom. Add the like this:
Thanks Thomas, now working great!
For anyone coming from the Eclipse GWT plugin, you can do this to keep it
consistant with how it used to work:
In your client pom. Add the like this:
net.ltgt.gwt.maven
gwt-maven-plugin
com.mycompany.mywebapp.App
On Sunday, February 25, 2024 at 12:34:44 AM UTC+1 ma...@craig-mitchell.com
wrote:
Sorry, I do see them in
mywebapp-client\target\gwt\deploy\mywebapp\symbolMaps
How do I get them from there, into the war?
Configure to somewhere inside the (preferably
inside WEB-INF so they won't be
Sorry, I do see them in
mywebapp-client\target\gwt\deploy\mywebapp\symbolMaps
How do I get them from there, into the war?
On Sunday 25 February 2024 at 10:30:14 am UTC+11 Craig Mitchell wrote:
> Hi George,
>
> What I did was:
>
>1. Run https://github.com/tbroyer/gwt-maven-archetypes to
Hi George,
What I did was:
1. Run https://github.com/tbroyer/gwt-maven-archetypes to generate the
sample app.
2. Modify module.gwt.xml to have:
3. Run mvn clean package.
Then when I look inside
mywebapp-server\target\mywebapp-server-HEAD-SNAPSHOT.war I see the mywebapp
folder
I see the symbolmaps generated in `
target/gwt/deploy//symbolMaps `
I believe it is generated by default.
On Friday, February 23, 2024 at 10:27:12 PM UTC-6 Craig Mitchell wrote:
> The symbol maps worked great with the Eclipse GWT plugin compiler.
>
> Now switched to use the Maven compiler
The symbol maps worked great with the Eclipse GWT plugin compiler.
Now switched to use the Maven compiler (with
the https://github.com/tbroyer/gwt-maven-archetypes architecture), I don't
see the symbol maps anywhere when doing a mvn clean package.
Do I need to do something extra to get them?
Thank you Alexander! That's what I was missing.
Called:
exception = SerializableThrowable.fromThrowable(exception);
before sending to the server, and now the stack traces show perfectly. :-)
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To
Do you wrapping exception with SerializableThrowable
(com.google.gwt.core.shared.SerializableThrowable.fromThrowable(Throwable))
before sending to server?
On Friday, May 17, 2019 at 12:56:33 AM UTC+3, Craig Mitchell wrote:
>
> I also tried compiling with Pretty and Detailed, both with the same
I also tried compiling with Pretty and Detailed, both with the same result
as Obfuscated.
When I debug the exception passed back to the server, the exception doesn't
have any detail about the JS line that is occurred. So, I don't understand
how the StackTraceDeobfuscator would ever work?
Using GWT 2.8.2. I started seeing errors being picked up by
the GWT.setUncaughtExceptionHandler. So, I implemented
the StackTraceDeobfuscator by adding the following to my .gwt.xml:
Passing the exception back to the server RemoteServiceServlet, and doing
the following:
String path =
Hi,
I do not know about version 2.8, but for 2.6 we did next:
- put value "PRETTY" in the pom.xml for gwt plugin
- put next loggin settings in the application gwt config file
as result we had a proper class names and line numbers in the stack-trace
massages
понеділок, 5
Depending on your browser versions you support, you could try enabling
source maps for other user agents as well. Currently it is only active for
safari permutation. If you deploy the generated source maps, the
StackTraceDeobfuscator could use them on the server to make better stack
traces.
I always deploy a version compiled with emulated stack traces alongside the
regular version so that if a problem can be replicated, I can get a proper
stack trace.
But I still share your pain. Trying to work out which line of obfuscated
JavaScript could possibly have given a null pointer
Hi,
Two issues that often frustrate me with GWT deobfuscated stack traces:
a) The stack trace is deobfuscated, but the error message is not, so you
get something like "com.google.gwt.core.client.JavaScriptException:
(TypeError) : Cannot read property 'a' of undefined".
b) The stack trace refers
16 matches
Mail list logo
