myfaces-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Myfaces Wiki] Update of "Extensions/Scripting/Setup" by WernerPunz
Date Thu, 31 Dec 2009 20:02:33 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Myfaces Wiki" for change notification.

The "Extensions/Scripting/Setup" page has been changed by WernerPunz.
http://wiki.apache.org/myfaces/Extensions/Scripting/Setup?action=diff&rev1=4&rev2=5

--------------------------------------------------

  
  [[http://svn.apache.org/repos/asf/myfaces/extensions/scripting/trunk|via the svn trunk]]
  
- Make sure you have following checklist on your machine installed before checking out
+ Make sure you have following requirements fulfilled before checking out:
  
   * A valid svn client
   * Java 5 or higher
   * Maven 2.0.9 or higher
  
- After checking out, you can run a full build via '''mvn clean install''' from the root directory
of your checkout.
+ After checkout, a full build can be obtained from the root directory of your checkout via
'''mvn clean install'''.
  
- After that you have a valid build installed, you can use further on. Additionally you can
find two blueprint projects which you can use as starting points for your own projects under
'''<checkoutDir>/examples''' which can be kickstarted via '''mvn jetty:run-exploded'''
+ Once finished, a valid build is installed, which can be used further on. Additionally you
can find two blueprint projects which you can use as starting points for your own projects
under '''<checkoutDir>/examples''' which can be kickstarted via '''mvn jetty:run-exploded'''
  
  == Setup of Ext-Scripting ==
  === Requirements ===
- Before setting up ext-scripting make sure following requirements are met.
+ Before setting up '''Ext-Scripting''' make sure following requirements are met.
  
   * JAVA_HOME points towards a valid Java SDK (JRE is not sufficient)
   * You know how to create and deploy a web application within your preferred setup (command
line, ide)
@@ -54, +54 @@

          <url-pattern>*.jsf</url-pattern>
  }}}
  ==== web.xml Root Sourcepaths ====
+ 
-  . Since the goal of '''Ext-Scripting''' is to provide scriptability to a running web application
it has to know where to find the sources it has to process. For this a default location has
been chosen according to the standards set by the Mojarra Groovy extension the location looks
like:
+ Since the goal of '''Ext-Scripting''' is to provide scriptability to a running web application
it has to know where to find the sources it has to process. For this a default location has
been chosen according to the standards set by the Mojarra Groovy extension the location looks
like:
  
  {{{
     <webapp>/WEB-INF/groovy
@@ -67, +68 @@

  as root location for java files.
  
  {{http://people.apache.org/%7Ewerpu/images/ext%5Fdefault%5Ffile.jpg}}
- 
  
  
  However in a normal development scenario, it is often undesirable to have the files located
in a deployment location, and a pointer mechanism towards the actual source locations would
be more desirable.

Mime
View raw message