|
|
Featured White Papers
- Why choose an Open Source BPM?
- 10 FAQs on Business Process Management
- Best Practices for Getting Started with BPM
- Free Your Devs From The Pain Of Java Redeploys
- Increase Velocity 40% by Using JRebel
- What Developers Want: The End of Application Redeploys
- Developer Productivity Report: Java Tools, Tech, Devs, and Data
- Coding with JRebel: Java Forever Changed
- Utilizing Fast Testing to Transform Java Development
- Do You Really Get Classloaders?
- Pragmatic Continuous Delivery with Jenkins, Nexus, and LiveRebel
- Your Next Java Web App: Less XML, No Long Restarts, Fewer Hassles
- Coding with JRebel, Java Forever Changed
- 2012 Developer Productivity Report: Java Tools, Tech, Devs, and Data
F3 Deployment
Submitted by Chris Oliver on Sat, 11/25/2006 - 14:35.One of the comments to my earlier posts expressed some concern that a lot of demo code seemed to be all in one file.
That's just because they were quick demos.
F3 supports packages and imports as in Java. So you can divide your application into as many separate files as you like.
The F3 interpreter actually loads F3 classes by means of the Java class loader. So to deploy F3 code you simply archive it in JAR files as in Java and then make such archives accessible to the Java class loader.
Our F3 IDE plugins are also closely integrated with the corresponding Java plugins. There is no special F3 "perspective" or F3 project type. In both Netbeans and Eclipse, you simply use normal Java projects, create packages using the existing Java facilities and then create F3 files in those packages. The normal build process will "do the right thing" and archive your F3 code into the output jar file of your project.