Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 1.1.1.Final
-
Fix Version/s: 1.1.3.Final, 1.1.3.SP1
-
Component/s: Java SE Support
-
Labels:None
-
Environment:SE 5 windows
-
Git Pull Request:
Description
using weld-se with SE 5 dont't work. We found out that classes uses methods that aren't declared in JDK 5 but in JDK 6.
E.G. weld-se (1.1.2.Final) org.jboss.weld.xml.BeansXmlHandler.getContainer() calls String.isEmpty().
Hence, the initialization of the container via 'WeldContainer weld = new Weld().initialize()' failed .
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
I'm on Mac, hence cannot easily test JDK5. 
Can you run the whole Weld testsuite or at least Weld SE – on JDK5?
And then provide a patch via github pull.
Show
Ales Justin
added a comment - I'm on Mac, hence cannot easily test JDK5.
Can you run the whole Weld testsuite or at least Weld SE – on JDK5?
And then provide a patch via github pull.
Ales Justin
added a comment - I'm on Mac, hence cannot easily test JDK5.
Can you run the whole Weld testsuite or at least Weld SE – on JDK5?
And then provide a patch via github pull. 
I'm sorry. This bug hides other bugs having similar cause.
E.G. org.jboss.weld.util.collections.ArraySetMultimap.putSingleElement(ArraySetMultimap.java:58) tried to access class java.util.AbstractMap$SimpleEntry.
This class has default scope in JDK 5, but public scope in JDK 6.
I cannot assure that this is the last issue of this kind.
Is there any chance to test weld-se in JDK 5 environment? Will JDK 5 be supported?