Issue Details (XML | Word | Printable)

Key: OSGI-128
Type: Bug Bug
Status: Resolved Resolved
Resolution: Duplicate
Priority: Minor Minor
Assignee: Costin Leau
Reporter: Bernd Kolb
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Spring OSGi

org.springframework.osgi.jstl.osgi should include standard.jar

Created: 18/May/07 04:48 AM   Updated: 04/Mar/08 03:42 AM
Component/s: WEB
Affects Version/s: 1.0 M2
Fix Version/s: 1.1 M1

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Related
 


 Description  « Hide
In the current version of org.springframework.osgi.jstl.osgi only jstl is exported, whereas org.apache.taglibs.standart.* is required. If you'd like to run an app which requires jstl. it reminds you that also the taglibs are needed. So you have to create a bundle containing the standard.jar. The problem with that is that by creating that bundle you are getting a cyclic dependency as standart taglibs are requiring jstl. So at the moment org.springframework.osgi.jstl.osgi is not usable.

 All   Comments   Work Log   Change History   FishEye   Builds      Sort Order: Ascending order - Click to sort in descending order
Costin Leau added a comment - 22/May/07 04:01 AM
interesting. The jars depend on each other. I wonder if there is anything in OSGi that can help with this one - maybe using optional imports (rather then Dynamic-Imports)?

Bernd Kolb added a comment - 22/May/07 10:52 AM
Optional will not solve the problem as there are still no cycles allowed AFAIK.

But when downloading the std taglib from apache you always also get jstl. So I think this is one lib in two jars.

Costin Leau added a comment - 26/Jun/07 09:53 AM
I've moved the priority on this one since jstl is not a jar we are currently using inside Spring/OSGi.

Costin Leau added a comment - 05/Nov/07 08:12 AM
Moved to 1.1 scope where web tier will be addressed.