| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
With this patch, the theme-and-default-widgetset target finishes in 50
seconds, whereas it takes about 80 seconds without the patch. This
happens at the cost of peak memory usage rising from ~750mb to ~850mb.
Change-Id: I969e9b3b01907e24bb8d411884d060ca1b539bde
|
|
|
|
| |
Change-Id: Ie561a3ef95fcc15e357d1edb65b45f596683e7e4
|
|
|
|
| |
Change-Id: Ie67372d1ea77ad025fe3cb42cfe7a6ecc94ee3df
|
|
|
|
| |
Change-Id: Icdac51322a90c32c122a182bc692c4eff3d8285b
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Offline apps need to know when server errors are 500 or 400 in
order to switch appropriatelly to the offline mode.
Also we need exported the fetchRootConfig method and a
reliable way to get loaded apps.
Related with change I29635982514071e63221a9771d6729da14273ad3 [1]
see temporal workaround in TouchKitServlet
[1] https://dev.vaadin.com/review/#/c/4037/
Change-Id: I339ca697d035508a67d1eb24480cd12c4b9c6c0e
|
|
|
|
| |
Change-Id: I4eb9409629f64c17f39b1560062e763270f1f582
|
|
|
|
| |
Change-Id: I02b68886b888ee0a0d99b41138755f0ea6e2a53d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Doing two times session.accessSynchronously is unnecessary effort in
multiple aspects:
* The session will be locked twice.
* CurrentInstances are set twice.
* CurrentInstances are restored twice.
* VaadinSession being checked for being the current via
VaadinService.verifyNoOtherSessionLocked(this);
When we leave requestEnd we unset all CurrentInstances. There is no need
to just restore them before doing so.
When we are in requestEnd, VaadinSession is set to "current" by
PushHandler.callWithUi() or VaadinService.handleRequest().
Also, the cleanupSession code does not need any of these thread locals,
so not having them set would also not hurt.
having an extra accessSynchronously call for just setting the duration
does not make a lot of sense. While it somehow wants to make the previous
accessSynchronously call to be counted completely into the duration it
invests an the same time that would have been left out additionally.
VaadinService removeClosedUIs is a cleanup which also locks and sets
CurrentInstances just to figure out that the UI it is checking is not
closing. This change moves that check out of ui.accessSynchronously.
In the end, the resulting code is a tiny bit less robust, however it
eliminates over 50% response time on trivial push request/responses.
Change-Id: If71d1dbbae5d1fd57d3d4e735c592fd263261a81
|
|
|
|
| |
Change-Id: Ib16d4b8922a139b37d551797ada163b6d6b5e720
|
|
|
|
|
| |
In some servlet definitions async-supported was before init-param
Change-Id: I2d4886a0aa4c37bad3b0385e25b51e91d59a4c31
|
|
|
|
| |
Change-Id: If241edbb79fecd3d99939a53f70c7c6d78f74e40
|
|
|
|
| |
Change-Id: Ibd6f890136d62a3b19f8c60158b4aa1397454f7e
|
|
|
|
| |
Change-Id: I5b6298be367e4fe820320a5e3fd6bf5aaa7e2047
|
|
|
|
| |
Change-Id: I59596630b71f5a6b78c13bc5dbeaf7ef5dfaccf9
|
|
|
|
|
|
|
| |
Atmosphere 2.1.2.vaadin3 includes fix for:
https://github.com/Atmosphere/atmosphere/issues/1643
Change-Id: I67c07dc3b32ebb3b0eed634bf143bac9a7e5efe2
|
|
|
|
| |
Change-Id: Ic35b71a01b207ff87072d2e46f34f171ec581fe0
|
|
|
|
| |
Change-Id: I14d782843684f623a2cf671f14d0ab062829ebac
|
|
|
|
|
|
|
| |
If the server sends no token and the client value remains "init" then
it's not sent back to the server.
Change-Id: I74fc470c5c22d57c4a48eab3e4476ae4cc2dd242
|
|
|
|
| |
Change-Id: I4a9db58e65b94ec0e46e849e6856817986bd750e
|
|
|
|
| |
Change-Id: Icd38631f8802fc86949fa29dd517f1aca0499c33
|
|
|
|
| |
Change-Id: I7ce7c61f842a09af1842a14fedec3412120944c7
|
|
|
|
|
|
|
|
|
| |
There are a few places in frequently used core classes which could
initialize collection classes with the correct (or slightly oversized)
length.
Maps are initialized with 2x the size due to its load factor.
Change-Id: I3aee5a60602937a8550ca5a200ec2a529ff36fe9
|
|
|
|
|
|
|
|
|
| |
This change reduces the amount of intermediate steps taken to initialize
the thread locals for a given ui or vaadin session.
It mainly takes advantage of reusing the old values from the map in set()
instead of creating new ones to put into the "old" map which is returned.
Change-Id: I4dbaff973f46e73f8f3a0c285b14c97603f2d5a4
|
|
|
|
|
|
|
|
|
| |
The setCurrent call on VaadinSession is not needed. the one extra call
can be saved because service.findVaadinSession will already set it.
Added a comment like it is done for UI (service.findUI will also set the
UI).
Change-Id: Ic24d922554d1316aae310813ef5d00a0bbfd418a
|
|
|
|
|
|
| |
Couldn't created an automated test in selenium - can't get it to drag text.
Change-Id: I1a0beab97840401423e3b446015ff0c729bc2ca2
|
|
|
|
| |
Change-Id: I733f21f5fc0795633ed3a658b6b19681d8f26b22
|
|
|
|
|
|
|
|
|
|
| |
Non obvious problem before. "config" is a property of AtmosphereFramework
which also has getInitParameter(String) method. So it compiles but does
not do what is intended: to check against the user defined web.xml
servlet init-prams.
(the variableName servletConfig has the same problem :-))
Change-Id: Ib02f0b94312327d482775456c2d63a904b1e8104
|
|
|
|
| |
Change-Id: I5ce36a5c3beffe7b686a8754b6f7311d83b00f87
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We actually want to pass around the primitive long values emulated by
GWT even though JavaScript code can't do anything with the values.
Skipping the unboxing caused long fields to always be 0 since that's how
JavaScript converts an object into a number.
This patch also makes the test assert that the expected state values are
received and updates those values to actually make sense in some
situations.
Change-Id: Id9c3696d699593bd9e59e249c5daf077873b85fc
|
|
|
|
| |
Change-Id: I513340db4123c40bba0832f8af77ec5e725c24e6
|
|
|
|
| |
Change-Id: I33d70c54b9118e85c9542e56b917b993516ae213
|
|
|
|
| |
Change-Id: I9b0566070af58afda7693936943237e70cea4a2f
|
|
|
|
| |
Change-Id: I04996df90cbbb449d54e54c3affc74ff40fddeeb
|
|
|
|
| |
Change-Id: I9f6486597c45180ef7f748ba128f3f287d28bd97
|
|
|
|
|
|
|
|
| |
Calling GWT RPC throw an exception when __gwtStatsEvent doesn't return
a boolean. This was in the Profiler.ensureNoLogger where the function
assigned was empty.
Change-Id: If97e15eb3c2c6512e80f3bde81ba180b8c95c947
|
|
|
|
| |
Change-Id: Icb47d8a0c737e27a3d88078b4162c633ba08739c
|
|
|
|
|
|
|
|
|
|
|
|
| |
API change from:
public static Iterable<ClientConnector> getAllChildrenIterable(final ClientConnector connector)
to
public static Iterable<? extends ClientConnector> getAllChildrenIterable(final ClientConnector connector)
avoids creating wrappers in case the component has either no subcomponents
or no extensions. This covers the vast majority of components.
Change-Id: I48ffd2f26f09c265fae6e1aaabdbaa655d52ffb8
|
|
|
|
| |
Change-Id: I3125dec887106e746b95c220f587a8d3e39be0f0
|
|
|
|
| |
Change-Id: I7bdaf849e79191183013ca05e7420e10411f0b2e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 1b73b00b2875c5eafa3c641b77f5d9efc2f7d929 as
well as the related changes to @since, release notes etc.
Conflicts:
client/src/com/vaadin/client/ResourceLoader.java
client/src/com/vaadin/client/communication/TranslatedURLReference.java
client/src/com/vaadin/client/ui/ui/UIConnector.java
server/src/com/vaadin/ui/UI.java
shared/src/com/vaadin/shared/ui/ui/UIState.java
uitest/src/com/vaadin/tests/tb3/AbstractTB3Test.java
Change-Id: Id882dc730f51055f6d17200964bcaf8a1f87a35f
|
|
|
|
| |
Change-Id: I62610ef647fbbb5a7cfae25ac5c7628f78f2c6ff
|
|
|
|
| |
Change-Id: I48c37a377d6764333b83512dc613798aaf39423c
|
|
|
|
| |
Change-Id: I49516f311315d3c84a177ec6bd937e1241e67351
|
|
|
|
| |
Change-Id: Ibf8888de795b08aed0446607165d7318f94ee6f4
|
|
|
|
| |
Change-Id: If297591d46979ce991921f9545ed04a0c2c92e41
|
|
|
|
|
|
| |
Fixed issue with SplitPanels which were not marking sets as dirty.
Change-Id: I23bb8bfca87a825aef132f249e05871cf7b36a34
|
|
|
|
| |
Change-Id: If3fcc88e69d797b219f5af5906853a42d81f693c
|
|
|
|
| |
Change-Id: Iad73c44852c207f29381d59bea25275ac8f24dbd
|
|
|
|
| |
Change-Id: I4c9d24fdf0fa43c1abbe1843887b1a0001084a60
|
|\
| |
| |
| |
| |
| |
| |
| | |
Updated release notes to the form previously used in master.
The ticket list link needs to be updated separately in the
7.3 branch.
Change-Id: I7b7d09a1281261d3a1b8793cfff9ba8951a07798
|