August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2716) NoClassDefFoundError: javax/servlet/http/HttpServletRequest after importing getting-started WFK Spring example

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBDS-2716?page=com.atlassian.jira.plugin.... ] Jiri Peterka updated JBDS-2716: ------------------------------- Attachment: spring-internal-error.png > NoClassDefFoundError: javax/servlet/http/HttpServletRequest after importing getting-started WFK Spring example > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2716 > URL: https://issues.jboss.org/browse/JBDS-2716 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rdPartyDependencies > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64 > Reporter: Jiri Peterka > Fix For: 7.0.1.GA > > Attachments: spring-internal-error.png > > > IDE reports error after importing getting-started spring wfk 2.3 demo project. Expecting this error is more general, not only this project specific. > {code} > java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) > at java.lang.Class.getDeclaredMethods(Class.java:1793) > at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:130) > at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:109) > at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:87) > at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:259) > at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:86) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:749) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:742) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:626) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:585) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:451) > at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at java.lang.ClassLoader.loadClass(ClassLoader.java:247) > ... 23 more > {code} -- 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] (JBDS-2716) NoClassDefFoundError: javax/servlet/http/HttpServletRequest after importing getting-started WFK Spring example

by Jiri Peterka (JIRA)

Jiri Peterka created JBDS-2716: ---------------------------------- Summary: NoClassDefFoundError: javax/servlet/http/HttpServletRequest after importing getting-started WFK Spring example Key: JBDS-2716 URL: https://issues.jboss.org/browse/JBDS-2716 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyDependencies Affects Versions: 7.0.0.GA Environment: JBDS 7.0.0.GA, L64 Reporter: Jiri Peterka Fix For: 7.0.1.GA IDE reports error after importing getting-started spring wfk 2.3 demo project. Expecting this error is more general, not only this project specific. {code} java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2436) at java.lang.Class.getDeclaredMethods(Class.java:1793) at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:130) at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:109) at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:87) at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:259) at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:86) at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:749) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:742) at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:626) at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:585) at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:451) at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) ... 23 more {code} -- 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-15356) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auo-regenerated composite*.xml files

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15356: ---------------------------------- Summary: Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auo-regenerated composite*.xml files Key: JBIDE-15356 URL: https://issues.jboss.org/browse/JBIDE-15356 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite Affects Versions: 4.1.0.Final Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.2.0.Alpha1 Be it proposed: {quote} that instead of an in-place move which reuses generic folder names like "staging" and "staging.previous", we composite build output using unique names like 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 {quote} We therefore need: a) to regenerate the composite site each time there's a new build published, in order to remove the oldest and add the newest (keeping only the Nth and N-1rst builds) (I have a script that might already work for this, or would need tweaking.) b) heuristics to determine when an older (N-2, N-3, ... N-z) build is no longer needed, perhaps simply by assuming no one needs it after 24hrs? 24 hours should be more that enough. c) a cleanup script which can purge all but the builds which are no more than 1 day old, keeping at all times at least two builds (N and N-1) (I have a script that already does this for folders like http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but might need to be tweaked to work for a new pattern of staging/${JOB_NAME}/<BUILD_ID>/ .) {quote} -- 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] (JBDS-2715) provide script & instructions for performing headless commandline installations of JBDS

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2715: -------------------------------- Summary: provide script & instructions for performing headless commandline installations of JBDS Key: JBDS-2715 URL: https://issues.jboss.org/browse/JBDS-2715 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 7.0.0.GA Reporter: Nick Boldt Assignee: Nick Boldt Script for linux: https://gist.github.com/nickboldt/6041754 Need a windows version & then to provide this somewhere along w/ the JBDS installer, perhaps on the CSP / EA pages? -- 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-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-141?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-141: ---------------------------------- PRs to move from /development/ to /stable/ URLs for ESB, now that it's released (trivial fix): https://github.com/jbosstools/jbosstools-integration-stack/pull/82 (master) https://github.com/jbosstools/jbosstools-integration-stack/pull/83 (40x branch) > fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb > ----------------------------------------------------------------------------- > > Key: JBTIS-141 > URL: https://issues.jboss.org/browse/JBTIS-141 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, ESB, jBPM3 > Affects Versions: 4.0.0, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.2, 4.1.2 > > > Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. > Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- 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-138) wrong target name attribute in core-base.target

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-138?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-138: ---------------------------------- Surely it's 4.1.3.Final? :D > wrong target name attribute in core-base.target > ----------------------------------------------- > > Key: JBTIS-138 > URL: https://issues.jboss.org/browse/JBTIS-138 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Trivial > > Both of these files [1], [2] use the same name attribute, which might confuse a user when they import the .target files into Eclipse. > {code}<target name="integration-stack-base-target">{code} > [1] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... > [2] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... -- 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-15355) The JBoss Central quickstarts should include the .html version of the readme files.

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-15355: ----------------------------------- Summary: The JBoss Central quickstarts should include the .html version of the readme files. Key: JBIDE-15355 URL: https://issues.jboss.org/browse/JBIDE-15355 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Reporter: Burr Sutter The helloworld quickstart on JBoss Central offers the end-user a readme.md - which is not easily readable by the average human. It includes a phrase that looks like If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. The JBoss Central quickstarts should include the .html version of the readme files. -- 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-15342) use latest parent pom & target platform so we can release ESB tooling v 1.5.300.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15342?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-15342. ------------------------------ Based on comments in JBIDE-15345 (https://issues.jboss.org/browse/JBIDE-15345?focusedCommentId=12797613&pag... ), I've pushed the 1.5.300 bits into this URL too: http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st... If that's in error, please let me know ASAP so I can revert. > use latest parent pom & target platform so we can release ESB tooling v 1.5.300.Final > ------------------------------------------------------------------------------------- > > Key: JBIDE-15342 > URL: https://issues.jboss.org/browse/JBIDE-15342 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: esb > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Brian Fitzpatrick > Fix For: 4.1.1.Final > > > Root pom should reference the latest final parent pom (4.1.0.Final-SNAPSHOT) instead of 4.1.0.CR1-SNAPSHOT. > Target platform referenced should be the Kepler version (4.1.1.Final) rather than the Juno version (4.0.0). > Once that's fixed and the build is blue, we should release ESB tooling v 1.5.300.Final and include it in the latest JBTIS 4.1.0 / 4.1.1 aggregate site builds. -- 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-15345) use latest parent pom & target platform so we can release ESB tooling v 1.5.200.Final

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15345?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-15345. ------------------------------ http://download.jboss.org/jbosstools/updates/stable/juno/integration-stac... is released. \o/ > use latest parent pom & target platform so we can release ESB tooling v 1.5.200.Final > ------------------------------------------------------------------------------------- > > Key: JBIDE-15345 > URL: https://issues.jboss.org/browse/JBIDE-15345 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: esb > Affects Versions: 4.0.1.Final > Reporter: Nick Boldt > Assignee: Brian Fitzpatrick > Fix For: 4.0.2.Final > > > Target platform referenced should be the latest Juno version (4.0.1.Final) rather than the 4.0.0-SNAPSHOT one. > Once that's fixed and the build is blue, we should release ESB tooling v 1.5.200.Final and include it in the latest JBTIS 4.0.x aggregate site builds. -- 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-138) wrong target name attribute in core-base.target

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-138?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-138: ---------------------------------- Missed 4.1.2.Final w/ this fix. It's checked in but don't know the future rev that it will belong to. > wrong target name attribute in core-base.target > ----------------------------------------------- > > Key: JBTIS-138 > URL: https://issues.jboss.org/browse/JBTIS-138 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Trivial > > Both of these files [1], [2] use the same name attribute, which might confuse a user when they import the .target files into Eclipse. > {code}<target name="integration-stack-base-target">{code} > [1] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... > [2] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... -- 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 August 2013