GTNWSRP-373 - Removed unused handler chains
From EAP 6.2 and on, the web services layer reports a WARN log on the logs when a handler chain file exists, but declares no handler chain. As such, we are removing this, which has the same effect as the current behavior, but won't generate any warns.
Revert "Ability to specify several URLs corresponding to individual prod...
…roducer nodes when specifying a consumer so that users' requests can be spread across a pool of available producer nodes" This reverts commit 754b7d0.
…nodes when specifying a consumer so that users' requests can be spread across a pool of available producer nodes Simple load-balancing strategy using a simple round-robin algorithm Simple failover capability: if a producer node is down, the consumer will try to move requests to the next available one transparently Sticky session support: users that started interacting with a specific producer node will stay assigned to it as long as the producer node stays up Cooldown period for down producer nodes: producer can automatically be re-added to the available pool after a configurable cooldown period
… URLFormat. Requires GTNPC-108 to be fixed to work properly. Added test case and clarified situation wrt to XML-encoding of URLs which depends on how Portlet URLs are output by portlets. :(
…nformation anymore since it was getting out of sync, delegates it (as it should have) to RegistrationInfo. Fixed ConsumerBean modifyRegistration method and let RegistrationProperty work without a valid listener since we don't want the restore-from-persistence use case to trigger property change events.
…d to use as a portlet instance key so used WindowContext.getId() instead. This should solve the issue of not being able to properly scope portlet session attributes.
…ment that's only rendered when local information is present.