[svn] 1013: Bug: LCDS-180 - [WebLogic 10.1 on Suse9] MxUnit Dynamic destination "SecurityEmployeeUser" test fails with a NullPointerException

Revision: 1013
Author: [email protected]
Date: 2008-03-28 17:24:25 -0700 (Fri, 28 Mar 2008)
Log Message:
Bug: LCDS-180 - [WebLogic 10.1 on Suse9] MxUnit Dynamic destination "SecurityEmployeeUser" test fails with a NullPointerException
QA: Yes
Doc: No
Details:
This prevents the NPE but for non-servlet endpoints you need to be sure to define your users/roles in Weblogic's default security realm. The test was failing because login was failing, most likely because the regression server wasn't fully configured.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-180
Modified Paths:
blazeds/branches/3.0.x/modules/opt/src/weblogic/flex/messaging/security/WeblogicLoginComm and.java

Similar Messages

[svn] 1720: Bugs: LCDS-304 - Authentication not working in all cases when using security constraint with NIO endpoints .

Revision: 1720
Author: [email protected]
Date: 2008-05-14 14:50:06 -0700 (Wed, 14 May 2008)
Log Message:
Bugs: LCDS-304 - Authentication not working in all cases when using security constraint with NIO endpoints.
QA: Yes
Doc: No
Details:
Update to the TomcatLoginCommand to work correctly with NIO endpoints.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-304
Modified Paths:
blazeds/branches/3.0.x/modules/opt/src/tomcat/flex/messaging/security/TomcatLoginCommand. java

Revision: 1720
Author: [email protected]
Date: 2008-05-14 14:50:06 -0700 (Wed, 14 May 2008)
Log Message:
Bugs: LCDS-304 - Authentication not working in all cases when using security constraint with NIO endpoints.
QA: Yes
Doc: No
Details:
Update to the TomcatLoginCommand to work correctly with NIO endpoints.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-304
Modified Paths:
blazeds/branches/3.0.x/modules/opt/src/tomcat/flex/messaging/security/TomcatLoginCommand. java

