To make it work you have to ensure, that <pe:importEnum> can access the enum class it references in the type attribute. Unfortunately ivy currently only supports the access to converters and managed beans from ivy projects. So the pe:importEnum will raise a classNotFoundException if your enum is defined in an ivyProject. To work around this problem you could copy the compiled enum class into the global webapp classes container: designer/webapps/ivy/WEB-INF/classes or if you already have it in a JAR put it into designer/webapps/ivy/WEB-INF/lib. A big drawback of this solution is, that you no longer can have different version of this classes in multiple PMVs. The class is global available for any PMV in your application. And of course you have to deploy it manually on the server side. ---------- To support java sources which will be compiled directly into this global webapp classes you could do the following: 1. Java Perspective -> Create a new Source Folder (e.g. src_webContent) 2. Add the enum you wan't to access from the pe:importEnum to this source folder 3. Add a virtual folder which references WEB-INF/classes into you project: Context Menu of Project -> New -> Folder -> Advanced -> Link to alternate Location -> Variables -> ECLIPSE_HOME -> Extend -> webapps/ivy/WEB-INF/classes -> OK ![alt text][1] 4. Configurate the src_webContent folder to use a specific output folder: Java Perspective -> Context Menu of Project -> Properties -> Java Build Path -> Source -> Check: Allow output folder for source folders -> Edit the output of src_webContent -> choose the virtual folder as target (which was create in step 3) ![alt text][2] 5. Done. Sources within this special src_webContent folder should be globally accessible within JSF views. This adventurous project configuration can be inspected within this demo project: [demoPrimeImportEnum-globalClasses_51.iar][3] [1]: http://answers.axonivy.com/upfiles/addVirtualFolderToWcClasses.PNGhttps://answers.axonivy.com/upfiles/addVirtualFolderToWcClasses.PNG [2]: http://answers.axonivy.com/upfiles/virtualFolderAsOutputLocation.PNGhttps://answers.axonivy.com/upfiles/virtualFolderAsOutputLocation.PNG [3]: http://developer.axonivy.com/q-and-a-attachments/demoPrimeImportEnum-globalClasses_51.iar/upfiles/demoPrimeImportEnum-globalClasses_51.iar

To make it work you have to ensure, that <pe:importEnum> can access the enum class it references in the type attribute. Unfortunately ivy currently only supports the access to converters and managed beans from ivy projects. So the pe:importEnum will raise a classNotFoundException if your enum is defined in an ivyProject. To work around this problem you could copy the compiled enum class into the global webapp classes container: designer/webapps/ivy/WEB-INF/classes or if you already have it in a JAR put it into designer/webapps/ivy/WEB-INF/lib. A big drawback of this solution is, that you no longer can have different version of this classes in multiple PMVs. The class is global available for any PMV in your application. And of course you have to deploy it manually on the server side. ---------- To support java sources which will be compiled directly into this global webapp classes you could do the following: 1. Java Perspective -> Create a new Source Folder (e.g. src_webContent) 2. Add the enum you wan't to access from the pe:importEnum to this source folder 3. Add a virtual folder which references WEB-INF/classes into you project: Context Menu of Project -> New -> Folder -> Advanced -> Link to alternate Location -> Variables -> ECLIPSE_HOME -> Extend -> webapps/ivy/WEB-INF/classes -> OK ![alt text][1] 4. Configurate the src_webContent folder to use a specific output folder: Java Perspective -> Context Menu of Project -> Properties -> Java Build Path -> Source -> Check: Allow output folder for source folders -> Edit the output of src_webContent -> choose the virtual folder as target (which was create in step 3) ![alt text][2] 5. Done. Sources within this special src_webContent folder should be globally accessible within JSF views. This adventurous project configuration can be inspected within this demo project: [demoPrimeImportEnum-globalClasses_51.iar][3] [1]: http://answers.axonivy.com/upfiles/addVirtualFolderToWcClasses.PNG [2]: http://answers.axonivy.com/upfiles/virtualFolderAsOutputLocation.PNG [3]: http://ivyteam.ch/downloads/q-and-a-attachments/demoPrimeImportEnum-globalClasses_51.iarhttp://developer.axonivy.com/q-and-a-attachments/demoPrimeImportEnum-globalClasses_51.iar

