[news.eclipse.tools.jdt] ClasspathContainerInitializer hell !

[ajenkins@xxxxxxxxxxxx (Adam Jenkins)]

Hi Guys,

I was wondering if someone could help me out with a classpath container 
initialization problem.  I've read through all the relevant help docos and 
search the lists dry and I'm still coming up short.  My plugin extension 
is:

	<!--The natures classpath-->
	<extension point="org.eclipse.jdt.core.classpathContainerInitializer">    
       
  		<classpathContainerInitializer                                        
 
     		id="XMLBEANS_LIB" 
class="net.adamjenkins.eclipseplugins.xmlbeans.XMLBeansClasspathContainerInitializer"/> 
                         
   </extension>

My initializer (which extends ClasspathContainerInitializer) just system 
outs a message and has a debug point on it (I removed the logic because I 
just want to get the binding correct, then I'll work on actually declaring 
the container)...in my AddNature action I have tried both the following 
calls (I got them from various list entries about classpath container 
initialization):

IClasspathContainer container = JavaCore.getClasspathContainer(new 
Path("net.adamjenkins.eclipseplugins.xmlbeans.XMLBEANS_LIB"), 
JavaCore.create(project));

IClasspathEntry entry = JavaCore.newContainerEntry(new 
Path("net.adamjenkins.eclipseplugins.xmlbeans.XMLBEANS_LIB"), false);

The first call gives me back a null object for 'container' and doesn't 
call the initializer...the second give me back a classpath entry, but 
doesn't call the initializer.

I have a break point and system outs in the initializer, but the break 
point never fires and the system out never prints, so one would deduce 
that my initializer is never being initialized.

net.adamjenkins.eclipseplugins.xmlbeans is my bundles symbolic name.

Can anyone see what I'm missing here, I've been working on this for days 
and it's diving me batty.

Cheers
Adam