On 14/05/12 14:50, BJ Hargrave wrote:
I don't think you need a naming convention. For a.b.C.D.E, you try to load a.b.C.D.E, then a.b.C.D$E, then a.b.C$D$E and so on until you find a class or nothing. Basically do whatever javac or javap do to locate the class.
Sounds good, thanks for the advice Sergey
-- *BJ Hargrave* Senior Technical Staff Member, IBM OSGi Fellow and CTO of the _OSGi Alliance_ <http://www.osgi.org/>_ [email protected]_ <mailto:[email protected]> office: +1 386 848 1781 mobile: +1 386 848 3788 From: Sergey Beryozkin <[email protected]> To: [email protected], Date: 2012/05/14 08:21 Subject: Re: [osgi-dev] Blueprint schema blocks nested static class names Sent by: [email protected] ------------------------------------------------------------------------ Hi, On 14/05/12 12:17, BJ Hargrave wrote: > Why don't you just say "a.b.MyClass.MyNestedClass" instead of > "a.b.MyClass$MyNestedClass" in the XML? The former is how you would > refer to it in java source code and also how javap expects it to be > referred to on the command line. > > Then you don't need to change the specification (which will take time). > You can just modify the implementation to support inner class names in > the XML. > That sounds reasonable, but I guess it means the implementation will need to resort to relying on the convention that if the last two tokens start from an upper-case character then it must be a nested class name, etc, example, is it the case of the nested static class or simply the package name not following the regular Java naming convention: a.b.C.D.E ? where we can have an 'a.b.C.D' package name. Cheers, Sergey > -- > > *BJ Hargrave* > Senior Technical Staff Member, IBM > OSGi Fellow and CTO of the _OSGi Alliance_ <http://www.osgi.org/>_ > [email protected]_ <mailto:[email protected]> > > office: +1 386 848 1781 > mobile: +1 386 848 3788 > > > > > > > > From: Sergey Beryozkin <[email protected]> > To: [email protected], > Date: 2012/05/14 07:05 > Subject: [osgi-dev] Blueprint schema blocks nested static class names > Sent by: [email protected] > > ------------------------------------------------------------------------ > > > > Hello All, > > I've recently reported an issue at the Apache Aries dev list [1] to do > with the > Blueprint schema blocking the nested static class names and I'm moving > the discussion to this list as recommended by Jeremy Hughes. > > The fix proposed at [1] is to relax the schema for Java (or I guess > other language VMs) to validate the class names as opposed to > restricting the names at the higher level in Blueprint schema. > > We came across the issue while working on migrating the application > including many code-generated nested classes to Blueprint. > > Any objections to me opening a bug at [2] ? > > Thanks, Sergey > > [1] > http://mail-archives.apache.org/mod_mbox/aries-dev/201204.mbox/ajax/%3C4F7A03DE.4060603%40gmail.com%3E > [2] https://www.osgi.org/bugzilla/ > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > > > _______________________________________________ > OSGi Developer Mail List > [email protected] > https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
-- Sergey Beryozkin Talend Community Coders http://coders.talend.com/ Blog: http://sberyozkin.blogspot.com _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
