August 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-811) Build Archive is synchronous?

by Petr Lindovsky (JIRA)

Build Archive is synchronous? ----------------------------- Key: JBIDE-811 URL: http://jira.jboss.com/jira/browse/JBIDE-811 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta3 Reporter: Petr Lindovsky When I invoke the Build Archive command on an EAR archive in the Project archives view, I don't see any progress of this task and don't see when it is finished. Eclipse just seems to freeze for a couple of seconds, which suggests that the build is synchronous, not run in background. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-826) Two wb-resources: Run on Server doesn't work with JBoss AS runtime

by Petr Lindovsky (JIRA)

Two wb-resources: Run on Server doesn't work with JBoss AS runtime ------------------------------------------------------------------ Key: JBIDE-826 URL: http://jira.jboss.com/jira/browse/JBIDE-826 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta3 Environment: Windows XP Reporter: Petr Lindovsky I have a Web project (the first attachment in http://jira.jboss.org/jira/browse/JBIDE-812 ) created in Europa and based on a JBoss 4.0 runtime supplied with Europa. If I invoke Run As > Run on Server in Europa, it works correctly. The same project - but migrated to RDHS (that is, using JBoss AS 4.0 runtime supplied with RDHS) - is in the second attachment. If I invoke Run As > Run on Server there, the project isn't correctly deployed. The problem is that the project has two wb-resource elements in .settings\org.jboss.tools.jst.web.xml, and in RDHS, the element ui/resources is simply not deployed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-705) Running the default seam project's startup page causes redirecting exceptions

by Marshall Culpepper (JIRA)

Running the default seam project's startup page causes redirecting exceptions ----------------------------------------------------------------------------- Key: JBIDE-705 URL: http://jira.jboss.com/jira/browse/JBIDE-705 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.Beta3 Reporter: Marshall Culpepper This issue happens under the following configurations (haven't tested any more yet): - JBossAS 4.2.0.GA + Seam 1.3.0.ALPHA - JBossAS 4.2.1.GA + Seam 2.0.0.BETA1 When I deploy a freshly created Seam project to JBoss (our adapter), the deployment happens under JBoss correctly, but when Eclipse's internal browser attempts to load the main page of the Seam application, I get the following exception repeated until the Tomcat stops the execution to avoid stack overflow: 11:55:42,551 ERROR [ExceptionFilter] exception root cause 11:55:42,555 ERROR [DebugPageHandler] redirecting to debug page javax.servlet.ServletException: Servlet execution threw an exception at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:313) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:87) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:63) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:46) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:127) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:277) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:63) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:140) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NoClassDefFoundError: org/jboss/el/lang/EvaluationContext at org.jboss.seam.jsf.SeamApplication.getExpressionFactory(SeamApplication.java:344) at com.sun.facelets.compiler.Compiler.createExpressionFactory(Compiler.java:131) at com.sun.facelets.impl.DefaultFaceletFactory.createFacelet(DefaultFaceletFactory.java:198) at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(DefaultFaceletFactory.java:144) at org.jboss.seam.debug.jsf.SeamDebugPhaseListener.beforePhase(SeamDebugPhaseListener.java:44) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:222) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) ... 34 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-847) New VPE Templates for new Cumponents in RichFaces 3.1

by Alexey Kazakov (JIRA)

New VPE Templates for new Cumponents in RichFaces 3.1 ----------------------------------------------------- Key: JBIDE-847 URL: http://jira.jboss.com/jira/browse/JBIDE-847 Project: JBoss Tools Issue Type: Feature Request Components: Visual Page Editor Affects Versions: 2.0.0.Beta3 Reporter: Alexey Kazakov Assigned To: Sergey Vasilyev You can find list of new components: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=116231 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-747) Shutdown Jboss AS - console Output stops to early

by Perry Rhodan (JIRA)

Shutdown Jboss AS - console Output stops to early ------------------------------------------------- Key: JBIDE-747 URL: http://jira.jboss.com/jira/browse/JBIDE-747 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta3 Reporter: Perry Rhodan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-797) NullPointerException in ArchivesBuilder

by Rob Stryker (JIRA)

NullPointerException in ArchivesBuilder --------------------------------------- Key: JBIDE-797 URL: http://jira.jboss.com/jira/browse/JBIDE-797 Project: JBoss Tools Issue Type: Bug Components: Archives Reporter: Rob Stryker NullPointerException in archives builder when getDelta(IProject) returns null. http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075203#4075203 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-483) Change text/messaging on WAR wizard

by Marshall Culpepper (JIRA)

Change text/messaging on WAR wizard ----------------------------------- Key: JBIDE-483 URL: http://jira.jboss.com/jira/browse/JBIDE-483 Project: JBoss Tools Issue Type: Bug Components: JBossAS Adapter Reporter: Marshall Culpepper Assigned To: Rob Stryker -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-710) Legal

by Denis Golovin (JIRA)

Legal ------ Key: JBIDE-710 URL: http://jira.jboss.com/jira/browse/JBIDE-710 Project: JBoss Tools Issue Type: Bug Reporter: Denis Golovin Assigned To: Max Andersen 1. EXECUTE: Select Help->About Red Hat Developer Studio 2. EXECUTE: Press 'Plug-in Details' button 3. EXECUTE: Select org.jboss.ide.eclipse.core plugin 4. ASSERT: Button 'Legal Info' is enabled It is always disabled 5. EXECUTE: Select org.jboss. tools.common.kb plugin 6. ASSERT: Button 'Legal Info' is enabled 7. EXECUTE: Press 'Legal Info' button 8. ASSERT: Legal information is showed It shows empty about.html, that contains <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> <HTML> <head> <title>About</title> <meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> </head> <BODY lang="EN-US"> <H3>About This Content</H3> <P>May 8, 2007</P> <H3>License</H3> <P>TBD: License and link here</P> </BODY> </HTML> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

4
25
0 / 0

[JBoss JIRA] Created: (JBIDE-501) Unable to start JBoss-Server 4.2GA

by Perry Rhodan (JIRA)

Unable to start JBoss-Server 4.2GA ---------------------------------- Key: JBIDE-501 URL: http://jira.jboss.com/jira/browse/JBIDE-501 Project: JBoss Tools Issue Type: Bug Components: JBossIDE Core Affects Versions: 2.0.0.Beta3, 2.0.0.GA Environment: Windows-XP, Eclipse 3.3 Europa, JBossTools-200706300254-nightly-ALL-win32.zip Reporter: Perry Rhodan Assigned To: Marshall Culpepper It's impossible to start a Jboss 4.2GA Server with JBossTools-200706300254-nightly-ALL-win32.zip under Eclipse Europa release. Every time the startup will be interrupted by an <problem occured> dialog with "Server <servername> failed to start" as detail. In the event-log will this failure be logged: Failure: NamingException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicatinException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out.] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-854) our adapter uses different vm-install constant than other servers

by Max Andersen (JIRA)

our adapter uses different vm-install constant than other servers ----------------------------------------------------------------- Key: JBIDE-854 URL: http://jira.jboss.com/jira/browse/JBIDE-854 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.Beta3 Reporter: Max Andersen Assigned To: Rob Stryker Priority: Minor Just wondering why we use public static String PROPERTY_VM_ID = "PROPERTY_VM_ID"; public static String PROPERTY_VM_TYPE_ID = "PROPERTY_VM_TYPE_ID"; when both tomcat and all generic servers uses protected static final String PROP_VM_INSTALL_TYPE_ID = "vm-install-type-id"; protected static final String PROP_VM_INSTALL_ID = "vm-install-id"; ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 5 months

3
3
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 2007