January 2016 - jbosstools-issues - Jboss List Archives

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[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

1
0
0 / 0

[JBoss JIRA] (JBIDE-21397) Content assist for facelet function does not work in an unclosed EL before next EL

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-21397: -------------------------------------- Summary: Content assist for facelet function does not work in an unclosed EL before next EL Key: JBIDE-21397 URL: https://issues.jboss.org/browse/JBIDE-21397 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. Add to page some facelet taglib with functions, let its namespace be 'p'. 2. Try content assist after ':' in {code} #{p: #{someBean} {code} It fails. 3. Close EL {code} #{p:} #{someBean} {code} Now, content assist works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21397) Content assist for facelet function does not work in an unclosed EL before next EL

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21397?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21397: ----------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.4.0.Alpha1) > Content assist for facelet function does not work in an unclosed EL before next EL > ---------------------------------------------------------------------------------- > > Key: JBIDE-21397 > URL: https://issues.jboss.org/browse/JBIDE-21397 > 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. Add to page some facelet taglib with functions, let its namespace be 'p'. > 2. Try content assist after ':' in > {code} > #{p: #{someBean} > {code} > It fails. > 3. Close EL > {code} > #{p:} #{someBean} > {code} > Now, content assist works. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2016