Thanks Stefan. But in my opinion method with too many parameter of same
type will require a developer to be more careful.
SearchAPI.lookup(Integer, String, String, String, String, String)
One has to be careful with parameter positions like 2nd is for name and so
on. Although IDE like eclipse
but its impossible to hijack the session itself.
Why is this important when you have a whole in your site due to XSS, as you
assume above?
If some script get full access to your site through XSS, it can set any
header it wants such that your backend can't see the diference between a
legal
A little out-of-time response but since this problem still exists in 2.5 I
think it's worth sharing another solution.
If you put javascript: into form's action attribute, nothing will happen
even if the event is not canceled. I know this isn't helpful in cases where
you need to validate the
Hi Jens,
Great, it works exactly as I want! Such a simple approach as well, it
should be part of GWT though.
David
On Thursday, February 2, 2012 1:23:57 AM UTC+1, espinosa_cz wrote:
Hi guys,
I manage to put my context panel to the middle of the browser page in
Vaadin. Seem my
On Thursday, April 18, 2013 9:30:51 AM UTC+2, Honza Rames wrote:
A little out-of-time response but since this problem still exists in 2.5 I
think it's worth sharing another solution.
If you put javascript: into form's action attribute, nothing will happen
even if the event is not
For some reason the combination of the new Eclipse plugin (3.2.2) and the
new GWT (2.5.1) is not working for me.
Outside eclipse all works fine.
All this worked fine two days ago with the previous plugin (3.2.1) and SDK
(2.5).
I'll appreciate any suggestions.
-- Reuben
On Monday, March 11,
Hi there,
I am somewhat of a GWT novice and I am attempting to create my first
application and I would appreciate if any wise old sages would be able to
offer some guidance... As part of this application I want to offer offline
functionality. My thoughts on how this will work are as follows:
Now that we have been using GWT for a while ... what do you think? Was it
the right choice or thinking of migrating to other framework?
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving
Hi,
Are you using the same server to run backend and front end? It is very
useful use two servers. Take a look at
https://github.com/tbroyer/gwt-maven-archetypes.
Juan
2013/4/18 Ani anice...@gmail.com
Now that we have been using GWT for a while ... what do you think? Was it
the right choice
Are you using Firefox? If so, there's an issue:
https://code.google.com/p/google-web-toolkit/issues/detail?id=7648
If not, I can report that SSD drives make a huge difference in GWT dev
mode.
On Thursday, April 18, 2013 10:22:15 AM UTC-7, Ani wrote:
Now that we have been using GWT for a
It's not enough to include it in the build path, you have to copy the
library to the lib folder in your server side (uder war/WEB-INF), and then
include it in the build path. This is so the server has access to the
library.
On Tuesday, April 16, 2013 12:36:15 AM UTC+3, Steve Morgan wrote:
Thomas,
This piece of code is in nocache.js
*function getDirectoryOfFile(path){*
* var hashIndex = path.lastIndexOf('#');*
* if (hashIndex == -1) {*
*hashIndex = path.length;*
* }*
* var queryIndex = path.indexOf('?');*
* if (queryIndex == -1) {*
*
performance improvement definitely seems to be an immediate priority. See
the draft roadmap
https://docs.google.com/document/d/1bmp0a-d5cb_Sqb4w9rZyfMhg7i6lYfLLt3zymIFoAmo/edit
On Thursday, April 18, 2013 1:22:15 PM UTC-4, Ani wrote:
Now that we have been using GWT for a while ... what do you
As its a mobile app you should always think about how to reduce server
requests by sending the server more information at once. Less requests =
less latency in using your app.
For example the above 4 steps you have described can be done with a single
request:
Request: Client logs in: Client
Hi Jens,
Thanks for your input - much appreciated! I had actually come to the same
conclusion after posting this when I was thinking about alternative
solutions to the issue.
Regarding accessing results of a callback elsewhere in the application (if
required), what is the best way to do this?
This is driving me crazy.
My (large) project uses Hibernate and Postgres.
On one machine it works perfectly.
On two machines:
- All works fine when running externally (from the web server)
- Other (non gwt) programs work fine, using the same eclipse project, same
classpath, same config
Update: I grabbed the hibernate code, extracted parts, and here's the
interesting bit:
PersistenceProviderResolver ppr =
PersistenceProviderResolverHolder.getPersistenceProviderResolver();
ListPersistenceProvider list = ppr.getPersistenceProviders();
On the good machine, the list has
That's more or less what I said: the odds that
getDirectoryOfFile($doc.location.href) is actually called are a) very low
b) dependent on how you call the *.nocache.js more than the runtime
environment.
Starting with 2.1.0, you can set the 'base' using meta
name=gwt:property value=baseUrl=foo/
I'd bet your driver's JAR is not in WEB-INF/lib.
On Thursday, April 18, 2013 10:04:35 PM UTC+2, Jamie wrote:
This is driving me crazy.
My (large) project uses Hibernate and Postgres.
On one machine it works perfectly.
On two machines:
- All works fine when running externally (from the web
Regarding accessing results of a callback elsewhere in the application (if
required), what is the best way to do this?
Somewhat depends on the concrete case.
If its very general data that multiple independent components are
interested in, you could publish that data on an app global
Fixed the issues mentioned by Thomas. Daniel, did you have any comments
on this?
http://gwt-code-reviews.appspot.com/1815803/diff/1/src/com/google/gwt/dom/client/DOMImpl.java
File src/com/google/gwt/dom/client/DOMImpl.java (right):
Thomas Broyer has posted comments on this change.
Change subject: removes block splitting logic that was specific to IE6/7
..
Patch Set 1: Code-Review-1
If we start removing IE6/7 support, we should start with removing the
22 matches
Mail list logo