[JBoss JIRA] (JBSEAM-5039) seam2.3 seam-gen generated project looks ugly compared with seam2.2
by Marek Schmidt (JIRA)
Marek Schmidt created JBSEAM-5039:
-------------------------------------
Summary: seam2.3 seam-gen generated project looks ugly compared with seam2.2
Key: JBSEAM-5039
URL: https://issues.jboss.org/browse/JBSEAM-5039
Project: Seam 2
Issue Type: Bug
Components: Tools
Affects Versions: 2.3.0.CR1
Environment: Seam2.3.0.CR1, AS 7.1.1
Reporter: Marek Schmidt
Assignee: Marek Novotny
Priority: Minor
Fix For: 2.3.0.Final
Seam2.2 seam-gen generated project has neatly aligned forms and tables nicely adjusted to the window width. Seam2.3 seam-gen generated project looks amateurish in comparison.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBSEAM-5040) Errors Importing seam booking example into JBDS
by Marek Schmidt (JIRA)
Marek Schmidt created JBSEAM-5040:
-------------------------------------
Summary: Errors Importing seam booking example into JBDS
Key: JBSEAM-5040
URL: https://issues.jboss.org/browse/JBSEAM-5040
Project: Seam 2
Issue Type: Bug
Components: Examples
Affects Versions: 2.3.0.CR1
Environment: JBDS 5.0.1
Reporter: Marek Schmidt
Priority: Minor
Fix For: 2.3.0.Final
There are XHTML errors in the "exp" html files in the Seam booking example.
Another problem seems to be the "distributable="${distributable}" attribute in components.xml, for some unknown reason.
{noformat}
Description Resource Path Location Type
The element type "INPUT" must be terminated by the matching end-tag "</INPUT>". introExp.html /booking-web/src/main/webapp/exp line 22 XHTML Problem
The element type "INPUT" must be terminated by the matching end-tag "</INPUT>". introExp.html /booking-web/target/m2e-wtp/web-resources/exp line 22 XHTML Problem
The element type "INPUT" must be terminated by the matching end-tag "</INPUT>". workspaceExp.html /booking-web/src/main/webapp/exp line 22 XHTML Problem
The element type "INPUT" must be terminated by the matching end-tag "</INPUT>". workspaceExp.html /booking-web/target/m2e-wtp/web-resources/exp line 22 XHTML Problem
The entity name must immediately follow the '&' in the entity reference. mainExp.html /booking-web/src/main/webapp/exp line 94 XHTML Problem
The entity name must immediately follow the '&' in the entity reference. mainExp.html /booking-web/target/m2e-wtp/web-resources/exp line 94 XHTML Problem
cvc-attribute.3: The value '${distributable}' of attribute 'distributable' on element 'core:init' is not valid with respect to its type, 'boolean'. components.xml /booking-web/src/main/webapp/WEB-INF line 13 XML Problem
cvc-datatype-valid.1.2.3: '${distributable}' is not a valid value of union type 'boolean'. components.xml /booking-web/src/main/webapp/WEB-INF line 13 XML Problem
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBSEAM-4978) Seam-gen commands using hibernate-tools doesn't work
by Tomas Remes (JIRA)
Tomas Remes created JBSEAM-4978:
-----------------------------------
Summary: Seam-gen commands using hibernate-tools doesn't work
Key: JBSEAM-4978
URL: https://issues.jboss.org/browse/JBSEAM-4978
Project: Seam 2
Issue Type: Bug
Components: Tools
Affects Versions: 2.3.0.BETA2
Reporter: Tomas Remes
Fix For: 2.3.0.CR1
Seam-gen commands like "generate-model","generate", "generate-ui" does not work, because it's using old hibernate-tools version. Major problem is that this old version is using classes from hibernate-core 3.2.4 (and probably many other jars) and those are not compatible with hibernate 4 versions. So when you try for example command "generate-model", you will get following error:
{noformat}
jboss-seam-2.3.0.CR1-SNAPSHOT/seam-gen/build.xml:1554: java.lang.NoClassDefFoundError: org/hibernate/engine/Mapping
{noformat}
I am trying/investigating how is this used in JBoss Tools, but as far as I've understood there is entirely bundled old hibernate 3 and its related stuff.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBSEAM-5002) Components included with ui:include src="#{pageScopedViewId} broken
by Marek Schmidt (JIRA)
Marek Schmidt created JBSEAM-5002:
-------------------------------------
Summary: Components included with ui:include src="#{pageScopedViewId} broken
Key: JBSEAM-5002
URL: https://issues.jboss.org/browse/JBSEAM-5002
Project: Seam 2
Issue Type: Bug
Components: JSF Integration
Affects Versions: 2.3.0.BETA2
Environment: JBoss AS 7.1.2, Seam 2.3.0.CR1-SNAPSHOT (r14986)
Reporter: Marek Schmidt
Assignee: Marek Novotny
Fix For: 2.3.0.CR1
The following scenario that used to work in AS5/Seam2.2 doesn't work anymore in AS7/Seam2.3 for page-scoped and conversation-scoped "viewId" components:
index.xhtml:
{code}
<h:form>
<h:commandButton action="#{viewId.component1}" value="Component 1" />
<h:commandButton action="#{viewId.component2}" value="Component 2" />
</h:form>
<ui:include src="#{viewId.viewId}"/>
{code}
{code}
@Scope(ScopeType.PAGE)
@Name("viewId")
public class ViewIdComponent implements Serializable
{
private String viewId = "/component1.xhtml";
public void setViewId(String viewId) {
this.viewId = viewId;
}
public String getViewId() {
return viewId;
}
public void component1() {
setViewId("/component1.xhtml");
}
public void component2() {
setViewId("/component2.xhtml");
}
}
{code}
(compoent1 and 2 are redacted, contain a simple form)
Only the first component works properly, actions in "component2" doesn't seem to be called after switching to "Component 2".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBSEAM-5036) seam-gen asks for an anachronism "Enter your JBoss AS domain [standalone]"
by Marek Schmidt (JIRA)
Marek Schmidt created JBSEAM-5036:
-------------------------------------
Summary: seam-gen asks for an anachronism "Enter your JBoss AS domain [standalone]"
Key: JBSEAM-5036
URL: https://issues.jboss.org/browse/JBSEAM-5036
Project: Seam 2
Issue Type: Bug
Components: Tools
Affects Versions: 2.3.0.CR1
Environment: as7.1.1.Final
Reporter: Marek Schmidt
Assignee: Marek Novotny
Fix For: 2.3.0.Final
It is not clear what the prompt
"Enter your JBoss AS domain [standalone]"
means in the context of AS7, as it has both a "domain" mode and a "standalone" mode, while what the question probably really asks for is a name of the standalone configuration file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] (JBSEAM-5037) seam-gen default datasource fails to deploy on AS7 "Missing required element driver-class in org.jboss.jca.common.metadata.ds.DataSourceImpl"
by Marek Schmidt (JIRA)
Marek Schmidt created JBSEAM-5037:
-------------------------------------
Summary: seam-gen default datasource fails to deploy on AS7 "Missing required element driver-class in org.jboss.jca.common.metadata.ds.DataSourceImpl"
Key: JBSEAM-5037
URL: https://issues.jboss.org/browse/JBSEAM-5037
Project: Seam 2
Issue Type: Bug
Components: Tools
Affects Versions: 2.3.0.CR1
Environment: as7.1.1
Reporter: Marek Schmidt
Assignee: Marek Novotny
Priority: Critical
Fix For: 2.3.0.Final
A seam-gen generated war project with default settings fails to deploy with "ant explode" on AS7.1.1.Final:
{noformat}
15:16:08,221 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."myproject-ds.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."myproject-ds.xml".PARSE: Failed to process phase PARSE of deployment "myproject-ds.xml"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: IJ010069: Missing required element driver-class in org.jboss.jca.common.metadata.ds.DataSourceImpl
at org.jboss.as.connector.deployers.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:85)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
Caused by: org.jboss.jca.common.api.validator.ValidateException: IJ010069: Missing required element driver-class in org.jboss.jca.common.metadata.ds.DataSourceImpl
at org.jboss.jca.common.metadata.ds.DataSourceImpl.validate(DataSourceImpl.java:454)
at org.jboss.jca.common.metadata.ds.DataSourceImpl.<init>(DataSourceImpl.java:124)
at org.jboss.jca.common.metadata.ds.DsParser.parseDataSource(DsParser.java:558)
at org.jboss.jca.common.metadata.ds.DsParser.parseDataSources(DsParser.java:166)
at org.jboss.jca.common.metadata.ds.DsParser.parse(DsParser.java:119)
at org.jboss.jca.common.metadata.ds.DsParser.parse(DsParser.java:82)
at org.jboss.as.connector.deployers.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:80)
... 6 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months
[JBoss JIRA] Created: (JBSEAM-4693) 6.12.2. Enabling Seam exception handling : web:exception-filter in components.xml
by simon lebettre (JIRA)
6.12.2. Enabling Seam exception handling : web:exception-filter in components.xml
---------------------------------------------------------------------------------
Key: JBSEAM-4693
URL: https://jira.jboss.org/browse/JBSEAM-4693
Project: Seam
Issue Type: Task
Components: Documentation Issues
Reporter: simon lebettre
this does not make sense :
"
6.12.2. Enabling Seam exception handling
To enable Seam's exception handling, we need to make sure we have the master servlet filter declared in web.xml:
"
==> Of course the master filter is in web.xml !
this would be more relevant :
"we need to make sure that <web:exception-filter url-pattern="*.seam" /> is declared in components.xml"
I m not being picky about the doc, it's been 7 months I have a bad user experience or loose some exception feedback because I forgot this line in components.xml !
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 6 months