[svn:fx-3.x] 7197: Bug: BLZ-354 - Client still polling after calling ChannelSet.logout() when subscribed to messaging destination.

Revision: 7197
Author:   [email protected]
Date:     2009-05-21 14:49:44 -0700 (Thu, 21 May 2009)
Log Message:
Bug: BLZ-354 - Client still polling after calling ChannelSet.logout() when subscribed to messaging destination.
QA: Yes
Doc: No
Checkintests: Pass
Details: In polling channels, stop polling as soon as logout ack is received.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-354
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

Any advice would be helpful. Thanks

Similar Messages

[svn:bz-3.x] 5036: Bug: BLZ-347 - Secure amf polling channel not working correctly on IE in BlazeDS /3.x branch.

Revision: 5036
Author: [email protected]
Date: 2009-02-23 06:24:31 -0800 (Mon, 23 Feb 2009)
Log Message:
Bug: BLZ-347 - Secure amf polling channel not working correctly on IE in BlazeDS/3.x branch.
QA: Yes
Doc: No
Checkintests: Pass
Details: This is BlazeDS part of the fix. For MSIE over HTTPS, we need to add additional Cache-Control headers.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-347
Modified Paths:
blazeds/branches/3.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.java

Revision: 5036
Author: [email protected]
Date: 2009-02-23 06:24:31 -0800 (Mon, 23 Feb 2009)
Log Message:
Bug: BLZ-347 - Secure amf polling channel not working correctly on IE in BlazeDS/3.x branch.
QA: Yes
Doc: No
Checkintests: Pass
Details: This is BlazeDS part of the fix. For MSIE over HTTPS, we need to add additional Cache-Control headers.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-347
Modified Paths:
blazeds/branches/3.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.java

[svn:bz-trunk] 5125: Update excludes.properties file for BlazeDS/ trunk to exclude tests due to bugs BLZ-354, BLZ-355, and BLZ-356.

Revision: 5125
Author: [email protected]
Date: 2009-03-02 05:55:42 -0800 (Mon, 02 Mar 2009)
Log Message:
Update excludes.properties file for BlazeDS/trunk to exclude tests due to bugs BLZ-354, BLZ-355, and BLZ-356.
Also exclude JMS tests on WebSphere due to configuration issues on the regression box. This is being tracked by QETOOLS-32 in jira.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-354
http://bugs.adobe.com/jira/browse/BLZ-355
http://bugs.adobe.com/jira/browse/BLZ-356
http://bugs.adobe.com/jira/browse/QETOOLS-32
Modified Paths:
blazeds/trunk/qa/features/excludes.properties

[svn] 2597: Bug: BLZ-217 - Should add a resources/ lib directory to BlazeDS turnkey with messaging jars

Revision: 2597
Author: [email protected]
Date: 2008-07-23 12:40:08 -0700 (Wed, 23 Jul 2008)
Log Message:
Bug: BLZ-217 - Should add a resources/lib directory to BlazeDS turnkey with messaging jars
QA: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-217
Modified Paths:
blazeds/branches/3.0.x/build.xml

Hi,
Can you mention the eclipse version you are using? And the platform in which you are trying to build?
I feel its always better to be platform specific when you go in for headless build. I can see that the configs value in your properties file is "configs=*,*,*". Try changing it to appropriate value and build your product. For example, I use "configs=win32, win32, x86" for building my product in 32-bit windows machine.

[svn] 3752: Bug: BLZ-195 - JMSAdapter not working after disconnect and resubscribe.

Revision: 3752
Author: [email protected]
Date: 2008-10-20 12:41:06 -0700 (Mon, 20 Oct 2008)
Log Message:
Bug: BLZ-195 - JMSAdapter not working after disconnect and resubscribe.
QA: Yes
Doc: No
Checkintests: Pass
Details: Merged change 3676 from trunk.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-195
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/messaging/adapters/J MSAdapter.java

