December 2007 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-1137) Tag <br> displays on VPE as unknown tag

by Anton Klimkovich (JIRA)

Tag <br> displays on VPE as unknown tag --------------------------------------- Key: JBIDE-1137 URL: http://jira.jboss.com/jira/browse/JBIDE-1137 Project: JBoss Tools Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.0.0.Beta4 Reporter: Anton Klimkovich Priority: Minor Attachments: br tag.PNG JSFKickStart project Open inpuUser.jsp Set cursor on Visual part Press enter button <br> will be inserted Tag <br> shouldn't be displayed as unknown tag in VPE Look at screenshot -- 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] Commented: (JBIDE-1498) XML/DTD issues

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-1498?page=comments#action_12392938 ] Max Andersen commented on JBIDE-1498: ------------------------------------- then close this issue with info on what is fixed and create new seperate issues for the things you would like to fix for 2.1 > 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

[JBoss JIRA] Resolved: (JBIDE-765) Factory org.jboss.tools.common.core.resources.XModelObjectEditorInputFactory returned null from createElement for editor id=org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor

by Viacheslav Kabanovich (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-765?page=all ] Viacheslav Kabanovich resolved JBIDE-765. ----------------------------------------- Resolution: Won't Fix Entries in the log warns user that the project has been removed externally and the reference preserved by the workspace cannot be loaded normally. This is the expected reporting of Eclipse, and we cannot and should not do anything about it. Besides, it is not relevant to the problem with XModelObjectEditorInputFactory. > Factory org.jboss.tools.common.core.resources.XModelObjectEditorInputFactory returned null from createElement for editor id=org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor > ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-765 > URL: http://jira.jboss.com/jira/browse/JBIDE-765 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 2.0.0.Beta3 > Reporter: Anton Klimkovich > Assigned To: Viacheslav Kabanovich > Fix For: 2.0.0.CR1 > > Attachments: 1.txt, 111.txt, 2.txt, NewLog.txt > > > Create JSFKickStart > Open any JSP page > Close RHDS without closing JSP Editor > Delete project from workspace manualy > Open RHDS > Factory org.jboss.tools.common.core.resources.XModelObjectEditorInputFactory returned null from createElement for editor id=org.jboss.tools.jst.jsp.jspeditor.JSPTextEditor ... > Log attached. > for Xhtml Editor similar exception. -- 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-1010) New entity produces error

by Slava Litskevich (JIRA)

New entity produces error ------------------------- Key: JBIDE-1010 URL: http://jira.jboss.com/jira/browse/JBIDE-1010 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.Beta4 Environment: RHDS 1.0.0 beta 2 JDK 1.5.0_12 Reporter: Slava Litskevich Fix For: 2.0.0.Beta4 Create new Seam Web Project: 1. File -> New -> Seam Web Project: new project dialog opens 2. Specifiy project name -> Next 3. Mark "Java Persistence" -> Next -> Next -> Next 4. Mark "Server Supplied JSF Implementation" -> Next -> Finish Run new project: 5. Rightclick project name in Package Explorer -> Run As... -> Run on Server: run dialog opens 6. Finish: wait until application opens in browser Add new entity: 7. Rightclick project name in Package Explorer -> New -> Seam Entity 8. Specify following values: Seam component name = ant, master page name = ant-edit, page name = ant-list -> Finish: ant-list.xhtml, ant-edit.xhtml and Ant.java appear in project content tree. Call new entity page: 9. Navigate to the page http://localhost:8080/[PROJECT_NAME]/ant-edit.seam: page opens correct. 10. Enter any text value in the input field and click "Save": "JBoss Seam Debug Page" opens. Exception during request processing: javax.servlet.ServletException: /ant-edit.xhtml @25,63 value="#{antHome.instance.name}": Target Unreachable, identifier 'antHome' resolved to null javax.faces.webapp.FacesServlet.service(FacesServlet.java:256) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96) org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Unknown Source) 11. Navigate to the page http://localhost:8080/[PROJECT_NAME]/ant-list.seam: page opens correct. 12. Click button "Create ant": nothing happens - empty list page is still displayed. -- 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-1009) New form produces error

by Slava Litskevich (JIRA)

New form produces error ----------------------- Key: JBIDE-1009 URL: http://jira.jboss.com/jira/browse/JBIDE-1009 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.Beta4 Environment: RHDS 1.0.0 beta 2 JDK 1.5.0_12 Reporter: Slava Litskevich Fix For: 2.0.0.Beta4 Create new Seam Web Project: 1. File -> New -> Seam Web Project: new project dialog opens 2. Specifiy project name -> Next 3. Mark "Java Persistence" -> Next -> Next -> Next 4. Mark "Server Supplied JSF Implementation" -> Next -> Finish Run new project: 5. Rightclick project name in Package Explorer -> Run As... -> Run on Server: run dialog opens 6. Finish: wait until application opens in browser Add new form: 7. Rightclick project name in Package Explorer -> New -> Seam Form 8. Specify following values: Seam component name = hello, POJO class name = Hello, method name = hello, page name = hello -> Finish: hello.xhtml and Hello.java appear in project content tree. Call new form: 9. Navigate to the page http://localhost:8080/[PROJECT_NAME]/hello.seam: page opens correct. 10. Click "hello" button: "JBoss Seam Debug Page" opens. 11. After server restart form works correct. Exception during request processing: javax.servlet.ServletException: /hello.xhtml @25,53 value="#{hello.value}": Target Unreachable, identifier 'hello' resolved to null javax.faces.webapp.FacesServlet.service(FacesServlet.java:256) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:63) org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:60) org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57) org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:79) org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:49) org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:84) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:96) org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter.java:220) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Unknown Source) -- 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
4
0 / 0

