[svn] 4116: Fix for BLZ-274.

Revision: 4116
Author: [email protected]
Date: 2008-11-14 13:00:15 -0800 (Fri, 14 Nov 2008)
Log Message:
Fix for BLZ-274. Modified instructions to note WTP checkbox is not always present.
Checkin tests not relevant.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-274
Modified Paths:
blazeds/branches/3.x/apps/samples/fb-project-setup.htm

Hi --
Are there any configuration changes or specific code changes that are required in order to enable this fix? Should browsers with cookies automatically work without any config changes?
Thanks

Similar Messages

[svn] 3766: Fix for BLZ-261: Null pointer exception in Websphere login code .

Revision: 3766
Author: [email protected]
Date: 2008-10-21 05:59:49 -0700 (Tue, 21 Oct 2008)
Log Message:
Fix for BLZ-261: Null pointer exception in Websphere login code.
Protect the debug logging from being called if the principal variable is null.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-261
Modified Paths:
blazeds/trunk/modules/opt/src/websphere/flex/messaging/security/WebSphereLoginCommand.jav a

Revision: 3766
Author: [email protected]
Date: 2008-10-21 05:59:49 -0700 (Tue, 21 Oct 2008)
Log Message:
Fix for BLZ-261: Null pointer exception in Websphere login code.
Protect the debug logging from being called if the principal variable is null.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-261
Modified Paths:
blazeds/trunk/modules/opt/src/websphere/flex/messaging/security/WebSphereLoginCommand.jav a

[svn] 3779: Continue fix for BLZ-262: null pointer exception on redeploy of web app/servlet.

Revision: 3779
Author: [email protected]
Date: 2008-10-21 10:23:55 -0700 (Tue, 21 Oct 2008)
Log Message:
Continue fix for BLZ-262: null pointer exception on redeploy of web app/servlet.
Remove finally block in servlet init() as the call to destroy() in the catch block will clear ThreadLocals
if there is an error. Move it to the end of try block instead since the init() thread doesn't need any
thread locals set.
Log the startup error before calling destroy() in init() catch clause.
QA: Yes
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-262
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageBrokerServlet.java

Hello!
I had a similar problem under WebLogic 6.1 SP4 after deploying a war-file with
a bug.
After deploying the corrected file, it seemed that the old version was deployed
again.
Perhaps this behaviour will help you to load the new application/ejb:
- undeploy
- remove from targets
- move to targets
- deploy
Claudia
"Marco" <[email protected]> wrote:
>
hi all,
i have found a werid problem in deploying applications in Solaris 8
for weblogic
7.0.
i have deployed one EJB, and the first time i access it (thru teh web
app embedded
in the .ear) it gave me a null pointer exception because i was failing
to lookup
one environment variable.
so, i fix the code, rebuild the ear and redeployed, and the same error
happened
again.
i am sure i did not do any mistakees because i have put some system.err
statements
in the bean code to show the workflow, and when i have deployed it on
Window 2k
the statemens appeared.
but in solaris they didnot appear, and i got the same exception that
i had before..
it looks like wls is caching teh ejb, because whenever i redeploy it
(adding more
and more system.err statements) it always execute the faulty code of
when deployed
the very first time.
anyone can help?
regards
marco

[svn] 1418: Remove the optimization that was added as part of the fix for BLZ-133.

Revision: 1418
Author: [email protected]
Date: 2008-04-25 11:16:16 -0700 (Fri, 25 Apr 2008)
Log Message:
Remove the optimization that was added as part of the fix for BLZ-133. We cannot depend on isRequestedSessionIdFromCookie reliably, instead we should rely on the fact that encodeURL returns the same url when cookies are enabled.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-133
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/endpoints/amf/SessionFilter.j ava

This indicates corrupt files. A restore should resolve.

[svn:bz-trunk] 10631: Proper fix for BLZ-343 and LCDS-1153.

Revision: 10631
Author:   [email protected]
Date:     2009-09-28 05:23:42 -0700 (Mon, 28 Sep 2009)
Log Message:
Proper fix for BLZ-343 and LCDS-1153.
Refactored the common logic for AMF0 and AMF3 back into AbstractAmfInput. Resolving class aliases, creating and registering a property proxy and instantiating the appropriate class are now handled in the superclass. The resolved className and the proxy are 'returned' to the subclasses via a holder array created in the subclasses and sent as a parameter.
blazeDS checkintests pass
lcds-trunk checkintests pass with the new flex-messaging-core.jar
lcds-trunk alltests-dataservice pass with the new flex-messaging-core.jar
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-343
    http://bugs.adobe.com/jira/browse/LCDS-1153
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/AbstractAmfInput.java
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf0Input.java
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf3Input.java