Welcome guy -
Unless you are using Spry menus as a learning experience, you should move forward to a menus system that will display properly on the millions of portable devices that won't work with Spry which was deprecated 2 years ago.
Many are using JQuery menus or pure HTML/CSS menus.
If you wish to continue your Spry for learning experience, we'll be glad to assist; please let us know.
By the way, your submenus are not showing because you need to add the red value to this rule in your vertical CSS
ul.MenuBarVertical ul.MenuBarSubmenuVisible{
width: 220px;
left: 180px;

[svn:fx-3.x] 7177: Bug: BLZ-192 - Channel. requestTimeout cannot be set via services-config.xml

Revision: 7177
Author:   [email protected]
Date:     2009-05-21 07:56:59 -0700 (Thu, 21 May 2009)
Log Message:
Bug: BLZ-192 - Channel.requestTimeout cannot be set via services-config.xml
QA: Yes
Doc: Yes
Details: This is only the client side of the fix.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-192
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/rpc/src/mx/messaging/Channel.as

Revision: 7177
Author:   [email protected]
Date:     2009-05-21 07:56:59 -0700 (Thu, 21 May 2009)
Log Message:
Bug: BLZ-192 - Channel.requestTimeout cannot be set via services-config.xml
QA: Yes
Doc: Yes
Details: This is only the client side of the fix.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-192
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/rpc/src/mx/messaging/Channel.as

[svn] 2440: Added test for bug BLZ-214

Revision: 2440
Author: [email protected]
Date: 2008-07-10 12:02:39 -0700 (Thu, 10 Jul 2008)
Log Message:
Added test for bug BLZ-214
Maps with enum keys return null values
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-214
Modified Paths:
blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/remoting/datatype/EnumTypeTest.java
blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/EnumTy peTest.mxml
blazeds/trunk/qa/resources/frameworks/qa-frameworks.zip

[svn] 3722: Bug: BLZ-260 - Error message for a legacy =3. 0 client poll failing against a =3.1 server is unclear

Revision: 3722
Author: [email protected]
Date: 2008-10-17 14:04:59 -0700 (Fri, 17 Oct 2008)
Log Message:
Bug: BLZ-260 - Error message for a legacy <=3.0 client poll failing against a >=3.1 server is unclear
QA: Yes
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-260
Modified Paths:
blazeds/trunk/modules/common/src/flex/messaging/errors.properties
blazeds/trunk/modules/core/src/flex/messaging/FlexSession.java
blazeds/trunk/modules/core/src/flex/messaging/client/FlexClient.java

your problem:
Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
Loader: oracle.bpel.common:10.1.3
Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
Configuration: <code-source> in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
It happens when server is custom installed, try to reinstall it as full version and problem should disappear otherwise your need another full installation to retrieve and replace orabpel.jar file from (or maybe more)

[svn] 1751: Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.

Revision: 1751
Author: [email protected]
Date: 2008-05-15 14:21:43 -0700 (Thu, 15 May 2008)
Log Message:
Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.
QA: No - customer verified the fix.
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-174
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageClient.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/MessageService.java

If you create a metadatatype with a single metdata block, and you reference that in your vm/cm cell attribute using a *one* based index, Excel seems to see the link and it honors it when saving the spreadsheet.
So, I ended up with something like:
<c ... cm="1"/> (I'm dealing with cell metadata, but the concept is equivalente to value metadata)
<metadataTypes count="1">
  <metadataType name="MyMetaType" .../>
</metadataTypes>
<futureMetadata count="1" name="MyMetaType">
  <bk>
    <extLst><ext
uri="http://example" xmlns:x="http://example"><x:val>87</x:val></ext></extLst>
  </bk>
</futureMetadata>
<cellMetadata count="1">
  <bk><rc
t="1" v="0"/></bk> 
</cellMetadata>
Hope this helps.

[svn:bz-trunk] 15217: Bug: BLZ-508 - If server receives message for an unknown destination it shouldn ' t include the destination name in the error message sent back to the client .

Revision: 15217
Revision: 15217
Author:   [email protected]
Date:     2010-04-05 03:43:36 -0700 (Mon, 05 Apr 2010)
Log Message:
Bug: BLZ-508 - If server receives message for an unknown destination it shouldn't include the destination name in the error message sent back to the client.
QA: Yes
Doc: No
Checkintests: Pass
Details: Changed the error message to not include destination id. I'm also checking in a few minor fixes I had locally.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-508
Modified Paths:
    blazeds/trunk/modules/common/src/flex/messaging/errors.properties
    blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java
    blazeds/trunk/modules/core/src/flex/messaging/cluster/JGroupsCluster.java

Thanx Mete, yeah i did...
but i solved it some other way... not entirely sure this was
it though as i was doing a lot of things at once...
it was fds.swc... possibly it was out of date or missing.

[svn] 949: Bug: BLZ-96 - When sending a HttpService request from ActionScript with multiple headers with the same name , it causes a ClassCastException in the server

Revision: 949
Author: [email protected]
Date: 2008-03-27 07:12:59 -0700 (Thu, 27 Mar 2008)
Log Message:
Bug: BLZ-96 - When sending a HttpService request from ActionScript with multiple headers with the same name, it causes a ClassCastException in the server
QA: Yes - try again with legacy-collection true and false.
Doc: No
Checkintests: Pass
Details: Another try in fixing this bug. When legacy-collection is false, Actionscript Array on the client becomes Java Array on the server and my fix yesterday assumed this case. However, when legacy-collection is true, Actionscript Array becomes Java ArrayList on the server. So added code to handle this case.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-96
Modified Paths:
blazeds/branches/3.0.x/modules/proxy/src/java/flex/messaging/services/http/proxy/RequestF ilter.java

Hi all!
Just to post the solution to this if anyone ever runs accross this thread...
For some reason i had it bad the first time, don't have time right now to see why but here is what worked for me:
HashMap primaryFile = new HashMap();
primaryFile.put("fileContent", bFile);
primaryFile.put("fileName", uploadedFile.getFilename());
operationBinding.getParamsMap().put("primaryFile", primaryFile);
HashMap customDocMetadata = new HashMap();
HashMap [] properties = new HashMap[1];
HashMap customMetadataPropertyRoom = new HashMap();
customMetadataPropertyRoom.put("name", "xRoom");
customMetadataPropertyRoom.put("value", "SOME ROOM");
properties[0] = customMetadataPropertyRoom;
customDocMetadata.put("property", properties);
operationBinding.getParamsMap().put("CustomDocMetaData", customDocMetadata);
Basically an unbounded wsdl type is an array of objects (HashMaps), makes sense, i thought i had it like this before, must have messed up somewhere...
Good luck all!

[svn] 931: Bug: BLZ-96 - When sending a HttpService request from ActionScript with multiple headers with the same name , it causes a ClassCastException in the server

Revision: 931
Author: [email protected]
Date: 2008-03-26 11:31:01 -0700 (Wed, 26 Mar 2008)
Log Message:
Bug: BLZ-96 - When sending a HttpService request from ActionScript with multiple headers with the same name, it causes a ClassCastException in the server
QA: Yes - we need automated tests for this basic case.
Doc: No
Checkintests: Pass
Details: RequestFilter was not handling multiple headers with the same name properly.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-96
Modified Paths:
blazeds/branches/3.0.x/modules/proxy/src/java/flex/messaging/services/http/proxy/RequestF ilter.java

Hi all!
Just to post the solution to this if anyone ever runs accross this thread...
For some reason i had it bad the first time, don't have time right now to see why but here is what worked for me:
HashMap primaryFile = new HashMap();
primaryFile.put("fileContent", bFile);
primaryFile.put("fileName", uploadedFile.getFilename());
operationBinding.getParamsMap().put("primaryFile", primaryFile);
HashMap customDocMetadata = new HashMap();
HashMap [] properties = new HashMap[1];
HashMap customMetadataPropertyRoom = new HashMap();
customMetadataPropertyRoom.put("name", "xRoom");
customMetadataPropertyRoom.put("value", "SOME ROOM");
properties[0] = customMetadataPropertyRoom;
customDocMetadata.put("property", properties);
operationBinding.getParamsMap().put("CustomDocMetaData", customDocMetadata);
Basically an unbounded wsdl type is an array of objects (HashMaps), makes sense, i thought i had it like this before, must have messed up somewhere...
Good luck all!

[svn:bz-trunk] 15163: Bug: BLZ-507 - JGroups 2.9. 0 GA not compatible with BlazeDS/LCDS

Revision: 15163
Revision: 15163
Author:   [email protected]
Date:     2010-03-31 06:31:12 -0700 (Wed, 31 Mar 2010)
Log Message:
Bug: BLZ-507 - JGroups 2.9.0 GA not compatible with BlazeDS/LCDS
QA: Yes
Doc: No
Checkintests: Pass
Details: Tweaked the clustering code to work with JGroups 2.9.0 while maintaining backwards compatibility with earlier versions of JGroups.
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-507
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/cluster/ClusterNode.java
    blazeds/trunk/modules/core/src/flex/messaging/cluster/JGroupsCluster.java

[svn] 2692: Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out .

Revision: 2692
Author: [email protected]
Date: 2008-07-31 13:05:35 -0700 (Thu, 31 Jul 2008)
Log Message:
Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out.
QA: Yes
Doc: No
Checkintests: Pass
Details: Fixed a memory leak with JMS adapter. Also a minor tweak to QA build file to not to start the server if the server is already running.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-227
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/messaging/adapters/J MSAdapter.java
blazeds/branches/3.0.x/qa/build.xml

Revision: 2692
Author: [email protected]
Date: 2008-07-31 13:05:35 -0700 (Thu, 31 Jul 2008)
Log Message:
Bug: BLZ-227 - When using JMS Destination, MessageClient and FlexClient not released from memory when the session times out.
QA: Yes
Doc: No
Checkintests: Pass
Details: Fixed a memory leak with JMS adapter. Also a minor tweak to QA build file to not to start the server if the server is already running.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-227
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/messaging/adapters/J MSAdapter.java
blazeds/branches/3.0.x/qa/build.xml

[svn] 4290: Bug: BLZ-288 - Consumer is only receiving first pushed message when Consumer and RemoteObject that is used to push the messages use different channel sets but same channel .

Revision: 4290
Author: [email protected]
Date: 2008-12-11 14:24:37 -0800 (Thu, 11 Dec 2008)
Log Message:
Bug: BLZ-288 - Consumer is only receiving first pushed message when Consumer and RemoteObject that is used to push the messages use different channel sets but same channel.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* The bug app was arguably generating bogus test data (messages with duplicate ids), and 99.9% of applications won't be configured this way (using multiple ChannelSets with overlapping Channels, pointing at the same server) but it's still worth making this work just right anyways.
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-288
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/ConsumerMessageDispatcher.as

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

[svn:fx-3.x] 7197: Bug: BLZ-354 - Client still polling after calling ChannelSet.logout() when subscribed to messaging destination.

Similar Messages

Maybe you are looking for