[JBoss JIRA] (TOOLSDOC-696) Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-696?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-696:
-------------------------------
Sprint: 04-Jan >> 17-Jan 2016-JBDS/JBT
Affects: Release Notes
> Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
> -----------------------------------------------------------------------------------
>
> Key: TOOLSDOC-696
> URL: https://issues.jboss.org/browse/TOOLSDOC-696
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Release Notes
> Environment: Build Name: 23115, 9.1 Beta1 Release Notes-9.1-Beta1
> Build Date: 18-12-2015 22:13:00
> Topic ID: 44506-773485 [Latest]
> Reporter: Len DiMaggio
> Assignee: Misha Ali
>
> Title: New Features
> Describe the issue:
> The text describing the new support fo rthe CDK in JBDS 9.1 is correct in the draft release notes:
> '...Integration with Red Hat Container Development Kit: A new server adapter has been added to help start and stop the Red Hat Container Development Kit (CDK), a set of tools meant to quickly set up an OpenShift instance inside a Docker container running inside a virtual machine. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its Vagrantfile. Once started, Docker and OpenShift connections should appear in their respective views, allowing the user to quickly create a new OpenShift application and begin developing their AwesomeApp in a highly-replicatable environment...'
> But - I'd suggest that this moved to a more prominent location in the release notes as it is a major reason for the creation of the beta1 release.
> Can we also add a screenshot?
> Suggestions for improvement:
> Additional information:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21380) EL syntax error: String is not closed with string concatenation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21380?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21380:
----------------------------------------
Yes, and this is why I recommend to disable EL validation, not KB support.
> EL syntax error: String is not closed with string concatenation
> ---------------------------------------------------------------
>
> Key: JBIDE-21380
> URL: https://issues.jboss.org/browse/JBIDE-21380
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.x
> Environment: Eclipse Mars.1 (4.5.1)
> Reporter: Andrei Ivanov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.x
>
>
> I get a {{EL syntax error: String is not closed.}} warning when an expression is composed using string concatenation:
> {code:java}
> String expression = "#{" + entry.getValue() + "}";
> {code}
> \\
> \\
> A different issue I think might be that when enabling the JSF support for the web module, the JBoss Tools Knowledge Support is enabled for the other modules too, including the data module.
> This leads to {{EL syntax error: Expecting expression.}} for a JPA query with Spring EL expressions:
> {code:java}
> import org.springframework.data.jpa.repository.Query;
> import org.springframework.data.repository.PagingAndSortingRepository;
> public interface FunctionsRepository extends PagingAndSortingRepository<Function, Integer> {
> @Query("SELECT DISTINCT r.workCenter.function"
> + " FROM StaffingAgreementDataRecord r"
> + " WHERE r.staffingAgreement.customer.id IN :customerIds"
> + " AND r.staffingAgreement.startDate <= :#{#interval.end}"
> + " AND r.staffingAgreement.endDate >= :#{#interval.start}")
> List<Function> findByCustomersAndInterval(List<Integer> customerIds, Interval interval);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21380) EL syntax error: String is not closed with string concatenation
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21380?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21380 at 1/4/16 5:12 PM:
-----------------------------------------------------------------------
But will not then a warning appear on dependent web project that it uses Java project with no KB support? Can we improve kb support preferences to allow that?
was (Author: scabanovich):
But will not then a warning appear on dependent web project that it uses Java project with no KB support. Can we improve kb support preferences to allow that?
> EL syntax error: String is not closed with string concatenation
> ---------------------------------------------------------------
>
> Key: JBIDE-21380
> URL: https://issues.jboss.org/browse/JBIDE-21380
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.x
> Environment: Eclipse Mars.1 (4.5.1)
> Reporter: Andrei Ivanov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.x
>
>
> I get a {{EL syntax error: String is not closed.}} warning when an expression is composed using string concatenation:
> {code:java}
> String expression = "#{" + entry.getValue() + "}";
> {code}
> \\
> \\
> A different issue I think might be that when enabling the JSF support for the web module, the JBoss Tools Knowledge Support is enabled for the other modules too, including the data module.
> This leads to {{EL syntax error: Expecting expression.}} for a JPA query with Spring EL expressions:
> {code:java}
> import org.springframework.data.jpa.repository.Query;
> import org.springframework.data.repository.PagingAndSortingRepository;
> public interface FunctionsRepository extends PagingAndSortingRepository<Function, Integer> {
> @Query("SELECT DISTINCT r.workCenter.function"
> + " FROM StaffingAgreementDataRecord r"
> + " WHERE r.staffingAgreement.customer.id IN :customerIds"
> + " AND r.staffingAgreement.startDate <= :#{#interval.end}"
> + " AND r.staffingAgreement.endDate >= :#{#interval.start}")
> List<Function> findByCustomersAndInterval(List<Integer> customerIds, Interval interval);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21380) EL syntax error: String is not closed with string concatenation
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21380?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21380:
-----------------------------------------------
But will not then a warning appear on dependent web project that it uses Java project with no KB support. Can we improve kb support preferences to allow that?
> EL syntax error: String is not closed with string concatenation
> ---------------------------------------------------------------
>
> Key: JBIDE-21380
> URL: https://issues.jboss.org/browse/JBIDE-21380
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.x
> Environment: Eclipse Mars.1 (4.5.1)
> Reporter: Andrei Ivanov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.x
>
>
> I get a {{EL syntax error: String is not closed.}} warning when an expression is composed using string concatenation:
> {code:java}
> String expression = "#{" + entry.getValue() + "}";
> {code}
> \\
> \\
> A different issue I think might be that when enabling the JSF support for the web module, the JBoss Tools Knowledge Support is enabled for the other modules too, including the data module.
> This leads to {{EL syntax error: Expecting expression.}} for a JPA query with Spring EL expressions:
> {code:java}
> import org.springframework.data.jpa.repository.Query;
> import org.springframework.data.repository.PagingAndSortingRepository;
> public interface FunctionsRepository extends PagingAndSortingRepository<Function, Integer> {
> @Query("SELECT DISTINCT r.workCenter.function"
> + " FROM StaffingAgreementDataRecord r"
> + " WHERE r.staffingAgreement.customer.id IN :customerIds"
> + " AND r.staffingAgreement.startDate <= :#{#interval.end}"
> + " AND r.staffingAgreement.endDate >= :#{#interval.start}")
> List<Function> findByCustomersAndInterval(List<Integer> customerIds, Interval interval);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21380) EL syntax error: String is not closed with string concatenation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21380?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21380:
----------------------------------------
Your project may be a plain Utility Module but it still can provide some java beans which will be used by another JSF project. So we need a KB support enabled for such modules to get them available in JSF project.
As a workaround I would recommend to disable EL Validation for your Utility or JPA projects. You can do it in Preferences. Or you can add the corresponding suppress warning annotation via a QuickFix.
> EL syntax error: String is not closed with string concatenation
> ---------------------------------------------------------------
>
> Key: JBIDE-21380
> URL: https://issues.jboss.org/browse/JBIDE-21380
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.x
> Environment: Eclipse Mars.1 (4.5.1)
> Reporter: Andrei Ivanov
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Fix For: 4.4.x
>
>
> I get a {{EL syntax error: String is not closed.}} warning when an expression is composed using string concatenation:
> {code:java}
> String expression = "#{" + entry.getValue() + "}";
> {code}
> \\
> \\
> A different issue I think might be that when enabling the JSF support for the web module, the JBoss Tools Knowledge Support is enabled for the other modules too, including the data module.
> This leads to {{EL syntax error: Expecting expression.}} for a JPA query with Spring EL expressions:
> {code:java}
> import org.springframework.data.jpa.repository.Query;
> import org.springframework.data.repository.PagingAndSortingRepository;
> public interface FunctionsRepository extends PagingAndSortingRepository<Function, Integer> {
> @Query("SELECT DISTINCT r.workCenter.function"
> + " FROM StaffingAgreementDataRecord r"
> + " WHERE r.staffingAgreement.customer.id IN :customerIds"
> + " AND r.staffingAgreement.startDate <= :#{#interval.end}"
> + " AND r.staffingAgreement.endDate >= :#{#interval.start}")
> List<Function> findByCustomersAndInterval(List<Integer> customerIds, Interval interval);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21172) CDK server in Starting state and cannot be stopped with wrong path to vagrant
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21172?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21172:
-------------------------------------
https://github.com/jbosstools/jbosstools-openshift/pull/875 fixes this issue. It doesn't fix the root cause, but it at least catches any exceptions during launch and ensures server is set to stopped.
> CDK server in Starting state and cannot be stopped with wrong path to vagrant
> -----------------------------------------------------------------------------
>
> Key: JBIDE-21172
> URL: https://issues.jboss.org/browse/JBIDE-21172
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> When I first set up a CDK 2 Beta3 server adapter in Eclipse, it had the launch config set up with the wrong path to vagrant - /usr/bin/vagrant instead of /usr/local/bin/vagrant which is the default location on OS X - I didn't notice this and just tried to start the adapter.
> Obviously it failed, but I was left in a state where the server was Starting and I couldn't stop it unless I restarted the IDE.
> I think it should fail more gracefully.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21398) EL var is not resolved correctly when value is set with bean method returning an array
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-21398:
--------------------------------------
Summary: EL var is not resolved correctly when value is set with bean method returning an array
Key: JBIDE-21398
URL: https://issues.jboss.org/browse/JBIDE-21398
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core, jsf
Affects Versions: 4.4.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.4.0.Alpha1
1. Create a bean class with property returning array:
{code}
public SignOffStatus[] getStatuses() {
return null;
}
{code}
2. Set collection value of an iterative tag with method call rather than property call
{code}
<p:selectOneMenu value="#{instancePage.instanceCriteria.status}">
<f:selectItem itemLabel="--select--" itemValue="#{null}" />
<f:selectItems value="#{appBean.getStatuses()}" var="stat" itemLabel="#{stat.label}" />
</p:selectOneMenu>
{code}
3. Failure: members of var are not resolved.
If value is set with property call
{code}
value="#{appBean.statuses}"
{code}
and/or if method getStatuses() returns a collection type, then var members resolution works ok.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21398) EL var is not resolved correctly when value is set with bean method returning an array
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21398?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21398:
-----------------------------------
Fix Version/s: 4.3.1.Beta2
(was: 4.4.0.Alpha1)
> EL var is not resolved correctly when value is set with bean method returning an array
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-21398
> URL: https://issues.jboss.org/browse/JBIDE-21398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, jsf
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.1.Beta2
>
>
> 1. Create a bean class with property returning array:
> {code}
> public SignOffStatus[] getStatuses() {
> return null;
> }
> {code}
> 2. Set collection value of an iterative tag with method call rather than property call
> {code}
> <p:selectOneMenu value="#{instancePage.instanceCriteria.status}">
> <f:selectItem itemLabel="--select--" itemValue="#{null}" />
> <f:selectItems value="#{appBean.getStatuses()}" var="stat" itemLabel="#{stat.label}" />
> </p:selectOneMenu>
> {code}
> 3. Failure: members of var are not resolved.
> If value is set with property call
> {code}
> value="#{appBean.statuses}"
> {code}
> and/or if method getStatuses() returns a collection type, then var members resolution works ok.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21398) EL var is not resolved correctly when value is set with bean method returning an array
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21398?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-21398.
------------------------------------
Resolution: Done
> EL var is not resolved correctly when value is set with bean method returning an array
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-21398
> URL: https://issues.jboss.org/browse/JBIDE-21398
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, jsf
> Affects Versions: 4.4.0.Alpha1
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.1.Beta2
>
>
> 1. Create a bean class with property returning array:
> {code}
> public SignOffStatus[] getStatuses() {
> return null;
> }
> {code}
> 2. Set collection value of an iterative tag with method call rather than property call
> {code}
> <p:selectOneMenu value="#{instancePage.instanceCriteria.status}">
> <f:selectItem itemLabel="--select--" itemValue="#{null}" />
> <f:selectItems value="#{appBean.getStatuses()}" var="stat" itemLabel="#{stat.label}" />
> </p:selectOneMenu>
> {code}
> 3. Failure: members of var are not resolved.
> If value is set with property call
> {code}
> value="#{appBean.statuses}"
> {code}
> and/or if method getStatuses() returns a collection type, then var members resolution works ok.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months