Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lps 72500 #11

Open
wants to merge 73 commits into
base: R4_5_maintenance
Choose a base branch
from
Open

Conversation

tinatian
Copy link

No description provided.

tjwatson and others added 30 commits January 7, 2016 10:56
cleaned up properly when unregistered

Change-Id: I45139c151a34a254e9347d1ac430026a60158018
Signed-off-by: Thomas Watson <[email protected]>
Change-Id: I125f389a742a26dd18a03da736bb0de34a5b4871
Signed-off-by: Thomas Watson <[email protected]>
Increment micro version by 100 for Mars.2
…y incompatible with Apache commons fileupload

Signed-off-by: Raymond Auge <[email protected]>
…spatcher type is REQUEST

Signed-off-by: Juan Gonzalez <[email protected]>
Change-Id: Icc74d86eb513fe9d01b0b26620980c7ab3a8b9bb
Signed-off-by: Thomas Watson <[email protected]>
…pl to HttpServletRequestWrapperImpl

Signed-off-by: Raymond Auge <[email protected]>
correctly for getAuthType or getRemoteUser

Change-Id: I70c78a5bb4610a3fd4c4958e523b8a217a52bd00
Signed-off-by: Thomas Watson <[email protected]>
Using `new Boolean()` results in the creation of a new object on the
heap, when the flyweight `Boolean.TRUE` and `Boolean.FALSE` are available.
Java 1.4 added a `Boolean.valueOf()` which can be used in place of
`new Boolean()` but which will use the existing flyweight values instead.

Globally change `new Boolean(...)` to `Boolean.valueOf(...)` and replace
constant valued expressions with their flyweight counterparts.

Bug: 470518
Change-Id: I25742c65162e57fd553dd1284ec057cd4b333dbb
Signed-off-by: Alex Blewitt <[email protected]>
…value is null, in order to fulfill httpSession.setAttribute API

Signed-off-by: Juan Gonzalez <[email protected]>
…methods too so everything cleans up

Signed-off-by: Juan Gonzalez <[email protected]>
mtambara and others added 30 commits June 29, 2016 14:01
Signed-off-by: Matthew Tambara <[email protected]>
…ibute, the synchronized protection should be per outter session based, no need to be system wide.

Signed-off-by: shuyangzhou <[email protected]>
…ng is fine. HttpSession is thread safe to ensure attributes' memory visibility, no need to sync on read.

Signed-off-by: shuyangzhou <[email protected]>
…()/removeReference(), when concurrent destroy() happens in between the addReference()/removeReference() window times, upgrade to write lock to ensure proper Condition waiting.

Signed-off-by: shuyangzhou <[email protected]>
…eference()/removeReference(), when concurrent destroy() happens in between the addReference()/removeReference() window times, upgrade to write lock to ensure proper Condition waiting."

This reverts commit 05be60b.
…he reading is fine. HttpSession is thread safe to ensure attributes' memory visibility, no need to sync on read."

This reverts commit f2c5790.
…n's attribute, the synchronized protection should be per outter session based, no need to be system wide."

This reverts commit aab7a09.
…() is never used, let's defer the toString value calculation when it is really needed."

This reverts commit ce3111a.
LPS-67139 Defer toString() value calculation
LPS-69622 Dead field, never initialized, never used.
LPS-69622 Use ConcurrentHashMap rather than synchronized all methods.
LPS-69622 Use AtomicInteger to prevent lost counting.
LPS-69622 Fallback to JDK6 only api. To ensure thread safety, createContextAttributes()/destroyContextAttributes() must still have the synchronized protection, consider they are only used during application initialization/destroy, there is no runtime overhead. At least this way getContextAttributes() is synchronized free, which is the most important thing to have.
LPS-69622 Avoid using Hashtable, it just needs to be a Dictionary, delegate to ConcurrentHashMap
LPS-69880 Avoid creating HttpSessionEvent unless there is any HttpSessionListener registered
LPS-69882 Avoid duplicated path string indexing and splitting
LPS-69883 The only creation of HttpServiceRuntimeImpl in Activator.addingService() is already wrapping the serviceProperties with UMDictionaryMap, inside HttpServiceRuntimeImpl constructor, there is no need to wrap it.
LPS-69903 Shortcut as early as possible
LPS-69903 Avoid using java.util.Stack, use LinkedList instead

Signed-off-by: shuyangzhou <[email protected]>
Signed-off-by: Matthew Tambara <[email protected]>
Signed-off-by: Raymond Auge <[email protected]>
… them. Fix ListenerRegistration.equals so it gets actually removed from available EventListeners

Signed-off-by: Juan Gonzalez <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants