[svn] 4713: -Updated the validator sample in resouces/config/ services-config.xml.

Revision: 4713
Author: [email protected]
Date: 2009-01-28 11:45:50 -0800 (Wed, 28 Jan 2009)
Log Message:
-Updated the validator sample in resouces/config/services-config.xml.
-Added a sample validator that logs out deserialized class names when they are first encountered; this can be used in figuring out what allowed/disallowed class lists to use in ClassDeserializationValidator.
Checkintests: Didn't run - no code change.
Modified Paths:
blazeds/trunk/resources/config/services-config.xml
Added Paths:
blazeds/trunk/resources/samples/
blazeds/trunk/resources/samples/validators/
blazeds/trunk/resources/samples/validators/ClassLoggingDeserializationValidator.java

Hey,
i found the solution in this thread: http://kr.forums.oracle.com/forums/thread.jspa?threadID=901911
I close JDev and rename the system folder in my application data. Start JDev again and run the sample.
Kind regards,
Marcel

Similar Messages

[svn:bz-trunk] 18958: Updated the Vector sample in the team app.

Revision: 18958
Revision: 18958
Author:   [email protected]
Date:     2010-12-02 07:38:12 -0800 (Thu, 02 Dec 2010)
Log Message:
Updated the Vector sample in the team app.
Modified Paths:
    blazeds/trunk/apps/team/WEB-INF/flex/services-config.xml
    blazeds/trunk/apps/team/WEB-INF/src/features/remoting/EchoService.java
    blazeds/trunk/apps/team/features/remoting/remoting_AMF_Vector.mxml

[svn] 1593: Updated the description of legacy-externalizable setting.

Revision: 1593
Author: [email protected]
Date: 2008-05-07 10:08:43 -0700 (Wed, 07 May 2008)
Log Message:
Updated the description of legacy-externalizable setting.
Modified Paths:
blazeds/trunk/resources/config/services-config.xml

Kiran,
Very good finding man.......
When you are doing transfer postings of legacy asset data's balances to asset recon accounts with OASV, you need to adjust this ord dep posted (curr yr dep) also.
For ex lets say-your APC value is 1000-Accum dep till last day of last FY is 200---and ord dep posted amount (curr yr dep, which is posted in legacy system) is 50. And in this scenario your adjustment entry in OASV will be as same as below entry.
1st entry) APC Value new GL Account   Dr         1000
                         Accum Dep new GL account   Cr                 250   (200+50)
                         Asset OB Upload clg acc         Cr                 750
2nd entry) Asset OB upload clg account Dr            750
                  Accum dep old GL A/c           Dr             250
                           APC value old GL account      Cr                1000
Here new GL account means, the recon GL account, which is using currently for asset APC and Accum Dep postings. And old means, the recon GL account numbers, those used in your legacy system.
My sincere advise is that, please use F-02 for transfer postings other than OASV, since F-02 is very flexible.
Before doing F-02 switch off recon indicators for all asset related GL accounts with OAMK and pass F-02 entry and switch it on again.
I hope this is more helpful to you.
Dont say that this is my last question or something else man....
This forum is meant for these kind discussions only.
Thanks,
Srinu

[svn] 1591: Updated the description of legacy-externalizable setting.

Revision: 1591
Author: [email protected]
Date: 2008-05-07 08:58:17 -0700 (Wed, 07 May 2008)
Log Message:
Updated the description of legacy-externalizable setting.
Modified Paths:
blazeds/branches/3.0.x/resources/config/services-config.xml

Kiran,
Very good finding man.......
When you are doing transfer postings of legacy asset data's balances to asset recon accounts with OASV, you need to adjust this ord dep posted (curr yr dep) also.
For ex lets say-your APC value is 1000-Accum dep till last day of last FY is 200---and ord dep posted amount (curr yr dep, which is posted in legacy system) is 50. And in this scenario your adjustment entry in OASV will be as same as below entry.
1st entry) APC Value new GL Account   Dr         1000
                         Accum Dep new GL account   Cr                 250   (200+50)
                         Asset OB Upload clg acc         Cr                 750
