On 10 January 2014 06:50, wrote:
> Thanks Dan,
>
> I saw the OIDMarshallaer code and used the other separated character than
> reserved characters for ISIS. Its working fine.
>
> But thing is that we have to restrict the PK fields not to have this
> separated character in its values. I hope JDO i
Issue with Compsite PK class with multiple
attributes.
Hi Varma,
There are, unfortunately, rather a lot of reserved characters that Isis has for
its encoding of OIDs, as you can see from the source [1]. (I find that regex
difficult to read, but the source code helps untangle the structure)
Hi Varma,
There are, unfortunately, rather a lot of reserved characters that Isis has
for its encoding of OIDs, as you can see from the source [1]. (I find that
regex difficult to read, but the source code helps untangle the structure).
In addition, as you've discovered, the '_' (underscore) cha
This one seems more related to the OID Marshaller than with JDO.
Perhaps Dan can give some light on it.
El 03/01/2014, a las 10:14, chittari.va...@wipro.com escribió:
>
> I am using ISIS 1.3.0 with JDO 3.0.1, Data Nucleus 3.2.4
>
>
> Using JDO Application Identity strategy, I have a compos
I am using ISIS 1.3.0 with JDO 3.0.1, Data Nucleus 3.2.4
Using JDO Application Identity strategy, I have a composite PK class with two
attributes(PK fields of type String).
As per the JDO specifications, PK class has overridden the following methods:
hascode, equals and toString.
And it has Co
I am using ISIS 1.3.0 with JDO 3.0.1, Data Nucleus 3.2.4
Using JDO Application Identity strategy, I have a composite PK class with two
attributes(PK fields of type String).
As per the JDO specifications, PK class has overridden the following methods:
hascode, equals and toString.
And it has C
