This helps test remoting services. It's used primarily for team development where there is a sharp break between actionscripter and java programmers, where java engineers are responsible for setting up the remoting services. The utility allows pinging the gateway and remoting service (if it's used with the java or spring invoker), passing it a number or basically typed arguments, to make sure it up before handing off to a actionscript programmer to create full fledged Actionscript and flash clients. This alleviates the dependency on having to have a Java engineer know or have flash for initial testing of the gateway and related services. This also allows sharing of the information (e.g. sending a screenshot of the parameters and results) between the team members.
The Java2AS utility helps speed creation of AS bean ( data centric business classes ) classes from Java ones. Especially initialiy in development, since the java is on a central server and changes requently, it's hard for actionscripters who don't run java to connect remotely and build the beans using a local executable version of the Java code. It is not a complete Java to Actionscript converstion utility, it doesn't introspect inside methods, this should always be done by hand.
Supports
//extends com.schematic.BaseObject
//implements com.schematic.AccountInterface
class com.schematic.AccountImplementer {
This only works in the openamf with examples distribution, and this needs to be added to openamf-config.xml for the java2As to work.
<service>
<name>Java2AS</name>
<service-location>org.openamf.examples.Java2AS</service-location>
<invoker-ref>Java</invoker-ref>
<method>
<!-- Operation's are matched by the name and parameters -->
<name>generateAS</name>
<parameter>
<type>*</type>
</parameter>
</method>
</service>