[svn:bz-trunk] 18928: fixing the sample service-config. xml for max-object-nest-level setting

Revision: 18928
Revision: 18928
Author:   [email protected]
Date:     2010-12-01 14:16:56 -0800 (Wed, 01 Dec 2010)
Log Message:
fixing the sample service-config.xml for max-object-nest-level setting
Modified Paths:
    blazeds/trunk/resources/config/services-config.xml

you have your driver jar in Tomcat\common\lib?
if so, check your classpath, it could be that.

Similar Messages

[svn:bz-trunk] 8823: Updated the sample messaging-config. xml with the new disallow-wildcard-subtopics configuration element.

Revision: 8823
Author:   [email protected]
Date:     2009-07-27 09:12:08 -0700 (Mon, 27 Jul 2009)
Log Message:
Updated the sample messaging-config.xml with the new disallow-wildcard-subtopics configuration element.
Modified Paths:
    blazeds/trunk/resources/config/messaging-config.xml

Hi,
could you let us know what version of OEPE you were running prior to the upgrade along with the Eclipse version ? Also was the previous installation a full OEPE install or was it installed via the update site ?
thanks
Raj

[svn] 3867: Add new user-agent info to the sample services-config.xml file.

Revision: 3867
Author: [email protected]
Date: 2008-10-24 07:13:10 -0700 (Fri, 24 Oct 2008)
Log Message:
Add new user-agent info to the sample services-config.xml file.
Modified Paths:
blazeds/trunk/resources/config/services-config.xml

Resolved! The problem was in the php code the wizard had generated as an example and that I had edited in Dreamweaver. I had tried to start a session and set session objects in the php code. I developed if() { statements} to check the session variable before executing the function in some of my data services. Apparently the wizard does not like this. I removed all references to session. I reconfigured the input types and the return types for each service. With the code now clean the wizard created the example code and placed the proper package in the scr.services package. I still have custom php code and it executes.
Things I learned:
If the php code stops when a session variable is not available in the if statement and the data service is refreshed, the wizard will not "look" beyond the if statement.
Functions downstream of a session variable misshap will show in the data services window but the functions will have a circle icon to the left of the function name and each variable to be passed to the php code will be declared as type = Object in Flashbuilder. The input types and return types will have to be reconfigured for each non-functioning function. Simply commenting out a portion of the php code and attempting a refresh will not make it work again.
When the wizard is unable to refresh properly because of a stop in the php code it stops working completely so additional refreshes or creation of code is not carried out.
I decided to create a My SQL table for user and other identifiers rather than attempting the session object again.
Sorry, I did not make screen shots as I solved this problem. I hope the solution is not hard to visualize.
Thanks for looking and considering how to help me. I hope my solution works for you.

[svn:fx-trunk] 17790: fix the samples.

Revision: 17790
Revision: 17790
Author:   [email protected]
Date:     2010-09-21 12:52:57 -0700 (Tue, 21 Sep 2010)
Log Message:
fix the samples. Have them refer to 10.1 playerglobal
QE notes: no
Doc notes: no
Bugs: no
Reviewer:no
Tests run: no
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/samples/themes/arcade/build.xml
    flex/sdk/trunk/samples/themes/cobalt/build.xml
    flex/sdk/trunk/samples/themes/graphite/build.xml
    flex/sdk/trunk/samples/themes/zen/build.xml

[svn:bz-trunk] 15129: Update the sample jgroups-tcp. xml file with proper explanations of each property after reviewing the JGroups documentation .

Revision: 15129
Revision: 15129
Author:   [email protected]
Date:     2010-03-30 06:17:55 -0700 (Tue, 30 Mar 2010)
Log Message:
Update the sample jgroups-tcp.xml file with proper explanations of each property after reviewing the JGroups documentation. This is still work in progress.
Modified Paths:
    blazeds/trunk/resources/clustering/jgroups-tcp.xml

It seems you are asking in wrong forum. AFAIK, you are asking "how to add HTTP header to response generated by my own script". It depend on WWW server we are speaking of and language of script itself. If you will fail to found solution within documentation of the HTTP server and/or scripting language you are using, then the better place for your question is a forum related to such language and HTTP server.
In meantime, you can try other solituin. The "Refresh: 0;..." header is required for correct function of SoftKey:Next which is displayed by default. But you can redefine the content of SoftKey area using your own key. Such configuration is part of DirectoryObject you sent to phone. See definition of SoftKey 3 in example bottom. It's not original SoftKey:Next that depend on Refresh header. It's my own custom soft-key named "Next" with exact URL defined as part of key definition (replace 'N' with number of next page). It doesn't depend on Refresh header in any way. You should consider such advice as "temporary workaround". You should discover how to send HTTP header 'Refresh' from your script. Note, it's not possible to redefine one SoftKey only. If you wish to redefine a soft-key, then all soft-keys need's to be defined by you.
... followed by Title, Prompt,up to 32 ...
Dial
SoftKey:Dial
1
EditDial
SoftKey:EditDial
2
Next
https://an-url-to-your-server-and-script/test-Directory.asp?page=N
3
Cancel
SoftKey:Cancel
4
Exit
SoftKey:Exit
5

