September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15520) Clean UI and Core dependencies

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15520?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15520: ---------------------------------- Description: Move all *.ui.* dependencies from jaxrs.core to jaxrs.ui (was: Move all *.ui.* dependencies from livereload.core to livereload.ui) > Clean UI and Core dependencies > ------------------------------ > > Key: JBIDE-15520 > URL: https://issues.jboss.org/browse/JBIDE-15520 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha1 > > > Move all *.ui.* dependencies from jaxrs.core to jaxrs.ui -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-166) Deploying BPEL project to a server is not working

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-166?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-166: ------------------------------------ Description: This bug was moved from JBIDE (from version 3.3) and is still present. The problem is as follows: Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS. You need to install JBoss AS feature from JBT Core update site. Note that this doesn't happen in JBDS (there already is the AS plugin). Without explicit installing AS plugin I'm getting two erros (when starting the server and when trying to deploy bpel project). See the attachments. Original description: Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. In JBDS 4 and 5 it works fine for both adapters. was: This bug was moved from JBIDE (from version 3.3) and is still present. So, what's the problem? Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS. You need to install JBoss AS feature from JBT Core update site. Note that this doesn't happen in JBDS (there already is the AS plugin). Without explicit installing AS plugin I'm getting two erros (when starting the server and when trying to deploy bpel project). See the attachments. Original description: Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. In JBDS 4 and 5 it works fine for both adapters. > Deploying BPEL project to a server is not working > ------------------------------------------------- > > Key: JBTIS-166 > URL: https://issues.jboss.org/browse/JBTIS-166 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL > Affects Versions: 4.1.2 > Environment: Eclipse 3.7.2 + JBoss AS 5.1.0 + RiftSaw 2.3.0 > Reporter: Andrej Podhradsky > Assignee: Robert (Bob) Brodt > Priority: Critical > Attachments: deploying_as51.log, deploying_as51.png, running_as51.log, running_as51.png > > > This bug was moved from JBIDE (from version 3.3) and is still present. The problem is as follows: > Installing the BPEL feature from JBTIS 4.1.2 update site is not enough for full working with BPEL and JBoss AS. > You need to install JBoss AS feature from JBT Core update site. Note that this doesn't happen in JBDS (there already is the AS plugin). > Without explicit installing AS plugin I'm getting two erros (when starting the server and when trying to deploy bpel project). > See the attachments. > Original description: > Deploying BPEL project to a server, which is created using JBoss AS 5.1 adapter, is not working - it seems that nothing happens. > But if I try to deploy the same project to a server created using JBoss Application Platform 5.x, it works fine. > In JBDS 4 and 5 it works fine for both adapters. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15518) Add to CDI model extensions provided without extension service

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-15518: --------------------------------------------- Summary: Add to CDI model extensions provided without extension service Key: JBIDE-15518 URL: https://issues.jboss.org/browse/JBIDE-15518 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi, cdi-extensions Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.2.0.Alpha1 CDI 1.1 specification recommends to register extensions in META-INF/services/javax.enterprise.inject.spi.Extension. However, Weld implementation and Wildfly choose to add extensions directly, without service. Now we find only extensions registered in service. We have to add 'hardcoded' extensions as well. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15507) Support injection of JMSContext

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15507?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15507: ---------------------------------------- It seems that wildfly use its internatl API to register JMSContext bean. See https://issues.jboss.org/browse/WFLY-1286 + PR https://github.com/wildfly/wildfly/pull/4841/files > Support injection of JMSContext > ------------------------------- > > Key: JBIDE-15507 > URL: https://issues.jboss.org/browse/JBIDE-15507 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdi, cdi-extensions > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > if I try to inject a JMSContext (part of JMS 2.0 in JavaEE7) into a bean (CDI bean or EJB): > @Inject > JMSContext context; > I get the following warning: "No bean is eligible for injection to the injection point [JSR-299 §5.2.1]". > Yet, there's no problem when I deploy the application on Wildfly (8.0.0.Alpha4, the latest release so far) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15507) Support injection of JMSContext

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15507?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-15507 at 9/24/13 7:27 PM: ----------------------------------------------------------------- It seems that wildfly uses its internal API to register JMSContext bean. See https://issues.jboss.org/browse/WFLY-1286 + PR https://github.com/wildfly/wildfly/pull/4841/files was (Author: akazakov): It seems that wildfly use its internatl API to register JMSContext bean. See https://issues.jboss.org/browse/WFLY-1286 + PR https://github.com/wildfly/wildfly/pull/4841/files > Support injection of JMSContext > ------------------------------- > > Key: JBIDE-15507 > URL: https://issues.jboss.org/browse/JBIDE-15507 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdi, cdi-extensions > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > if I try to inject a JMSContext (part of JMS 2.0 in JavaEE7) into a bean (CDI bean or EJB): > @Inject > JMSContext context; > I get the following warning: "No bean is eligible for injection to the injection point [JSR-299 §5.2.1]". > Yet, there's no problem when I deploy the application on Wildfly (8.0.0.Alpha4, the latest release so far) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15507) Support injection of JMSContext

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15507?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-15507 at 9/24/13 7:28 PM: ----------------------------------------------------------------- It seems that wildfly uses its internal API to register JMSContext bean. See WFLY-1286 + PR https://github.com/wildfly/wildfly/pull/4841/files was (Author: akazakov): It seems that wildfly uses its internal API to register JMSContext bean. See https://issues.jboss.org/browse/WFLY-1286 + PR https://github.com/wildfly/wildfly/pull/4841/files > Support injection of JMSContext > ------------------------------- > > Key: JBIDE-15507 > URL: https://issues.jboss.org/browse/JBIDE-15507 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdi, cdi-extensions > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > if I try to inject a JMSContext (part of JMS 2.0 in JavaEE7) into a bean (CDI bean or EJB): > @Inject > JMSContext context; > I get the following warning: "No bean is eligible for injection to the injection point [JSR-299 §5.2.1]". > Yet, there's no problem when I deploy the application on Wildfly (8.0.0.Alpha4, the latest release so far) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15507) Support injection of JMSContext

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15507?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-15507 at 9/24/13 5:33 PM: ------------------------------------------------------------------------ Project wildfly-messaging has producer method org.jboss.as.messaging.deployment.JMSContextProducer.getJMSContext(InjectionPoint) that produces bean JMSContext. However, JBoss Tools CDI model cannot detect this bean because wildfly-messaging has in classpath CDI API of 1.1 version and has no beans.xml, which makes bean archive wildfly-messaging an implicit bean archive by CDI 1.1 spec, hence only beans in managed bean classes with scope annotations are to be detected. Class JMSContextProducer has no explicit scope annotation. Have I misunderstood bean detection? How this producer is detected by CDI runtime 1.1? was (Author: scabanovich): Project wildfly-messaging has producer method org.jboss.as.messaging.deployment.JMSContextProducer.getJMSContext(InjectionPoint) that produces bean JMSContext. However, JBoss Tools CDI model cannot detect this bean because wildfly-messaging has in classpath CDI API of 1.1 version and has no beans.xml, which makes bean archive wildfly-messaging an implicit bean archive by CDI 1.1 spec, hence only beans in managed bean classes with scope annotations are to be detected. Have I misunderstood bean detection? How this producer is detected by CDI runtime 1.1? > Support injection of JMSContext > ------------------------------- > > Key: JBIDE-15507 > URL: https://issues.jboss.org/browse/JBIDE-15507 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdi, cdi-extensions > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > if I try to inject a JMSContext (part of JMS 2.0 in JavaEE7) into a bean (CDI bean or EJB): > @Inject > JMSContext context; > I get the following warning: "No bean is eligible for injection to the injection point [JSR-299 §5.2.1]". > Yet, there's no problem when I deploy the application on Wildfly (8.0.0.Alpha4, the latest release so far) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15507) Support injection of JMSContext

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15507?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-15507: ----------------------------------------------- Project wildfly-messaging has producer method org.jboss.as.messaging.deployment.JMSContextProducer.getJMSContext(InjectionPoint) that produces bean JMSContext. However, JBoss Tools CDI model cannot detect this bean because wildfly-messaging has in classpath CDI API of 1.1 version and has no beans.xml, which makes bean archive wildfly-messaging an implicit bean archive by CDI 1.1 spec, hence only beans in managed bean classes with scope annotations are to be detected. Have I misunderstood bean detection? How this producer is detected by CDI runtime 1.1? > Support injection of JMSContext > ------------------------------- > > Key: JBIDE-15507 > URL: https://issues.jboss.org/browse/JBIDE-15507 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdi, cdi-extensions > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > if I try to inject a JMSContext (part of JMS 2.0 in JavaEE7) into a bean (CDI bean or EJB): > @Inject > JMSContext context; > I get the following warning: "No bean is eligible for injection to the injection point [JSR-299 §5.2.1]". > Yet, there's no problem when I deploy the application on Wildfly (8.0.0.Alpha4, the latest release so far) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15494) Software/Update page - Cannot create temporary directory

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15494?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15494: --------------------------------------------- Bug is now public at https://bugs.openjdk.java.net/browse/JDK-8025128 > Software/Update page - Cannot create temporary directory > -------------------------------------------------------- > > Key: JBIDE-15494 > URL: https://issues.jboss.org/browse/JBIDE-15494 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Final, 4.1.1.Alpha1 > Reporter: Radim Hopp > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.1.1.Alpha2 > > > Recently, Software/Update page of JBoss Central stopped working (No Connectors Found). > Error log: > {noformat} > Cannot download bundle at http://download.jboss.org/jbosstools/updates/development/kepler/plugins/o...: Unable to create temporary file > {noformat} > {noformat} > a.io.IOException: Unable to create temporary file > at java.io.File$TempDirectory.generateFile(File.java:1891) > at java.io.File.createTempFile(File.java:1979) > at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:217) > at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > {noformat} > This issue affects both JBDS and JBT, both not only in 7.1.0 (4.1.1) but also in 7.0.0.Final (4.1.0.Final), thus it's marked as blocker. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15499: --------------------------------------------- "if some other client adds other operations, DND won't work" ...do you mean if a third client does it will break or if just we do it ? could we just override mpc and if mpc is installed delegate to its install mechanism ? (but this is definitely starting to be a "dirty" hack :/ ) > Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15499 > URL: https://issues.jboss.org/browse/JBIDE-15499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds. > Similar to eclipse marketplace for marketplace urls something like: > * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or > * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra... > would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e" > This would allow drag'n'drop install from html docs. > Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing. -- 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

12 years, 7 months

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 September 2013