q Right now, when wriFng a web app we need to walk through mulFple layers of technology § HTML(5)/JS, PHP/Ruby/Java, ORM(SQL) q InformaFon captured at the client need to be transformed at each layer § JSON/CSV/XML q Its not straighWorward to build a naFvely REST/JSON app q Developing an API coupled to the app is a nightmare
all parts of the Web applicaFons and services § Eliminates the mismatches across different layers q Closes the gap between Web apps from Web services by allowing one to create both applicaFons and APIs at the same Fme.
q The runFme augments the features of a web server q It talks smoothly in JSON q Can handle URL pa8erns q Can talk to databases q A Shell that can execute the jaggery scripts q Its a new plaWorm, we believe everybody will start building cool things
directory you prefer. lets call it JAGGERY_HOME q Navigate to {JAGGERY_HOME}/bin directory which contains all the Jaggery execuFon scripts. q Run sh {JAGGERY_HOME}/bin/server.sh ({JAGGERY_HOME}/bin/ server.bat in windows) command to start the server q Point the browser URL to http://localhost:9763/taskmaster
called helloapp at {JAGGERY_HOME}/ apps/ q Create a jaggery file helloworld.jag inside the helloapp directory and add the following code snippet q Thats it! now point to {http://localhost:9443/ helloapp/helloworld.jag}
q Yeah ! go on write some J q You can import any script which is wri8en for commonjs as a jaggery module q If nothing for the rescue, you can expose even a JAVA library as a module for Jaggery
[email protected] q Report your issues at https://wso2.org/jira/ browse/JAGGERY q The source is at (which will be soon moved to GitHub) http://svn.wso2.org/repos/wso2/carbon/ platform/trunk/products/jaggery/