[JBoss JIRA] (JBIDE-10089) Remove updating <style> tag from VpeVisualDomBuilder.updateElement(Node sourceNode) method
by Denis Maliarevich (Created) (JIRA)
Remove updating <style> tag from VpeVisualDomBuilder.updateElement(Node sourceNode) method
------------------------------------------------------------------------------------------
Key: JBIDE-10089
URL: https://issues.jboss.org/browse/JBIDE-10089
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.3.0.M4
Reporter: Denis Maliarevich
Assignee: Denis Maliarevich
Priority: Optional
Fix For: 3.3.0.Beta1
There is a bad way of updating <style> tag in updateElement(Node sourceNode) method:
{code}
/*
* special processing of "style" element
*
* for unification of updating nodes - or redevelop updating
* mechanism (for example : transfer this function to template )
* or redevelop template of "style" element
*/
if (HTML.TAG_STYLE.equalsIgnoreCase(sourceNode.getNodeName())) {
// refresh style node
VpeStyleUtil.refreshStyleElement(this, elementMapping);
return;
}
{code}
Should be removed to the style template.
--
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, 4 months
[JBoss JIRA] (JBIDE-9829) @PathParam validation broken
by Jozef Hartinger (Created) (JIRA)
@PathParam validation broken
----------------------------
Key: JBIDE-9829
URL: https://issues.jboss.org/browse/JBIDE-9829
Project: Tools (JBoss Tools)
Issue Type: Bug
Environment: JBoss JAX-RS Tools 1.2.2.v20110915-1723-H22-M3
Reporter: Jozef Hartinger
Fix For: 3.3.0.M4
Having a class:
@Path("/foo/{id}")
public class Foo {
@Path("/bar")
public void bar(@PathParam("id") String id)
{
// noop
}
}
the following error is recognized by JBoss Tools:
"@PathParam annotation value 'id' does not match any parameter of the same method or type @Path annotation(s)."
Although the "id" parameter matches the id path parameter defined within class-level @Path annotation.
Besides, to implement this correctly, it is also important to consider that the JAX-RS resource may actually be a sub-resource. Thus, a path parameter can be defined on the resource that delegates to Foo and not on Foo itself.
--
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, 4 months
[JBoss JIRA] Created: (JBIDE-9747) Possibility of update node instead of recreating has been removed in VPE templates
by Maxim Areshkau (JIRA)
Possibility of update node instead of recreating has been removed in VPE templates
----------------------------------------------------------------------------------
Key: JBIDE-9747
URL: https://issues.jboss.org/browse/JBIDE-9747
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor Templates
Affects Versions: 3.3.0.M2
Reporter: Maxim Areshkau
Assignee: Yahor Radtsevich
Priority: Critical
Possibility of update node instead of recreating has been removed in VPE templates what is reason of performance issues. For example when we update style in some div, it will call rebuild of all div chidren, instead of updating style in visual div. Previously the updating was done via VpeAbstractTemplate.recreateAtAttrChange function.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBIDE-9177) Enable JAX-RS and I sometimes get a frozen IDE
by Max Rydahl Andersen (JIRA)
Enable JAX-RS and I sometimes get a frozen IDE
-----------------------------------------------
Key: JBIDE-9177
URL: https://issues.jboss.org/browse/JBIDE-9177
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.3.0.M2
Reporter: Max Rydahl Andersen
Fix For: 3.3.0.M3
I right clicked on a dynamic web project and chose configure > enable jax rs 1.1 and Eclipse froze.
I ran jstack on it and noticed this trace:
"main" prio=6 tid=0000000013000800 nid=0xa0705540 in Object.wait() [00000000bfffd000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0000000016914448> (a org.eclipse.core.internal.jobs.Semaphore)
at org.eclipse.core.internal.jobs.Semaphore.acquire(Semaphore.java:39)
- locked <0000000016914448> (a org.eclipse.core.internal.jobs.Semaphore)
at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:847)
at org.eclipse.core.internal.jobs.InternalJob.join(InternalJob.java:380)
at org.eclipse.core.runtime.jobs.Job.join(Job.java:385)
at org.jboss.tools.ws.jaxrs.ui.cnf.UriMappingsContentProvider.getChildren(UriMappingsContentProvider.java:67)
at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:96)
at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:275)
at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:94)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$1.run(NavigatorContentServiceContentProvider.java:152)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.internalGetChildren(NavigatorContentServiceContentProvider.java:139)
at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.getChildren(NavigatorContentServiceContentProvider.java:125)
at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1352)
at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:391)
at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:917)
Looks like it is forcing a wait or lock on the project ?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBIDE-9332) new rest services are not visible under REST services node
by Lukas Jungmann (JIRA)
new rest services are not visible under REST services node
----------------------------------------------------------
Key: JBIDE-9332
URL: https://issues.jboss.org/browse/JBIDE-9332
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.3.0.M3
Environment: v. 1.2.2.v20110712-0303-H390-M3; ubuntu 11.04+gnome3
Reporter: Lukas Jungmann
Priority: Critical
-create fresh new workspace (important!)
-add EAP-5.1 to servers in the IDE
-create new dynamic web project for EAP-5.1
-do Configure -> Add JAX-RS 1.1 support...
=> REST services node remains in "Building RESTful Web Services..." state
-create new Sample RESTful Web Service
=> REST services node moves to "RESTful Web Services" state but remains empty
-create new dummy java class and edit it to:
{code}
package x;
@javax.ws.rs.Path("/x")
public class X {
@javax.ws.rs.GET public String x() { return "x"; }
}
{code}
=> REST services does not still show any RESTful services from the project
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months