[jacorb-developer] IDL generator does not initialize typedef strings

[Flock, Matthias]

Hi Nick,

the MARSHAL Exception is thrown when an instance of the object, where
"id" was not set, should be written via the generated Helper class
(MyStructHelper.write).

Currently we removed all these typedefs and defined the fields directly
as strings. I can live with that, but generally it would be easier if
they would be initialized.

Matthias

-----Original Message-----

Hi,

Currently, this is its intended behaviour - but I agree it would be
better if it was initialised to be the same as the other string.

Where does it cause a MARSHAL ?

Regards

Nick


On 04/11/13 09:08, Flock, Matthias wrote:
> We recently moved from another ORB to JacORB and are now facing a 
> problem with the generation from IDL.
>
> For easier reading we use some string typedefs (small example):
>
> module IDL {
> 	typedef string PartId;
> 		
> 	struct MyStruct
> 	{
> 	   string name;
> 	   PartId id;
> 	};
> };
>
> In the generated java classes the field "name" is initialized with "",

> but the "id" is not, even though it is also a string in java. The 
> other generator we used did also initialize them. This causes MARSHAL 
> excpetions because of null values.
>
> Can the generation be changed via config or is this intended behaviour

> or is it a bug?
>
> Matthias
> _______________________________________________
> jacorb-developer maillist  -  
> jacorb-developer at lists.spline.inf.fu-berlin.de
> https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-develope
> r
>

_______________________________________________
jacorb-developer maillist  -
jacorb-developer at lists.spline.inf.fu-berlin.de
https://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer