December 2007 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-1475) NPE opening html file if JBossTools installed with Local Site

by Joseph Sondow (JIRA)

NPE opening html file if JBossTools installed with Local Site ------------------------------------------------------------- Key: JBIDE-1475 URL: http://jira.jboss.com/jira/browse/JBIDE-1475 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.CR1 Environment: WinXP SP2 Eclipse 3.3.1.1 for Java EE Reporter: Joseph Sondow Attachments: eclipse-error.txt JBossTools plugin installation has a bug where some editors throw a NullPointerException if the plugin is installed using Local Site. Steps to reproduce: 1. Install Eclipse 3.3.1.1 JEE using eclipse-jee-europa-fall2-win32.zip by unzipping to C:\eclipse 2. Unzip JBossTools-2.0.0.CR1-ALL-win32.zip to C:\jbosstoolsinstall 3. Start Eclipse with eclipse.exe -clean 4. Help > Software Updates > Find and Install > Search for new features to install > Next 5. New Local SIte > C:\jbosstoolsinstall 6. Finish plugin installation by following prompts. Quit Eclipse and restart it with eclipse.exe -clean 7. Create a new empty simple project. Create an html file. It opens automatically with the JBoss Tools HTML Editor, immediately throwing a NullPointerException (See attached error log). The same happens if you create an XHTML or JSP file, or try to open an existing file of type HTML, XHTML, or JSP. Tested on 2 similar computers. The behavior is consistent. Workaround: Don't use Local Site to install JBossTools plugins. Instead, just copy the contents of the features and plugins folders into the corresponding Eclipse folders, then restart Eclipse. -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1446) "Change Timestamp" doesn't work after switching servers

by Juergen Zimmermann (JIRA)

"Change Timestamp" doesn't work after switching servers ------------------------------------------------------- Key: JBIDE-1446 URL: http://jira.jboss.com/jira/browse/JBIDE-1446 Project: JBoss Tools Issue Type: Bug Components: JBossAS Environment: JDK 1.6.0_03, Eclipse 3.3.1.1, WTP 2.0.1, JBoss Tools nightly build 20071203 Reporter: Juergen Zimmermann I've two servers configured: 1) JBoss 4.2.1 2) JBoss 4.2.2 I've an EAR project configured for the 1st server. After configuring the 2nd server this one is the default. Then I used the JBoss icon from the Eclipse toolbar to switch from the 2nd to the 1st one. Starting the server and deploying the ear project works fine. However, when I want to click at "Change timestamp..." nothing happens. Looking at the Windows filesystem it shows that the timestamp didn't change. The only workaround I see is: undeploy and redeploy the project. -- 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, 3 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-1430) Adding EntityManger to generated Authenticator.java

by Jim Tyrrell (JIRA)

Adding EntityManger to generated Authenticator.java --------------------------------------------------- Key: JBIDE-1430 URL: http://jira.jboss.com/jira/browse/JBIDE-1430 Project: JBoss Tools Issue Type: Bug Reporter: Jim Tyrrell Trying to inject an EntityManager into the Authenticator.java results in the following error noted below: All I add in this class src/action/org/domain/Blogging/session/Authenticator.java is the line @In EntityManager em; and the import statement. It should be noted that this then breaks the login screen from coming up. 14:40:08,837 ERROR [SeamPhaseListener] uncaught exception java.lang.IllegalArgumentException: value of context variable is not an instance of the component bound to the context variable: userHome at org.jboss.seam.Component.getInstance(Component.java:1655) at org.jboss.seam.Component.getInstance(Component.java:1610) at org.jboss.seam.Component.getValueToInject(Component.java:1885) at org.jboss.seam.Component.injectAttributes(Component.java:1368) at org.jboss.seam.Component.inject(Component.java:1195) at org.jboss.seam.interceptors.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:46) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.ManagedEntityIdentityInterceptor.aroundInvoke(ManagedEntityIdentityInterceptor.java:37) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:34) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.TransactionInterceptor$1.work(TransactionInterceptor.java:32) at org.jboss.seam.util.Work.workInTransaction(Work.java:37) at org.jboss.seam.interceptors.TransactionInterceptor.aroundInvoke(TransactionInterceptor.java:27) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.interceptors.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:27) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:69) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:103) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:151) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:87) at org.domain.Blogging.entity.PostHome_$$_javassist_8.clearDirty(PostHome_$$_javassist_8.java) at org.jboss.seam.contexts.Lifecycle.isAttributeDirty(Lifecycle.java:525) at org.jboss.seam.contexts.ServerConversationContext.flush(ServerConversationContext.java:230) at org.jboss.seam.contexts.Lifecycle.flushAndDestroyContexts(Lifecycle.java:419) at org.jboss.seam.contexts.Lifecycle.endRequest(Lifecycle.java:315) at org.jboss.seam.jsf.AbstractSeamPhaseListener.afterRender(AbstractSeamPhaseListener.java:256) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:115) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) 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) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220) 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:595) -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Updated: (JBIDE-1498) XML/DTD issues

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-1498?page=all ] Max Andersen updated JBIDE-1498: -------------------------------- Fix Version/s: 2.0.1 was this fixed or not ? > XML/DTD issues > -------------- > > Key: JBIDE-1498 > URL: http://jira.jboss.com/jira/browse/JBIDE-1498 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: Cleanup > Affects Versions: 2.0.0.GA > Reporter: Max Andersen > Assigned To: Viacheslav Kabanovich > Priority: Critical > Fix For: 2.0.1 > > > There seem to be a big mix of mixed and uppercase tag names and file names in xml and dtd's used by exadel. > e.g. kb-schema_1.0.dtd has BodyContent, StartTag, EndTag, Boolean instead of body-content, start-tag and end-tag. > Many xml files doesn't have a DTD/XSD reference hence is not validatable. > setting files uses UPPERCASE in xml (e.g. old .exadelproject file) -- 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, 3 months

