Eclipse Community Forums: JavaServer Faces » Programmatically add a existing component library to a JSF project

Search

Help

Login

Home » Eclipse Projects » JavaServer Faces » Programmatically add a existing component library to a JSF project

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

Switch to threaded view of this topic

Create a new topic

Submit Reply

Programmatically add a existing component library to a JSF project [message #472958]

Mon, 18 September 2006 17:54

William is currently offline

Friend

Messages: 23
Registered: July 2009

Junior Member

I want to develope a plugin which can automatically add a existing
component library to jsf project. The component library comes with the
plugin which defines from the extension point
org.eclipse.jst.jsf.core.jsfLibraries.

If anybody knows how to add the library to the project programmatically?

Thanks

William

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #472959 is a reply to message #472958]

Mon, 18 September 2006 23:12

Justin Chen is currently offline

Friend

Messages: 39
Registered: July 2009

Member

William,

It sounds like that you have implemented and deployed a jsfLibraries
extension. Hence, your component library is available during JSF facet
installation.

I am not sure what you mean by adding the component library to a project
pragmatically. Would you mind describing the use case more in details?

Thanks,
Justin

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #472960 is a reply to message #472959]

Tue, 19 September 2006 06:21

william is currently offline

Friend

Messages: 15
Registered: July 2009

Junior Member

Thanks Justin,

What I want is to either make the plugin provided component library listed
in selected library list in new project wizard page so that user doesn't
have to click > to add the component library
or set the component library selected from JSFLibrary or
JSFLibraryRegistry etc before jst.jsf install action happens.

By either way, once user selects my project facet, the component library
should be selected by default through my plugin.

I wonder if this is clear?

Thanks

William

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #472961 is a reply to message #472959]

Tue, 19 September 2006 06:26

william is currently offline

Friend

Messages: 15
Registered: July 2009

Junior Member

Thanks Justin,

What I want is to either make the plugin provided component library listed
in selected library list in new project wizard page so that user doesn't
have to click > to add the component library
or set the component library selected from JSFLibrary or
JSFLibraryRegistry etc before jst.jsf install action happens.

By either way, once user selects my project facet, the component library
should be selected by default through my plugin.

I wonder if this is clear?

Thanks

William

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #472963 is a reply to message #472961]

Tue, 19 September 2006 17:56

Justin Chen is currently offline

Friend

Messages: 39
Registered: July 2009

Member

William,

The fix for bug 146052 may not be the exact answer to your request.
But, it may covers most of the cases once your component library selection
become sticky. I.e., your component library has to be picked once in a
new workspace.

We have the concept of default for implementation library, but not for
component library. Hence, w/o anything being selected, a default
implementation is picked. But, no component library is selected by
default.

I think you are looking for the concept of default component libraries.
We will evaluate the need for a default component library.

Thanks,
Justin

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #472964 is a reply to message #472963]

Tue, 19 September 2006 19:06

William is currently offline

Friend

Messages: 23
Registered: July 2009

Junior Member

Thanks Justin,

The fix for 146052 is not what i need. What I want is the way of
selecting the my custom component library supplied by my plugin by
default if my facet is selected.

Thanks anyway!

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #475027 is a reply to message #472964]

Thu, 16 August 2007 03:41

Samrat Dhillon is currently offline

Friend

Messages: 19
Registered: July 2009

Junior Member

William wrote:
> Thanks Justin,
>
> The fix for 146052 is not what i need. What I want is the way of
> selecting the my custom component library supplied by my plugin by
> default if my facet is selected.
>
> Thanks anyway!

William,

Were you able to find a workaround to do this? I am working on a similar
kind of plugin.

Regards
Samrat Dhillon

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #475039 is a reply to message #475027]

Mon, 20 August 2007 23:41

Cameron Bateman is currently offline

Cameron Bateman

Friend

Messages: 481
Registered: July 2009

Senior Member

Hi Samrat,

Can you clarify? Is it that you want your component library to appear
automatically in the list of component libraries provided in the "JSF
Capabilities" page of the New Dynamic Project Wizard?

--Cam

Samrat Dhillon wrote:

> William wrote:
>> Thanks Justin,
>>
>> The fix for 146052 is not what i need. What I want is the way of
>> selecting the my custom component library supplied by my plugin by
>> default if my facet is selected.
>>
>> Thanks anyway!

> William,

> Were you able to find a workaround to do this? I am working on a similar
> kind of plugin.

> Regards
> Samrat Dhillon

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #475040 is a reply to message #475039]

Wed, 22 August 2007 07:52

Samrat Dhillon is currently offline

Friend

Messages: 19
Registered: July 2009

Junior Member

Hi Cameron,

I want to specify the location of the JSF implementation libraries
programmatically, rather than through the preference page.

I am packaging myfaces libraries inside my plugin. This plugin extends
webproject wizard. I want to specify the location programmatically so
that user does not have to configure with the change of workspace.

Thanks
Samrat

Cameron Bateman wrote:
> Hi Samrat,
>
> Can you clarify? Is it that you want your component library to appear
> automatically in the list of component libraries provided in the "JSF
> Capabilities" page of the New Dynamic Project Wizard?
>
>
> --Cam
>
> Samrat Dhillon wrote:
>
>> William wrote:
>>> Thanks Justin,
>>>
>>> The fix for 146052 is not what i need. What I want is the way of
>>> selecting the my custom component library supplied by my plugin by
>>> default if my facet is selected.
>>>
>>> Thanks anyway!
>
>> William,
>
>> Were you able to find a workaround to do this? I am working on a
>> similar kind of plugin.
>
>> Regards
>> Samrat Dhillon
>
>

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #475041 is a reply to message #475040]

Wed, 22 August 2007 16:10

Cameron Bateman is currently offline

Cameron Bateman

Friend

Messages: 481
Registered: July 2009

Senior Member

The plugin-provided library extension may be of some help
(org.eclipse.jst.jsf.core.pluginProvidedJsfLibraries). This allows you to
provide a collection name and a
PluginProvidedJSFLibraryArchiveFilesDelegate implementation that points to
the jars. The isImplementation flag needs to be set for it to appear in
the drop down box of runtimes; otherwise it will appear in the shuttle
list of component libs.

Have a look and let us know if that gets you any closer to your goal.

--Cam

Samrat Dhillon wrote:

> Hi Cameron,

> I want to specify the location of the JSF implementation libraries
> programmatically, rather than through the preference page.

> I am packaging myfaces libraries inside my plugin. This plugin extends
> webproject wizard. I want to specify the location programmatically so
> that user does not have to configure with the change of workspace.

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #475066 is a reply to message #475041]

Thu, 23 August 2007 10:01

Samrat Dhillon is currently offline

Friend

Messages: 19
Registered: July 2009

Junior Member

Hi Cameron,

Thanks a lot. I have implemented the plugin.

Regards
Samrat Dhillon

Cameron Bateman wrote:
> The plugin-provided library extension may be of some help
> (org.eclipse.jst.jsf.core.pluginProvidedJsfLibraries). This allows you
> to provide a collection name and a
> PluginProvidedJSFLibraryArchiveFilesDelegate implementation that points
> to the jars. The isImplementation flag needs to be set for it to appear
> in the drop down box of runtimes; otherwise it will appear in the
> shuttle list of component libs.
>
> Have a look and let us know if that gets you any closer to your goal.
>
>
> --Cam
>
> Samrat Dhillon wrote:
>
>> Hi Cameron,
>
>> I want to specify the location of the JSF implementation libraries
>> programmatically, rather than through the preference page.
>
>> I am packaging myfaces libraries inside my plugin. This plugin extends
>> webproject wizard. I want to specify the location programmatically so
>> that user does not have to configure with the change of workspace.
>

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #476119 is a reply to message #475066]

Thu, 30 April 2009 12:02

shilpa is currently offline

Friend

Messages: 24
Registered: July 2009

Junior Member

Cameron,

I have implemented extension point
org.eclipse.jst.jsf.core.pluginProvidedJsfLibraries to add a few libraries
when a new project is created using my library name.
It works fine when I launch an eclipse using my Plugin.xml for testing.
but when I actually install the plugin, it throws an error and the jars
doesn't get added. I feel the problem is in the way I am exporting or
installing the plugin.

The error message is -
Failed while installing JavaServer Faces 1.1.
assertion failed: Path for IClasspathEntry must be absolute:
file:C:/Program
Files/IBM/SDPShared/plugins/plugins/com.hsbc.glti.jsf.taglib metadata.jhx_1.0.0.jar!/lib/commons-beanutils-1.7.0.jar

Can you suggest some documentation which provides a clear picture of
exporting and packaging the plugin? or if u know any solution to this
problem

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #476127 is a reply to message #476119]

Fri, 01 May 2009 01:52

Cameron Bateman is currently offline

Cameron Bateman

Friend

Messages: 481
Registered: July 2009

Senior Member

Off the top of my head, this looks like the "jar inside jar" problem that
some Eclipse file location APIs have. What happens if you export the
plugin in exploded form rather than jar form?

I should also note that in Galileo, the jsf libraries provider mechanism
is deprecated. Going forward, JSF runtime and component libraries need to
be provided through the new facet library provider mechanism.

Thanks,

Cameron

shilpa wrote:

> Cameron,

> I have implemented extension point
> org.eclipse.jst.jsf.core.pluginProvidedJsfLibraries to add a few libraries
> when a new project is created using my library name.
> It works fine when I launch an eclipse using my Plugin.xml for testing.
> but when I actually install the plugin, it throws an error and the jars
> doesn't get added. I feel the problem is in the way I am exporting or
> installing the plugin.

> The error message is -
> Failed while installing JavaServer Faces 1.1.
> assertion failed: Path for IClasspathEntry must be absolute:
> file:C:/Program
>
Files/IBM/SDPShared/plugins/plugins/com.hsbc.glti.jsf.taglib metadata.jhx_1.0.0.jar!/lib/commons-beanutils-1.7.0.jar

> Can you suggest some documentation which provides a clear picture of
> exporting and packaging the plugin? or if u know any solution to this
> problem

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #607617 is a reply to message #472958]

Mon, 18 September 2006 23:12

Justin Chen is currently offline

Friend

Messages: 39
Registered: July 2009

Member

William,

It sounds like that you have implemented and deployed a jsfLibraries
extension. Hence, your component library is available during JSF facet
installation.

I am not sure what you mean by adding the component library to a project
pragmatically. Would you mind describing the use case more in details?

Thanks,
Justin

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #607618 is a reply to message #472959]

Tue, 19 September 2006 06:21

william is currently offline

Friend

Messages: 15
Registered: July 2009

Junior Member

Thanks Justin,

What I want is to either make the plugin provided component library listed
in selected library list in new project wizard page so that user doesn't
have to click > to add the component library
or set the component library selected from JSFLibrary or
JSFLibraryRegistry etc before jst.jsf install action happens.

By either way, once user selects my project facet, the component library
should be selected by default through my plugin.

I wonder if this is clear?

Thanks

William

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #607619 is a reply to message #472959]

Tue, 19 September 2006 06:26

william is currently offline

Friend

Messages: 15
Registered: July 2009

Junior Member

Thanks Justin,

What I want is to either make the plugin provided component library listed
in selected library list in new project wizard page so that user doesn't
have to click > to add the component library
or set the component library selected from JSFLibrary or
JSFLibraryRegistry etc before jst.jsf install action happens.

By either way, once user selects my project facet, the component library
should be selected by default through my plugin.

I wonder if this is clear?

Thanks

William

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #607623 is a reply to message #472961]

Tue, 19 September 2006 17:56

Justin Chen is currently offline

Friend

Messages: 39
Registered: July 2009

Member

William,

The fix for bug 146052 may not be the exact answer to your request.
But, it may covers most of the cases once your component library selection
become sticky. I.e., your component library has to be picked once in a
new workspace.

We have the concept of default for implementation library, but not for
component library. Hence, w/o anything being selected, a default
implementation is picked. But, no component library is selected by
default.

I think you are looking for the concept of default component libraries.
We will evaluate the need for a default component library.

Thanks,
Justin

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #607626 is a reply to message #472963]

Tue, 19 September 2006 19:06

William is currently offline

Friend

Messages: 23
Registered: July 2009

Junior Member

Thanks Justin,

The fix for 146052 is not what i need. What I want is the way of
selecting the my custom component library supplied by my plugin by
default if my facet is selected.

Thanks anyway!

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #614180 is a reply to message #472964]

Thu, 16 August 2007 03:41

Samrat Dhillon is currently offline

Friend

Messages: 19
Registered: July 2009

Junior Member

William wrote:
> Thanks Justin,
>
> The fix for 146052 is not what i need. What I want is the way of
> selecting the my custom component library supplied by my plugin by
> default if my facet is selected.
>
> Thanks anyway!

William,

Were you able to find a workaround to do this? I am working on a similar
kind of plugin.

Regards
Samrat Dhillon

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #614218 is a reply to message #475027]

Mon, 20 August 2007 23:41

Cameron Bateman is currently offline

Cameron Bateman

Friend

Messages: 481
Registered: July 2009

Senior Member

Hi Samrat,

Can you clarify? Is it that you want your component library to appear
automatically in the list of component libraries provided in the "JSF
Capabilities" page of the New Dynamic Project Wizard?

--Cam

Samrat Dhillon wrote:

> William wrote:
>> Thanks Justin,
>>
>> The fix for 146052 is not what i need. What I want is the way of
>> selecting the my custom component library supplied by my plugin by
>> default if my facet is selected.
>>
>> Thanks anyway!

> William,

> Were you able to find a workaround to do this? I am working on a similar
> kind of plugin.

> Regards
> Samrat Dhillon

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #614222 is a reply to message #475039]

Wed, 22 August 2007 07:52

Samrat Dhillon is currently offline

Friend

Messages: 19
Registered: July 2009

Junior Member

Hi Cameron,

I want to specify the location of the JSF implementation libraries
programmatically, rather than through the preference page.

I am packaging myfaces libraries inside my plugin. This plugin extends
webproject wizard. I want to specify the location programmatically so
that user does not have to configure with the change of workspace.

Thanks
Samrat

Cameron Bateman wrote:
> Hi Samrat,
>
> Can you clarify? Is it that you want your component library to appear
> automatically in the list of component libraries provided in the "JSF
> Capabilities" page of the New Dynamic Project Wizard?
>
>
> --Cam
>
> Samrat Dhillon wrote:
>
>> William wrote:
>>> Thanks Justin,
>>>
>>> The fix for 146052 is not what i need. What I want is the way of
>>> selecting the my custom component library supplied by my plugin by
>>> default if my facet is selected.
>>>
>>> Thanks anyway!
>
>> William,
>
>> Were you able to find a workaround to do this? I am working on a
>> similar kind of plugin.
>
>> Regards
>> Samrat Dhillon
>
>

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #614226 is a reply to message #475040]

Wed, 22 August 2007 16:10

Cameron Bateman is currently offline

Cameron Bateman

Friend

Messages: 481
Registered: July 2009

Senior Member

The plugin-provided library extension may be of some help
(org.eclipse.jst.jsf.core.pluginProvidedJsfLibraries). This allows you to
provide a collection name and a
PluginProvidedJSFLibraryArchiveFilesDelegate implementation that points to
the jars. The isImplementation flag needs to be set for it to appear in
the drop down box of runtimes; otherwise it will appear in the shuttle
list of component libs.

Have a look and let us know if that gets you any closer to your goal.

--Cam

Samrat Dhillon wrote:

> Hi Cameron,

> I want to specify the location of the JSF implementation libraries
> programmatically, rather than through the preference page.

> I am packaging myfaces libraries inside my plugin. This plugin extends
> webproject wizard. I want to specify the location programmatically so
> that user does not have to configure with the change of workspace.

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #614402 is a reply to message #475041]

Thu, 23 August 2007 10:01

Samrat Dhillon is currently offline

Friend

Messages: 19
Registered: July 2009

Junior Member

Hi Cameron,

Thanks a lot. I have implemented the plugin.

Regards
Samrat Dhillon

Cameron Bateman wrote:
> The plugin-provided library extension may be of some help
> (org.eclipse.jst.jsf.core.pluginProvidedJsfLibraries). This allows you
> to provide a collection name and a
> PluginProvidedJSFLibraryArchiveFilesDelegate implementation that points
> to the jars. The isImplementation flag needs to be set for it to appear
> in the drop down box of runtimes; otherwise it will appear in the
> shuttle list of component libs.
>
> Have a look and let us know if that gets you any closer to your goal.
>
>
> --Cam
>
> Samrat Dhillon wrote:
>
>> Hi Cameron,
>
>> I want to specify the location of the JSF implementation libraries
>> programmatically, rather than through the preference page.
>
>> I am packaging myfaces libraries inside my plugin. This plugin extends
>> webproject wizard. I want to specify the location programmatically so
>> that user does not have to configure with the change of workspace.
>

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #618747 is a reply to message #475066]

Thu, 30 April 2009 12:02

shilpa is currently offline

Friend

Messages: 24
Registered: July 2009

Junior Member

Cameron,

I have implemented extension point
org.eclipse.jst.jsf.core.pluginProvidedJsfLibraries to add a few libraries
when a new project is created using my library name.
It works fine when I launch an eclipse using my Plugin.xml for testing.
but when I actually install the plugin, it throws an error and the jars
doesn't get added. I feel the problem is in the way I am exporting or
installing the plugin.

The error message is -
Failed while installing JavaServer Faces 1.1.
assertion failed: Path for IClasspathEntry must be absolute:
file:C:/Program
Files/IBM/SDPShared/plugins/plugins/com.hsbc.glti.jsf.taglib metadata.jhx_1.0.0.jar!/lib/commons-beanutils-1.7.0.jar

Can you suggest some documentation which provides a clear picture of
exporting and packaging the plugin? or if u know any solution to this
problem

Report message to a moderator

Re: Programmatically add a existing component library to a JSF project [message #618755 is a reply to message #476119]

Fri, 01 May 2009 01:52

Cameron Bateman is currently offline

Cameron Bateman

Friend

Messages: 481
Registered: July 2009

Senior Member

Off the top of my head, this looks like the "jar inside jar" problem that
some Eclipse file location APIs have. What happens if you export the
plugin in exploded form rather than jar form?

I should also note that in Galileo, the jsf libraries provider mechanism
is deprecated. Going forward, JSF runtime and component libraries need to
be provided through the new facet library provider mechanism.

Thanks,

Cameron

shilpa wrote:

> Cameron,

> I have implemented extension point
> org.eclipse.jst.jsf.core.pluginProvidedJsfLibraries to add a few libraries
> when a new project is created using my library name.
> It works fine when I launch an eclipse using my Plugin.xml for testing.
> but when I actually install the plugin, it throws an error and the jars
> doesn't get added. I feel the problem is in the way I am exporting or
> installing the plugin.

> The error message is -
> Failed while installing JavaServer Faces 1.1.
> assertion failed: Path for IClasspathEntry must be absolute:
> file:C:/Program
>
Files/IBM/SDPShared/plugins/plugins/com.hsbc.glti.jsf.taglib metadata.jhx_1.0.0.jar!/lib/commons-beanutils-1.7.0.jar

> Can you suggest some documentation which provides a clear picture of
> exporting and packaging the plugin? or if u know any solution to this
> problem

Report message to a moderator

Switch to threaded view of this topic

Create a new topic

Submit Reply

Previous Topic:	Help required on org.eclipse.osgi
Next Topic:	Announce: Non-breaking API change in IElementEdit due to bug 267962

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Apr 20 16:17:59 GMT 2024

Powered by FUDForum. Page generated in 0.06116 seconds

.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top