April 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-8342) top-down ws does not honour user selected JAX-WS spec version

by Lukas Jungmann (JIRA)

top-down ws does not honour user selected JAX-WS spec version ------------------------------------------------------------- Key: JBIDE-8342 URL: https://issues.jboss.org/browse/JBIDE-8342 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.CR1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -register JBossAS 6 in the IDE -create new dynamic web module (version 3.0) -open new web service wizard -set the type to top down, use some arbitrary WSDL, press next -see that JAX-WS spec version is set to 2.0 -finish the wizard -open generated *Service.java file => generated file contains among others following constructor: public EchoWSService(WebServiceFeature ... features) { super(WSDL_LOCATION, SERVICE, features); } problem is that the WebServiceFeature class has been introduced in JAX-WS 2.1 hence the mismatch of the "user" selected JAX-WS version in the wizard - 2.0 - and the version of sources generated by wsconsume - they're actually of version 2.2 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6527) [tester] include prefixed namespace definition instead of anonymous one in generated SOAP message

by Lukas Jungmann (JIRA)

[tester] include prefixed namespace definition instead of anonymous one in generated SOAP message ------------------------------------------------------------------------------------------------- Key: JBIDE-6527 URL: https://jira.jboss.org/browse/JBIDE-6527 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick it would be maybe good to include prefixed namespace definition instead of anonymous one in generated SOAP message, in the other words generate: <ns1:GetSearchResults xmlns:ns1 = "http://www.ecubicle.net/webservices"/> instead of current <GetSearchResults xmlns = "http://www.ecubicle.net/webservices"/>. The reason for this change is that it is pretty common that child elements of the root element are usually from no namespace and if the root element contains anonymous namespace definition the inheritance rules will cause that child elements will be taken from that "anonymous" namespace too, which is wrong, ...unless user tweak it. [originally mentioned in JBIDE-6497] -- 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

14 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;

by Alexey Kazakov (JIRA)

No bean is eligible for @Inject BeanManager manager; ---------------------------------------------------- Key: JBIDE-8017 URL: https://issues.jboss.org/browse/JBIDE-8017 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 See the spec.: 11.3. The BeanManager object Portable extensions sometimes interact directly with the container via programmatic API call. The interface javax.enterprise.inject.spi.BeanManager provides operations for obtaining contextual references for beans, along with many other operations of use to portable extensions. The container provides a built-in bean with bean type BeanManager, scope @Dependent and qualifier @Default. The builtin implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies". Thus, any bean may obtain an instance of BeanManager by injecting it: @Inject BeanManager manager; -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
23
0 / 0

[JBoss JIRA] Created: (JBIDE-8578) Load beans from weld jars

by Alexey Kazakov (JIRA)

Load beans from weld jars ------------------------- Key: JBIDE-8578 URL: https://issues.jboss.org/browse/JBIDE-8578 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.Final Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M1, 3.2.0.CR1 Weld jars don't have beans.xml files so we have to load them in a special way. So far we load any jars which start with weld-* but it's not enough. Some jar files have names that don't match this mask. For example @Inject UserTransaction injects bean from arquillian-weld-ee-embaded-*.jar -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8726) CDI validator doesn't re-validate projects.

by Alexey Kazakov (JIRA)

CDI validator doesn't re-validate projects. ------------------------------------------- Key: JBIDE-8726 URL: https://issues.jboss.org/browse/JBIDE-8726 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.Final Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.2.1, 3.3.0.M1 1. Create any Java Project. 2. Enable CDI there. 3. Build the project. 4. Delete the project. 5. Create a new project with the same name. 6. Enable CDI. 7. Build/clean-up/re-build the project. CDI validator won't validate the project until Eclipse is not restarted. The reason of this issue is that WST doesn't initialize validation helpers if a new project with the old name is created. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8398) Remote redeployment fails if you switch from exploded to archive

by Andre Dietisheim (JIRA)

Remote redeployment fails if you switch from exploded to archive ---------------------------------------------------------------- Key: JBIDE-8398 URL: https://issues.jboss.org/browse/JBIDE-8398 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud, JBossAS Affects Versions: 3.2.0.CR2 (tentative) Reporter: Andre Dietisheim Assignee: Rob Stryker Priority: Minor how to reproduce: 1) have a AS server adapter for a remote server 2) have a WTP project added to it 3) make sure the server adapter is set to deploy as exploded war (2nd tab of the server adapter editor "Deploymen": checkbox "Deploy projects as compressed archives" not set 4) (ev. start the adapter) publish your project 5) check the checkbox "Deploy projects as..." 6) Choose "Full publish" on your project or "Clean" on the adapter in the servers view Result: Deployment fails, the console shows the following exception: failed to delete /opt/jboss-as6/server/default/deploy/gwt-helloworld.war org.eclipse.rse.services.files.RemoteFileIOException: Operation failed. File system input or output error at org.eclipse.rse.internal.services.ssh.files.SftpFileService.makeSystemMessageException(SftpFileService.java:449) at org.eclipse.rse.internal.services.ssh.files.SftpFileService.upload(SftpFileService.java:752) at org.jboss.ide.eclipse.as.rse.core.archives.RSEZippedJSTPublisher.publishModule(RSEZippedJSTPublisher.java:77) at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:77) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:67) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1025) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1115) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:948) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:775) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2889) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:337) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-6830) Cannot recreate a service created by the wizard

