May 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8715) Support unwrapping producer methods (@Unwraps)

by Alexey Kazakov (JIRA)

Support unwrapping producer methods (@Unwraps) ---------------------------------------------- Key: JBIDE-8715 URL: https://issues.jboss.org/browse/JBIDE-8715 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x See http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/unwraps.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8685) Exceptions when creating JSF 1.2 Kickstart project.

by Alexey Kazakov (JIRA)

Exceptions when creating JSF 1.2 Kickstart project. --------------------------------------------------- Key: JBIDE-8685 URL: https://issues.jboss.org/browse/JBIDE-8685 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.M1 Environment: Eclipse Indigo Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M1 org.eclipse.core.commands.ExecutionException: Failed while installing JavaServer Faces 1.2. at org.eclipse.wst.common.componentcore.internal.operation.FacetProjectCreationOperation.execute(FacetProjectCreationOperation.java:110) at org.jboss.tools.jst.web.ui.operation.WebNatureOperation.createWTPNature2(WebNatureOperation.java:486) at org.jboss.tools.jst.web.ui.operation.WebNatureOperation.run(WebNatureOperation.java:246) at org.eclipse.ui.actions.WorkspaceModifyDelegatingOperation.execute(WorkspaceModifyDelegatingOperation.java:69) at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2310) at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1029) at org.jboss.tools.jst.web.ui.wizards.project.NewWebProjectWizard.performFinish(NewWebProjectWizard.java:66) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3568) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3189) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.actions.NewProjectAction.run(NewProjectAction.java:117) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3568) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3189) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) Caused by: org.eclipse.wst.common.project.facet.core.FacetedProjectFrameworkException: Failed while installing JavaServer Faces 1.2. at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1508) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:442) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1182) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1118) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:325) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2310) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:340) at org.eclipse.wst.common.componentcore.internal.operation.FacetProjectCreationOperation.execute(FacetProjectCreationOperation.java:83) ... 50 more Caused by: org.eclipse.jst.jsf.core.internal.project.facet.JSFFacetException: 'jsf12' : unable to configure web module for JavaServer Faces at org.eclipse.jst.jsf.core.internal.project.facet.JSFFacetInstallDelegate.execute(JSFFacetInstallDelegate.java:94) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1478) ... 57 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9045) Wrong OpenOn for <div> tag

by Daniel Azarov (JIRA)

Wrong OpenOn for <div> tag -------------------------- Key: JBIDE-9045 URL: https://issues.jboss.org/browse/JBIDE-9045 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.M1 Reporter: Daniel Azarov Assignee: Daniel Azarov Fix For: 3.3.0.M2 Attachments: DivOpenOn.png EXECUTE: Create Seam Web Project EXECUTE: Open home.xhtml EXECUTE: Type <div></div> EXECUTE: Ctrl+Click on <div> tag FAILURE: OpenOn window appears with s.tld and s.taglib.xml items -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8716) Support @DefaultBean

by Alexey Kazakov (JIRA)

Support @DefaultBean -------------------- Key: JBIDE-8716 URL: https://issues.jboss.org/browse/JBIDE-8716 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x If a default bean is installed and no other bean with the same type and qualifiers are installed, then the default bean should be used. But if there is some bean with the same type and qualifiers then we should ignore the default one when we resolve injection points. For instance we have two beans. One is annotated @DefaultBean and another one is a usual bean. So, IBeanManager.getBeans(true, injectionPoint) should return the usual bean but IBeanManager.getBeans(false, injectionPoint) should return both beans. Be aware that {quote} Any producer methods or producer fields declared on a default managed bean are automatically registered as default producers, with Method.getGenericReturnType() or Field.getGenericType() determining the type of the default producer. The default producer type can be overridden by specifying @DefaultBean on the producer method or field. {quote} See http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/defaultbe... for details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8717) Support service handlers

by Alexey Kazakov (JIRA)

Support service handlers ------------------------ Key: JBIDE-8717 URL: https://issues.jboss.org/browse/JBIDE-8717 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x We should be able to resolve injection points with types which use service handler facility. See http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/serviceha... for details. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8713) Support @MessageBundle

by Alexey Kazakov (JIRA)

Support @MessageBundle ---------------------- Key: JBIDE-8713 URL: https://issues.jboss.org/browse/JBIDE-8713 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x User can define an interface annotated @MessageBundle {code} @MessageBundle interface TrainMessages { @Message("No trains spotted to %s") String noTrainsSpotted(String cause); } {code} and then just inject the bean {code} @Inject @MessageBundle TrainMessages messages; {code} Seam Solder will create the bean programmaticlly. See http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/logging.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8712) Support @MessageLogger

