Re: Re: Re: Re: Shark 1.1 CORBA from .NET

David Forslund <[email protected]>
Newsgroups gmane.comp.java.enhydra.shark
Message-ID <[email protected]>
To further clarify my comments below.  Normally the #pragma prefix 
controls both the IDL/CORBA Namespace and in Java the class namespace.   
The namespace of the implementation of Shark today has the Java class 
namespace defined by the commandline of the idlj compiler and the 
IDL/CORBA Namespace is empty.  That is the objects are defined as 
IDL:WorflowService/CacheAdministration:1.0, e.g.  I think a more 
consistent approach would be to use the pragma so the namespace is 
IDL:corba.shark.enhydra.org/WorkflowService/CacheAdministration:1.0 
which would require the #pragma prefix "corba.shark.enhydra.org"  in the 
IDL files that are specific to Shark.  It sounds like IIOP.NET continues 
the #pragma prefix from the included modules which is inconsistent with 
other IDL compilers.

Dave


David Forslund wrote:

> I don't know about IIOP.NET, but the namespace on the Java side should 
> be controlled by the #pragma statements, which Sun's idlj compiler 
> doesn't recognize.  Instead the namespace is specified with a 
> commandline argument in idlj.   It would appear that there should be a 
> #pragma statement in the WorkflowService and ExpressionBuilder idl 
> files but isn't because the idlj compiler doesn't use it.   The 
> namespaces in the Java are correct as intended.  One needs to 
> understand how to make IIOP.NET use an equivalent namespace.  Perhaps 
> correcting the idl would help.
>
> Dave
> [email protected] wrote:
>
>> Sasa,
>>
>> I was suggesting that the orignal IDL should include the correct 
>> namespace rather than using a switch to compile it.  As a user, 
>> modifying the IDL or finding switches each time I need to rebuild 
>> this are really the same problem.  If I must do something, I'd rather 
>> it be a workaround to IIOP.NET, than something missing out of the IDL 
>> definition.
>> Actually, after some additional research I found that IIOP.NET does 
>> have a known problem with resetting #pragma prefix.  The workaround 
>> is to include the #pragma prefix "" at the end of the IDL once it is 
>> no longer needed.  If this is done in the WorkflowModel.idl and 
>> WfBase.idl, using #pragma prefix "org.enhydra.shark.corba" in 
>> WorkflowServices.idl and ExpressionBuilder.idl will build the 
>> expected namespace. Unfortunately, this does not work and produces 
>> the origianal INTF_REPOS exception.
>>
>> What does work is using $pragma prefix "" at the beginning to clear 
>> the namespace in WorkflowServices.idl and ExpressionBuilder.idl  (the 
>> other assignments don't seem to be used, although it may add 
>> something internally that I haven't seen). Since this works properly, 
>> I would question whether these modules really exist in the correct 
>> namespace on the Java side.
>> Brian 
>>  
>>
>>
message.footer (text/plain, 271 B)
--
You receive this message as a subscriber of the [email protected] mailing list.
To unsubscribe: mailto:[email protected]
For general help: mailto:[email protected]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.