[JBoss JIRA] (JBDS-2425) JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2425?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2425:
----------------------------------
[~mmurray] "We" is "the team responsible for building, maintaining, and distributing JBDS". Or more simply, "Red Hat".
Any chance you can throw me a PR or patch instead of a list of fixes?
Source is here: https://github.com/jbdevstudio/jbdevstudio-website/blob/master/content/up... or https://devstudio.jboss.com/updates/7.0/central/index.html
> JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2425
> URL: https://issues.jboss.org/browse/JBDS-2425
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Central
> Affects Versions: 6.0.0.CR1
> Environment: Version: 6.0.0.CR1
> Build id: CR1-v20121204-0201-B166
> Build date: 20121204-0201
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Fix For: 7.0.x, 8.0.x, 7.1.x
>
> Attachments: 2425.png, 2425_2.png, 2425_3.png
>
>
> In JBoss Central (see attached screenshot), features are listed as "tested" or "supported" - but the active links provided take the user to: https://devstudio.jboss.com/download/
> Where these terms are not defined.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15317) LiveReload script injection corrupted html encoding
by Pei-Tang Huang (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15317?page=com.atlassian.jira.plugi... ]
Pei-Tang Huang commented on JBIDE-15317:
----------------------------------------
Besides, is it possible to retrieve the file encoding from Eclipse, as what I saw in File Properties / Resource / Text File encoding? This proposal seems more elegant and flexible.
> LiveReload script injection corrupted html encoding
> ---------------------------------------------------
>
> Key: JBIDE-15317
> URL: https://issues.jboss.org/browse/JBIDE-15317
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.1.0.Final
> Reporter: Pei-Tang Huang
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: encoding, livereload
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
> Attachments: chinese.html
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> LiveReload script injection dissmisses the encoding of the original HTML content, my page contains CJK character in UTF-8 all became "?" character.
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project with Seam 2.3.Final
by Darryl Miles (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ]
Darryl Miles edited comment on JBIDE-14629 at 8/17/13 12:34 AM:
----------------------------------------------------------------
Report the problem as per comment https://issues.jboss.org/browse/JBIDE-14629?focusedCommentId=12777985&pag...
with the project https://issues.jboss.org/browse/JBMETA
Request that all part, current and future JBoss XSD are passed through validators there should be no problem issuing an update to the XSD to correct a matter that never have existed.
was (Author: dlmiles):
Report the problem as per comment https://issues.jboss.org/browse/JBIDE-14629?focusedCommentId=12777985&pag...
with the project https://issues.jboss.org/browse/JBMETA
> Errors when creating and deploying seam2 project with Seam 2.3.Final
> ---------------------------------------------------------------------
>
> Key: JBIDE-14629
> URL: https://issues.jboss.org/browse/JBIDE-14629
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206 with bundled JBoss EAP 6.1.0.Beta1
> Reporter: Vlado Pakan
> Assignee: Alexey Kazakov
> Fix For: 4.1.1.Final
>
> Attachments: seamerror.png
>
>
> ERROR: DefaultDS Database connection is defined with incorrect link to hsqldb.jar file with JDBC driver for HSQLDB.
> 1. Fix DefaultDS Database connection definition
> ASSERT: It's possible to connect to DefaultDS
> 2. Create new seam project with bundled JBoss EAP and JBoss Seam 2.3.Final
> ERROR: There is error in Problems view:
> !seamerror.png!
> 3. Start seam project on server
> ERROR: This error appear in Server log. Application is not deployed:
> {noformat}
> 3:58:45,950 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012: Deployment deployment "seam.war" contains CDI annotations but beans.xml was not found.
> 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam-ds.xml" (runtime-name : "seam-ds.xml")
> 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam.war" (runtime-name : "seam.war")
> 13:58:46,431 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "hsqldb.jar" (runtime-name : "hsqldb.jar")
> 13:58:46,436 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.jdbc-driver.hsqldb_jar (missing) dependents: [service jboss.data-source.java:/seamDatasource]
> {noformat}
> Is this supported scenario?
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project with Seam 2.3.Final
by Darryl Miles (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ]
Darryl Miles edited comment on JBIDE-14629 at 8/17/13 12:34 AM:
----------------------------------------------------------------
Report the problem as per comment https://issues.jboss.org/browse/JBIDE-14629?focusedCommentId=12777985&pag...
with the project https://issues.jboss.org/browse/JBMETA
Request that all past, current and future JBoss XSD are passed through XSD validators there should be no problem issuing an update to the XSD to correct a matter that never have existed.
was (Author: dlmiles):
Report the problem as per comment https://issues.jboss.org/browse/JBIDE-14629?focusedCommentId=12777985&pag...
with the project https://issues.jboss.org/browse/JBMETA
Request that all part, current and future JBoss XSD are passed through validators there should be no problem issuing an update to the XSD to correct a matter that never have existed.
> Errors when creating and deploying seam2 project with Seam 2.3.Final
> ---------------------------------------------------------------------
>
> Key: JBIDE-14629
> URL: https://issues.jboss.org/browse/JBIDE-14629
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206 with bundled JBoss EAP 6.1.0.Beta1
> Reporter: Vlado Pakan
> Assignee: Alexey Kazakov
> Fix For: 4.1.1.Final
>
> Attachments: seamerror.png
>
>
> ERROR: DefaultDS Database connection is defined with incorrect link to hsqldb.jar file with JDBC driver for HSQLDB.
> 1. Fix DefaultDS Database connection definition
> ASSERT: It's possible to connect to DefaultDS
> 2. Create new seam project with bundled JBoss EAP and JBoss Seam 2.3.Final
> ERROR: There is error in Problems view:
> !seamerror.png!
> 3. Start seam project on server
> ERROR: This error appear in Server log. Application is not deployed:
> {noformat}
> 3:58:45,950 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012: Deployment deployment "seam.war" contains CDI annotations but beans.xml was not found.
> 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam-ds.xml" (runtime-name : "seam-ds.xml")
> 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam.war" (runtime-name : "seam.war")
> 13:58:46,431 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "hsqldb.jar" (runtime-name : "hsqldb.jar")
> 13:58:46,436 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.jdbc-driver.hsqldb_jar (missing) dependents: [service jboss.data-source.java:/seamDatasource]
> {noformat}
> Is this supported scenario?
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-14629) Errors when creating and deploying seam2 project with Seam 2.3.Final
by Darryl Miles (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14629?page=com.atlassian.jira.plugi... ]
Darryl Miles commented on JBIDE-14629:
--------------------------------------
Report the problem as per comment https://issues.jboss.org/browse/JBIDE-14629?focusedCommentId=12777985&pag...
with the project https://issues.jboss.org/browse/JBMETA
> Errors when creating and deploying seam2 project with Seam 2.3.Final
> ---------------------------------------------------------------------
>
> Key: JBIDE-14629
> URL: https://issues.jboss.org/browse/JBIDE-14629
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.1.0.Beta1
> Environment: JBDS 7.0.0.Beta1-v20130519-0601-B206 with bundled JBoss EAP 6.1.0.Beta1
> Reporter: Vlado Pakan
> Assignee: Alexey Kazakov
> Fix For: 4.1.1.Final
>
> Attachments: seamerror.png
>
>
> ERROR: DefaultDS Database connection is defined with incorrect link to hsqldb.jar file with JDBC driver for HSQLDB.
> 1. Fix DefaultDS Database connection definition
> ASSERT: It's possible to connect to DefaultDS
> 2. Create new seam project with bundled JBoss EAP and JBoss Seam 2.3.Final
> ERROR: There is error in Problems view:
> !seamerror.png!
> 3. Start seam project on server
> ERROR: This error appear in Server log. Application is not deployed:
> {noformat}
> 3:58:45,950 WARN [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016012: Deployment deployment "seam.war" contains CDI annotations but beans.xml was not found.
> 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam-ds.xml" (runtime-name : "seam-ds.xml")
> 13:58:46,430 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "seam.war" (runtime-name : "seam.war")
> 13:58:46,431 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "hsqldb.jar" (runtime-name : "hsqldb.jar")
> 13:58:46,436 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.jdbc-driver.hsqldb_jar (missing) dependents: [service jboss.data-source.java:/seamDatasource]
> {noformat}
> Is this supported scenario?
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15351) Implement bean discovery in explicit and implicit archives
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15351?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich updated JBIDE-15351:
------------------------------------------
Description:
http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#bean_archive
1. Create CDI 1.1 project.
2. Create other CDI 1.1 projects and export them to jars or to class folders,
these projects may vary in beans.xml:
- no beans.xml
- empty beans.xml
- beans.xml with 1.0 schema
- beans.xml with 1.1 schema and all possible values
of bean-discovery-mode attribute ("annotated"/"none"/"all")
and have classes with and without scope declaration.
3. Add these archives to classpath of project (1).
4. Create a bean with injections to types defined in the archives.
5. Check that injection is satisfied or not according to bean discovery rules given by specification.
Examples:
- Archive has no beans.xml: only annotated beans will be resolved;
- Archive has empty beans.xml, or beans.xml with 1.0 schema: all beans will be resolved;
- Archive has beans.xml with version 1.1: beans will be resolved according to the value of bean-discovery-attribute.
was:
http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#bean_archive
1. Create CDI 1.1 project.
2. Create other CDI 1.1 projects and export them to jars or to class folders,
these projects may vary in beans.xml:
- no beans.xml
- empty beans.xml
- beans.xml with 1.0 schema
- beans.xml with 1.1 schema and all possible values
of bean-discovery-mode attribute ("annotated"/"none"/"all")
and have classes with and without scope declaration.
3. Add these archives to classpath of project (1).
4. Create a bean with injections to types defined in the archives.
5. Check that injection is satisfied or not according to bean discovery rules given by specification.
Examples:
- Archive has no beans.xml: only annotated beans will be resolved;
- Archive has empty beans.xml, or beans.xml with 1.0 schema: all beans will be resolved;
- Archive has beans.xml with version 1.1: beans will be resolved according to the value of bean-discovery-attribute.
> Implement bean discovery in explicit and implicit archives
> -----------------------------------------------------------
>
> Key: JBIDE-15351
> URL: https://issues.jboss.org/browse/JBIDE-15351
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: CDI
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Alpha1
>
>
> http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#bean_archive
> 1. Create CDI 1.1 project.
> 2. Create other CDI 1.1 projects and export them to jars or to class folders,
> these projects may vary in beans.xml:
> - no beans.xml
> - empty beans.xml
> - beans.xml with 1.0 schema
> - beans.xml with 1.1 schema and all possible values
> of bean-discovery-mode attribute ("annotated"/"none"/"all")
> and have classes with and without scope declaration.
> 3. Add these archives to classpath of project (1).
> 4. Create a bean with injections to types defined in the archives.
> 5. Check that injection is satisfied or not according to bean discovery rules given by specification.
> Examples:
> - Archive has no beans.xml: only annotated beans will be resolved;
> - Archive has empty beans.xml, or beans.xml with 1.0 schema: all beans will be resolved;
> - Archive has beans.xml with version 1.1: beans will be resolved according to the value of bean-discovery-attribute.
--
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
12 years, 7 months