Details
-
Type:
Task
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 3.3.0.M4
-
Component/s: cdi-extensions
-
Labels:
-
Release Notes Docs Status:Not Required
Description
Gliffy Diagrams
Issue Links
- relates to
-
JBIDE-9400
Tooling shows warning for Seam 3 Persistence created EntityManager injection
-
- Closed
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
just reopening for verification of this from JBIDE-9400:
"This is an issue again because the annotation @ExtensionManaged was moved from org.jboss.seam.solder.core.ExtensionManaged to org.jboss.solder.core.ExtensionManaged in Seam 3.1 Beta3"
this specific class rename isn't in your list of problems so just reopening this to see if it was missed or just not listed.
Show
Max Rydahl Andersen
added a comment - just reopening for verification of this from JBIDE-9400 :
"This is an issue again because the annotation @ExtensionManaged was moved from org.jboss.seam.solder.core.ExtensionManaged to org.jboss.solder.core.ExtensionManaged in Seam 3.1 Beta3"
this specific class rename isn't in your list of problems so just reopening this to see if it was missed or just not listed.
Max Rydahl Andersen
added a comment - just reopening for verification of this from JBIDE-9400 :
"This is an issue again because the annotation @ExtensionManaged was moved from org.jboss.seam.solder.core.ExtensionManaged to org.jboss.solder.core.ExtensionManaged in Seam 3.1 Beta3"
this specific class rename isn't in your list of problems so just reopening this to see if it was missed or just not listed. Yes, that should be done.
Show
Viacheslav Kabanovich
added a comment - Yes, that should be done.
Viacheslav Kabanovich
added a comment - Yes, that should be done. Alexey, please verify.
Show
Viacheslav Kabanovich
added a comment - Alexey, please verify.
Viacheslav Kabanovich
added a comment - Alexey, please verify. fixed
Show
Alexey Kazakov
added a comment - fixed
Alexey Kazakov
added a comment - fixed This issue is not required for JBDS release notes
Show
Isaac Rooskov
added a comment - This issue is not required for JBDS release notes
Isaac Rooskov
added a comment - This issue is not required for JBDS release notes 
Changes that concern our tools:
Package renaming
org.jboss.solder instead of org.jboss.seam.solder
org.jboss.solder.config instead of org.jboss.seam.config
org.jboss.solder.servlet instead of org.jboss.seam.servlet
Extension renaming caused by package renaming
org.jboss.solder.config.xml.bootstrap.XmlConfigExtension instead of org.jboss.seam.config.xml.bootstrap.XmlConfigExtension
org.jboss.solder.servlet.ServletExtension instead of org.jboss.seam.servlet.ServletExtension
org.jboss.solder.bean.generic.GenericBeanExtension instead of org.jboss.seam.solder.bean.generic.GenericBeanExtension
org.jboss.solder.bean.defaultbean.DefaultBeanExtension instead of org.jboss.seam.solder.bean.defaultbean.DefaultBeanExtension
org.jboss.solder.core.CoreExtension instead of org.jboss.seam.solder.core.CoreExtension
org.jboss.solder.unwraps.UnwrapsExtension instead of org.jboss.seam.solder.unwraps.UnwrapsExtension
org.jboss.solder.logging.TypedMessageLoggerExtension instead of org.jboss.seam.solder.logging.TypedMessageLoggerExtension
org.jboss.solder.serviceHandler.ServiceHandlerExtension instead of org.jboss.seam.solder.serviceHandler.ServiceHandlerExtension
Now we can choose between two options:
1) Just migrate extensions to new namespace. Stop supporting Seam 3.0.0. That is the only disadvantage - some customers might prefer to stay with Seam 3.0.0 (will they?).
2) Add new set of extensions for Seam 3.1.0. At this moment 95% of code can be shared in supporting both versions so that it may be almost as easy to do as option (1). But it is quite likely that Seam will continue to be developed so that sharing code between old frozen version and new developing version will make our code messy. So, a safe way is to clone our code for the old version, and add version suffix to its package names, and support both versions separately.
Guys, please vote.