ObjectWeb Consortium
Search ObjectWeb Mail Archive: 

Advanced Search - Powered by Google

Mail Archive Home | jawe List | June 2004 Index

<--  Date Index  --> <--  Thread Index  -->

Re: [jawe] Types definitions not inherited


WfMC spec. states that only Participants, Applications and WorkflowProcess 
Ids are "inherited" from external package.
So, there is no way to do this, because if we would implement it, we would go 
beyond WfMC spec.
You could create the same TypeDeclaration in the main package as you do in 
external one, but I think JaWE/Shark will report
validation error if appropriate formal parameter mode is different that "IN" 
(I think this could be changed in JaWE - it should
relax checking on Declared types).
Also, we could maybe implement possibility to automatically import 
TypeDeclarations from external packages if user wants so
(something like this happens when we are importing processes from other 
packages - see Package->Import external process).


----- Original Message -----
From: <Peter.Wagner@xxxxxxxxx>
To: <jawe@xxxxxxxxxxxxx>
Sent: Thursday, June 24, 2004 2:54 PM
Subject: [jawe] Types definitions not inherited


in counterpart to Application definitions, the Type definitions apparently
are not inherited when that package is referenced as an external package.

Is there any way to create an "include file" that contains declarations of
business objects, reducing the need of typing the fully-qualified class
for every actual and formal parameter?

Mit freundlichen Grüssen
   / Best Regards,
Ing. Peter Wagner
BM.I Support Unit ZMR
Tel: +43 1 31346 39159


> --
> You receive this message as a subscriber of the jawe@xxxxxxxxxxxxx mailing 
> list.
> To unsubscribe: mailto:jawe-unsubscribe@xxxxxxxxxxxxx
> For general help: mailto:sympa@xxxxxxxxxxxxx?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

<--  Date Index  --> <--  Thread Index  -->

Reply via email to:

Powered by MHonArc.

Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster.