[JBoss JIRA] (JBIDE-14120) Can not debug OSGI Bundles deployed in JBoss EAP 6.1 with JBossTools 4.0.1
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14120?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-14120:
-------------------------------------
I've done some debugging on our support of osgi deployments, but https://bugs.eclipse.org/bugs/show_bug.cgi?id=338633 is still present, and nobody from platform or PDE have responded on the bug in some years.
> Can not debug OSGI Bundles deployed in JBoss EAP 6.1 with JBossTools 4.0.1
> --------------------------------------------------------------------------
>
> Key: JBIDE-14120
> URL: https://issues.jboss.org/browse/JBIDE-14120
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.0.1.Final
> Reporter: Thomas Wiesner
> Fix For: 4.2.x
>
> Attachments: eclipse_juno_jboss_tools_4.0.1_osgi_debug, scr.zip, standalone.xml
>
>
> Starting JBoss EAP 6.1 in debug mode with JBoss Tools 4.0.1 in eclipse juno runs into following exception:
> [0m[0m16:54:53,618 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "de.ebcot.osgi.web.war" (runtime-name: "de.ebcot.osgi.web.war")
> [0m[0m16:54:53,618 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "de.ebcot.osgi.core.jar" (runtime-name: "de.ebcot.osgi.core.jar")
> [0m[0m16:54:53,777 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011006: OSGi Framework - 2.1.0.CR12
> [0m[31m16:54:53,789 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."de.ebcot.osgi.core.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."de.ebcot.osgi.core.jar".PARSE: JBAS018733: Failed to process phase PARSE of deployment "de.ebcot.osgi.core.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
> Caused by: java.lang.NullPointerException
> at org.jboss.as.osgi.service.FrameworkActivator.activate(FrameworkActivator.java:76)
> at org.jboss.as.osgi.deployment.FrameworkActivateProcessor.deploy(FrameworkActivateProcessor.java:72)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
> ... 5 more
> https://community.jboss.org/thread/223957?tstart=0
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19173) Palette: Update jQuery and ionic JS/CSS links
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-19173:
--------------------------------------
Summary: Palette: Update jQuery and ionic JS/CSS links
Key: JBIDE-19173
URL: https://issues.jboss.org/browse/JBIDE-19173
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: jsp/jsf/xml/html source editing
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 4.3.0.Alpha1
The latest JS/CSS:
Ionic: 1.0.0-beta.14
jQueryMobile: 1.4.5
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18678) Make dependencies to org.jboss.tools.usage optional
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18678:
-----------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.x)
> Make dependencies to org.jboss.tools.usage optional
> ---------------------------------------------------
>
> Key: JBIDE-18678
> URL: https://issues.jboss.org/browse/JBIDE-18678
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: browsersim, usage
> Affects Versions: 4.2.0.CR1
> Reporter: Kaloyan Raev
> Assignee: Alexey Kazakov
> Fix For: 4.3.0.Alpha2
>
>
> I am interested in adopting the CordovaSim feature in our product. However, most of the browsersim bundles have a strong dependency to org.jboss.tools.usage bundle, which force a Usage Reporting popup on startup. I want to avoid this and have the org.jboss.tools.usage excluded from my build.
> Is it possible to make the dependencies to org.jboss.tools.usage optional?
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18113) Wrong 'dirty regions' values passed to the 'as-you-type' validator
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18113?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18113:
-----------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Alpha1)
> Wrong 'dirty regions' values passed to the 'as-you-type' validator
> ------------------------------------------------------------------
>
> Key: JBIDE-18113
> URL: https://issues.jboss.org/browse/JBIDE-18113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.2.0.Beta3
> Reporter: Xavier Coulon
> Assignee: Victor Rubezhny
> Fix For: 4.3.0.Alpha2
>
>
> The as-you-type validator received an array of dirty regions that can be wrong when the region contains a String.
> Steps to reproduce:
> - grab the latest changes in jbosstools-webservices repo
> - start a runtime workbench
> - create a new dynamic web project targeting Wildfly 8.x (the example below uses JAX-RS 2.0 APIs)
> - add support for JAX-RS
> - create a class with the following content:
> {code}
> package jaxrs;
> import java.io.IOException;
> import javax.ws.rs.GET;
> import javax.ws.rs.Path;
> import javax.ws.rs.PathParam;
> import javax.ws.rs.container.ContainerRequestContext;
> import javax.ws.rs.container.ContainerResponseContext;
> import javax.ws.rs.container.ContainerResponseFilter;
> import javax.ws.rs.core.Response;
> import javax.ws.rs.ext.Provider;
> @Path("/")
> public class RestService {
>
> @GET
> @Path("/{ide}")
> public Response get(@PathParam("ide") String id) {
> System.out.println("Just passed in method");
> return Response.ok().build();
> }
>
> @Provider
> public static class AuthorizedResponseFilter implements ContainerResponseFilter {
> @Override
> public void filter(ContainerRequestContext arg0,
> ContainerResponseContext arg1) throws IOException {
> System.out.println("Just passed in filter");
> }
> }
> }
> {code}
> - In your development workspace, open {{org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator}} and put a breakpoint on line 441
> - Back in the runtime workspace, remove the @Provider annotation and see the value for 'dirtyRegion'. In my last test, this one alone looked good (offset=559)
> - DO NOT SAVE THE FILE
> - remove the @Path("/") annotation on the RestService type, this time you should have *4* dirty regions, with unexpected values (ie, pointing at other locations in the document).
> As [~akazakov] commented in a private mail:
> {quote}
> JaxrsMetamodelValidator implements IJavaElementValidator and IStringValidator.
> When you remove @Provider then you get the region with offset of the removed JavaElement because you validator implements IJavaElementValidator.
> This interface tells our validation manager that the validator is interested in validating of changes in java elements.
> When you remove @Path("/") you also remove a string ("/") and since your validator implements IStringValidator this validator is notified and you got a list of the regions of all the strings of the file: 4 regions in your case.
> The problem is that you also should have been notified about removed java element because this annotation is not just a String. It's also a java element. That looks like a bug for me.
> So if you remove any code with a string inside then you will get a list of strings of the file (but only if you implements IStringValidator).
> If you don't implement IStringValidator and remove any java element which contains a string you won't be notified at all. This is a bug.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months