[JBoss JIRA] Created: (JBIDE-4764) OpenOns don't work for xhtml pages with installed maven's plug-ins.
by Yura Zhishko (JIRA)
OpenOns don't work for xhtml pages with installed maven's plug-ins.
-------------------------------------------------------------------
Key: JBIDE-4764
URL: https://jira.jboss.org/jira/browse/JBIDE-4764
Project: JBoss Tools
Issue Type: Bug
Components: common, jsp/jsf/xml source editing, Visual Page Editor core
Affects Versions: 3.1.0.M3
Environment: Eclipse 3.5 win_32 with DTP, EMF, XSD, GEF, WTP plug-ins installed.
Maven plug-ins were installed from http://m2eclipse.sonatype.org/update/ update site (exclude Maven SCM handler for Subclipse and Maven Integration for AJDT)
JBT were installed from http://download.jboss.org/jbosstools/updates/nightly/trunk/ update site.
Reporter: Yura Zhishko
Assignee: Alexey Kazakov
Priority: Critical
1) Create new JSF kick start Project with Facelets
2) Open inputName.xhtml with JBossTools editor
3) Try to make Open-On on a "/templates/common.xhtml" link
RESULT: Nothing. Open-On doesn't work.
The possible reason is a conflict with Doxia Xhtml Editor. When we try to make Open-On in this editor an exception is thrown:
java.lang.AbstractMethodError
at org.eclipse.mylyn.internal.tasks.ui.TasksUiPlugin$11.run(TasksUiPlugin.java:1164)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.runtime.Platform.run(Platform.java:888)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.mylyn.internal.tasks.ui.TasksUiPlugin.getRepositoryForResource(TasksUiPlugin.java:1157)
at org.eclipse.mylyn.tasks.ui.AbstractTaskHyperlinkDetector.getTaskRepository(AbstractTaskHyperlinkDetector.java:166)
at org.eclipse.mylyn.tasks.ui.AbstractTaskHyperlinkDetector.getTaskRepositories(AbstractTaskHyperlinkDetector.java:130)
at org.eclipse.mylyn.internal.tasks.ui.editors.TaskHyperlinkDetector.detectHyperlinks(TaskHyperlinkDetector.java:38)
at org.eclipse.mylyn.tasks.ui.AbstractTaskHyperlinkDetector.detectHyperlinks(AbstractTaskHyperlinkDetector.java:93)
at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:263)
at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:439)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:199)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBIDE-3235) Missing properties view for servers elements
by Max Rydahl Andersen (JIRA)
Missing properties view for servers elements
--------------------------------------------
Key: JBIDE-3235
URL: https://jira.jboss.org/jira/browse/JBIDE-3235
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Reporter: Max Rydahl Andersen
Fix For: 3.0.0.cr1
Before I could directly edit properties for ports in properties view.
Now I need to right click and choose Change Value and get a non-standard edit in the tree.
This I could probably live with if I could just double click the value and edit it like in properties view.
Properties view was though also nice to give other details than just access to edit.
i.e.. I could copy values to get the value of file names etc. I can't copy elements from the tree and get a textual representation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 3 months
[JBoss JIRA] Created: (JBIDE-4185) Simpler load time weaving configuration
by Galder Zamarreño (JIRA)
Simpler load time weaving configuration
---------------------------------------
Key: JBIDE-4185
URL: https://jira.jboss.org/jira/browse/JBIDE-4185
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS
Reporter: Galder Zamarreño
Assignee: Rob Stryker
Right now, if you wanna use load time weaving, you need to modify jboss.aop:service=AspectManager
MBean to have EnableLoadtimeWeaving to true and you need to pass the pluggable instrumentor in
the VM parameters, i.e.
-javaagent:/home/galder/access/eap-rel/4.3.0.ga.cp04/server/279798/deploy/jboss-aop-jdk50.deployer/pluggable-instrumentor.jar
>From JBDS, you need to put the full path to this, whereas if running standalone, you can just do:
JAVA_OPTS="$JAVA_OPTS -javaagent:server/279798/deploy/jboss-aop-jdk50.deployer/pluggable-instrumentor.jar"
Now, it'd be really helpful if the JBoss AS/EAP server had an option that added did this (at least the javaagent part)
if load time weaving was enabled (a new option server configuration window (i.e. double click server name))
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-2240) Speed up creation of runtime/servers, specially when creating clusters
by Galder Zamarreno (JIRA)
Speed up creation of runtime/servers, specially when creating clusters
----------------------------------------------------------------------
Key: JBIDE-2240
URL: http://jira.jboss.com/jira/browse/JBIDE-2240
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Galder Zamarreno
We need to look at a way to streamline the creation of
runtime/servers as I'm finding it really tedious, specially
when it comes to clusters.
First, I think It'd be nice to create a runtime and a server in
a single step. This would fit very well my model where I take
an EAP version, create a server configuration (could Tools do
this for me as well? instead of me having to
"cp -r server/default server/12345"), create a runtime for it and
a server and the server's name to be exactly the same as the one
from the runtime (no need to add the " Server" name clutter).
Secondly, once I've created a server configuration + runtime +
server, an ability to copy paste that one, having only to change the
server configuration name (server/12345_1, server/12345_2....configurations)
, runtime/server name and bind address (for those that don't do multiple IP
addresses, enable binding manager and allow selecting the port collection,
ports-01...etc).
All this needs further baking and you have to take into account my specific
use where I'm creating server configurations on a daily basis.
--
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
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-1246) service beans code completion is broken
by Max Andersen (JIRA)
service beans code completion is broken
---------------------------------------
Key: JBIDE-1246
URL: http://jira.jboss.com/jira/browse/JBIDE-1246
Project: JBoss Tools
Issue Type: Bug
Components: JBossAS
Reporter: Max Andersen
Assigned To: Rob Stryker
Fix For: 2.1
While fixing the identification of service xml I found that the code completion is broken in service.xml
It looks like the code is searching for code completions manually and assumes way too much about what the searchengine can/should find.
e.g. PackageTypeSearcher.getPackage() assumes only one packagefragment per name will be found, but that is not the case if you have multiple projects with the same jar or simply uses the same package name in diffeerent projects.
One way to solve it is to use the built in codecompetlion in JDT - an example of that is to be found in CompletionHelper.java in the hibernate plugins.
--
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
14 years, 5 months
[JBoss JIRA] Created: (JBIDE-5235) Error during struts kick start project execution on bundled EAP 5.0
by Jiri Peterka (JIRA)
Error during struts kick start project execution on bundled EAP 5.0
-------------------------------------------------------------------
Key: JBIDE-5235
URL: https://jira.jboss.org/jira/browse/JBIDE-5235
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, struts/shale
Affects Versions: 3.1.0.CR1
Environment: jbdevstudio-eap-linux-gtk-x86_64-3.0.0.v200911180352M-H96-M4
sun jdk-6u17-linux-x64
Reporter: Jiri Peterka
Steps to reproduce:
1. Use bundled EAP 5.0 as runtime
2. Create Struts kick start project
3. Run it on the server
4. Open page in eclipse web browser
Error message:
TTP Status 500 -
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: An exception occurred processing JSP page /pages/inputname.jsp at line 8
5: <title>KickStart: Input name</title>
6: </head>
7: <body>
8: <html:form action="/greeting.do">
9: <table border="0" cellspacing="0" cellpadding="0">
10: <tr>
11: <td><b>Input name:</b></td>
0:05:19,647 ERROR [RequestUtils] Error creating form bean of class demo.GetNameForm
java.lang.ClassNotFoundException: demo.GetNameForm
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at org.apache.struts.util.RequestUtils.applicationClass(RequestUtils.java:207)
at org.apache.struts.util.RequestUtils.applicationInstance(RequestUtils.java:231)
at org.apache.struts.util.RequestUtils.createActionForm(RequestUtils.java:837)
at org.apache.struts.taglib.html.FormTag.initFormBean(FormTag.java:552)
at org.apache.struts.taglib.html.FormTag.doStartTag(FormTag.java:520)
at org.apache.jsp.pages.inputname_jsp._jspx_meth_html_005fform_005f0(inputname_jsp.java:133)
at org.apache.jsp.pages.inputname_jsp._jspx_meth_html_005fhtml_005f0(inputname_jsp.java:106)
at org.apache.jsp.pages.inputname_jsp._jspService(inputname_jsp.java:73)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:322)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:249)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
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:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
Workaround: After server restart it works.
Note: Unable to simulate this without JBDS/JBT so it seems like JBDS/JBT issue
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months