[svn:bz-trunk] 21327: Updated the sample destination config to show the new "none" value for cluster-message-routing

Revision: 21327
Revision: 21327
Author:   [email protected]
Date:     2011-06-02 08:51:22 -0700 (Thu, 02 Jun 2011)
Log Message:
Updated the sample destination config to show the new "none" value for cluster-message-routing
Modified Paths:
    blazeds/trunk/resources/config/messaging-config.xml

Thanks Carlo for your reply.
I have read again the link and you are correct that in using the preferred command together with localhost under POTS dial-peer, I can now select which correct path to choose for my outbound calls. I'm just not very strong with dial-peer and translation rules at the moment.
I will try this solution during the weekend and let you know. But it would have been better if there was a sample configuration for this option.

[svn:bz-trunk] 20609: Change the default max object nest level from 1024 to 512.

Revision: 20609
Revision: 20609
Author:   [email protected]
Date:     2011-03-04 10:23:41 -0800 (Fri, 04 Mar 2011)
Log Message:
Change the default max object nest level from 1024 to 512. A max object nest level of 512 should be more than enough for most applications which probably will not be sending deeply nested object graphs over the wire. For applications that are sending deeply nested object graphs over the wire and that bump up against this limit, the limit can be increased but you should also do testing to make sure that serializing/deserializing these deeply nested object graphs doesn't cause stack overflow errors.
Update documentation for the max object nest level setting to reflect the new default.
Add documentation for the new max collection nest level setting.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.java
    blazeds/trunk/resources/config/services-config.xml

You should be able to get some more precise information from your Xorg logs, but I would bet it is related to the evdev driver. Some of the options in your xorg.conf no longer work with the latest version. For now you should be able to either map your mouse directly to the appropriate /dev/event* entry or change to the standard mouse driver, both of those methods should be in the wiki.
You are supposed to be able to use the evdev driver without the input section of your xorg.conf by using dbus/hal autodetection, but AFAIK at the moment the xorg-server package still isn't compiled with hal support, so you would have to patch and rebuild the package.

[svn:bz-3.x] 20876: Change default max object nest level to 512.

Revision: 20876
Revision: 20876
Author:   [email protected]
Date:     2011-03-16 09:02:36 -0700 (Wed, 16 Mar 2011)
Log Message:
Change default max object nest level to 512. A max object nest level of 512 should be more than enough for most applications which probably will not be sending deeply nested object graphs over the wire. For applications that are sending deeply nested object graphs over the wire and that bump up against this limit, the limit can be increased but you should also do testing to make sure that serializing/deserializing these deeply nested object graphs doesn't cause stack overflow errors.
Add documentation for the max object nest level setting.
Add documentation for the max collection nest level setting.
Checkintests: passed
Modified Paths:
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.java
    blazeds/branches/3.x/resources/config/services-config.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:bz-4.0.0_fixes] 20874: Change default max object nest level to 512.

Revision: 20874
Revision: 20874
Author:   [email protected]
Date:     2011-03-16 06:55:37 -0700 (Wed, 16 Mar 2011)
Log Message:
Change default max object nest level to 512. A max object nest level of 512 should be more than enough for most applications which probably will not be sending deeply nested object graphs over the wire. For applications that are sending deeply nested object graphs over the wire and that bump up against this limit, the limit can be increased but you should also do testing to make sure that serializing/deserializing these deeply nested object graphs doesn't cause stack overflow errors.
Add documentation for the max object nest level setting.
Add documentation for the max collection nest level setting.
Remove max-string-length-bytes setting from the example services-config.xml as this setting doesn't exist.
Checkintests: passed
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.j ava
    blazeds/branches/4.0.0_fixes/resources/config/services-config.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:bz-trunk] 20873: Update description of class deserialization validators functionality in example services-config .xml for BlazeDS/trunk.

Revision: 20873
Revision: 20873
Author:   [email protected]
Date:     2011-03-16 06:35:10 -0700 (Wed, 16 Mar 2011)
Log Message:
Update description of class deserialization validators functionality in example services-config.xml for BlazeDS/trunk.
Checkintests: Not run. No code changes.
Modified Paths:
    blazeds/trunk/resources/config/services-config.xml

Thanks Carlo for your reply.
I have read again the link and you are correct that in using the preferred command together with localhost under POTS dial-peer, I can now select which correct path to choose for my outbound calls. I'm just not very strong with dial-peer and translation rules at the moment.
I will try this solution during the weekend and let you know. But it would have been better if there was a sample configuration for this option.

