Specialised access points

Beatrix's access points by default are simple proxies. Access points always download in response to a service bind from a consumer with a warrant, and by default that access point will always be the same proxying netlet, sending instructions back to a managed netlet which has the relevant service provider plugin.

To make a specialised access point we need create the launch descriptor. Recall the command line:

% jtrixmaker -type beatrix -outfile skeleton-launcher.xml \
     -x500dn o=jtrix,cn=skeleton2 -jardirs /home/nik/build/bin \
     -jars skeleton2.jar beatrix.jar libjtrix.jar jaxp.jar parser.jar \
         facets1.jar \
     -access ap \
     -codebase ap skeleton2.jar beatrix.jar libjtrix.jar facets1.jar \
     -plugins org.jtrix.project.skeleton2.plugins.LifeCyclePlugin
% 

The -access option may be used any number of times to specify different access point definitions. The service type tells Beatrix (or, rather, SAS with the help of Beatrix) that this access point needs to be delivered when a consumer binds the given service. All the JARs are delivered (this is very inefficient and will change) and the netlet is initialised at the main class, which is the one implementing INetlet.

See Appendix  for a concrete example of an application (Webtrix) which uses a specialised access point.