1
0
0 / 0

[jbosside-issues] [JBoss JIRA] Created: (JBIDE-420) Typo in eclipse doc

by Philippe Ombredanne (JIRA)

Typo in eclipse doc ------------------- Key: JBIDE-420 URL: http://jira.jboss.com/jira/browse/JBIDE-420 Project: JBoss IDE Issue Type: Bug Components: JBossIDE Core Affects Versions: 2.0.0.Beta2 Reporter: Philippe Ombredanne Assigned To: Marshall Culpepper Priority: Trivial In the help tutorial: in Procedure 7.2. Webdoclet Configuration "Select the Web configuration. In the lower-left area, right-click to popup the menu and choose Add Doclet. A list of available doclets will appear. Choose webdoclet and click OK. On the lower-right area, you see the properties of the ejbdoclet." The last line should be instead: "On the lower-right area, you see the properties of the webdoclet." -- 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (RHDS-218) Web Project Settings missing

by Remo Liechti (JIRA)

Web Project Settings missing ---------------------------- Key: RHDS-218 URL: http://jira.jboss.com/jira/browse/RHDS-218 Project: Red Hat Developer Studio Issue Type: Bug Components: integration Environment: MyEclipse 6.0 RichFaces-VPE-win32-2.0.0.beta4.zip Reporter: Remo Liechti Priority: Critical Installed VPE editor by RichFaces-VPE-win32-2.0.0.beta4.zip into MyEclipse 6.0 Missing "Web Project Settings" in the project settings of my project. I'm not able to configure the webroot that way, which is pretty bad. This configuration setting is available when using RHDS, but not in a hybrid of MyEclipse and VPE. -- 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, 3 months

2
5
0 / 0

[JBoss JIRA] Updated: (JBIDE-719) Hibernate Tools should be able to use a named Eclipse provided connection

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-719?page=all ] Max Andersen updated JBIDE-719: ------------------------------- Fix Version/s: 2.1 (was: 2.0.1) > Hibernate Tools should be able to use a named Eclipse provided connection > ------------------------------------------------------------------------- > > Key: JBIDE-719 > URL: http://jira.jboss.com/jira/browse/JBIDE-719 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Hibernate > Reporter: Max Andersen > Priority: Optional > Fix For: 2.1 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > currently we use the settings specified in hibernate.properties/cfg.xml/persistence.xml > Users should be able to say to use a named WTP provided database connection. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-1365) Incorrect hint

by Svetlana mukhina (JIRA)

Incorrect hint -------------- Key: JBIDE-1365 URL: http://jira.jboss.com/jira/browse/JBIDE-1365 Project: JBoss Tools Issue Type: Bug Components: jbpm Affects Versions: 2.0.0.CR1 Reporter: Svetlana mukhina Assigned To: Koen Aers Fix For: 2.0.0.GA The hind on editor palette when hovering transition item is incorrect -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-1503) JUnit tests for Seam templates

by Maxim Areshkau (JIRA)

JUnit tests for Seam templates ------------------------------ Key: JBIDE-1503 URL: http://jira.jboss.com/jira/browse/JBIDE-1503 Project: JBoss Tools Issue Type: Feature Request Affects Versions: 2.0.0.GA Environment: Eclipse 3.3.1.1, eclipse test framework Reporter: Maxim Areshkau Assigned To: Dzmitry Sakovich Fix For: 2.0.1 Create Junt tests for seam templates in VPE. Create in scope of this request subtasks for every seam template: s:decorate, s:validate and etc... -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-1394) Create standalone tool for converting .packages to .packaging

by Max Andersen (JIRA)

Create standalone tool for converting .packages to .packaging ------------------------------------------------------------- Key: JBIDE-1394 URL: http://jira.jboss.com/jira/browse/JBIDE-1394 Project: JBoss Tools Issue Type: Feature Request Components: Archives Reporter: Max Andersen Assigned To: Marshall Culpepper Fix For: 2.0.1 we should whip together a conversion utility going from jbide 1.6 to jbide 2.0 packaging. available as something you can run like java -jar upgradearchiving.jar .packaging and then create the .packages file. -- 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, 3 months

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