by Alexey Kazakov (JIRA)

Support @MessageLogger ---------------------- Key: JBIDE-8712 URL: https://issues.jboss.org/browse/JBIDE-8712 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.x User can define an interface annotated @MessageLogger {code} @MessageLogger interface TrainSpotterLog { @LogMessage @Message("Spotted %s diesel trains") void dieselTrainsSpotted(int number); } {code} and then just inject the bean {code} @Inject @Category("trains") TrainSpotterLog log {code} Seam Solder will create the bean programmaticlly. See http://docs.jboss.org/seam/3/solder/latest/reference/en-US/html/logging.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8198) Support @Exact annotation

by Alexey Kazakov (JIRA)

Support @Exact annotation ------------------------- Key: JBIDE-8198 URL: https://issues.jboss.org/browse/JBIDE-8198 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.x 2.2. @Exact Annotating an injection point with @Exact allows you to select an exact implementation of the injection point type to inject. For example: interface PaymentService { ... } class ChequePaymentService implements PaymentService { ... } class CardPaymentService implements PaymentService { ... } class PaymentProcessor { @Inject @Exact(CardPaymentService.class) PaymentService paymentService; ... } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8200) Support @FullyQualified annotation

by Alexey Kazakov (JIRA)

Support @FullyQualified annotation ---------------------------------- Key: JBIDE-8200 URL: https://issues.jboss.org/browse/JBIDE-8200 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: cdi (jsr-299) Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.x 2.5. @FullyQualified bean names According to the CDI standard, the @Named annotation assigns a name to a bean equal to the value specified in the @Named annotation or, if a value is not provided, the simple name of the bean class. This behavior aligns is with the needs of most application developers. However, framework writers should avoid trampling on the "root" bean namespace. Instead, frameworks should specify qualified names for built-in components. The motivation is the same as qualifying Java types. The @FullyQualified provides this facility without sacrificing type-safety. Seam Solder allows you to customize the bean name using the complementary @FullyQualified annotation. When the @FullyQualified annotation is added to a @Named bean type, producer method or producer field, the standard bean name is prefixed with the name of the Java package in which the bean resides, the segments separated by a period. The resulting fully-qualified bean name (FQBN) replaces the standard bean name. package com.acme; @FullyQualified @Named public class NamedBean { public String getAge() { return 5; } } The bean in the previous code listing is assigned the name com.acme.namedBean. The value of its property age would be referenced in an EL expression (perhaps in a JSF view template) as follows: #{com.acme.namedBean.age} The @FullyQualified annotation is permitted on a bean type, producer method or producer field. It can also be used on a Java package, in which case all @Named beans in that package get a bean name which is fully-qualified. @FullyQualified package com.acme; If you want to use a different Java package as the namespace of the bean, rather than the Java package of the bean, you specify any class in that alternative package in the annotation value. package com.acme; @FullyQualified(ClassInOtherPackage.class) @Named public class CustomNamespacedNamedBean { ... } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9005) OpenOn on JSP tags works wrongly if project contains many jars with the same name

by Daniel Azarov (JIRA)

OpenOn on JSP tags works wrongly if project contains many jars with the same name --------------------------------------------------------------------------------- Key: JBIDE-9005 URL: https://issues.jboss.org/browse/JBIDE-9005 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.M1 Reporter: Daniel Azarov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M2 If project contains many jars with the same taglib and the same name OpenOn on JSP tags show one line for each jar. But every OpenOn menu items opens the same taglib from the same jar Test case: 1. Create JSF KickStart Project 2. Create WebContent/WEB-INF/lib2 folder 3. Copy jsf-tlds.jar from WebContent/WEB-INF/lib to WebContent/WEB-INF/lib2 4. Open hello.jsp in Visual Page Editor 5. Point mouse to f:view tag then press Ctrl key ASSERT: OpenOn windows appears 6. Select first item 'jsf-tlds.jar : jsf_core.tld : view' ASSERT: JBoss Tools Tag Library Editor appears for jsf-tlds.jar from WebContent/WEB-INF/lib folder 7. Select second item 'jsf-tlds.jar : jsf_core.tld : view' FAIL: JBoss Tools Tag Library Editor appears for jsf-tlds.jar from WebContent/WEB-INF/lib folder -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
4
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 May 2011