[JBoss JIRA] Created: (JBIDE-9363) JAX-RS support doesn't add correctly to all dynamic web projects
by Isaac Rooskov (JIRA)
JAX-RS support doesn't add correctly to all dynamic web projects
----------------------------------------------------------------
Key: JBIDE-9363
URL: https://issues.jboss.org/browse/JBIDE-9363
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.3.0.M2
Environment: Fedora 14, JBoss Enterprise Portal Platform 5.1 (with integrated application server), JBT 3.3.0.M2
Reporter: Isaac Rooskov
Assignee: Xavier Coulon
Fix For: 3.3.0.Final
Hey Xavier, firstly I appreciate the time you are spending taking a look into this for me.
The issue is that when I add JAX-RS support through either the context menu or Properties -> Project Facets the 'Simple_Portlet' project gets a RESTful Web Services component with children, however the 'test' project doesn't.
The 'Simple_Portlet' project is a Dynamic Web Project with Portlet facets added, whereas the 'test' project is just a straight Dynamic Web Project.
I have attached the two projects.
Thanks,
Isaac
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBIDE-10019) NPE - during validator parse VPE content
by Vitali Yemialyanchyk (Created) (JIRA)
NPE - during validator parse VPE content
----------------------------------------
Key: JBIDE-10019
URL: https://issues.jboss.org/browse/JBIDE-10019
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Affects Versions: 3.3.0.M4
Reporter: Vitali Yemialyanchyk
Assignee: Alexey Kazakov
java.lang.NullPointerException
at org.apache.xerces.util.XMLAttributesImpl.getTableViewBucket(Unknown Source)
at org.apache.xerces.util.XMLAttributesImpl.prepareAndPopulateTableView(Unknown Source)
at org.apache.xerces.util.XMLAttributesImpl.addAttribute(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanAttribute(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.jboss.tools.jsf.web.validation.XHTMLValidator$MySAXParser.parse(XHTMLValidator.java:692)
at org.jboss.tools.jsf.web.validation.XHTMLValidator$XHTMLElementHandler.isWellFormedXHTML(XHTMLValidator.java:554)
at org.jboss.tools.jsf.web.validation.XHTMLValidator.validate(XHTMLValidator.java:159)
at org.eclipse.wst.xml.core.internal.validation.core.AbstractNestedValidator.validate(AbstractNestedValidator.java:280)
at org.eclipse.wst.xml.core.internal.validation.core.AbstractNestedValidator.validate(AbstractNestedValidator.java:85)
at org.jboss.tools.jsf.web.validation.XHTMLValidator.validate(XHTMLValidator.java:138)
at org.eclipse.wst.validation.Validator$V2.validate(Validator.java:1159)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704)
at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665)
at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810)
at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669)
at org.eclipse.wst.validation.internal.ValBuilderJob$Visitor.visit(ValBuilderJob.java:299)
at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:106)
at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:65)
at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86)
at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:75)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:104)
at org.eclipse.core.internal.resources.Resource.accept(Resource.java:88)
at org.eclipse.wst.validation.internal.ValBuilderJob.fullBuild(ValBuilderJob.java:219)
at org.eclipse.wst.validation.internal.ValBuilderJob.run(ValBuilderJob.java:178)
at org.eclipse.wst.validation.internal.ValBuilderJob.runInWorkspace(ValBuilderJob.java:126)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBIDE-10091) NPE in VPE -> org.jboss.tools.common.text.xml.info.ChainTextHover
by Vitali Yemialyanchyk (Created) (JIRA)
NPE in VPE -> org.jboss.tools.common.text.xml.info.ChainTextHover
-----------------------------------------------------------------
Key: JBIDE-10091
URL: https://issues.jboss.org/browse/JBIDE-10091
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing, UpStream, Visual Page Editor core
Affects Versions: 3.3.0.M3
Reporter: Vitali Yemialyanchyk
Assignee: Alexey Kazakov
{code}
java.lang.NullPointerException
at org.eclipse.wst.sse.ui.internal.taginfo.AnnotationHoverProcessor.getHoverInfo(AnnotationHoverProcessor.java:120)
at org.jboss.tools.common.text.xml.info.ChainTextHover.getHoverInfo2(ChainTextHover.java:145)
at org.jboss.tools.common.text.xml.info.ChainTextHover.getHoverInfo2(ChainTextHover.java:132)
at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166)
{code}
- I can't provide exact steps to reproduce.
Only 1 statement - in AnnotationHoverProcessor.getHoverInfo line 120:
hoverRegion can't be null during code inspecting,
but variable p - can be null.
so look like UpStream exception
{code}
java.lang.NullPointerException
at org.eclipse.jst.jsf.facelet.core.internal.cm.ElementCMAdapter.getLength(ElementCMAdapter.java:109)
at org.eclipse.wst.xml.core.internal.contentmodel.basic.CMNamedNodeMapImpl.<init>(CMNamedNodeMapImpl.java:40)
at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.getCMAttributeDeclaration(XMLTagInfoHoverProcessor.java:206)
at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeTagAttNameHelp(XMLTagInfoHoverProcessor.java:122)
at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeRegionHelp(XMLTagInfoHoverProcessor.java:108)
at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.computeHoverHelp(XMLTagInfoHoverProcessor.java:86)
at org.eclipse.wst.xml.ui.internal.taginfo.XMLTagInfoHoverProcessor.getHoverInfo(XMLTagInfoHoverProcessor.java:257)
at org.eclipse.jst.jsf.facelet.ui.internal.hover.FaceletHover.getHoverInfo(FaceletHover.java:58)
at org.jboss.tools.common.text.xml.info.ChainTextHover.getHoverInfo2(ChainTextHover.java:145)
at org.jboss.tools.common.text.xml.info.ChainTextHover.getHoverInfo2(ChainTextHover.java:132)
at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:166)
{code}
- in this case something wrong in jboss tools can be cause of exception
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBIDE-9756) Openon for expressions with multiple options doesn't work on Mac
by Max Rydahl Andersen (JIRA)
Openon for expressions with multiple options doesn't work on Mac
----------------------------------------------------------------
Key: JBIDE-9756
URL: https://issues.jboss.org/browse/JBIDE-9756
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml source editing
Reporter: Max Rydahl Andersen
Assignee: Alexey Kazakov
Priority: Critical
Fix For: 3.3.0.M4
when trying to open on for this snippet in kitchensink quickstart:
<h:commandButton id="register"
action="#{memberRegistration.register}" value="Register" />
tooltip hover shows the right class
F3 doesn't do anything
Ctrl+Click shows a white box that looks like it should contain a list of possible open ons.
...tried on Mac
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBIDE-10162) form-login-page verification failure with correct data
by Jesper Skov (Created) (JIRA)
form-login-page verification failure with correct data
------------------------------------------------------
Key: JBIDE-10162
URL: https://issues.jboss.org/browse/JBIDE-10162
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.3.0.M4
Environment: Windows XP, Eclipse Indigo SR1
Reporter: Jesper Skov
In a web.xml file we have this bit of code:
{code}
<servlet>
<description></description>
<display-name>LoginServlet</display-name>
<servlet-name>LoginServlet</servlet-name>
<servlet-class>dk.jyskebank.core.jsf.login.FacesLoginServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>LoginServlet</servlet-name>
<url-pattern>/loginServlet</url-pattern>
</servlet-mapping>
<login-config>
<auth-method>FORM</auth-method>
<form-login-config>
<form-login-page>/loginServlet</form-login-page>
<form-error-page>/login/loginfail.jsp</form-error-page>
</form-login-config>
</login-config>
{code}
The 'Check form-login-page attribute' verification rule marks this as a failure, saying:
error: Attribute form-login-page references to /loginServlet that does not exist in web content
In a way, the verifier is right; the jar with the LoginServlet.class lives outside the web content folder, but it copied into WEB-INF/lib as part of Deployment Assembly.
And the jar is on build classpath, obviously.
I tried copying the jar into the web content folder directly, but it has no effect on the verifier.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] (JBIDE-10059) Intermittent, random, but recurring - where Indigo + JBT M4 crashes in JBoss Central
by Len DiMaggio (Created) (JIRA)
Intermittent, random, but recurring - where Indigo + JBT M4 crashes in JBoss Central
------------------------------------------------------------------------------------
Key: JBIDE-10059
URL: https://issues.jboss.org/browse/JBIDE-10059
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 3.3.0.M4
Environment: RHEL6
Firefox 3.6.23
Version: Indigo Release
Build id: 20110615-0604
JBoss Tools 3.3.0.M4
Reporter: Len DiMaggio
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.Beta1
Attachments: JBT_330M4_strace.txt, log
Seeing a problem - intermittent, random, but recurring - where Indigo + JBT M4 crashes in JBoss Central - sometimes while refreshing the news, other times while looking at preferences. No real pattern yet. Has anyone else seen this?
only clue is:
(npviewer.bin:4218): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",
Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory
But - and this is on RHEL6 - it is installed:
$ rpm -qa | grep libcanberra
libcanberra-0.22-1.el6.i686
libcanberra-0.22-1.el6.x86_64
libcanberra-gtk2-0.22-1.el6.x86_64
strace and .log files attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBIDE-9778) Maven embedded projects are not properly generated as jars in the deploy folder
by Eric B (JIRA)
Maven embedded projects are not properly generated as jars in the deploy folder
-------------------------------------------------------------------------------
Key: JBIDE-9778
URL: https://issues.jboss.org/browse/JBIDE-9778
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 3.2.1.Final, 3.2.0.Final
Environment: Eclipse Helios SR1
Reporter: Eric B
Assignee: Fred Bricon
I have a Maven eclipse webapp project created and deployed in my JBoss server. I have the deploy set to deploy as an exploded war, so I can see all the files that it produces in the deployment directory.
My webapp project is dependent on another Eclipse project (server.jar artifact). If I have both projects open in Eclipse at the same time, everything works fine.
My server.jar project is also dependent on other Eclipse projects (supportLib.jar). If I have those dependent projects opened at the same time, then the exploded jar file is invalid. Instead of exporting everything in src/main/java/* to the jar file, it exports everything from src/*. Consequently, the TopLevel in my jar file in the embedded projects is main.java.myTLD instead of myTLD.
For example, if I have the supportLib.jar project with files "src/main/java/myTld/file.java" opened at the same time as server.jar and webapp.war, then the exported war for supportLib.jar in the webapp.war folder is contains "META-INF and main" rather than "META-INF and myTLD".
I have updated to the latest version of JBoss Tools from the Helios update site and continue to see this problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months