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. -- BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargr...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From: Sergey Beryozkin <sberyoz...@gmail.com> To: osgi-dev@mail.osgi.org, Date: 2012/05/14 07:05 Subject: [osgi-dev] Blueprint schema blocks nested static class names Sent by: osgi-dev-boun...@mail.osgi.org 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 osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