[svn:bz-4.0.0_fixes] 20451: backporting bug fix BLZ-570/ BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError .

Revision: 20451
Revision: 20451
Author:   [email protected]
Date:     2011-02-24 08:33:31 -0800 (Thu, 24 Feb 2011)
Log Message:
backporting bug fix BLZ-570/BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError. the default max object nest level is 1024 and it can be configured in the endpoint/serialziation section in service-config.xml. This needs documentation. Checkintests pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-570
    http://bugs.adobe.com/jira/browse/BLZ-620
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/common/src/flex/messaging/errors.properties
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.j ava
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/SerializationContext.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/Amf0Input.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/Amf3Input.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/AmfIO.java

Dear Pallavi,
Very useful post!
I am looking for similar accelerators for
Software Inventory Accelerator
Hardware Inventory Accelerator
Interfaces Inventory
Customization Assessment Accelerator
Sizing Tool
Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
Request help on such accelerators... Any clues?
Any reply, help is highly appreciated.
Regards
Manish Madhav

[svn:bz-3.x] 20443: back porting bug fix BLZ-570/ BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError .

Revision: 20443
Revision: 20443
Author:   [email protected]
Date:     2011-02-23 21:19:22 -0800 (Wed, 23 Feb 2011)
Log Message:
back porting bug fix BLZ-570/BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError. the default max object nest level is 1024 and it can be configured in the endpoint/serialziation section in service-config.xml. This needs documentation. Checkintests pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-570
    http://bugs.adobe.com/jira/browse/BLZ-620
Modified Paths:
    blazeds/branches/3.x/modules/common/src/java/flex/messaging/errors.properties
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/SerializationContext.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/Amf0Input.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/Amf3Input.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/AmfIO.java

[svn:bz-trunk] 20927: Didn't realize I also needed to modify SerialContext. java in addition to AbstractEndpoint. java to change the default max object nest level.

Revision: 20927
Revision: 20927
Author:   [email protected]
Date:     2011-03-20 11:48:41 -0700 (Sun, 20 Mar 2011)
Log Message:
Didn't realize I also needed to modify SerialContext.java in addition to AbstractEndpoint.java to change the default max object nest level. Change maxObjectNestLevel in SerializationContext.java to 512 to change the default max object nest level from 1024 to 512.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/SerializationContext.java

As the server.xml is big enough, I took the minimum portion of it. Hope u can proceed with it.

<Context path="" docBase="ROOT" debug="0"/>

<Context path="/xyz" docBase="pathTo_xyz" debug="0" crossContext="true"/>
<Context path="/pqr" docBase="pathTo_pqr" debug="0" crossContext="true"/>

<Context path="/examples" docBase="examples" debug="0"
reloadable="true" crossContext="true">
You should also provide a WEB-INF folder under pqr or xyz folder.
You should also provide a web.xml file under each WEB-INF folder.
The minimal web.xml is
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/j2ee/dtd/web-app_2_3.dtd">
<web-app>
</web-app>
That's it. Try it out. Hope it is OK.
Hafizur Rahman
SCJP

[svn:bz-4.0.0_fixes] 20928: Needed to change maxObjectNestLevel in SerializationContext. java to 512 to change the default max object nest level from 1024 to 512.

Revision: 20928
Revision: 20928
Author:   [email protected]
Date:     2011-03-21 07:02:01 -0700 (Mon, 21 Mar 2011)
Log Message:
Needed to change maxObjectNestLevel in SerializationContext.java to 512 to change the default max object nest level from 1024 to 512.
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/SerializationContext.java

Hi Diego,
i have a question.
i know that we need SRM 4.0 installation on WAS and ITS to be installed.
my question to you is....
do we need to install EBP separately if we have already installed SRM 4.0 ( in other words is EBP part of SRM 4.0 installation or is it separate)
and for ITS i am running WAS 6.4 and i know that ITS is an integral part of it so how do we activate ITS for SRM 4.0
Thanks a lot in advance
Harish

Services-config.xml for AIR application

Hello,
I am relatively new to flex. I am primarily a .net developer. I want to know how can I make a sample applicaion which uses services-config.xml
Is there a tutorial which can help me...
Any help is appriciated on this.
Regards,
Pavas

The information in the compiled swf needs to match the information used at
server runtime. It basically uses the endpoint URL and perhaps a few other
tidbits from the config.
We have tokens in the URL for server, port and context root, which help the
'portability' of the swf, but if you change the MessageBroker servlet
mapping for instance, this will probably break the swf.
You *can* however, control the endpoint used by the client by using
Actionscript APIs (see the docs), but you still of course have to code that
in to the compiled application unless you prompt the user for that info.
Does that help?
Tom Jordahl
Adobe

[svn:bz-trunk] 18928: fixing the sample service-config. xml for max-object-nest-level setting

Similar Messages

Maybe you are looking for