[ https://jira.jboss.org/browse/JBIDE-6863?page=com.atlassian.jira.plugin.s... ] Libor Zoubek updated JBIDE-6863: -------------------------------- Attachment: NPE.log -- 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

[ https://jira.jboss.org/browse/JBIDE-6863?page=com.atlassian.jira.plugin.s... ] Viacheslav Kabanovich commented on JBIDE-6863: ---------------------------------------------- In new ESB project wizard, version of config is selected in the last page, now option 1.3 is missing, it is to be added in org.jboss.tools.esb.project.ui.wizards.pages.ESBFacetInstallationPage class. I could not reproduce the issue following the steps, but could simulate it by modifying code. Two causes are possible. 1) ESB content folder is not found by tools. 2) A consequence of the same problem as in JBIDE-6314. The first case is most probable as description says that NPE happens with any *.jar while to activate the second case one has to open specific trouble-making *.jar. Libor, does the browse dialog have 'esbcontent' folder, or there is an empty line under root node (this would be the evidence that tool could not find 'esbcontent' folder)? Could you please check that created project has (1) 'esbcontent' folder; (2) /.settings/org.eclipse.wst.common.component file with reference to resource /esbcontent? Does restart of Eclipse solves the problem with project created in earlier sessions? It is easy to fix NPE in tools for the case when 'esbcontent' folder is missing, but we need to know exactly why it is not found in your project. -- 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

[ https://jira.jboss.org/browse/JBIDE-6863?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick commented on JBIDE-6863: ------------------------------------------ Is there a reason you're not creating an ESB project directly instead of creating a Java project initially? -- 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

[ https://jira.jboss.org/browse/JBIDE-6863?page=com.atlassian.jira.plugin.s... ] Viacheslav Kabanovich resolved JBIDE-6863. ------------------------------------------ Resolution: Done I think it is sufficient in this case to prevent null value from being added into the selection tree instead of missing esb content folder. It is not a common practice in Eclipse to suggest (or force) project conversion when a new file is created; and adding ESB facet includes creation of esb config file. -- 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

[ https://jira.jboss.org/browse/JBIDE-6863?page=com.atlassian.jira.plugin.s... ] Libor Zoubek closed JBIDE-6863. ------------------------------- verified on JBT H96 Beta1 -- 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