2nd entry) Asset OB upload clg account Dr            750
                  Accum dep old GL A/c           Dr             250
                           APC value old GL account      Cr                1000
Here new GL account means, the recon GL account, which is using currently for asset APC and Accum Dep postings. And old means, the recon GL account numbers, those used in your legacy system.
My sincere advise is that, please use F-02 for transfer postings other than OASV, since F-02 is very flexible.
Before doing F-02 switch off recon indicators for all asset related GL accounts with OAMK and pass F-02 entry and switch it on again.
I hope this is more helpful to you.
Dont say that this is my last question or something else man....
This forum is meant for these kind discussions only.
Thanks,
Srinu

[svn:bz-trunk] 10020: Had previously updated user-agent string for Opera 10 in resources/config/ services-config.xml on DataServices/trunk.

Revision: 10020
Author:   [email protected]
Date:     2009-09-04 07:35:51 -0700 (Fri, 04 Sep 2009)
Log Message:
Had previously updated user-agent string for Opera 10 in resources/config/services-config.xml on DataServices/trunk. Forgot to do this for the file on BlazeDS/trunk.
Modified Paths:
    blazeds/trunk/resources/config/services-config.xml

Revision: 10020
Author:   [email protected]
Date:     2009-09-04 07:35:51 -0700 (Fri, 04 Sep 2009)
Log Message:
Had previously updated user-agent string for Opera 10 in resources/config/services-config.xml on DataServices/trunk. Forgot to do this for the file on BlazeDS/trunk.
Modified Paths:
    blazeds/trunk/resources/config/services-config.xml

[svn:bz-trunk] 9839: Document enforce-endpoint-validation in resources/ config/services-config.xml.

Revision: 9839
Author:   [email protected]
Date:     2009-08-31 11:29:03 -0700 (Mon, 31 Aug 2009)
Log Message:
Document enforce-endpoint-validation in resources/config/services-config.xml.
Modified Paths:
    blazeds/trunk/resources/config/services-config.xml

Do I need the 'java-polling-amf in my services-config.xml if I'm using coldfusion

Do I need the 'java-polling-amf in my services-config.xml if I'm using coldfusion?
Im using IntelliJ IDEA with a flex project and for some reason its stopping comilation with this error:
[SUITE (Flex Application 1)] flex.messaging.config.ConfigurationException: The services configuration includes a channel-definition 'java-polling-amf' that has an endpoint with a context.root token but a context root has not been defined. Please specify a context-root compiler argument.
when I was using flex builder with CF builder I never needed to specify the context.root

I don't use IDEA, so I don't know what kind of configuration settings it has for Flex project development.
You don't need the java-polling-amf channel for CF development. By default, CF development uses CF-specific channels:
my-cfamf
cf-polling-amf
my-cfamf-secure
any custom channels you've created yourself for CF to use
That said, all the channels require a context root setting for your project to compile properly. If you still have Flash Builder handy, take a look at your compiler switches for a project there to see what you're missing in IDEA.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
http://training.figleaf.com/

[svn] 1723: Updating the team app with send/subscribe samples.

Revision: 1723
Author: [email protected]
Date: 2008-05-14 15:26:30 -0700 (Wed, 14 May 2008)
Log Message:
Updating the team app with send/subscribe samples.
Modified Paths:
blazeds/branches/3.0.x/apps/team/WEB-INF/flex/messaging-config.xml
blazeds/branches/3.0.x/apps/team/features/messaging/sendsubscribeconstraint/messaging_AMF _Poll_SendSubscribeConstraint.mxml
blazeds/branches/3.0.x/apps/team/features/messaging/sendsubscribeconstraint/messaging_HTT P_Poll_SendSubscribeConstraint.mxml
Added Paths:
blazeds/branches/3.0.x/apps/team/features/messaging/sendsubscribeconstraint/messaging_AMF _LongPoll_SendSubscribeConstraint.mxml
blazeds/branches/3.0.x/apps/team/features/messaging/sendsubscribeconstraint/messaging_AMF _Stream_SendSubscribeConstraint.mxml

