[JBoss JIRA] Created: (JBIDE-2957) Seam 2.1 causes errors in components.xml
by Max Rydahl Andersen (JIRA)
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.cr1
Reporter: Max Rydahl Andersen
Fix For: 3.0.0.alpha
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
17 years, 4 months
[JBoss JIRA] Created: (JBIDE-1542) Empty "Driver Class" property for modified connection profiles
by Alexandros Karypidis (JIRA)
Empty "Driver Class" property for modified connection profiles
--------------------------------------------------------------
Key: JBIDE-1542
URL: http://jira.jboss.com/jira/browse/JBIDE-1542
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam, seam-gen
Affects Versions: 2.0.0.GA
Environment: 32-bit Ubuntu Linux 7.10, Eclipse 3.3.1.1 (M20071023-1652), WTP 2.0.1 (v200709110510), DTP 1.5.1
Reporter: Alexandros Karypidis
Priority: Minor
The Seam Web Project wizard complains that "Driver Class proberty is empty for selected 'x' connection profile" on the Seam Facet page and will not proceed. This occurs for perfectly valid connection profiles, when they have been modified since their creation. To reproduce:
1) Open the Database Development perspective
2) Create a connection profile. Type an incorrect JDBC connection URL.
3) Edit the connection profile. Fix the JDBC connection URL.
4) Start the Seam Web Project wizard and select the connection profile.
5) The wizard does not accept the connection and will not move forward from the "Seam Facet" page.
If you skip step 3 and not modify the connection profile, the problem does not occur.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 4 months