[JBoss JIRA] (JBIDE-26173) Validation for 'oc executable location' in Preferences OpenShift 3 page does not allow to keep value empty
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26173?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26173:
------------------------------------------
I would think that this is correct since the tooling wont work properly in many areas if you dont have an oc binary.
I can fix this by hitting "Restore Default". OC then gets filled out by what is found on $PATH (if it exists). Doesn't this work for you?
> Validation for 'oc executable location' in Preferences OpenShift 3 page does not allow to keep value empty
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26173
> URL: https://issues.jboss.org/browse/JBIDE-26173
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Ondrej Dockal
> Assignee: Andre Dietisheim
> Priority: Critical
>
> When user chooses Preferences -> Jboss Tools -> OpenShift 3 and does nothing (ie. when one just clicked to wrong page), the page cannot be changed, 'Could not accept changes' dialog pops up and user must cancel Preferences dialog.
> I suggest to not validate empty oc location.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26029) Incorrect warning for @Inject ServletContext
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26029?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26029:
---------------------------------------
Cannot change PRs label. Strange. Resolving once more.
> Incorrect warning for @Inject ServletContext
> --------------------------------------------
>
> Key: JBIDE-26029
> URL: https://issues.jboss.org/browse/JBIDE-26029
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.5.3.Final
> Reporter: Rich DiCroce
> Assignee: Jeff MAURY
> Fix For: 4.6.0.AM3
>
>
> If you inject ServletContext into a CDI bean, it gets flagged with this warning:
> {quote}
> No bean is eligible for injection to the injection point [JSR-346 §5.2.2]
> {quote}
> This warning appears to be correct for CDI 1.0, but not for later versions. From CDI 2.0 spec section 18.8 (also CDI 1.1/1.2 section 3.8):
> {quote}
> A servlet container must provide the following built-in beans, all of which have qualifier @Default:
> * a bean with bean type javax.servlet.http.HttpServletRequest, allowing injection of a reference to the HttpServletRequest
> * a bean with bean type javax.servlet.http.HttpSession, allowing injection of a reference to the HttpSession,
> * a bean with bean type javax.servlet.ServletContext, allowing injection of a reference to the ServletContext,
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26094) Debugging support: Basic Implementation
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26094?page=com.atlassian.jira.plugi... ]
Jan Richter commented on JBIDE-26094:
-------------------------------------
Trying to launch wildfly 12 in debug mode, gets stuck 'starting', the only output from the server process is
{noformat}Listening for transport dt_socket at address: 34881{noformat}
The debug info from server/startServerAsync
{noformat}Object {status: Object, details: Object}
details: Object {cmdLine: Array(23), workingDir: "/home/jrichter/Downloads/wildfly-12.0.0.Final/bin", properties: Object}
cmdLine: Array(23) ["/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc…", "-agentlib:jdwp=transport=dt_socket,server=y,suspen…", "-Dprogram.name=JBossTools: id", …]
length: 23
0: "/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/bin/java"
1: "-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=localhost:41881"
2: "-Dprogram.name=JBossTools: id"
3: "-server"
4: "-Xms64m"
5: "-Xmx512m"
6: "-Dorg.jboss.resolver.warning=true"
7: "-Djava.net.preferIPv4Stack=true"
8: "-Dsun.rmi.dgc.client.gcInterval=3600000"
9: "-Dsun.rmi.dgc.server.gcInterval=3600000"
10: "-Djboss.modules.system.pkgs=org.jboss.byteman"
11: "-Djava.awt.headless=true"
12: "-Dorg.jboss.boot.log.file=/home/jrichter/Downloads/wildfly-12.0.0.Final/standalone/log/boot.log"
13: "-Dlogging.configuration=file:/home/jrichter/Downloads/wildfly-12.0.0.Final/standalone/configuration/logging.properties"
14: "-Djboss.home.dir=/home/jrichter/Downloads/wildfly-12.0.0.Final"
15: "-Dorg.jboss.logmanager.nocolor=true"
16: "-Djboss.bind.address.management=localhost"
17: "-classpath"
18: "/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.172-9.b11.fc27.x86_64/jre/lib/charsets.jar:/home/jrichter/Downloads/wildfly-12.0.0.Final/jboss-modules.jar"
19: "org.jboss.modules.Main"
20: "-mp"
21: "/home/jrichter/Downloads/wildfly-12.0.0.Final/modules"
22: "org.jboss.as.standalone"
properties: Object {debug.details.host: "localhost", debug.details.type: "java", debug.details.port: "41881", …}
debug.details.host: "localhost"
debug.details.port: "41881"
debug.details.type: "java"
debug.java.server: "y"
debug.java.suspend: "y"
debug.java.transport: "dt_socket"
workingDir: "/home/jrichter/Downloads/wildfly-12.0.0.Final/bin"
status: Object {severity: 0, pluginId: "unknown", code: 0, …}
code: 0
message: "ok"
pluginId: "unknown"
severity: 0{noformat}
Is the implementation too basic for the server to start, or am I missing something?
> Debugging support: Basic Implementation
> ---------------------------------------
>
> Key: JBIDE-26094
> URL: https://issues.jboss.org/browse/JBIDE-26094
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: stack-server-protocol
> Affects Versions: 4.6.0.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.Final
>
>
> Allow for basic support for debugging. The two usecases which should be covered are:
> 1) server/getLaunchCommand
> 2) server/startServerAsync
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26101) CreateServer request fails when ssp is running in Apache Felix
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26101?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-26101.
-------------------------------
Verified, closing.
> CreateServer request fails when ssp is running in Apache Felix
> --------------------------------------------------------------
>
> Key: JBIDE-26101
> URL: https://issues.jboss.org/browse/JBIDE-26101
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Environment: server is running in Apache Felix as
> {code}java -jar bin/felix.jar{code}
> server/createServer request fails with exceptions
> {code}SEVERE: Internal error: java.lang.reflect.InvocationTargetException
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.lambda$null$0(GenericEndpoint.java:63)
> at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.request(GenericEndpoint.java:116)
> at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handleRequest(RemoteEndpoint.java:252)
> at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.consume(RemoteEndpoint.java:181)
> at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.handleMessage(StreamMessageProducer.java:183)
> at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:92)
> at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:95)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.lsp4j.jsonrpc.services.GenericEndpoint.lambda$null$0(GenericEndpoint.java:61)
> ... 11 more
> Caused by: java.lang.NoClassDefFoundError: org/jboss/tools/ssp/server/spi/model/polling/IPollResultListener
> at org.jboss.tools.ssp.server.wildfly.servertype.impl.JBossServerFactory.createServerDelegate(JBossServerFactory.java:41)
> at org.jboss.tools.ssp.server.model.ServerModel.createServer(ServerModel.java:97)
> at org.jboss.tools.ssp.server.ServerManagementServerImpl.createServer(ServerManagementServerImpl.java:215)
> ... 16 more
> Caused by: java.lang.ClassNotFoundException: org.jboss.tools.ssp.server.spi.model.polling.IPollResultListener not found by org.jboss.tools.ssp.server [12]
> at org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1639)
> at org.apache.felix.framework.BundleWiringImpl.access$200(BundleWiringImpl.java:80)
> at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:2053)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 19 more
> {code}
> Reporter: Denis Golovin
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.6.0.Final
>
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (JBIDE-26070) [SSP] Client Managed workflow
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26070?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-26070.
-------------------------------
Closing as done.
> [SSP] Client Managed workflow
> -----------------------------
>
> Key: JBIDE-26070
> URL: https://issues.jboss.org/browse/JBIDE-26070
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Affects Versions: 4.6.0.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.0.AM3
>
>
> aged flow
> @startuml
> Client -> Adaptor : findservers
> Client <- Adaptor : serverlist
> Client -> Adaptor : create server
> Client <- Adaptor : serverAdded (id)
> Client -> Adaptor : getLaunchProperties()
> Adapter -> Client : here’s a list
> Client -> Adaptor : getLaunchCommand(String serverId, String mode, Map<String,String> properties)
> Client <- Adaptor : launch string (id)
> Client -> Adaptor : server started
> Client -> Adaptor : server stopped
> Client -> Adaptor : publish
> @enduml
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months