[svn] 4804: Bugs: LCDS-548: add code to deal with contentType="application/ xml" with one parameter (avoid

Revision: 4804
Author: [email protected]
Date: 2009-02-02 17:56:22 -0800 (Mon, 02 Feb 2009)
Log Message:
Bugs: LCDS-548: add code to deal with contentType="application/xml" with one parameter (avoid
name/value encoding in that case)
LCDS-405: baseURL on HTTPMultiService should accept URLs which start with "/"
Added convertParametersHandler and convertResultsHandler function hooks to RemoteObject
to support framework code which wants to modify the service behavior.
Moved "properties" from rpc/http/AbstractOperation to rpc/AbstractOperation so we can use
it for customizing the handling of remote object results
Couple of minor ASDoc fixes and one tab -> spaces change
Doc: minor asdoc edits
QE: LCDS QE will verify the bugs in this one
Reviewers: Mete, Pete, Seth, Ed reviewed different parts of this checkin
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-548
http://bugs.adobe.com/jira/browse/LCDS-405
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/AbstractInvoker.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/AbstractOperation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/AbstractOperation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/HTTPMultiService.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/http/Operation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/remoting/Operation.as
flex/sdk/trunk/frameworks/projects/rpc/src/mx/rpc/remoting/RemoteObject.as

Hello,
How about this as an alternative:
Use a functional global which has 3 cases:
1. open config file - it opens the config file and reads the contents into a string (which is the functional global data), and you only do this one time at the beginning of the program.
2. edit config data - it edits the string, which are really the contents of the file, but doesn't worry about writing to the file. you could even get fancy here, and allow an array of tags and an array of values as input, and it would go update/edit all the tags to have the corresponding values.
3. close config file - it writes the current string data (the functional global data) to the file and closes it.
Using the functions in the string palette, I think you'll find most of the code for that module/functional global will be easy to write.
I hope this helps!
Best Regards,
JLS
Best,
JLS
Sixclear

[svn] 4226: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4226 Author: [email protected] Date: 2008-12-03 15:25:17 -0800 (Wed, 03 Dec 2008) Log Message: ----------- Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working. QA: Yes Doc: No Checkintests Pass: Yes Details: * Make sure the <reliable/> option is treated as a nested element rather than an attribute of its parent <network> element. Ticket Links: ------------ http://bugs.adobe.com/jira/browse/LCDS-517 Modified Paths: -------------- blazeds/trunk/modules/core/src/flex/messaging/Destination.java

Revision: 4226 Author: [email protected] Date: 2008-12-03 15:25:17 -0800 (Wed, 03 Dec 2008) Log Message: ----------- Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working. QA: Yes Doc: No Checkintests Pass: Yes Details: * Make sure the <reliable/> option is treated as a nested element rather than an attribute of its parent <network> element. Ticket Links: ------------ http://bugs.adobe.com/jira/browse/LCDS-517 Modified Paths: -------------- blazeds/trunk/modules/core/src/flex/messaging/Destination.java

[svn] 4195: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4195
Author: [email protected]
Date: 2008-11-26 13:08:23 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ServerConfig.as

Revision: 4195
Author: [email protected]
Date: 2008-11-26 13:08:23 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/config/ServerConfig.as

[svn] 4193: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.

Revision: 4193
Author: [email protected]
Date: 2008-11-26 11:40:05 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* Foundational update to include destination config in what we collect for runtime config exchange with new clients for destinations with network/reliable=true (LCDS only).
* Also typo in comment in AbstractConnectionAwareSession fixed.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/AbstractConnectionAwareSession.java
blazeds/trunk/modules/core/src/flex/messaging/Destination.java
blazeds/trunk/modules/core/src/flex/messaging/services/AbstractService.java

Revision: 4193
Author: [email protected]
Date: 2008-11-26 11:40:05 -0800 (Wed, 26 Nov 2008)
Log Message:
Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* Foundational update to include destination config in what we collect for runtime config exchange with new clients for destinations with network/reliable=true (LCDS only).
* Also typo in comment in AbstractConnectionAwareSession fixed.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-517
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/AbstractConnectionAwareSession.java
blazeds/trunk/modules/core/src/flex/messaging/Destination.java
blazeds/trunk/modules/core/src/flex/messaging/services/AbstractService.java

[svn] 4323: Bug: LCDS-544 - Scenario where two components have seperate channel sets with overlapping channels not working .

Revision: 4323
Author: [email protected]
Date: 2008-12-15 19:23:10 -0800 (Mon, 15 Dec 2008)
Log Message:
Bug: LCDS-544 - Scenario where two components have seperate channel sets with overlapping channels not working.
QA: Yes
Doc: No
Checkintests Pass: Yes
Details:
* Hunting to a new channel within a channelset never triggered a disconnect from the previous channel(s). This isn't a problem in general, but does becomes a problem when an app defines two distinct channelsets containing at least one shared channel at the head of the list. In this case, the first channelset hunts past it and connects on a later channel. But when the second channelset hunts through (triggering a connect fault when it hits that initial shared channel that can't connect), the fault is processed by the first channelset as well (incorrectly).
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-544
Modified Paths:
flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/ChannelSet.as

Running the script by python2 solves it for me:
su - mythtv -c "nice -n 19 python2 /usr/bin/tv_grab_nl_py --output ~/listings.xml"
Best regards,
Cedric

[svn] 4258: Bug: LCDS-522 - Add more configurable reconnect handling for connecting up again over the same channel when there is a connection failure /outage.

Revision: 4258
Author: [email protected]
Date: 2008-12-08 16:33:17 -0800 (Mon, 08 Dec 2008)
Log Message:
Bug: LCDS-522 - Add more configurable reconnect handling for connecting up again over the same channel when there is a connection failure/outage.
QA: Yes
Doc: No
Checkintests Passes: Yes
Details:
* Updates to configuration handling code and MXMLC code-gen to support new long-duration reliable reconnect setting.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-522
Modified Paths:
blazeds/trunk/modules/common/src/flex/messaging/config/ClientConfiguration.java
blazeds/trunk/modules/common/src/flex/messaging/config/ClientConfigurationParser.java
blazeds/trunk/modules/common/src/flex/messaging/config/ConfigurationConstants.java
blazeds/trunk/modules/common/src/flex/messaging/config/ServicesDependencies.java
blazeds/trunk/modules/common/src/flex/messaging/errors.properties
Added Paths:
blazeds/trunk/modules/common/src/flex/messaging/config/FlexClientSettings.java
Removed Paths:
blazeds/trunk/modules/core/src/flex/messaging/config/FlexClientSettings.java

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] 1043: Bug: LCDS-184 - Concurrent modification exception thrown during remote subscription management

