Eclipse Community Forums: ServerTools (WTP) » ModuleFactoryDelegate Question

Help

Home

Home » Language IDEs » ServerTools (WTP) » ModuleFactoryDelegate Question

Show: Today's Messages :: Show Polls :: Message Navigator

ModuleFactoryDelegate Question [message #181041]

Fri, 06 October 2006 16:23

Bruno Wassermann

Messages: 21
Registered: July 2009

Junior Member

Hi,

I have implemented a ModuleFactoryDelegate to discover BPEL modules.

I found that the code gets called (by the server framework) upon the first
instance of a user opening the 'Add/Remove...' wizard on a server and that
it presents the correct list of modules. However, when a new module gets
created afterwards in the same workbench session, the module factory
delegate code does not get called anymore and hence that particular module
is not available for addition to the server until the workbench session is
restarted. New module instances do not get discovered.

Am I missing something here? Is there something my code needs to do when
creating a new module instance so that the framework can call the module
factory delegate again? Or is this maybe a known issue (that I haven't been
able to find any info on?)

Regards,

-- Bruno

Report message to a moderator

Re: ModuleFactoryDelegate Question [message #181340 is a reply to message #181041]

Tue, 10 October 2006 16:06

Bruno Wassermann

Messages: 21
Registered: July 2009

Junior Member

As there was no reply to this question, let me rephrase it.

ProjectModuleFactoryDelegate has a handleGlobalProjectChange(), which takes
care of calling ModuleFactory.clearModuleCache() and thereby ensures that
the user is presented with an up-to-date list of modules in the Add and
Remove Projects... wizard. Changes to projects are detected in
ResourceManager, which invokes handleGlobalProjectChange(). This works fine
for project modules.

In my case though modules are simply BPEL files, not entire projects. My
question is how I can achieve the same behaviour that we get for projects
that have a delta. How can I detect and react to changes occurring to files
(not projects) in the same way as can currently be done for projects?

Any help would be very much appreciated!!!

-- Bruno

"Bruno Wassermann" <B.Wassermann@cs.ucl.ac.uk> wrote in message
news:eg5vu6$uge$1@utils.eclipse.org...
> Hi,
>
> I have implemented a ModuleFactoryDelegate to discover BPEL modules.
>
> I found that the code gets called (by the server framework) upon the first
> instance of a user opening the 'Add/Remove...' wizard on a server and that
> it presents the correct list of modules. However, when a new module gets
> created afterwards in the same workbench session, the module factory
> delegate code does not get called anymore and hence that particular module
> is not available for addition to the server until the workbench session is
> restarted. New module instances do not get discovered.
>
> Am I missing something here? Is there something my code needs to do when
> creating a new module instance so that the framework can call the module
> factory delegate again? Or is this maybe a known issue (that I haven't
> been able to find any info on?)
>
> Regards,
>
> -- Bruno
>

Report message to a moderator

Re: ModuleFactoryDelegate Question [message #182665 is a reply to message #181340]

Tue, 14 November 2006 10:52

Eclipse User

Originally posted by: contact.noelios.com

I have encountered the same issue as Bruno. The only solution I see now
is to implement my own
org.eclipse.core.resources.IResourceChangeListener in my modules factory.

IMO, the Server framework should support the update of modules not based
on projects.

Thanks,
Jerome

Bruno Wassermann a écrit :
> As there was no reply to this question, let me rephrase it.
>
> ProjectModuleFactoryDelegate has a handleGlobalProjectChange(), which takes
> care of calling ModuleFactory.clearModuleCache() and thereby ensures that
> the user is presented with an up-to-date list of modules in the Add and
> Remove Projects... wizard. Changes to projects are detected in
> ResourceManager, which invokes handleGlobalProjectChange(). This works fine
> for project modules.
>
> In my case though modules are simply BPEL files, not entire projects. My
> question is how I can achieve the same behaviour that we get for projects
> that have a delta. How can I detect and react to changes occurring to files
> (not projects) in the same way as can currently be done for projects?
>
> Any help would be very much appreciated!!!
>
> -- Bruno

--
Jerome Louvel
http://www.noelios.com

Report message to a moderator

Re: ModuleFactoryDelegate Question [message #182687 is a reply to message #182665]

Tue, 14 November 2006 14:46

Eclipse User

Originally posted by: contact.noelios.com

FYI, using a custom workspace listener that invalidates the modules
cache works. I've added a request to have such a mechanism built in the
framework: https://bugs.eclipse.org/bugs/show_bug.cgi?id=164474

--
Jerome Louvel
http://www.noelios.com

Report message to a moderator

Previous Topic:	Cannot create dynamic web project
Next Topic:	http post

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 01:28:07 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter