Nick, I don't know if JNDI would be the right way to go either. You go a head and just implement the plugin as you were proceeding. There is a long road a head even if the JNDI route was taken.
We need to implement this stuff a few times. Make some mistakes and then go back to the drawing board. But you need to get the plugin out to give a major impact. You are self contained and are not publishing out an API that needs to be managed carefully. The value of the plugin is in the UI. Once a solid API stabilizes then we can retrofit it. You are in a great place to make merlin the de facto standard container by building out this plugin. I should leave you alone so you can succeed ;-). Alex > -----Original Message----- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Sent: Sunday, November 09, 2003 1:37 AM > To: Avalon Developers List > Subject: Re: Eclipse Plug-in > > On Sunday 09 November 2003 14:17, Alex Karasulu wrote: > > Another approach could be to use an existing and generic access > > interface like JNDI. > > In fact, now looking at JNDI beyond my very basic knowledge; > > Why shouldn't the Eclipse Repository Browser Plug-In just use JNDI > straight > off the shelf?? > > And if the answer is "Yeah", then the follow-up would be, there is > probably a > capable browser out there already, and my effort so far is wasted. > > Hmmm.... > > Cheers, > Niclas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
