You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2011/01/21 06:49:47 UTC

[jira] Commented: (GERONIMODEVTOOLS-700) Automatically create target platform with geronimo server bundles when server is created

    [ 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.