To make it work you have to ensure, that <pe:importEnum> can access the enum class it references in the type attribute. Unfortunately ivy currently only supports the access to converters and managed beans from ivy projects. So the pe:importEnum will raise a classNotFoundException if your enum is defined in an ivyProject. To work around this problem you could copy the compiled enum class into the global webapp classes container: designer/webapps/ivy/WEB-INF/classes or if you already have it in a JAR put it into designer/webapps/ivy/WEB-INF/classes.designer/webapps/ivy/WEB-INF/lib. A big drawback of this solution is, that you no longer can have different version of this classes in multiple PMVs. The class is global available for any PMV in your application. And of course you have to deploy it manually on the server side. ---------- To support java sources which will be compiled directly into this global webapp classes you could do the following: 1. Java Perspective -> Create a new Source Folder (e.g. src_webContent) 2. Add the enum you wan't to access from the pe:importEnum to this source folder 3. Add a virtual folder which references WEB-INF/classes into you project: Context Menu of Project -> New -> Folder -> Advanced -> Link to alternate Location -> Variables -> ECLIPSE_HOME -> Extend -> webapps/ivy/WEB-INF/classes -> OK ![alt text][1] 4. Configurate the src_webContent folder to use a specific output folder: Java Perspective -> Context Menu of Project -> Properties -> Java Build Path -> Source -> Check: Allow output folder for source folders -> Edit the output of src_webContent -> choose the virtual folder as target (which was create in step 3) ![alt text][2] 5. Done. Sources within this special src_webContent folder should be globally accessible within JSF views. This adventurous project configuration can be inspected within this demo project: [demoPrimeImportEnum-globalClasses_51.iar][3] [1]: http://answers.axonivy.com/upfiles/addVirtualFolderToWcClasses.PNG [2]: http://answers.axonivy.com/upfiles/virtualFolderAsOutputLocation.PNG [3]: http://ivyteam.ch/downloads/q-and-a-attachments/demoPrimeImportEnum-globalClasses_51.iar

Yes it works just as shown on the primefaces showcase. The special thing about it To make it work you have to ensure, that <pe:importEnum> can access the enum class it references in the type attribute. Unfortunately ivy currently only supports the access to converters and managed beans from ivy projects. So the pe:importEnum will raise a classNotFoundException if your enum is defined in an ivyProject. To work around this problem you could copy the compiled enum class into the global webapp classes container: designer/webapps/ivy/WEB-INF/classes or if you already have it in a JAR put it into designer/webapps/ivy/WEB-INF/classes. A big drawback of this solution is, that there you no longer can have different version of this classes in multiple PMVs. The class is not need to set the namespace of the Enum anywhere. For an ivy Demo see the project i've just created: [demoPrimeImportEnum_51.iar][1] global available for any PMV in your application. And of course you have to deploy it manually on the server side. ---------- To support java sources which will be compiled directly into this global webapp classes you could do the following: 1. Java Perspective -> Create a new Source Folder (e.g. src_webContent) 2. Add the enum you wan't to access from the pe:importEnum to this source folder 3. Add a virtual folder which references WEB-INF/classes into you project: Context Menu of Project -> New -> Folder -> Advanced -> Link to alternate Location -> Variables -> ECLIPSE_HOME -> Extend -> webapps/ivy/WEB-INF/classes -> OK ![alt text][1] 4. Configurate the src_webContent folder to use a specific output folder: Java Perspective -> Context Menu of Project -> Properties -> Java Build Path -> Source -> Check: Allow output folder for source folders -> Edit the output of src_webContent -> choose the virtual folder as target (which was create in step 3) ![alt text][2] 5. Done. Sources within this special src_webContent folder should be globally accessible within JSF views. This adventurous project configuration can be inspected within this demo project: [demoPrimeImportEnum-globalClasses_51.iar][3] [1]: http://www.ivyteam.ch/downloads/q-and-a-attachments/demoPrimeImportEnum_51.iarhttp://answers.axonivy.com/upfiles/addVirtualFolderToWcClasses.PNG [2]: http://answers.axonivy.com/upfiles/demoPrimeImportEnum.PNGhttp://answers.axonivy.com/upfiles/virtualFolderAsOutputLocation.PNG [3]: http://ivyteam.ch/downloads/q-and-a-attachments/demoPrimeImportEnum-globalClasses_51.iar

Yes it works just as shown on the primefaces showcase. The special thing about it is, that there is not need to set the namespace of the Enum anywhere. For an ivy Demo see the project i've just created: [demoPrimeImportEnum_51.iar][1] ![alt text][2] [1]: http://www.ivyteam.ch/downloads/q-and-a-attachments/demoPrimeImportEnum_51.iarhttp://www.ivyteam.ch/downloads/q-and-a-attachments/demoPrimeImportEnum_51.iar [2]: http://answers.axonivy.com/upfiles/demoPrimeImportEnum.PNG

Yes it works just as shown on the primefaces showcase. The special thing about it is, that there is not need to set the namespace of the Enum anywhere. For an ivy Demo see the project i've just created: [demoPrimeImportEnum_51.iar][1] [1]: http://www.ivyteam.ch/downloads/q-and-a-attachments/demoPrimeImportEnum_51.iar