by Lukas Jungmann (JIRA)

Cannot recreate a service created by the wizard ----------------------------------------------- Key: JBIDE-6830 URL: https://jira.jboss.org/browse/JBIDE-6830 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -have a dynamic web project 1) create a sample web service in the project using default values in the wizard 2) delete created file 3) delete entries added to web.xml by the wizard 4) save all changes 5) create a sample web service using default values in the wizard again 6) open web.xml file => contains: <servlet> <display-name>HelloWorld</display-name> <servlet-name>HelloWorld</servlet-name> <servlet-class>org.jboss.samples.webservices.HelloWorld</servlet-class> </servlet> <servlet-mapping> <servlet-name>HelloWorld</servlet-name> <url-pattern>/HelloWorld</url-pattern> </servlet-mapping> <servlet> <display-name>HelloWorld1</display-name> <servlet-name>HelloWorld1</servlet-name> <servlet-class>org.jboss.samples.webservices.HelloWorld</servlet-class> </servlet> <servlet-mapping> <servlet-name>HelloWorld1</servlet-name> <url-pattern>/HelloWorld1</url-pattern> </servlet-mapping> but since we did step 3 it should contain only: <servlet> <display-name>HelloWorld1</display-name> <servlet-name>HelloWorld1</servlet-name> <servlet-class>org.jboss.samples.webservices.HelloWorld</servlet-class> </servlet> <servlet-mapping> <servlet-name>HelloWorld1</servlet-name> <url-pattern>/HelloWorld1</url-pattern> </servlet-mapping> 7) delete all created files from the project, remove servlet related entries from the web.xml and save all files 8) create a sample web service using "HelloWorld" as the web service name => see attached screenshot - web.xml is empty but wizard says that web.xml already contains servlet "HelloWorld" -- 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

14 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (JBIDE-8779) java.lang.NoClassDefFoundError in I18nValidator

by Alexey Kazakov (JIRA)

java.lang.NoClassDefFoundError in I18nValidator ----------------------------------------------- Key: JBIDE-8779 URL: https://issues.jboss.org/browse/JBIDE-8779 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: jsp/jsf/xml source editing Affects Versions: 3.3.0.M1 Reporter: Alexey Kazakov Assignee: Yahor Radtsevich 1. Create JSF 2 KickStart project. Got the following exception in eclipse log: java.lang.NoClassDefFoundError: org/jboss/tools/jsf/jsf2/model/JSF2ComponentModelManager at org.jboss.tools.jsf.web.validation.i18n.I18nValidator.validate(I18nValidator.java:91) at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704) at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665) at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669) at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299) at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:113) at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:65) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:75) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:111) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:95) at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219) at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178) at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.ClassNotFoundException: org.jboss.tools.jsf.jsf2.model.JSF2ComponentModelManager at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429) at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) ... 22 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-6919) [tester] uid/pwd is not passed to the server in GET requests

by Lukas Jungmann (JIRA)

[tester] uid/pwd is not passed to the server in GET requests ------------------------------------------------------------ Key: JBIDE-6919 URL: https://jira.jboss.org/browse/JBIDE-6919 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M2 Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick 1) Copy URL to URL field - https://svn.JBoss.org/repos/jbosstools 2) Set operation to GET 3) Hit invoke 4) When uid/pwd dialog appears use your SVN uid/pwd, click OK. => uid/pwd appears again and again until you press Cancel button Workaround is to use/check "Prompt for basic authentication" stting/checkbox -- 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

14 years, 11 months

2
18
0 / 0

[JBoss JIRA] Created: (JBIDE-8347) top down ws impl class should contain throws clause if it's present in generated ws interface

by Lukas Jungmann (JIRA)

top down ws impl class should contain throws clause if it's present in generated ws interface --------------------------------------------------------------------------------------------- Key: JBIDE-8347 URL: https://issues.jboss.org/browse/JBIDE-8347 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Reporter: Lukas Jungmann Assignee: Brian Fitzpatrick -have attached WSDL which defines operations with faults -create a web service in a web project from it => generated web service implementation class does not contain 'throws' clause for methods which do have it declared in generated SEI -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
16
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 April 2011