Hi,
in addition to my previous mail, there is another problem when handling XML
digital signatures for which I have no satisfactory fix.
In an XML signature, one of the used element names is "Object", this
represents the objects that have been digitally signed. In the generated
source code, there is plenty of use of the java.lang.Object as abstract base
class (in all the handlers for example). This leads to uncompilable source
code as "Object" is interpreted as the generated "Object" class
(corresponding to the element name).
I've applied a temporary fix to the source generator which consists of
adding the following import statement to all generated classes (including
the descriptor classes):
import java.lang.Object;
This however still requires me to modify the following generated classes:
Object.java -> remove import again, otherwise clash with java.lang.Object!
SingatureType.java, SignatureTypeDescriptor.java -> include full class name
(for example nl.sbti.interfaces.dsig.Object) where Object is meant to be
nl.sbti.interfaces.dsig.Object
Maybe you can give me a hint on how to implement a solution that does not
require me to modify these generated classes. The idea is to have the
generator recognise an element with name "Object" and to generate source
code that does not clash with java.lang.Object.
Kind regards,
Francis
----------------------------------------------------------------------------
-----------------
ATOS/ORIGIN
Ing. Francis (FRA) Vermeulen
Senior Consultant e-business
mobile: +31 (0) 6 222 03 856
e-mail: [EMAIL PROTECTED] of
[EMAIL PROTECTED]
----------------------------------------------------------------------------
-------------
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