Revision: 1043
Author: [email protected]
Date: 2008-03-31 15:22:13 -0700 (Mon, 31 Mar 2008)
Log Message:
Bug: LCDS-184 - Concurrent modification exception thrown during remote subscription management
QA: Yes
Doc: No
Details:
Make the 'subscriptions' set in MessageClient/RemoteMessageClient concurrent modification safe.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-184
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/messaging/RemoteMess ageClient.java

[svn] 1044: Bug: LCDS-184 - Concurrent modification exception thrown during remote subscription management

Revision: 1044
Author: [email protected]
Date: 2008-03-31 15:23:07 -0700 (Mon, 31 Mar 2008)
Log Message:
Bug: LCDS-184 - Concurrent modification exception thrown during remote subscription management
QA: Yes
Doc: No
Details:
Make the 'subscriptions' set in MessageClient/RemoteMessageClient concurrent modification safe.
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-184
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageClient.java

[svn] 3026: Bugs: LCDS-370 - Passing user credentials from Flex app to WAS 6.1 returns java. lang.ClassCastException

Revision: 3026
Author: [email protected]
Date: 2008-08-28 11:35:50 -0700 (Thu, 28 Aug 2008)
Log Message:
Bugs: LCDS-370 - Passing user credentials from Flex app to WAS 6.1 returns java.lang.ClassCastException
QA: Yes
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/LCDS-370
Modified Paths:
blazeds/branches/3.0.x/modules/opt/src/websphere/flex/messaging/security/WebSphereLoginCo mmand.java

Please test with the new Java Plug-In available in 6u10 at http://jdk6.dev.java.net/6u10ea.html. The Java/JavaScript bridge has been completely rewritten and is now more complete and portable than ever before. Longstanding issues should be fixed with this new version. Please try it and post if you continue to have problems.

[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:bz-trunk] 8910: Bug: LCDS-936 - Should have better error message in servlet log if server in services-config .xml is configured to use wrong class.

Revision: 8910
Author:   [email protected]
Date:     2009-07-29 14:22:26 -0700 (Wed, 29 Jul 2009)
Log Message:
Bug: LCDS-936 - Should have better error message in servlet log if server in services-config.xml is configured to use wrong class.
QA: Yes
Doc: No
Checkintests: Pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-936
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/MessageBrokerServlet.java

After many hard working days.i finally found the error cause,i needed to make weblogic datasource also ADF doesnt work on internet explorer browser,it works on safary.hope it helps somebody

[svn:bz-trunk] 13746: Bug: LCDS-952

Revision: 13746
Revision: 13746
Author:   [email protected]
Date:     2010-01-25 07:44:49 -0800 (Mon, 25 Jan 2010)
Log Message:
Bug: LCDS-952
QA: Yes - please make sure that:
-This change didn't cause any regressions. Last time, it caused some issues but we don't seem to remember what they were.
-Make sure the max limit is being enforced and the JVM option to change it actually works.
Doc: Yes, might want to document about default max string length of 25MB and the JVM option to change it.
Checkintests: Pass
Details: Limited maximum incoming string length to 25MB by default. Also provided a JVM option called max-string-bytes that one can use to change this limit (using -Dmax-string-bytes=1000 for example).
Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-952
Modified Paths:
    blazeds/trunk/modules/common/src/flex/messaging/errors.properties
    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:fx-trunk] 14719: Bug: LCDS-1522 - RTE running reliable messaging test over NIO HTTP endpoint caused by checkin 272187 .

Revision: 14719
Revision: 14719
Author:   [email protected]
Date:     2010-03-12 02:20:41 -0800 (Fri, 12 Mar 2010)
Log Message:
Bug: LCDS-1522 - RTE running reliable messaging test over NIO HTTP endpoint caused by checkin 272187.
QA: Yes
Doc: No
Checkintests: Pass
Details: Checkin 272187 fixed small messages to work on NIO HTTP endpoints but this exposed a bug in HTTPChannel. HTTPChannel is not supposed to support small messaging feature but there was one place where small messages feature were still being enabled which caused the bug.
Ticket Links:
    http://bugs.adobe.com/jira/browse/LCDS-1522
Modified Paths:
    flex/sdk/trunk/frameworks/projects/rpc/src/mx/messaging/channels/HTTPChannel.as

[svn] 1013: Bug: LCDS-180 - [WebLogic 10.1 on Suse9] MxUnit Dynamic destination "SecurityEmployeeUser" test fails with a NullPointerException

Similar Messages

Maybe you are looking for