[JBoss JIRA] Created: (JBIDE-992) Run on server on War in EAR causes duplicate deploy

by Max Andersen (JIRA)

Run on server on War in EAR causes duplicate deploy --------------------------------------------------- Key: JBIDE-992 URL: http://jira.jboss.com/jira/browse/JBIDE-992 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.Beta3 Reporter: Max Andersen Priority: Blocker Fix For: 2.0.0.Beta4 Create seam ear project run EAR on server (deploys fine) run WAR on server (now both EAR and WAR is deployed side-by-side...for other adapters it just deploys into the ear since its already there as far as i can see) Let me know how hard this is to fix - if too hard we will need to slip it. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBIDE-973) java.lang.NullPointerException after import *.ear project into workspace.

by Anton Klimkovich (JIRA)

java.lang.NullPointerException after import *.ear project into workspace. -------------------------------------------------------------------------- Key: JBIDE-973 URL: http://jira.jboss.com/jira/browse/JBIDE-973 Project: JBoss Tools Issue Type: Bug Components: Archives Affects Versions: 2.0.0.Beta3 Reporter: Anton Klimkovich Create JSFKickStart project Create EAR archive using Project archives (Window->Show View->JBoss Tools->Project archives) Import created EAR file using Import->J2EE->Ear file In Enterprise Application Import Wizard click Browse button and select created EAR java.lang.NullPointerException will be occur. Log attached. -- 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
7
0 / 0

[JBoss JIRA] Created: (JBIDE-979) Seam form/entity/etc. wizard should show "something" when finished

by Max Andersen (JIRA)

Seam form/entity/etc. wizard should show "something" when finished ------------------------------------------------------------------ Key: JBIDE-979 URL: http://jira.jboss.com/jira/browse/JBIDE-979 Project: JBoss Tools Issue Type: Feature Request Components: Seam Affects Versions: 2.0.0.Beta3, 2.0.0.Beta4 Reporter: Max Andersen Assigned To: Denis Golovin Fix For: 2.0.0.CR1 When a user have executed the wizards he does not know what just happend... We should show a message and/or at least show the "primary file" in the editor. e.g. for Seam Entity it would be the created entity Seam Form or Action the action bean 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

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-965) classes directory is not deployed in war

by Max Andersen (JIRA)

classes directory is not deployed in war ---------------------------------------- Key: JBIDE-965 URL: http://jira.jboss.com/jira/browse/JBIDE-965 Project: JBoss Tools Issue Type: Bug Components: JBoss Tools Core Affects Versions: 2.0.0.Beta3 Environment: linux Reporter: Max Andersen Assigned To: Rob Stryker Priority: Blocker Fix For: 2.0.0.Beta4 create new seam project, deploy/run on server. Everything seem fine, except /web-inf/classes is not there. -- 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
7
0 / 0

[JBoss JIRA] Created: (JBIDE-951) Seam Web Project in war configuration has an error '' right after creating under linux

by Denis Golovin (JIRA)

Seam Web Project in war configuration has an error '' right after creating under linux -------------------------------------------------------------------------------------- Key: JBIDE-951 URL: http://jira.jboss.com/jira/browse/JBIDE-951 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta3 Environment: FC6 Linux Reporter: Denis Golovin Assigned To: Denis Golovin Fix For: 2.0.0.Beta4 that's happend because WTP doesn't update org.eclipse.wst.common.component file in .settings on Linux. Under windows it looks like <?xml version="1.0" encoding="UTF-8"?> <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="s1"><?xml version="1.0" encoding="UTF-8"?> <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="s3"> <wb-resource deploy-path="/" source-path="/WebContent"/> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/> <property name="context-root" value="s3"/> <property name="java-output-path" value="build/classes"/> <property name="web_app_libraries_processed" value="true"/> <property name="ear_libraries_processed" value="true"/> </wb-module> </project-modules> <wb-resource deploy-path="/" source-path="/WebContent"/> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/action"/> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src/model"/><?xml version="1.0" encoding="UTF-8"?> <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="s3"> <wb-resource deploy-path="/" source-path="/WebContent"/> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/> <property name="context-root" value="s3"/> <property name="java-output-path" value="build/classes"/> <property name="web_app_libraries_processed" value="true"/><?xml version="1.0" encoding="UTF-8"?> <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="s3"> <wb-resource deploy-path="/" source-path="/WebContent"/> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/> <property name="context-root" value="s3"/> <property name="java-output-path" value="build/classes"/> <property name="web_app_libraries_processed" value="true"/> <property name="ear_libraries_processed" value="true"/> </wb-module> </project-modules> <property name="ear_libraries_processed" value="true"/> </wb-module> </project-modules> <property name="context-root" value="s1"/> <property name="java-output-path" value="build/classes"/> <property name="web_app_libraries_processed" value="true"/> <property name="ear_libraries_processed" value="true"/> </wb-module> </project-modules> right after seam web project is created in WAR deployment configuration. Under linux it looks different: <?xml version="1.0" encoding="UTF-8"?> <project-modules id="moduleCoreId" project-version="1.5.0"> <wb-module deploy-name="s3"> <wb-resource deploy-path="/" source-path="/WebContent"/> <wb-resource deploy-path="/WEB-INF/classes" source-path="/src"/> <---- source folder is still the same <property name="context-root" value="s3"/> <property name="java-output-path" value="build/classes"/> <property name="web_app_libraries_processed" value="true"/> <property name="ear_libraries_processed" value="true"/> </wb-module> </project-modules> -- 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
2
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