[JBoss JIRA] (JBIDE-12592) El is not revalidated in java comments
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12592?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-12592:
-----------------------------------
Description:
1. Create the following class:
{code}
package test;
import javax.enterprise.inject.Produces;
import javax.inject.Named;
public class Bean_Broken {
public void foo() {
String s = "#{string.ss}";
}
@Named
@Produces
public String string() {
return "";
}
}
{code}
2. The EL is marked as a problem
3. Ctrl + / on {code}String s = "#{string.ss}";{code} Don't save the file.
4. FAILURE: There is still a validation problem on the EL.
5. Save the file. The problem in the comment is gone.
was:
1. Create the following class:
{code}
package test;
import javax.enterprise.inject.Produces;
import javax.inject.Named;
public class Bean_Broken {
public void foo() {
String s = "#{string.ss}";
}
@Named
@Produces
public String string() {
return "";
}
}
{code}
2. The EL is marked as a problem
3. Ctrl + / on {code}s1 = "#{string.ss}";{code} Don't save the file.
4. FAILURE: There is still a validation problem on the EL.
5. Save the file. The problem in the comment is gone.
> El is not revalidated in java comments
> --------------------------------------
>
> Key: JBIDE-12592
> URL: https://issues.jboss.org/browse/JBIDE-12592
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.0.0.Alpha1
> Environment: Juno
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Alpha1
>
>
> 1. Create the following class:
> {code}
> package test;
> import javax.enterprise.inject.Produces;
> import javax.inject.Named;
> public class Bean_Broken {
> public void foo() {
> String s = "#{string.ss}";
> }
> @Named
> @Produces
> public String string() {
> return "";
> }
> }
> {code}
> 2. The EL is marked as a problem
> 3. Ctrl + / on {code}String s = "#{string.ss}";{code} Don't save the file.
> 4. FAILURE: There is still a validation problem on the EL.
> 5. Save the file. The problem in the comment is gone.
--
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, 3 months
[JBoss JIRA] (JBIDE-12592) El is not revalidated in java comments
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12592?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-12592:
-----------------------------------
Description:
1. Create the following class:
{code}
package test;
import javax.enterprise.inject.Produces;
import javax.inject.Named;
public class Bean_Broken {
public void foo() {
String s = "#{string.ss}";
}
@Named
@Produces
public String string() {
return "";
}
}
{code}
2. The EL is marked as a problem
3. Ctrl + / on {code}s1 = "#{string.ss}";{code} Don't save the file.
4. FAILURE: There is still a validation problem on the EL.
5. Save the file. The problem in the comment is gone.
was:
1. Create the following class:
{code}
package test;
import javax.enterprise.inject.Produces;
import javax.inject.Named;
public class Bean_Broken {
public void foo() {
String s = "#{string.ss}";
}
@Named
@Produces
public String string() {
return "";
}
}
{code}
2. The EL is marked as a problem
3. Ctrl + / on s1 = "#{string.ss}"; Don't save the file.
4. FAILURE: There is still a validation problem on the EL.
5. Save the file. The problem in the comment is gone.
> El is not revalidated in java comments
> --------------------------------------
>
> Key: JBIDE-12592
> URL: https://issues.jboss.org/browse/JBIDE-12592
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.0.0.Alpha1
> Environment: Juno
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Alpha1
>
>
> 1. Create the following class:
> {code}
> package test;
> import javax.enterprise.inject.Produces;
> import javax.inject.Named;
> public class Bean_Broken {
> public void foo() {
> String s = "#{string.ss}";
> }
> @Named
> @Produces
> public String string() {
> return "";
> }
> }
> {code}
> 2. The EL is marked as a problem
> 3. Ctrl + / on {code}s1 = "#{string.ss}";{code} Don't save the file.
> 4. FAILURE: There is still a validation problem on the EL.
> 5. Save the file. The problem in the comment is gone.
--
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, 3 months
[JBoss JIRA] (JBIDE-12592) El is not revalidated in java comments
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12592?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-12592:
-----------------------------------
Description:
1. Create the following class:
{code}
package test;
import javax.enterprise.inject.Produces;
import javax.inject.Named;
public class Bean_Broken {
public void foo() {
String s = "#{string.ss}";
}
@Named
@Produces
public String string() {
return "";
}
}
{code}
2. The EL is marked as a problem
3. Ctrl + / on s1 = "#{string.ss}"; Don't save the file.
4. FAILURE: There is still a validation problem on the EL.
5. Save the file. The problem in the comment is gone.
was:
1. Create the following class:
{code}
package test;
import javax.enterprise.inject.Produces;
import javax.inject.Named;
public class Bean_Broken {
public void foo() {
String s = "#{string.ss}";
String s2 = "#{string.ss}";
}
@Named
@Produces
public String string() {
return "";
}
}
{code}
2. Both ELs are marked as a problem
3. Ctrl + / on s2 = "#{string.ss}"; Don't save the file.
4. FAILURE: There is still the validation problem on the second EL.
5. Save the file. The problem in the comment is gone.
> El is not revalidated in java comments
> --------------------------------------
>
> Key: JBIDE-12592
> URL: https://issues.jboss.org/browse/JBIDE-12592
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.0.0.Alpha1
> Environment: Juno
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Alpha1
>
>
> 1. Create the following class:
> {code}
> package test;
> import javax.enterprise.inject.Produces;
> import javax.inject.Named;
> public class Bean_Broken {
> public void foo() {
> String s = "#{string.ss}";
> }
> @Named
> @Produces
> public String string() {
> return "";
> }
> }
> {code}
> 2. The EL is marked as a problem
> 3. Ctrl + / on s1 = "#{string.ss}"; Don't save the file.
> 4. FAILURE: There is still a validation problem on the EL.
> 5. Save the file. The problem in the comment is gone.
--
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, 3 months
[JBoss JIRA] (JBIDE-13340) An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
by andrea tomassi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ]
andrea tomassi updated JBIDE-13340:
-----------------------------------
Attachment: img1.png
Image 1
> An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13340
> URL: https://issues.jboss.org/browse/JBIDE-13340
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: Windows 7
> Eclipse Juno 64 bit
> Jdk 1.7 64 bit
> Reporter: andrea tomassi
> Assignee: Rob Stryker
> Labels: jboss
> Attachments: Img0.png, img1.png, Img2.png
>
>
> 1) Install JBoss Tools version 4.0 (Juno)
> 2) Create a new workspace
> 3) Select Java EE Eclipse perspective
> 3) Define a new JBoss Server and new JBoss Runtime with 6.x server adapter from JBoss Tools (using jboss-6.1.0.final)
> 4) Create an EJB Project (Targeted runtime: JBoss 6.x, EJB module version: 3.1, default options)
> 5) Click with right mouse button on the server, than select "Add and Remove...".
> 6) The EJB project on the left list. It is still possible to deploy the EJB project into the server (See image 0)
> 7) Create a Dynamic Web Project (default options)
> 8) Put the EJB project in the Deployement Assembly of the Dynamic Web Project (see image 1)
> 9) Click again with right mouse button on the server, than select "Add and Remove...".
> 10) The EJB project is no more present in the left list. It isn't possible to deploy the EJB project into the server (See image 2)
--
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, 3 months
[JBoss JIRA] (JBIDE-13340) An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
by andrea tomassi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ]
andrea tomassi updated JBIDE-13340:
-----------------------------------
Attachment: Img2.png
Image 2
> An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13340
> URL: https://issues.jboss.org/browse/JBIDE-13340
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: Windows 7
> Eclipse Juno 64 bit
> Jdk 1.7 64 bit
> Reporter: andrea tomassi
> Assignee: Rob Stryker
> Labels: jboss
> Attachments: Img0.png, img1.png, Img2.png
>
>
> 1) Install JBoss Tools version 4.0 (Juno)
> 2) Create a new workspace
> 3) Select Java EE Eclipse perspective
> 3) Define a new JBoss Server and new JBoss Runtime with 6.x server adapter from JBoss Tools (using jboss-6.1.0.final)
> 4) Create an EJB Project (Targeted runtime: JBoss 6.x, EJB module version: 3.1, default options)
> 5) Click with right mouse button on the server, than select "Add and Remove...".
> 6) The EJB project on the left list. It is still possible to deploy the EJB project into the server (See image 0)
> 7) Create a Dynamic Web Project (default options)
> 8) Put the EJB project in the Deployement Assembly of the Dynamic Web Project (see image 1)
> 9) Click again with right mouse button on the server, than select "Add and Remove...".
> 10) The EJB project is no more present in the left list. It isn't possible to deploy the EJB project into the server (See image 2)
--
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, 3 months
[JBoss JIRA] (JBIDE-13340) An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
by andrea tomassi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ]
andrea tomassi updated JBIDE-13340:
-----------------------------------
Component/s: (was: JBossAS/Servers)
> An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13340
> URL: https://issues.jboss.org/browse/JBIDE-13340
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.0.0.Final
> Environment: Windows 7
> Eclipse Juno 64 bit
> Jdk 1.7 64 bit
> Reporter: andrea tomassi
> Assignee: Rob Stryker
> Labels: jboss
> Attachments: Img0.png, img1.png, Img2.png
>
>
> 1) Install JBoss Tools version 4.0 (Juno)
> 2) Create a new workspace
> 3) Select Java EE Eclipse perspective
> 3) Define a new JBoss Server and new JBoss Runtime with 6.x server adapter from JBoss Tools (using jboss-6.1.0.final)
> 4) Create an EJB Project (Targeted runtime: JBoss 6.x, EJB module version: 3.1, default options)
> 5) Click with right mouse button on the server, than select "Add and Remove...".
> 6) The EJB project on the left list. It is still possible to deploy the EJB project into the server (See image 0)
> 7) Create a Dynamic Web Project (default options)
> 8) Put the EJB project in the Deployement Assembly of the Dynamic Web Project (see image 1)
> 9) Click again with right mouse button on the server, than select "Add and Remove...".
> 10) The EJB project is no more present in the left list. It isn't possible to deploy the EJB project into the server (See image 2)
--
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, 3 months
[JBoss JIRA] (JBIDE-13340) An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
by andrea tomassi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ]
andrea tomassi updated JBIDE-13340:
-----------------------------------
Component/s: JBossAS/Servers
> An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13340
> URL: https://issues.jboss.org/browse/JBIDE-13340
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: Windows 7
> Eclipse Juno 64 bit
> Jdk 1.7 64 bit
> Reporter: andrea tomassi
> Assignee: Rob Stryker
> Labels: jboss
> Attachments: Img0.png, img1.png, Img2.png
>
>
> 1) Install JBoss Tools version 4.0 (Juno)
> 2) Create a new workspace
> 3) Select Java EE Eclipse perspective
> 3) Define a new JBoss Server and new JBoss Runtime with 6.x server adapter from JBoss Tools (using jboss-6.1.0.final)
> 4) Create an EJB Project (Targeted runtime: JBoss 6.x, EJB module version: 3.1, default options)
> 5) Click with right mouse button on the server, than select "Add and Remove...".
> 6) The EJB project on the left list. It is still possible to deploy the EJB project into the server (See image 0)
> 7) Create a Dynamic Web Project (default options)
> 8) Put the EJB project in the Deployement Assembly of the Dynamic Web Project (see image 1)
> 9) Click again with right mouse button on the server, than select "Add and Remove...".
> 10) The EJB project is no more present in the left list. It isn't possible to deploy the EJB project into the server (See image 2)
--
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, 3 months
[JBoss JIRA] (JBIDE-13340) An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
by andrea tomassi (JIRA)
andrea tomassi created JBIDE-13340:
--------------------------------------
Summary: An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
Key: JBIDE-13340
URL: https://issues.jboss.org/browse/JBIDE-13340
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Final
Environment: Windows 7
Eclipse Juno 64 bit
Jdk 1.7 64 bit
Reporter: andrea tomassi
Assignee: Rob Stryker
Attachments: Img0.png
1) Install JBoss Tools version 4.0 (Juno)
2) Create a new workspace
3) Select Java EE Eclipse perspective
3) Define a new JBoss Server and new JBoss Runtime with 6.x server adapter from JBoss Tools (using jboss-6.1.0.final)
4) Create an EJB Project (Targeted runtime: JBoss 6.x, EJB module version: 3.1, default options)
5) Click with right mouse button on the server, than select "Add and Remove...".
6) The EJB project on the left list. It is still possible to deploy the EJB project into the server (See image 0)
7) Create a Dynamic Web Project (default options)
8) Put the EJB project in the Deployement Assembly of the Dynamic Web Project (see image 1)
9) Click again with right mouse button on the server, than select "Add and Remove...".
10) The EJB project is no more present in the left list. It isn't possible to deploy the EJB project into the server (See image 2)
--
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, 3 months
[JBoss JIRA] (JBIDE-13340) An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
by andrea tomassi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13340?page=com.atlassian.jira.plugi... ]
andrea tomassi updated JBIDE-13340:
-----------------------------------
Attachment: Img0.png
Image 0
> An EJB project cannot be deployed to a server if it is also into Deployement Assembly of another Dynamic Web Project
> --------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13340
> URL: https://issues.jboss.org/browse/JBIDE-13340
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: Windows 7
> Eclipse Juno 64 bit
> Jdk 1.7 64 bit
> Reporter: andrea tomassi
> Assignee: Rob Stryker
> Labels: jboss
> Attachments: Img0.png
>
>
> 1) Install JBoss Tools version 4.0 (Juno)
> 2) Create a new workspace
> 3) Select Java EE Eclipse perspective
> 3) Define a new JBoss Server and new JBoss Runtime with 6.x server adapter from JBoss Tools (using jboss-6.1.0.final)
> 4) Create an EJB Project (Targeted runtime: JBoss 6.x, EJB module version: 3.1, default options)
> 5) Click with right mouse button on the server, than select "Add and Remove...".
> 6) The EJB project on the left list. It is still possible to deploy the EJB project into the server (See image 0)
> 7) Create a Dynamic Web Project (default options)
> 8) Put the EJB project in the Deployement Assembly of the Dynamic Web Project (see image 1)
> 9) Click again with right mouse button on the server, than select "Add and Remove...".
> 10) The EJB project is no more present in the left list. It isn't possible to deploy the EJB project into the server (See image 2)
--
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, 3 months