[svn:bz-trunk] 19323: Revert fix for BLZ-578 (checkin 19214).

Revision: 19323
Revision: 19323
Author:   [email protected]
Date:     2010-12-13 12:10:28 -0800 (Mon, 13 Dec 2010)
Log Message:
Revert fix for BLZ-578 (checkin 19214). The BlazeDS/LCDS Spring integration code had a dependency on the thread local stuff that was removed as part of this bug fix. Revert the fix so we can move forward with lockdown testing. We can add this change back in when we resolve the dependency issue (tracked by Watson 2774331) if that's the appropriate thing to do.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-578
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/FlexContext.java
    blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java
    blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java
    blazeds/trunk/modules/core/src/flex/messaging/MessageException.java

[svn:bz-trunk] 23118: bug fix for blz 567

Revision: 23118
Revision: 23118
Author:   [email protected]
Date:     2011-10-25 13:04:50 -0700 (Tue, 25 Oct 2011)
Log Message:
bug fix for blz 567
Add and indicator to the Fault event that the number of max-streaming-connections-per-session have been exceeded.
consist with the response code to be SC_SERVICE_NOTAVAILABLE,
for errorMessage, cross out the limit configuration.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseStreamingHTTPEndpoint.java

[svn:bz-trunk] 19598: Add back fix for BLZ-578.

Revision: 19598
Revision: 19598
Author:   [email protected]
Date:     2011-01-05 08:50:58 -0800 (Wed, 05 Jan 2011)
Log Message:
Add back fix for BLZ-578. This fix was reverted because the LCDS Spring integration code had a dependency on thread local stuff that was removed by this fix. The LCDS Spring integration code was updated to not have the dependency any more so we should be able to add this fix back.
Checkintests: passed.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-578
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/FlexContext.java
    blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java
    blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java
    blazeds/trunk/modules/core/src/flex/messaging/MessageException.java

[svn:bz-trunk] 10281: Fix for BLZ-343.

Revision: 10281
Author:   [email protected]
Date:     2009-09-15 15:30:27 -0700 (Tue, 15 Sep 2009)
Log Message:
Fix for BLZ-343.
Move common code from AbstractAmfInput back to the subclasses Amf0Input and Amf3Input. A proxy instance was being created locally in the superclass method, but was unavaliable to the remaining code in the subclasses. The subclasses were therefore using the wrong proxy to unwrap the value, which caused problems when deserializing Enums.
reviewed by Mete
checkintests pass (minus 2 that have been failing intermittently)
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-343
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/AbstractAmfInput.java
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf0Input.java
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf3Input.java
    blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/dataTypesTest/E numTypeTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/EnumTy peTest.mxml

[svn:fx-3.x] 7499: Addendum to fix for BLZ-233 - adjust visibility of new internal heartbeat util methods to protected from private .

Revision: 7499
Author:   [email protected]
Date:     2009-06-02 16:10:08 -0700 (Tue, 02 Jun 2009)
Log Message:
Addendum to fix for BLZ-233 - adjust visibility of new internal heartbeat util methods to protected from private.
QA: No
Doc: No
Checkintests Pass: Yes
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-233
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

inspired2apathy wrote:
... The goal is a ScrollPane that automatically wraps the text inside it. I've just about got it, but I have one thing that's not working. If I just put the JTextArea{s} in as the Editor, then you lose the any text that doesn't fit inside whatever the initial size was. Instead, I put the JTextAreas inside a JScrollPane which works fine, except that I still have to determine the size of the JScrollPane in advance. I would like to make each Editor/JScrollPane start out with just a single line of text and expand until it reaches a certain small number of lines.
... What am I missing?THE BASICS. See if this isn't what you are trying to do.
import javax.swing.JFrame;
import javax.swing.JScrollPane;
import javax.swing.JTextArea;
public class Test
public static void main(String[] args) {
    JTextArea ta = new JTextArea();
    ta.setLineWrap(true);
    ta.setWrapStyleWord(true);
    JScrollPane sp = new JScrollPane(ta);
    JFrame f = new JFrame();
    f.getContentPane().add(sp, "Center");
    f.setBounds(0, 0, 400, 300);
    f.setDefaultCloseOperation(f.EXIT_ON_CLOSE);
    f.setVisible(true);
}OP, your code was too long and complicated for me to compile and run. However, aren't you forgetting the two simple methods <tt>JTextArea.setLineWrap()</tt> and <tt>JTextArea.setWrapStyleWord()</tt>? Furthermore, I absolutely see no need for you to extend SWING components for demonstration this simple -- that is, if I understand your problem correctly.

