[
https://jira.jboss.org/jira/browse/JBIDE-2957?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen commented on JBIDE-2957:
--------------------------------------------
okey - so this set is just iterated in no specific order ?
Slava, here is the changeset for the change in Seam 2.1:
http://fisheye.jboss.org/viewrep/Seam/trunk/src/main/org/jboss/seam/secur...
What we need to scan for is package-info.java/class which contains stuff like:
@Namespace(value="http://jboss.com/products/seam/security",
prefix="org.jboss.seam.security")
@AutoCreate
package org.jboss.seam.security.permission;
Which add's the org.jboss.seam.security.permission as a package to look for classes in
the appointed namespace.
Seam 2.1 causes errors in components.xml
----------------------------------------
Key: JBIDE-2957
URL:
https://jira.jboss.org/jira/browse/JBIDE-2957
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.0.0.alpha
Reporter: Max Rydahl Andersen
Fix For: 3.0.0.cr1
when using Seam 2.1 components.xml contains <security:rule-based-permission-resolver
security-rules="#{securityRules}"/>
This is marked as an error:
"org.jboss.seam.security.RuleBasedPermissionResolver" cannot be resolved to a
type
Which is caused because seam tooling until now just assumed the xml could be mapped
directly as org.jboss.seam.[postcolonname].[camelcaseoftagname]
That is true 99% of the time but Seam 2.1 introduced that the xml can be mapped to
multiple packages causing this mapping to fail + extenders of Seam would
bump into this too if they use a package name other than org.jboss.seam.
We should implement the proper packageInfo lookups so we get this done properly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira