You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Han Hong Fang (JIRA)" <ji...@apache.org> on 2011/01/21 04:19:43 UTC
[jira] Created: (GERONIMODEVTOOLS-700) Automatically create target
platform with geronimo server bundles when server is created
Automatically create target platform with geronimo server bundles when server is created
----------------------------------------------------------------------------------------
Key: GERONIMODEVTOOLS-700
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700
Project: Geronimo-Devtools
Issue Type: Improvement
Components: eclipse-plugin
Affects Versions: 3.0_M1
Reporter: Han Hong Fang
Assignee: Han Hong Fang
Fix For: 3.0
Problem:
The javax.servlet.jsp.jstl.* are not listed in the exported packages list
Workaround:
javax.servlet.jsp.jstl.* is not a standard spec API in Java EE , its implementation varies with different app server, that's why eclipse doesn't include javax.servlet.jsp.jstl.* by default. So if you want to make it appear on exported package list, you should import jstl implement bundle into workspace, for example, import geronimo jstl-1.2_1.jar and geronimo-el_2.2.jar under $server_home/repository/org/apache/geronimo/bundles/jstl/1.2_1&$server_home/repository/org/apache/geronimo/specs/geronimo-el_2.2_spec, then you can select jstl from export package list.
Solution:
Your suggestion would work. But then it is hard to import each and every jar that you would depend on, to your workspace.
The recommended way is to set the workspace target platform to point to the target server jars location.
You can do that by going to Windows > Preferences > Plug-in Development > Target Platform and select Add and point to the location that contains your Geronimo jars (assuming these jars have a Manifest that exports the packages within the jar). and Click OK.
This would allow your application to compile against all of the jars, and can import any package that is exported by any of them. Another advantage is that would ensure your application would resolve these dependencies when you deploy to that server.
In RAD we do this step automatically when you target WAS 8 or WAS 7 server. In the OSGi free tools, users have to do this step manually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-700) Automatically create
target platform with geronimo server bundles when server is created
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993836#comment-12993836 ]
Jarek Gawor commented on GERONIMODEVTOOLS-700:
----------------------------------------------
In revision 1070031 I also exposed OSGi spec jars as part of the server runtime.
> Automatically create target platform with geronimo server bundles when server is created
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-700
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Affects Versions: 3.0_M1
> Reporter: Han Hong Fang
> Assignee: Han Hong Fang
> Fix For: 3.0-M2, 3.0
>
>
> [Problem] The javax.servlet.jsp.jstl.* are not listed in the exported packages list
> [Workaround] javax.servlet.jsp.jstl.* is not a standard spec API in Java EE , its implementation varies with different app server, that's why eclipse doesn't include javax.servlet.jsp.jstl.* by default. So if you want to make it appear on exported package list, you should import jstl implement bundle into workspace, for example, import geronimo jstl-1.2_1.jar and geronimo-el_2.2.jar under $server_home/repository/org/apache/geronimo/bundles/jstl/1.2_1&$server_home/repository/org/apache/geronimo/specs/geronimo-el_2.2_spec, then you can select jstl from export package list.
> [Solution] Your suggestion would work. But then it is hard to import each and every jar that you would depend on, to your workspace.
> The recommended way is to set the workspace target platform to point to the target server jars location.
> You can do that by going to Windows > Preferences > Plug-in Development > Target Platform and select Add and point to the location that contains your Geronimo jars (assuming these jars have a Manifest that exports the packages within the jar). and Click OK.
> This would allow your application to compile against all of the jars, and can import any package that is exported by any of them. Another advantage is that would ensure your application would resolve these dependencies when you deploy to that server.
> In RAD we do this step automatically when you target WAS 8 or WAS 7 server. In the OSGi free tools, users have to do this step manually.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-700) Automatically create
target platform with geronimo server bundles when server is created
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984581#action_12984581 ]
Jarek Gawor commented on GERONIMODEVTOOLS-700:
----------------------------------------------
javax.servlet.jsp.jstl.* packages are part of the Java EE 6. See http://download.oracle.com/javaee/6/api/overview-summary.html
> Automatically create target platform with geronimo server bundles when server is created
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-700
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Affects Versions: 3.0_M1
> Reporter: Han Hong Fang
> Assignee: Han Hong Fang
> Fix For: 3.0
>
>
> [Problem] The javax.servlet.jsp.jstl.* are not listed in the exported packages list
> [Workaround] javax.servlet.jsp.jstl.* is not a standard spec API in Java EE , its implementation varies with different app server, that's why eclipse doesn't include javax.servlet.jsp.jstl.* by default. So if you want to make it appear on exported package list, you should import jstl implement bundle into workspace, for example, import geronimo jstl-1.2_1.jar and geronimo-el_2.2.jar under $server_home/repository/org/apache/geronimo/bundles/jstl/1.2_1&$server_home/repository/org/apache/geronimo/specs/geronimo-el_2.2_spec, then you can select jstl from export package list.
> [Solution] Your suggestion would work. But then it is hard to import each and every jar that you would depend on, to your workspace.
> The recommended way is to set the workspace target platform to point to the target server jars location.
> You can do that by going to Windows > Preferences > Plug-in Development > Target Platform and select Add and point to the location that contains your Geronimo jars (assuming these jars have a Manifest that exports the packages within the jar). and Click OK.
> This would allow your application to compile against all of the jars, and can import any package that is exported by any of them. Another advantage is that would ensure your application would resolve these dependencies when you deploy to that server.
> In RAD we do this step automatically when you target WAS 8 or WAS 7 server. In the OSGi free tools, users have to do this step manually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-700) Automatically create target
platform with geronimo server bundles when server is created
Posted by "Han Hong Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Han Hong Fang resolved GERONIMODEVTOOLS-700.
--------------------------------------------
Resolution: Fixed
OSGi API is added in revision: 1064446
> Automatically create target platform with geronimo server bundles when server is created
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-700
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Affects Versions: 3.0_M1
> Reporter: Han Hong Fang
> Assignee: Han Hong Fang
> Fix For: 3.0-M2, 3.0
>
>
> [Problem] The javax.servlet.jsp.jstl.* are not listed in the exported packages list
> [Workaround] javax.servlet.jsp.jstl.* is not a standard spec API in Java EE , its implementation varies with different app server, that's why eclipse doesn't include javax.servlet.jsp.jstl.* by default. So if you want to make it appear on exported package list, you should import jstl implement bundle into workspace, for example, import geronimo jstl-1.2_1.jar and geronimo-el_2.2.jar under $server_home/repository/org/apache/geronimo/bundles/jstl/1.2_1&$server_home/repository/org/apache/geronimo/specs/geronimo-el_2.2_spec, then you can select jstl from export package list.
> [Solution] Your suggestion would work. But then it is hard to import each and every jar that you would depend on, to your workspace.
> The recommended way is to set the workspace target platform to point to the target server jars location.
> You can do that by going to Windows > Preferences > Plug-in Development > Target Platform and select Add and point to the location that contains your Geronimo jars (assuming these jars have a Manifest that exports the packages within the jar). and Click OK.
> This would allow your application to compile against all of the jars, and can import any package that is exported by any of them. Another advantage is that would ensure your application would resolve these dependencies when you deploy to that server.
> In RAD we do this step automatically when you target WAS 8 or WAS 7 server. In the OSGi free tools, users have to do this step manually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-700) Automatically create target
platform with geronimo server bundles when server is created
Posted by "Han Hong Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Han Hong Fang resolved GERONIMODEVTOOLS-700.
--------------------------------------------
Resolution: Fixed
Fix Version/s: 3.0-M2
A target platform will be added which points to geronimo bundles in following directories:
"repository/org/apache/geronimo/specs",
"repository/org/apache/geronimo/javamail/geronimo-javamail_1.4_mail",
"repository/org/apache/geronimo/bundles/jaxb-impl", "repository/org/apache/geronimo/bundles/jstl",
"repository/org/apache/myfaces/core/myfaces-bundle",
"repository/org/apache/geronimo/framework/geronimo-jdbc"
commit implementation at revision: 1063134.
> Automatically create target platform with geronimo server bundles when server is created
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-700
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Affects Versions: 3.0_M1
> Reporter: Han Hong Fang
> Assignee: Han Hong Fang
> Fix For: 3.0-M2, 3.0
>
>
> [Problem] The javax.servlet.jsp.jstl.* are not listed in the exported packages list
> [Workaround] javax.servlet.jsp.jstl.* is not a standard spec API in Java EE , its implementation varies with different app server, that's why eclipse doesn't include javax.servlet.jsp.jstl.* by default. So if you want to make it appear on exported package list, you should import jstl implement bundle into workspace, for example, import geronimo jstl-1.2_1.jar and geronimo-el_2.2.jar under $server_home/repository/org/apache/geronimo/bundles/jstl/1.2_1&$server_home/repository/org/apache/geronimo/specs/geronimo-el_2.2_spec, then you can select jstl from export package list.
> [Solution] Your suggestion would work. But then it is hard to import each and every jar that you would depend on, to your workspace.
> The recommended way is to set the workspace target platform to point to the target server jars location.
> You can do that by going to Windows > Preferences > Plug-in Development > Target Platform and select Add and point to the location that contains your Geronimo jars (assuming these jars have a Manifest that exports the packages within the jar). and Click OK.
> This would allow your application to compile against all of the jars, and can import any package that is exported by any of them. Another advantage is that would ensure your application would resolve these dependencies when you deploy to that server.
> In RAD we do this step automatically when you target WAS 8 or WAS 7 server. In the OSGi free tools, users have to do this step manually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMODEVTOOLS-700) Automatically create target
platform with geronimo server bundles when server is created
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor reopened GERONIMODEVTOOLS-700:
------------------------------------------
OSGi core & compendium jars are not included in the platform definition so projects using OSGi API cannot be compiled.
> Automatically create target platform with geronimo server bundles when server is created
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-700
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Affects Versions: 3.0_M1
> Reporter: Han Hong Fang
> Assignee: Han Hong Fang
> Fix For: 3.0-M2, 3.0
>
>
> [Problem] The javax.servlet.jsp.jstl.* are not listed in the exported packages list
> [Workaround] javax.servlet.jsp.jstl.* is not a standard spec API in Java EE , its implementation varies with different app server, that's why eclipse doesn't include javax.servlet.jsp.jstl.* by default. So if you want to make it appear on exported package list, you should import jstl implement bundle into workspace, for example, import geronimo jstl-1.2_1.jar and geronimo-el_2.2.jar under $server_home/repository/org/apache/geronimo/bundles/jstl/1.2_1&$server_home/repository/org/apache/geronimo/specs/geronimo-el_2.2_spec, then you can select jstl from export package list.
> [Solution] Your suggestion would work. But then it is hard to import each and every jar that you would depend on, to your workspace.
> The recommended way is to set the workspace target platform to point to the target server jars location.
> You can do that by going to Windows > Preferences > Plug-in Development > Target Platform and select Add and point to the location that contains your Geronimo jars (assuming these jars have a Manifest that exports the packages within the jar). and Click OK.
> This would allow your application to compile against all of the jars, and can import any package that is exported by any of them. Another advantage is that would ensure your application would resolve these dependencies when you deploy to that server.
> In RAD we do this step automatically when you target WAS 8 or WAS 7 server. In the OSGi free tools, users have to do this step manually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-700) Automatically create
target platform with geronimo server bundles when server is created
Posted by "viola.lu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986881#action_12986881 ]
viola.lu commented on GERONIMODEVTOOLS-700:
-------------------------------------------
Verification done, pls close it.
> Automatically create target platform with geronimo server bundles when server is created
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-700
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Affects Versions: 3.0_M1
> Reporter: Han Hong Fang
> Assignee: Han Hong Fang
> Fix For: 3.0-M2, 3.0
>
>
> [Problem] The javax.servlet.jsp.jstl.* are not listed in the exported packages list
> [Workaround] javax.servlet.jsp.jstl.* is not a standard spec API in Java EE , its implementation varies with different app server, that's why eclipse doesn't include javax.servlet.jsp.jstl.* by default. So if you want to make it appear on exported package list, you should import jstl implement bundle into workspace, for example, import geronimo jstl-1.2_1.jar and geronimo-el_2.2.jar under $server_home/repository/org/apache/geronimo/bundles/jstl/1.2_1&$server_home/repository/org/apache/geronimo/specs/geronimo-el_2.2_spec, then you can select jstl from export package list.
> [Solution] Your suggestion would work. But then it is hard to import each and every jar that you would depend on, to your workspace.
> The recommended way is to set the workspace target platform to point to the target server jars location.
> You can do that by going to Windows > Preferences > Plug-in Development > Target Platform and select Add and point to the location that contains your Geronimo jars (assuming these jars have a Manifest that exports the packages within the jar). and Click OK.
> This would allow your application to compile against all of the jars, and can import any package that is exported by any of them. Another advantage is that would ensure your application would resolve these dependencies when you deploy to that server.
> In RAD we do this step automatically when you target WAS 8 or WAS 7 server. In the OSGi free tools, users have to do this step manually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-700) Automatically create
target platform with geronimo server bundles when server is created
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989067#comment-12989067 ]
Jarek Gawor commented on GERONIMODEVTOOLS-700:
----------------------------------------------
Hmm.... I wonder if we should expose additional jars as part of the target platform. For example the pax logging api or xbean bundleutils, etc. Thoughts?
> Automatically create target platform with geronimo server bundles when server is created
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-700
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Affects Versions: 3.0_M1
> Reporter: Han Hong Fang
> Assignee: Han Hong Fang
> Fix For: 3.0-M2, 3.0
>
>
> [Problem] The javax.servlet.jsp.jstl.* are not listed in the exported packages list
> [Workaround] javax.servlet.jsp.jstl.* is not a standard spec API in Java EE , its implementation varies with different app server, that's why eclipse doesn't include javax.servlet.jsp.jstl.* by default. So if you want to make it appear on exported package list, you should import jstl implement bundle into workspace, for example, import geronimo jstl-1.2_1.jar and geronimo-el_2.2.jar under $server_home/repository/org/apache/geronimo/bundles/jstl/1.2_1&$server_home/repository/org/apache/geronimo/specs/geronimo-el_2.2_spec, then you can select jstl from export package list.
> [Solution] Your suggestion would work. But then it is hard to import each and every jar that you would depend on, to your workspace.
> The recommended way is to set the workspace target platform to point to the target server jars location.
> You can do that by going to Windows > Preferences > Plug-in Development > Target Platform and select Add and point to the location that contains your Geronimo jars (assuming these jars have a Manifest that exports the packages within the jar). and Click OK.
> This would allow your application to compile against all of the jars, and can import any package that is exported by any of them. Another advantage is that would ensure your application would resolve these dependencies when you deploy to that server.
> In RAD we do this step automatically when you target WAS 8 or WAS 7 server. In the OSGi free tools, users have to do this step manually.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMODEVTOOLS-700) Automatically create target
platform with geronimo server bundles when server is created
Posted by "Han Hong Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Han Hong Fang updated GERONIMODEVTOOLS-700:
-------------------------------------------
Description:
[Problem] The javax.servlet.jsp.jstl.* are not listed in the exported packages list
[Workaround] javax.servlet.jsp.jstl.* is not a standard spec API in Java EE , its implementation varies with different app server, that's why eclipse doesn't include javax.servlet.jsp.jstl.* by default. So if you want to make it appear on exported package list, you should import jstl implement bundle into workspace, for example, import geronimo jstl-1.2_1.jar and geronimo-el_2.2.jar under $server_home/repository/org/apache/geronimo/bundles/jstl/1.2_1&$server_home/repository/org/apache/geronimo/specs/geronimo-el_2.2_spec, then you can select jstl from export package list.
[Solution] Your suggestion would work. But then it is hard to import each and every jar that you would depend on, to your workspace.
The recommended way is to set the workspace target platform to point to the target server jars location.
You can do that by going to Windows > Preferences > Plug-in Development > Target Platform and select Add and point to the location that contains your Geronimo jars (assuming these jars have a Manifest that exports the packages within the jar). and Click OK.
This would allow your application to compile against all of the jars, and can import any package that is exported by any of them. Another advantage is that would ensure your application would resolve these dependencies when you deploy to that server.
In RAD we do this step automatically when you target WAS 8 or WAS 7 server. In the OSGi free tools, users have to do this step manually.
was:
Problem:
The javax.servlet.jsp.jstl.* are not listed in the exported packages list
Workaround:
javax.servlet.jsp.jstl.* is not a standard spec API in Java EE , its implementation varies with different app server, that's why eclipse doesn't include javax.servlet.jsp.jstl.* by default. So if you want to make it appear on exported package list, you should import jstl implement bundle into workspace, for example, import geronimo jstl-1.2_1.jar and geronimo-el_2.2.jar under $server_home/repository/org/apache/geronimo/bundles/jstl/1.2_1&$server_home/repository/org/apache/geronimo/specs/geronimo-el_2.2_spec, then you can select jstl from export package list.
Solution:
Your suggestion would work. But then it is hard to import each and every jar that you would depend on, to your workspace.
The recommended way is to set the workspace target platform to point to the target server jars location.
You can do that by going to Windows > Preferences > Plug-in Development > Target Platform and select Add and point to the location that contains your Geronimo jars (assuming these jars have a Manifest that exports the packages within the jar). and Click OK.
This would allow your application to compile against all of the jars, and can import any package that is exported by any of them. Another advantage is that would ensure your application would resolve these dependencies when you deploy to that server.
In RAD we do this step automatically when you target WAS 8 or WAS 7 server. In the OSGi free tools, users have to do this step manually.
> Automatically create target platform with geronimo server bundles when server is created
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-700
> URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-700
> Project: Geronimo-Devtools
> Issue Type: Improvement
> Components: eclipse-plugin
> Affects Versions: 3.0_M1
> Reporter: Han Hong Fang
> Assignee: Han Hong Fang
> Fix For: 3.0
>
>
> [Problem] The javax.servlet.jsp.jstl.* are not listed in the exported packages list
> [Workaround] javax.servlet.jsp.jstl.* is not a standard spec API in Java EE , its implementation varies with different app server, that's why eclipse doesn't include javax.servlet.jsp.jstl.* by default. So if you want to make it appear on exported package list, you should import jstl implement bundle into workspace, for example, import geronimo jstl-1.2_1.jar and geronimo-el_2.2.jar under $server_home/repository/org/apache/geronimo/bundles/jstl/1.2_1&$server_home/repository/org/apache/geronimo/specs/geronimo-el_2.2_spec, then you can select jstl from export package list.
> [Solution] Your suggestion would work. But then it is hard to import each and every jar that you would depend on, to your workspace.
> The recommended way is to set the workspace target platform to point to the target server jars location.
> You can do that by going to Windows > Preferences > Plug-in Development > Target Platform and select Add and point to the location that contains your Geronimo jars (assuming these jars have a Manifest that exports the packages within the jar). and Click OK.
> This would allow your application to compile against all of the jars, and can import any package that is exported by any of them. Another advantage is that would ensure your application would resolve these dependencies when you deploy to that server.
> In RAD we do this step automatically when you target WAS 8 or WAS 7 server. In the OSGi free tools, users have to do this step manually.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.