[JBoss JIRA] (JBIDE-20536) Several quickstarts fail; jboss-ejb3-2_0.xsd cannot resolve jboss elements
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20536?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20536:
-----------------------------------
Fix Version/s: 4.4.0.Alpha3
(was: 4.4.0.Alpha2)
> Several quickstarts fail; jboss-ejb3-2_0.xsd cannot resolve jboss elements
> ---------------------------------------------------------------------------
>
> Key: JBIDE-20536
> URL: https://issues.jboss.org/browse/JBIDE-20536
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server, upstream
> Reporter: Rob Stryker
> Labels: xml_validation_quickstarts_eap7, xml_validation_quickstarts_wildfly, xml_validation_schema_error
> Fix For: 4.4.0.Alpha3
>
>
> Several errors fail with the following error message:
> Referenced file contains errors (file:/home/rob/code/fuseide/fuseide/targetplatform/target/org.fusesource.ide.targetplatform.target.repo/../../../../../jbtools/github/jbosstools-server/as/plugins/org.jboss.tools.as.catalog/schema/xsd/jboss-ejb3-2_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> The schema seems to fail to resolve any elements that have 'jboss' in them, for example:
> {code}
> <xs:element name="enterprise-beans" type="javaee:jboss-enterprise-beansType"/>
> {code}
> When looking at the entire xsd space, I see no attempt to reference or import any remote schema or any jboss schema url or namespace.
> The offending schema file is here:
> {code}<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
> targetNamespace="http://www.jboss.com/xml/ns/javaee"
> xmlns="http://www.jboss.com/xml/ns/javaee"
> xmlns:javaee="http://java.sun.com/xml/ns/javaee"
> elementFormDefault="qualified"
> attributeFormDefault="unqualified"
> version="2.0">
> <!-- xs:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="ejb-jar_3_1.xsd"/ -->
> <!-- xs:import namespace="http://java.sun.com/xml/ns/javaee" schemaLocation="http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"/ -->
> <xs:import namespace="http://java.sun.com/xml/ns/javaee"/>
> <xs:element name="ejb" type="javaee:jboss-ejb-beanType"/>
> <xs:element name="ejb-jar" type="javaee:jboss-ejb-jarType"/>
> <xs:element name="enterprise-beans" type="javaee:jboss-enterprise-beansType"/>
> <xs:element name="destination-jndi-name" type="xs:string" />
> <xs:element name="distinct-name" type="xs:string">
> <xs:annotation>
> <xs:documentation>
> The distinct-name for this EJB module.
> </xs:documentation>
> </xs:annotation>
> </xs:element>
> </xs:schema>
> {code}
> Perhaps I'm not understanding xml enough, but I kinda agree with the validator here, in that there's no clear way to resolve any of the jboss-* elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21606?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21606:
-----------------------------------
Fix Version/s: 4.4.0.Alpha3
(was: 4.4.0.Alpha2)
> Consider using java 8 for EAP 6.4 by default
> --------------------------------------------
>
> Key: JBIDE-21606
> URL: https://issues.jboss.org/browse/JBIDE-21606
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha3
>
>
> Here's the problem that I just hit:
> I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime.
> Then on the project, I just Run -> Run on Server.
> The server started, but deployment failed on Unsupported version: 51.0
> Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6.
> So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22175) Warnings in JBDS after importing kitchensink-jsp quickstart
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22175?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22175:
-----------------------------------
Fix Version/s: 4.4.0.Alpha3
(was: 4.4.0.Alpha2)
> Warnings in JBDS after importing kitchensink-jsp quickstart
> -----------------------------------------------------------
>
> Key: JBIDE-22175
> URL: https://issues.jboss.org/browse/JBIDE-22175
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, upstream
> Reporter: Sande Gilda
> Assignee: Victor Rubezhny
> Fix For: 4.4.0.Alpha3
>
>
> After importing the quickstart into JBDS, the following warnings are produced
> * The tag handler class for "c:forEach" (org.apache.taglibs.standard.tag.rt.core.ForEachTag) was not found on the Java Build Path
> * The tag handler class for "c:out" (org.apache.taglibs.standard.tag.rt.core.OutTag) was not found on the Java Build Path
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-20687) Deployed war is NOT the specified war name
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20687?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-20687:
-----------------------------------
Fix Version/s: 4.4.0.Alpha3
(was: 4.4.0.Alpha2)
> Deployed war is NOT the specified war name
> ------------------------------------------
>
> Key: JBIDE-20687
> URL: https://issues.jboss.org/browse/JBIDE-20687
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, server, upstream
> Affects Versions: 4.3.0.CR1
> Reporter: ehsavoie Hugonnet
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 4.4.0.Alpha3
>
>
> The deployed war name is the *artifactId* and not the specified *warName* from the war plugin nor the *finalName*.
> Sample pom.xml which exibits the issue
> {code:xml}<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.glassfish-samples</groupId>
> <artifactId>auction</artifactId>
> <version>4.0-SNAPSHOT</version>
> <packaging>war</packaging>
> <name>WebSocket Auction Sample Application</name>
>
> <dependencies>
> <dependency>
> <groupId>javax</groupId>
> <artifactId>javaee-api</artifactId>
> <version>7.0</version>
> <scope>provided</scope>
> </dependency>
> </dependencies>
>
> <build>
> <finalName>websocket-auction</finalName>
> <plugins>
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>3.1</version>
> <configuration>
> <source>1.8</source>
> <target>1.8</target>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.3</version>
> <configuration>
> <failOnMissingWebXml>false</failOnMissingWebXml>
> <warName>websocket-auction</warName>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </project>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22193) Can't deploy locally built docker images
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22193?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22193:
-----------------------------------
Fix Version/s: 4.4.0.Alpha3
(was: 4.4.0.Alpha2)
> Can't deploy locally built docker images
> ----------------------------------------
>
> Key: JBIDE-22193
> URL: https://issues.jboss.org/browse/JBIDE-22193
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift, upstream
> Affects Versions: 4.3.1.Final
> Reporter: Fred Bricon
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 4.4.0.Alpha3
>
>
> I can't deploy locally built docker images, pushed to the CDK docker registry, to OpenShift
> Trying to adapt the steps from https://github.com/redhat-developer-tooling/openshift-vagrant#how-to-run-... to Eclipse, I can't seem to be able to deploy anything
> Here's what the CLI generates from
> {quote}
> eval "$(vagrant service-manager env docker)"
> $ oc login 10.1.2.2:8443 -u openshift-dev -p devel
> Login successful.
> $ oc new-project my-ghost
> Now using project "my-ghost" on server "https://10.1.2.2:8443".
> $ docker pull ghost
> $ docker tag ghost hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost
> $ docker login -u openshift-dev -p `oc whoami -t` -e foo(a)bar.com hub.openshift.rhel-cdk.10.1.2.2.xip.io
> $ docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost
> $ oc new-app --image-stream=ghost --name=ghost
> $ oc expose service ghost --hostname=my-ghost-blog.rhel-cdk.10.1.2.2.xip.io
> {quote}
> Deployment Config
> {noformat}
> {
> "kind" : "DeploymentConfig",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "ghost",
> "namespace" : "my-ghost",
> "selfLink" : "/oapi/v1/namespaces/my-ghost/deploymentconfigs/ghost",
> "uid" : "a7dafee5-03c8-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "29849",
> "creationTimestamp" : "2016-04-16T11:45:02Z",
> "labels" : {"app" : "ghost"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftNewApp"}
> },
> "spec" : {
> "strategy" : {
> "type" : "Rolling",
> "rollingParams" : {
> "updatePeriodSeconds" : 1,
> "intervalSeconds" : 1,
> "timeoutSeconds" : 600,
> "maxUnavailable" : "25%",
> "maxSurge" : "25%"
> }
> },
> "triggers" : [
> {"type" : "ConfigChange"},
> {
> "type" : "ImageChange",
> "imageChangeParams" : {
> "automatic" : true,
> "containerNames" : ["ghost"],
> "from" : {
> "kind" : "ImageStreamTag",
> "namespace" : "my-ghost",
> "name" : "ghost:latest"
> },
> "lastTriggeredImage" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8"
> }
> }
> ],
> "replicas" : 1,
> "selector" : {
> "app" : "ghost",
> "deploymentconfig" : "ghost"
> },
> "template" : {
> "metadata" : {
> "labels" : {
> "app" : "ghost",
> "deploymentconfig" : "ghost"
> },
> "annotations" : {
> "openshift.io/container.ghost.image.entrypoint" : "[\"/entrypoint.sh\",\"npm\",\"start\"]",
> "openshift.io/generated-by" : "OpenShiftNewApp"
> }
> },
> "spec" : {
> "volumes" : [{"name" : "ghost-volume-1"}],
> "containers" : [{
> "name" : "ghost",
> "image" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8",
> "ports" : [{
> "containerPort" : 2368,
> "protocol" : "TCP"
> }],
> "volumeMounts" : [{
> "name" : "ghost-volume-1",
> "mountPath" : "/var/lib/ghost"
> }],
> "terminationMessagePath" : "/dev/termination-log",
> "imagePullPolicy" : "Always"
> }],
> "restartPolicy" : "Always",
> "terminationGracePeriodSeconds" : 30,
> "dnsPolicy" : "ClusterFirst"
> }
> }
> },
> "status" : {
> "latestVersion" : 1,
> "details" : {"causes" : [{"type" : "ConfigChange"}]}
> }
> }
> {noformat}
> Image Stream
> {noformat}
> {
> "kind" : "ImageStream",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "ghost",
> "namespace" : "my-ghost",
> "selfLink" : "/oapi/v1/namespaces/my-ghost/imagestreams/ghost",
> "uid" : "98a32494-03c8-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "29842",
> "creationTimestamp" : "2016-04-16T11:44:37Z",
> "annotations" : {"openshift.io/image.dockerRepositoryCheck" : "2016-04-16T11:44:37Z"}
> },
> "status" : {
> "dockerImageRepository" : "172.30.178.20:5000/my-ghost/ghost",
> "tags" : [{
> "tag" : "latest",
> "items" : [{
> "created" : "2016-04-16T11:44:37Z",
> "dockerImageReference" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8",
> "image" : "sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8"
> }]
> }]
> }
> }
> {noformat}
> When following these steps in Eclipse, no deployment occurs. Going to the web console et clicking deploy on the Deployment, no image is found to deploy.
> {quote}
> - Clone https://github.com/burrsutter/cdk_helloworlds/
> - import java/wildflyswarm_helloworld as a Maven Project
> - Run a Maven build (Run As > Maven > package)
> - Edit Dockerfile: replace `FROM rhel7` with `FROM centos`
> - right click on Dockerfile > Run As > Docker Image build
> - Select `CDK Server Adapter at localhost` connection
> - Repository Name : hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm
> - from OpenShift explorer, create a fredo project
> - In OpenShift explorer, right-click the fredo project and Deploy Docker Image...
> - select hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm:latest for the image
> - swarm as resource name
> - click next
> - Deployment configuration & scalability page displays, click next
> - click add route button, click finish
> - resources are created, but no deployment happens
> {quote}
> Here are the resources created from Eclipse:
> Deployment Config
> {noformat}
> {
> "metadata" : {
> "name" : "swarm",
> "namespace" : "fredo",
> "selfLink" : "/oapi/v1/namespaces/fredo/deploymentconfigs/swarm",
> "uid" : "2e9d1df4-03cc-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "30206",
> "creationTimestamp" : "2016-04-16T12:10:17Z",
> "labels" : {"deploymentconfig" : "swarm"},
> "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"}
> },
> "spec" : {
> "strategy" : {
> "type" : "Rolling",
> "rollingParams" : {
> "updatePeriodSeconds" : 1,
> "intervalSeconds" : 1,
> "timeoutSeconds" : 600,
> "maxUnavailable" : "25%",
> "maxSurge" : "25%"
> }
> },
> "triggers" : [
> {"type" : "ConfigChange"},
> {
> "type" : "ImageChange",
> "imageChangeParams" : {
> "automatic" : true,
> "containerNames" : ["swarm"],
> "from" : {
> "kind" : "ImageStreamTag",
> "name" : "swarm:latest"
> }
> }
> }
> ],
> "replicas" : 1,
> "selector" : {"deploymentconfig" : "swarm"},
> "template" : {
> "metadata" : {"labels" : {"deploymentconfig" : "swarm"}},
> "spec" : {
> "containers" : [{
> "name" : "swarm",
> "image" : "fredo/swarm:latest",
> "ports" : [{
> "name" : "8080-tcp",
> "containerPort" : 8080,
> "protocol" : "TCP"
> }],
> "terminationMessagePath" : "/dev/termination-log",
> "imagePullPolicy" : "Always"
> }],
> "restartPolicy" : "Always",
> "terminationGracePeriodSeconds" : 30,
> "dnsPolicy" : "ClusterFirst"
> }
> }
> },
> "apiVersion" : "v1",
> "kind" : "DeploymentConfig"
> }
> {noformat}
> Image Stream
> {noformat}
> {
> "metadata" : {
> "name" : "swarm",
> "namespace" : "fredo",
> "selfLink" : "/oapi/v1/namespaces/fredo/imagestreams/swarm",
> "uid" : "2e42dfc8-03cc-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "30202",
> "creationTimestamp" : "2016-04-16T12:10:16Z",
> "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"}
> },
> "spec" : {"dockerImageRepository" : "hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm"},
> "status" : {"dockerImageRepository" : "172.30.178.20:5000/fredo/swarm"},
> "apiVersion" : "v1",
> "kind" : "ImageStream"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22239:
-----------------------------------
Fix Version/s: 4.4.0.Alpha3
(was: 4.4.0.Alpha2)
> Allow a user to choose to permanently update their desired replicas for their deployment
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-22239
> URL: https://issues.jboss.org/browse/JBIDE-22239
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff Cantrill
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha3
>
>
> When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest:
> * Adding a custom dialog in the "..to.." option
> * Update to use a spinner
> * Add a checkbox to 'make the change perminent'
> * If checkbox=true, you should only need to update the dc if it has a configchange trigger.
> * Optionally show checkbox if unable to determine the dc associated with the deployment.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months