[svn] 3753: Merge fix for BLZ-215 from trunk to 3.0.x.

Revision: 3753
Author: [email protected]
Date: 2008-10-20 13:13:54 -0700 (Mon, 20 Oct 2008)
Log Message:
Merge fix for BLZ-215 from trunk to 3.0.x.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-215
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/client/EndpointPushHandler.ja va
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/client/EndpointPushNotifier.j ava
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/client/FlexClient.java

[svn] 2030: Merge fix for BLZ-188 from branches/3.0.x to trunk.

Revision: 2030
Author: [email protected]
Date: 2008-06-10 15:42:20 -0700 (Tue, 10 Jun 2008)
Log Message:
Merge fix for BLZ-188 from branches/3.0.x to trunk.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-188
Modified Paths:
blazeds/trunk/modules/core/src/java/flex/management/jmx/MBeanServerGateway.java

[svn] 2650: Add fix for blz-221 and BLZ-225 for samples app

Revision: 2650
Author: [email protected]
Date: 2008-07-29 09:48:41 -0700 (Tue, 29 Jul 2008)
Log Message:
Add fix for blz-221 and BLZ-225 for samples app
Ticket Links:
http://bugs.adobe.com/jira/browse/blz-221
http://bugs.adobe.com/jira/browse/BLZ-225
Modified Paths:
blazeds/branches/3.0.x/apps/samples/WEB-INF/flex-src/traderdesktop/src/traderdesktop.mxml
blazeds/branches/3.0.x/apps/samples/WEB-INF/src/flex/samples/marketdata/Stock.java

Revision: 2650
Author: [email protected]
Date: 2008-07-29 09:48:41 -0700 (Tue, 29 Jul 2008)
Log Message:
Add fix for blz-221 and BLZ-225 for samples app
Ticket Links:
http://bugs.adobe.com/jira/browse/blz-221
http://bugs.adobe.com/jira/browse/BLZ-225
Modified Paths:
blazeds/branches/3.0.x/apps/samples/WEB-INF/flex-src/traderdesktop/src/traderdesktop.mxml
blazeds/branches/3.0.x/apps/samples/WEB-INF/src/flex/samples/marketdata/Stock.java

[svn] 3668: Fix for SDK-15941: selectedItem/ selectedIndex does not render as selected.

Revision: 3668
Author: [email protected]
Date: 2008-10-15 15:25:04 -0700 (Wed, 15 Oct 2008)
Log Message:
Fix for SDK-15941: selectedItem/selectedIndex does not render as selected.
Reviewer: Deepa
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-15941
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxList.as
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/baseClasses/FxListBase.as

This bug figures out also when creating a custom spark ComboBox, then trying to programatically update the userProposedSelectedIndex property. The proposed selected index is selected, but does not apply the same skin as when mouse is on rollover or item is selected due to up and down keys.
The issue seems like updating the status of the item renderer to rollover or selected to get the same skin applied.
Please could you attach DropDow nList.as that you edited ?
Thank you so much.

[svn] 3390: Fix for SDK-17067 - @exampleText does not work in mxml comments

Revision: 3390
Author: [email protected]
Date: 2008-09-26 15:08:34 -0700 (Fri, 26 Sep 2008)
Log Message:
Fix for SDK-17067 - @exampleText does not work in mxml comments
Fix for SDK-17076 - Mxml component with id but no mxml comment is not added to generated document
QA: Yes
Doc:
Reviewed By: Pete
Tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17067
http://bugs.adobe.com/jira/browse/SDK-17076
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/ImplementationGenerator.java

Wow, that's an interesting one - seems as though the sharedCursorPane has
some hard requirement that the base App be mx (this isn't terribly
surprising, considering it was built with the mx components, but it's still
a bug). Can you link against the source code (provided for player 10 now!),
and change that line in sharedCursorPane :
From :
Application(mx.core.Application.application).stage.removeEventListener(Mouse
Event.MOUSE_MOVE, onMouseMove);
To :
stage.removeEventListener(MouseEvent.MOUSE_MOVE, onMouseMove);
and see if that works for you? I can't honestly tell why we're using the
line that was there... It's possible this was a workaround for another
issue. Anyhow, if you wouldn't mind being the guinea pig for this one, we
can get to the bottom of it.
thanks!
nigel

[svn] 4116: Fix for BLZ-274.

Similar Messages

Maybe you are looking for