[JBoss JIRA] Created: (JBIDE-6334) Preferences to control DnD markers parameters like Color, What kind of markers to show and what colors should be used
by Denis Golovin (JIRA)
Preferences to control DnD markers parameters like Color, What kind of markers to show and what colors should be used
---------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6334
URL: https://jira.jboss.org/browse/JBIDE-6334
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core
Affects Versions: 3.2.0.M1
Reporter: Denis Golovin
Assignee: Yahor Radtsevich
Priority: Optional
Fix For: 3.2.0.M2, 3.2.next
DnD markers behavior should be explained somewhere and have preferences to control at least color, because at first sight I would prefer different color scheme. Red for possible positions and black for position where dropped element is going to be inserted.
Here option candidates:
1. Show Possible Drop Markers : Yes/No checkbox
2. Possible Drop Location Marker color: Color Chooser
3. Drop Location Marker Color
4. Highlight Drop Target Element: yes/No checkbox
5. Highlighted element Border color: Color Chooser
6. Highlighted element Background color: Color Chooser
7. Highlighting Transparency: 50-100%
--
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, 7 months
[JBoss JIRA] (JBIDE-12402) Ambiguous EL names in case of producers of alternative bean classes
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12402:
--------------------------------------
Summary: Ambiguous EL names in case of producers of alternative bean classes
Key: JBIDE-12402
URL: https://issues.jboss.org/browse/JBIDE-12402
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.Final
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.4.0.M1
See the example from https://github.com/pmuir/jboss-as-developer-guide/tree/master/quickstarts
There is org.jboss.as.quickstarts.login.EJBUserManager:
{code:title=org.jboss.as.quickstarts.login.EJBUserManager|borderStyle=solid}
...
@Named("userManager")
@RequestScoped
@Alternative
@Stateful
public class EJBUserManager implements UserManager {
...
@Produces
@Named
@RequestScoped
public List<User> getUsers() throws Exception {
...
}
...
}
{code}
And there is also another bean org.jboss.as.quickstarts.login.ManagedBeanUserManager:
{code:title=org.jboss.as.quickstarts.login.ManagedBeanUserManager|borderStyle=solid}
...
@Named("userManager")
@RequestScoped
public class ManagedBeanUserManager implements UserManager {
@SuppressWarnings("unchecked")
@Produces
@Named
@RequestScoped
public List<User> getUsers() throws Exception {
...
}
...
}
{code}
We have two beans with EL name #{users}
Try to inject it in some bean:
@Inject List<User> users;
There is a warning about ambiguous beans that is not correct.
See WELD-930 for details.
--
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, 7 months
[JBoss JIRA] (JBIDE-12518) JBDS shows "false" "no bean is eligible" warnings for WELD
by Shay Matasaro (JIRA)
Shay Matasaro created JBIDE-12518:
-------------------------------------
Summary: JBDS shows "false" "no bean is eligible" warnings for WELD
Key: JBIDE-12518
URL: https://issues.jboss.org/browse/JBIDE-12518
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Shay Matasaro
JBDS shows WELD "no bean is eligible"
warnings that are not correct in the following situations:
1) Taking Class A and Class B, and where B is marked as @Alternative , and injected into A.
2) @Parameters String[] paramsArray
3) @Inject BoundRequestContext boundRequestContext;
4) @Inject BoundSessionContext boundSessionContext;
--
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, 7 months
[JBoss JIRA] (JBIDE-12436) False validation problem for elements annotated @SuppressWarnings
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12436:
--------------------------------------
Summary: False validation problem for elements annotated @SuppressWarnings
Key: JBIDE-12436
URL: https://issues.jboss.org/browse/JBIDE-12436
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 3.4.0.M1
Reporter: Alexey Kazakov
Assignee: Victor Rubezhny
Fix For: 3.4.0.M1
1. Create a cdi project.
2. Create the following class:
{code}
public class TestNamed {
@SuppressWarnings("cdi-ambiguous-dependency")
@Inject String s; // Ambiguous
@Produces
public String foo1;
@Produces
public String foo2;
}
{code}
3. Change "cdi-ambiguous-dependency" to "xyz"
4. There is a warning on @Inject
5. Change "xyz" to "cdi-ambiguous-dependency" back (don't save the file!)
6. There is still the same warning on @Inject. This is a bug.
7. Edit @Inject String s -> @Inject String ss
8. There is no warning any more on @Inject
--
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, 7 months
[JBoss JIRA] (JBIDE-12503) CDI Bean types are not updated
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12503:
--------------------------------------
Summary: CDI Bean types are not updated
Key: JBIDE-12503
URL: https://issues.jboss.org/browse/JBIDE-12503
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: CDI
Affects Versions: 4.0.0.M1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 4.0.0.M1
1. Create the following types:
{code}
package cditest;
import javax.enterprise.inject.Typed;
@Typed(LocalTest.class)
public class NewTest implements LocalExtendedTest {
}
{code}
{code}
package cditest;
public interface LocalTest {
}
{code}
{code}
package cditest;
public interface LocalExtendedTest {
}
{code}
2. Build the project.
3. There is a validation problem on NewTest bean since @Typed is not correct
4. Edit LocalExtendedTest.java:
{code}
package cditest;
public interface LocalExtendedTest extends LocalTest {
}
{code}
5. Save the file.
6. FAILURE: NewTest in not re-validated and the error is not gone.
--
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, 7 months
[JBoss JIRA] (JBIDE-12417) KB validators should report problems in order as they appears in the file.
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12417:
--------------------------------------
Summary: KB validators should report problems in order as they appears in the file.
Key: JBIDE-12417
URL: https://issues.jboss.org/browse/JBIDE-12417
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI, common/jst/core, JSF
Affects Versions: 3.3.1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 3.4.0.M1
1. Create a cdi project.
2. Create the following bean 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}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}" +
#{string.ss}";
}
@Named
@Produces
public String string() {
return "";
}
}
{code}
3. Save the file.
4. By default JBT will report only 20 problems. But it should be the first 20 problems. Now it's a random. It may be any 20 of all the problem.
The same problem for JSF and CDI validators.
--
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, 7 months