Archived
This forum has been archived. Please start a new discussion on GitHub.
Ice module name
Comments
-
Everything that starts with "ice" is not permissible as an identifier. This allows us to have our own internal namespaces and nested namespaces, for which there can be no name clashes.
Can't you just use "FrozenWater"?0 -
Originally posted by marc
Everything that starts with "ice" is not permissible as an identifier. This allows us to have our own internal namespaces and nested namespaces, for which there can be no name clashes.
Can't you just use "FrozenWater"?
Not bad
Well,
if you design a service in a layered manner, with the real impl that is
middleware independent, you could put CORBA access point,
Ice access point, SOAP access point around it (I know is'nt that easy,
but, at least, ease testing phase).
With this in mind, if your service is defined as:
com.mycompany.servicexx.spec for interface specification
com.mycompany.servicexx.impl for implementation
a module naming could be
com.mycompany.servicexx.ice.spec for ice generated
com.mycompany.servicexx.ice.impl for ice implementation
Maybe iceimpl module name works better:)
Guido.0