January 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8193) Mavenized new Seam web project cannot be built

by Libor Zoubek (JIRA)

Mavenized new Seam web project cannot be built ---------------------------------------------- Key: JBIDE-8193 URL: https://issues.jboss.org/browse/JBIDE-8193 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.2.0.CR1 Reporter: Libor Zoubek Assignee: Snjezana Peco -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-138) All links to images are broken in nightly-docs

by Yahor Radtsevich (JIRA)

All links to images are broken in nightly-docs ---------------------------------------------- Key: TOOLSDOC-138 URL: https://issues.jboss.org/browse/TOOLSDOC-138 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: General documentation issues Reporter: Yahor Radtsevich Assignee: Isaac Rooskov When I open any (html) or (html single) from http://download.jboss.org/jbosstools/nightly-docs/ , I do not see any images there. Just one example from http://download.jboss.org/jbosstools/nightly-docs/en/jsf/html_single/inde... : Figure 3.42. Visual Page Editor links to file:/mnt/hudson_workspace/workspace/jbosstools-docs-nightly/jsf/docs/userguide/target/docbook/staging/images/images/visual_page/visual_page_1.png -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7832) there is a error report for ws topdown that is not required

by Feng Qian (JIRA)

there is a error report for ws topdown that is not required ----------------------------------------------------------- Key: JBIDE-7832 URL: https://jira.jboss.org/browse/JBIDE-7832 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.Beta1 Environment: windows Reporter: Feng Qian Assignee: Feng Qian Fix For: 3.2.0.CR1 when use ws module to generate web service from a wsdl, if you use jre, not jdk, there is a error report: [ERROR] com.sun.tools.javac.Main is not available in the classpath, requires Suns JDK version 5.0 or latter. unknown location compilation failed, errors should have been reported Failed to invoke WsImport java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:220) at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:223) at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:81) This is caused by ws runtime, which need jdk to complie these codes, but in jboss tools, we don't need ws runtime to compile. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7925) web service client sample java file has a error when using a wsdl that uses a primitive type as parameter of a wsdl operation to generate client

by Lukas Jungmann (JIRA)

web service client sample java file has a error when using a wsdl that uses a primitive type as parameter of a wsdl operation to generate client ------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7925 URL: https://issues.jboss.org/browse/JBIDE-7925 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Reporter: Lukas Jungmann Assignee: Feng Qian -create a ws client from http://footballpool.dataaccess.eu/data/info.wso?WSDL => generated ClientSample.java class is uncompilable - 'null' argument is generated even for methods requiring primitive type (ie int) argument related to JBIDE-5022 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBIDE-7776) CDI tools core doesn't take into account disabled beans while resolving beans.

by Alexey Kazakov (JIRA)

CDI tools core doesn't take into account disabled beans while resolving beans. ------------------------------------------------------------------------------ Key: JBIDE-7776 URL: https://jira.jboss.org/browse/JBIDE-7776 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.CR1 5.1.2. Enabled and disabled beans A bean is said to be enabled if: • it is deployed in a bean archive, and • it is not a producer method or field of a disabled bean, and • it is not specialized by any other enabled bean, as defined in Section 4.3, "Specialization", and either • it is not an alternative, or it is a selected alternative of at least one bean archive. org.jboss.tools.cdi.core.test.tck.ResolutionByNameTest.testAmbiguousELNamesResolved() should pass. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7952) NullPointerException in CDI validator for @Injection

by Alexey Kazakov (JIRA)

NullPointerException in CDI validator for @Injection ---------------------------------------------------- Key: JBIDE-7952 URL: https://issues.jboss.org/browse/JBIDE-7952 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.CR1 1. If @Injection resolves to the only class which is from jar then the following NPE is thrown: org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInjectionPoint(CDICoreValidator.java:1337) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7955) EL validation doesn't work in projects without JBT JSF nature.

by Alexey Kazakov (JIRA)

EL validation doesn't work in projects without JBT JSF nature. -------------------------------------------------------------- Key: JBIDE-7955 URL: https://issues.jboss.org/browse/JBIDE-7955 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.0.CR1 1. Create Dynamic Web Project with JSF facet. 2. Enable CDI on this project. 3. Add some @Named bean (for example @Named("foo)) 4. Create any xhtml/jsp 5. Try to use wrong property in #{foo.wrongProperty} in the page 6. Save the page. Validation should work. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7932) New Seam EAR project fails to deploy to JBoss AS 6 CR1

by Jozef Hartinger (JIRA)

New Seam EAR project fails to deploy to JBoss AS 6 CR1 ------------------------------------------------------ Key: JBIDE-7932 URL: https://issues.jboss.org/browse/JBIDE-7932 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.Beta2 Environment: Linux 64bit JDK 1.6.0_23 JBoss Tools 3.2.0 Beta 2 (20101206) Seam 2.2.1.CR2 Reporter: Jozef Hartinger Assignee: Alexey Kazakov Priority: Critical Steps to reproduce: 1) Unzip JBoss AS 6 CR1 2) Add the server to JBoss Tools 3) Create new Seam 2.2 project (select EAR project and either HSQLDB or MySQL) 4) Start the application server 5) An exception is thrown during deployment of the project (see the attached file for the stacktrace) Note that an WAR project deploys without problems. Also, and EAR or WAR project generated via seam-gen works as expected. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

7
25
0 / 0

[JBoss JIRA] Created: (JBIDE-8019) Injection point is not resolved to producer from jar.

by Alexey Kazakov (JIRA)

Injection point is not resolved to producer from jar. ----------------------------------------------------- Key: JBIDE-8019 URL: https://issues.jboss.org/browse/JBIDE-8019 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.CR1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.2.0.CR1 1. Project A has weld-se-core-1.1.0.Beta1-sources.jar in its class path. 2. weld-se-core-1.1.0.Beta1-sources.jar has ParametersFactory.class: @Produces @Parameters public List<String> getArgs() { return argsList; } and Parameters.class: @Qualifier @Retention(RUNTIME) @Target({ PARAMETER, METHOD, FIELD, TYPE }) public @interface Parameters {} 3. Project A also has the following class: public class ShellImpl { @Inject @Parameters private List<String> parameters; } 4. But private List<String> parameters; is not resolved to getArgs() producer. This example is from froge-shell (seam-forge) project. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7747) JBossWS errors on B2

by Max Andersen (JIRA)

JBossWS errors on B2 -------------------- Key: JBIDE-7747 URL: https://jira.jboss.org/browse/JBIDE-7747 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.Beta2 Reporter: Max Andersen Assignee: Brian Fitzpatrick Fix For: 3.2.0.Beta2, 3.2.0.CR1 JBossWS tests seem to fail because of URI not being valid; maybe tests are assuming plugins are exploded on disk but aren't when actually packaged up and run !? see http://hudson.qa.jboss.com/hudson/view/DevStudio_Stable_Branch/portlet/da... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
6
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 2011