Difference between revisions of "Developing codeunits"
Jump to navigation
Jump to search
old>Admin |
old>Admin |
||
| Line 1: | Line 1: | ||
Steps for creating a new codeunit | |||
== Steps for creating a new codeunit == | |||
# Create a new Java project in your favorite IDE | # Create a new Java project in your favorite IDE | ||
| Line 9: | Line 10: | ||
# Compile and build | # Compile and build | ||
# Deploy to webservser: [Application]\WEB-INF\lib | # Deploy to webservser: [Application]\WEB-INF\lib | ||
After first test of the codeunit a server reboot is needed for each redeployment, as there is no way of removing the loaded classes from memory. | |||
== Error handling == | == Error handling == | ||
Exceptions are handled by themselves using the errorRegistration(Exception e) method. | Exceptions are handled by themselves using the errorRegistration(Exception e) method. | ||
== Different codeunit types == | |||
Please read the: [[Codeunit_reference]] | |||
Revision as of 17:53, 21 February 2013
Steps for creating a new codeunit
- Create a new Java project in your favorite IDE
- Import the p2eShared.jar in the project
- Create a new class:
- The abstract parts are found in: dk.p2e.blanket.codeunit
- Implement all abstract methods
- Code the method bodies (normally "execute")
- Compile and build
- Deploy to webservser: [Application]\WEB-INF\lib
After first test of the codeunit a server reboot is needed for each redeployment, as there is no way of removing the loaded classes from memory.
Error handling
Exceptions are handled by themselves using the errorRegistration(Exception e) method.
Different codeunit types
Please read the: Codeunit_reference