Hi Pratibha,
Thank you for posting in MSND forum.
Since
this forum is to discuss: Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor.
Based
on your issue, since it is related to the Deployment Framework for Biztalk (BTDF), so I suggest you could consult this issue directly to this Deployment Framework for Biztalk (BTDF) website:
https://biztalkdeployment.codeplex.com/discussions , you will get better support.
Thanks for your understanding.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

[svn] 1531: update the flex-sdk-description to 3.0.1

Revision: 1531
Author: [email protected]
Date: 2008-05-02 08:38:50 -0700 (Fri, 02 May 2008)
Log Message:
update the flex-sdk-description to 3.0.1
update the manifest variables so the versions will be in sync with the description file
bug: https://bugs.adobe.com/jira/browse/SDK-15416
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-15416
Modified Paths:
flex/sdk/branches/3.0.x/build.properties

Hi,
Have you tried updating to Flex Builder 3.0.2 and then using Flex SDK 3.5?
Updates are available here: http://www.adobe.com/support/flex/downloads_updaters.html#flex3
Alternatively, Flash Builder 4 also provides full support for Flex SDK 3.5.
Thanks,
Andrew
Senior Product Manager, Flash Builder

[svn] 1594: Update the warning message when outbound throttle policy of REPLACE is used one more time .

Revision: 1594
Author: [email protected]
Date: 2008-05-07 11:10:27 -0700 (Wed, 07 May 2008)
Log Message:
Update the warning message when outbound throttle policy of REPLACE is used one more time. Now the warning says this. . .
Throttle outbound policy 'REPLACE' found on message destination 'MESSAGE_DESTINATION'. The 'REPLACE' throttle outbound policy has been deprecated. Please remove it from your configuration file.
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageDestination.java

hamish72 wrote:
You can still download as much as you can only a lot slower during peak times off peak will not be restricted.
Thanks for this explanation. I had taken it that it was at all times.
As I said in the first place it will be great if they throttle me to 1Mb at peak times as it will be better half the time than I am getting anyway!!!!!!!!!
hamish72 wrote:
Have you chased up why your line is so bad, long way from exchange and so on
Posting your router stats may get advice from someone
enter for homehub for other routers will differ
192.168.1.254 in browser click A to Z top right
then ADSL enter pas and click MORE DETAIL
POST RESULTS
Also post results of test at ( best done from master test socket)
http://speedtester.bt.com/
Connection Information
Line state
Connected
Connection time
6 days, 11:57:55
Downstream
5,760 Kbps
Upstream
448 Kbps
ADSL Settings
VPI/VCI
0/38
Type
PPPoA
Modulation
G.992.1 Annex A
Latency type
Interleaved
Noise margin (Down/Up)
5.7 dB / 21.0 dB
Line attenuation (Down/Up)
44.6 dB / 24.0 dB
Output power (Down/Up)
8.9 dBm / 1.6 dBm
Loss of Framing (Local/Remote)
0 / 0
Loss of Signal (Local/Remote)
0 / 0
Loss of Power (Local/Remote)
0 / 0
FEC Errors (Down/Up)
25279 / 134
CRC Errors (Down/Up)
700 / 196
HEC Errors (Down/Up)
5427 / 142
Error Seconds (Local/Remote)
477 / 102

[svn] 1636: update the framework build file we put in the sdk pkg.

Revision: 1636
Author: [email protected]
Date: 2008-05-09 10:05:15 -0700 (Fri, 09 May 2008)
Log Message:
update the framework build file we put in the sdk pkg. I think this is probably going to go away, but I wanted to make sure it worked while it is still being put in.
Modified Paths:
flex/sdk/trunk/frameworks/build_framework.xml

Hi Kevin,
Dunno if you saw my other post to you, but I've put up a copy of the SDK that you were looking for and asked that we change our procedures going forward. As for the actual issue, would you mind creating a bug report at bugbase.adobe.com if you haven't already?
Thanks
Chris

[svn] 3917: update the stage target to not copy the flex tasks license. txt since it ain't there any longer

