Using CenterStage services from JavaScript

This sample shows an application called "MiniStage". It is built using ExtJs and it consumes CenterStage services using our DWR bindings. It shows how to call the CenterStage ListService to execute queries and how to integrate those results into an ExtJs grid using the DataStore framework.

The sample can be built into a WAR file that should be deployed alongside CenterStagePro.war. Because this sample code is hosted in a separate web application from CenterStage (and DWR), it is important to disable HTTP sessions in CenterStage. If you do not disable sessions, DWR will reject service calls to protect against CSRF (Cross-Site Request Forgery) attacks.

To disable HTTP sessions in CenterStage, add the following to "magellan.properties" inside CenterStagePro.war:

magellan.config.disable_sessions=true

You can also disable DWR's CSRF protection by configuring the DWR servlet, but this is not recommended for production environments. See the DWR servlet configuration guide for more about this.

The sample was tested with CenterStage Pro 1.1 hosted on Tomcat 6.0.18. If you have issues with other application servers, post a comment.

MiniStage.zip

Find more posts tagged with

Comments

HKristian

Hi Andrew

I am currently trying to get this one deployed. Seems like your system is different than the GA release. I am able to change some values but others I am not.

I have added ext 3.1.1 to the app-server, changed the repository name, changed icon address etc.

However, the thing I am not able to do is change the path of the centerstage services LoginService.js, ListService.js & engine.js. When I try to search for them on my deployment I only find wsdl-versions of the same.

Where should I look? Or do this example require a newer build of CenterStage?

agoodale

Those three .js files are generated dynamically by the DWR servlet, so you won't find them in the WAR.

The sample is designed to be deployed alongside CenterStage on the same appserver. You should not have to "add ext 3.1.1 to the app server" since the sample is using the Ext deployed within CenterStage. Maybe the issue is that CenterStage's app context is not "/CenterStage"? The sample's index.html is trying to reference ExtJS and the DWR files using relative URLs with "/CenterStage" as the assumed app context. If yours is different ("/CenterStagePro"?), then you need to update the URLs in index.html.

Can you describe your deployment in a little more detail? Are you putting the sample on the same app server as CenterStage?

HKristian

Got it working now.

I did deploy on the same app-server (the j-boss method server) and I already changed the relative URLs to CenterstagePro for the ext-resources. When I did.not find the three js-files I gave up without trying to change the relative URL and giving it a try (not familiar with the DWR servlet).

I still think ext 3.1.1 needs to be added. Alternatively the reference in index.html should be changed to the version that ships with the available Centerstage (ext version 2.2)

agoodale

Thanks Hans, I updated the sample's index.html to reference ExtJS 2.2. I was building the sample using CenterStage 1.1. :-)

pvalliamee

Hi Andrew,

I'm agree with Hans : Ext 3.2.1 is needed since Ext.list.ListView doesn't exist in the 2.2 version ;-)

Thanks for the sample,