Revision: 3917
Author: [email protected]
Date: 2008-10-27 16:29:55 -0700 (Mon, 27 Oct 2008)
Log Message:
update the stage target to not copy the flex tasks license.txt since it ain't there any longer
Modified Paths:
flex/sdk/branches/3.2.0/build.xml

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] 762: -update the 3.0 branch to use build. properties to create the flex-sdk-description.xml

Revision: 762
Author: [email protected]
Date: 2008-03-10 07:44:49 -0700 (Mon, 10 Mar 2008)
Log Message:
-update the 3.0 branch to use build.properties to create the flex-sdk-description.xml
Modified Paths:
flex/sdk/branches/3.0.x/build.properties
flex/sdk/branches/3.0.x/build.xml
Added Paths:
flex/sdk/branches/3.0.x/collateral/en_US/flex-sdk-description.xml

By the way, simply adding the quotes around the lexical names in the sql statement doesn't work. That causes the lexical references to be ignored as simple string values:
SELECT
   '&FLEX_GL_BALANCING_APROMPT' alias_gl_balancing_aprompt
,'&FLEX_GL_ACCOUNT_LPROMPT'   alias_gl_account_lprompt
,'&ACCT_BAL_LPROMPT'          alias_acct_bal_lprompt
FROM dualI turned on statement-level debugging via xdodebug.cfg and saw how it compiled the lexicals. By replicating the call to apps.fnd_flex_xml_publisher_apis.kff_segments_metadata that I found there, I was able to hack together a workaround for this issue.
Please point me to a better way of doing this if possible, as I had to GRANT EXECUTE on this apps package to my custom code schema. Is there a better lexical/flexfields reference than the XML Publisher documentation?
Here is the call I made in my before-report trigger:
--set ACCT_BAL_LPROMPT flexfield segment metadata lexical
begin
apps.fnd_flex_xml_publisher_apis.kff_segments_metadata(
'FLEX_ACCT_BAL_LPROMPT',
'SQLGL',
'GL#',
101,
'GL_BALANCING',
'Y',
'LEFT_PROMPT',
c_FLEX_ACCT_BAL_LPROMPT
end;

[svn] 3839: Update the channel url to reflect the change in the runtime channel

Revision: 3839
Author: [email protected]
Date: 2008-10-23 07:42:37 -0700 (Thu, 23 Oct 2008)
Log Message:
Update the channel url to reflect the change in the runtime channel
Modified Paths:
blazeds/branches/3.0.x/qa/apps/qa-manual/ajax/messaging/TextMessageRuntimeDest.html

Many ways to do this. The easiest is to have a method in one of your classes that reads the data from the database and creates all the proper structure under a RootNode and then returns that RootNode.
Whenever you want to refresh the tree, just call that method to recreate the root node (and all the underlying structure/nodes) and then re-set the root node of your tree model using the setRoot() method. That will cause it to refresh the display given the new root node.
Once you have that working, you can get fancier and make it more efficient (only updating/firing events for the nodes that actually changed, etc).

[svn] 3061: update the framework build. xml that gets included in the package

Revision: 3061
Author: [email protected]
Date: 2008-09-02 12:38:17 -0700 (Tue, 02 Sep 2008)
Log Message:
update the framework build.xml that gets included in the package
-use target-player = 10 for most frameworks
-updated utilities target to use FlexContentHolder.swc and framework.swc
Modified Paths:
flex/sdk/trunk/frameworks/build_framework.xml

The problem with re-using an existing WSUS is that ConfigMgr doesn't do anything with the existing approved and declenid updates. ConfigMgr will only use the metadata of the updates in WSUS. This could cause problems as the ConfigMgr client simply tells
the WUA agent to scan against WSUS for compliance and then uses the update groups to tell the client which updates should be installed. In case the WUA agent finds updates directly on WSUS that are approved then it will also start to install those updates...
That's why you should use one of them, as they will interfere with eachother..
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

[svn] 4713: -Updated the validator sample in resouces/config/ services-config.xml.

Similar Messages

Maybe you are looking for