[JBoss JIRA] (JBDS-954) JBoss Server View shown w/o "Deprecated" text in title.
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBDS-954?page=com.atlassian.jira.plugin.... ]
Josef Kopriva closed JBDS-954.
------------------------------
Closing, nothing to do.
> JBoss Server View shown w/o "Deprecated" text in title.
> -------------------------------------------------------
>
> Key: JBDS-954
> URL: https://issues.redhat.com/browse/JBDS-954
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: server
> Environment: WindowsXP SP2
> JBoss Developer Studio
> Version: 3.0.0.M4
> Build id: jbdevstudio-eap-win32-3.0.0.v200911161447M-H94-M4
> JRE 1.6
> Reporter: Aliaksey Nis
> Priority: Optional
> Fix For: 3.0.0.M4
>
>
> JBoss Server View in this build shown w/o "Deprecated" text in title.
> And i think it will be better to replace JBoss Server view with Servers view in default Seam perspective.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-20826) Web module's URL is not detected correctly
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-20826?page=com.atlassian.jira.plug... ]
Josef Kopriva updated JBIDE-20826:
----------------------------------
Fix Version/s: 4.16.0.AM1
> Web module's URL is not detected correctly
> ------------------------------------------
>
> Key: JBIDE-20826
> URL: https://issues.redhat.com/browse/JBIDE-20826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, maven, server
> Affects Versions: 4.3.0.CR1
> Reporter: Lucia Jelinkova
> Assignee: Rob Stryker
> Priority: Major
> Fix For: 4.3.x, 4.16.0.AM1
>
>
> The module's URL is not detected correctly in case project name is different to context-root mentioned in .settings/org.eclipse.wst.common.component.
> This could happen for example when you import Maven project using Easymport.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-20541) wildfly-jts-application-component-2 quickstart fails to validate
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-20541?page=com.atlassian.jira.plug... ]
Josef Kopriva updated JBIDE-20541:
----------------------------------
Component/s: project-examples
> wildfly-jts-application-component-2 quickstart fails to validate
> -----------------------------------------------------------------
>
> Key: JBIDE-20541
> URL: https://issues.redhat.com/browse/JBIDE-20541
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: project-examples, server
> Affects Versions: 4.3.0.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Major
> Labels: xml_validation_quickstart_content, xml_validation_quickstarts_wildfly
> Fix For: 4.3.0.Final
>
>
> See https://issues.jboss.org/browse/WFLY-5250 for followup.
> The above quickstart fails to validate in eclipse. It has the following lines in it:
> {code}
> <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
> xmlns="http://java.sun.com/xml/ns/javaee"
> xmlns:iiop="urn:iiop"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd
> http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-spec-2_0.xsd
> urn:iiop jboss-ejb-iiop_1_0.xsd"
> version="3.1"
> impl-version="2.0">
> <assembly-descriptor>
> <iiop:iiop>
> <ejb-name>InvoiceManagerEJBImpl</ejb-name>
> <iiop:binding-name>jts-quickstart/InvoiceManagerEJBImpl</iiop:binding-name>
> </iiop:iiop>
> </assembly-descriptor>
> </jboss:ejb-jar>
> {code}
> The key line to note is:
> {code}
> urn:iiop jboss-ejb-iiop_1_0.xsd"
> {code}
> Using relative paths cannot guarantee the resolution of a dependent schema. I suggest you replace this with:
> {code}
> urn:iiop http://www.jboss.org/schema/jbossas/jboss-ejb-iiop_1_0.xsd"
> {code}
> However, even once that is fixed, the quickstart still has other problems. For one example:
> {code}
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'iiop:iiop'. One of '{"http://
> java.sun.com/xml/ns/javaee":security-role, "http://java.sun.com/xml/ns/javaee":method-
> permission, "http://java.sun.com/xml/ns/javaee":container-transaction, "http://java.sun.com/xml/ns/
> javaee":interceptor-binding, "http://java.sun.com/xml/ns/javaee":message-destination, "http://
> java.sun.com/xml/ns/javaee":exclude-list, "http://java.sun.com/xml/ns/javaee":application-
> exception}' is expected.
> {code}
> I strongly suggest someone test the quickstart in JBossTools and help come up with a descriptor that passes validation.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-20537) wildfly-ejb-multi-server-app-one-ejb quickstart content incomplete
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-20537?page=com.atlassian.jira.plug... ]
Josef Kopriva updated JBIDE-20537:
----------------------------------
Component/s: project-examples
> wildfly-ejb-multi-server-app-one-ejb quickstart content incomplete
> ------------------------------------------------------------------
>
> Key: JBIDE-20537
> URL: https://issues.redhat.com/browse/JBIDE-20537
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: project-examples, server
> Affects Versions: 4.3.0.CR1
> Reporter: Rob Stryker
> Priority: Major
> Labels: xml_validation_quickstart_content, xml_validation_quickstarts_wildfly
> Fix For: 4.3.0.CR1
>
>
> Even after fixing https://issues.jboss.org/browse/JBIDE-20536 to import some namespaces using exact schema locations on the web, wildfly-ejb-multi-server-app-one-ejb fails to validate.
> The file jboss-ejb3.xml has the following content (trimmed for brevity):
> {code}
> <jboss:ejb-jar (cut out xml:ns stuff) version="3.1" impl-version="2.0">
> <enterprise-beans>
> </enterprise-beans>
> <assembly-descriptor>
> </assembly-descriptor>
> </jboss:ejb-jar>
> {code}
> Unfortunately, empty enterprise-beans tags are invalid according to the xsd against which this is validated. Error message as follows:
> {code}
> cvc-complex-type.2.4.b: The content of element 'enterprise-beans' is not complete. One of '{"http://
> java.sun.com/xml/ns/javaee":session, "http://java.sun.com/xml/ns/javaee":entity, "http://
> java.sun.com/xml/ns/javaee":message-driven}' is expected.
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-20533) Bean-validation quickstart fails to validate in jbt
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-20533?page=com.atlassian.jira.plug... ]
Josef Kopriva updated JBIDE-20533:
----------------------------------
Component/s: project-examples
> Bean-validation quickstart fails to validate in jbt
> ---------------------------------------------------
>
> Key: JBIDE-20533
> URL: https://issues.redhat.com/browse/JBIDE-20533
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: project-examples, server
> Affects Versions: 4.3.0.CR1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Major
> Labels: xml_validation_quickstart_content, xml_validation_quickstarts_wildfly
> Fix For: 4.3.0.CR1
>
>
> bean-validation quickstart fails to validate in arquillian.xml.
> The arquillian_1_0.xsd file includes the following:
> {code}
> <element name="container">
> <complexType>
> <choice minOccurs="1" maxOccurs="unbounded">
> <element ref="tns:configuration" minOccurs="0" maxOccurs="1" />
> <!--
> <element ref="tns:dependencies" minOccurs="0" maxOccurs="1" />
> -->
> <element ref="tns:protocol" minOccurs="0" maxOccurs="unbounded" />
> </choice>
> <attribute name="qualifier" type="string" use="required" />
> <attribute name="default" type="boolean" use="optional" default="false" />
> <attribute name="mode" use="optional" default="suite">
> <simpleType>
> <restriction base="string">
> <enumeration value="suite" />
> <enumeration value="class" />
> <enumeration value="manual" />
> <enumeration value="custom" />
> </restriction>
> </simpleType>
> </attribute>
> </complexType>
> <unique name="unique-protocol-within-container">
> <annotation>
> <documentation>
> @type must be unique between all
> protocols in a container.
> </documentation>
> </annotation>
> <selector xpath="tns:protocol" />
> <field xpath="@type" />
> </unique>
> </element>
> {code}
> The arquillian.xml included in the example includes the following:
> {code}
> <container qualifier="jboss" default="true">
> <!-- By default, arquillian will use the JBOSS_HOME environment variable. Alternatively, the configuration below can be uncommented. -->
> <!--<configuration> -->
> <property name="jbossHome">C:/tools/wildfly-9.0.0.Final</property>
> <!--</configuration> -->
> </container>
> {code}
> Validation error is that "property" is not a valid sub-element, which is true based on the xsd file.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-19328) wf8.2 in fs+rse mode with strange publish behavior (cmd line)
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-19328?page=com.atlassian.jira.plug... ]
Josef Kopriva closed JBIDE-19328.
---------------------------------
Closing, WF 8 is not supported anymore.
> wf8.2 in fs+rse mode with strange publish behavior (cmd line)
> -------------------------------------------------------------
>
> Key: JBIDE-19328
> URL: https://issues.redhat.com/browse/JBIDE-19328
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rob Stryker
> Priority: Major
> Fix For: 4.16.0.AM1
>
>
> 1) Start with a clean wf8.2
> {code}
> rm -rf wildfly-8.2.0.Final.zip.expanded/
> cd ../zipped
> ls -1 wildfly-8.2.0.Final.zip | ./unzipAndMove.sh
> cd ../unzipped/wildfly-8.2.0.Final.zip.expanded/bin/
> ./add-user.sh
> {code}
> 2) Start server in eclipse. filesystem + rse, defaults, localhost, no changes, all standard
> Process command line appears to be as follows:
> 22608 pts/1 Sl+ 0:10 java -Dprogram.name=JBossTools: WildFly 8.x -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/log/boot.log -Dlogging.configuration=file:/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/configuration/logging.properties -Djboss.home.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded -Dorg.jboss.logmanager.nocolor=true -jar /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/jboss-modules.jar -mp /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone
> 3) Copy a simple exploded web project into your deployments folder with a cp -R command. Then, touch WebProjectName.war.dodeploy to ensure it is picked up by server
> 4) Observe following sysout from server:
> 07:23:49,973 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
> 07:23:53,921 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
> 07:23:54,990 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "WebApp1.war" (runtime-name: "WebApp1.war")
> 07:23:55,295 INFO [org.wildfly.extension.undertow] (MSC service thread 1-16) JBAS017534: Registered web context: /WebApp1
> 07:23:55,347 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "WebApp1.war" (runtime-name : "WebApp1.war")
> 07:24:00,366 INFO [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017535: Unregistered web context: /WebApp1
> 07:24:00,381 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-14) HV000001: Hibernate Validator 5.1.3.Final
> 07:24:00,413 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment WebApp1.war (runtime-name: WebApp1.war) in 51ms
> 07:24:00,448 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "WebApp1.war" (runtime-name: "WebApp1.war")
> 07:24:05,451 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
> If we repeat but instead of starting from eclipse, we start from cmd line (standalone.sh) it seems to work, which may indicate a problem in how we're launching (?). Process details when started via standalone are as follows:
> 23536 pts/3 Sl+ 0:10 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/log/server.log -Dlogging.configuration=file:/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/configuration/logging.properties -jar /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/jboss-modules.jar -mp /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/modules org.jboss.as.standalone -Djboss.home.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded -Djboss.server.base.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-19328) wf8.2 in fs+rse mode with strange publish behavior (cmd line)
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-19328?page=com.atlassian.jira.plug... ]
Josef Kopriva closed JBIDE-19328.
---------------------------------
Resolution: Done
> wf8.2 in fs+rse mode with strange publish behavior (cmd line)
> -------------------------------------------------------------
>
> Key: JBIDE-19328
> URL: https://issues.redhat.com/browse/JBIDE-19328
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rob Stryker
> Priority: Major
> Fix For: 4.16.0.AM1
>
>
> 1) Start with a clean wf8.2
> {code}
> rm -rf wildfly-8.2.0.Final.zip.expanded/
> cd ../zipped
> ls -1 wildfly-8.2.0.Final.zip | ./unzipAndMove.sh
> cd ../unzipped/wildfly-8.2.0.Final.zip.expanded/bin/
> ./add-user.sh
> {code}
> 2) Start server in eclipse. filesystem + rse, defaults, localhost, no changes, all standard
> Process command line appears to be as follows:
> 22608 pts/1 Sl+ 0:10 java -Dprogram.name=JBossTools: WildFly 8.x -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/log/boot.log -Dlogging.configuration=file:/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/configuration/logging.properties -Djboss.home.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded -Dorg.jboss.logmanager.nocolor=true -jar /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/jboss-modules.jar -mp /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone
> 3) Copy a simple exploded web project into your deployments folder with a cp -R command. Then, touch WebProjectName.war.dodeploy to ensure it is picked up by server
> 4) Observe following sysout from server:
> 07:23:49,973 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
> 07:23:53,921 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
> 07:23:54,990 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "WebApp1.war" (runtime-name: "WebApp1.war")
> 07:23:55,295 INFO [org.wildfly.extension.undertow] (MSC service thread 1-16) JBAS017534: Registered web context: /WebApp1
> 07:23:55,347 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "WebApp1.war" (runtime-name : "WebApp1.war")
> 07:24:00,366 INFO [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017535: Unregistered web context: /WebApp1
> 07:24:00,381 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-14) HV000001: Hibernate Validator 5.1.3.Final
> 07:24:00,413 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment WebApp1.war (runtime-name: WebApp1.war) in 51ms
> 07:24:00,448 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "WebApp1.war" (runtime-name: "WebApp1.war")
> 07:24:05,451 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
> If we repeat but instead of starting from eclipse, we start from cmd line (standalone.sh) it seems to work, which may indicate a problem in how we're launching (?). Process details when started via standalone are as follows:
> 23536 pts/3 Sl+ 0:10 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/log/server.log -Dlogging.configuration=file:/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/configuration/logging.properties -jar /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/jboss-modules.jar -mp /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/modules org.jboss.as.standalone -Djboss.home.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded -Djboss.server.base.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-19328) wf8.2 in fs+rse mode with strange publish behavior (cmd line)
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-19328?page=com.atlassian.jira.plug... ]
Josef Kopriva updated JBIDE-19328:
----------------------------------
Fix Version/s: 4.16.0.AM1
> wf8.2 in fs+rse mode with strange publish behavior (cmd line)
> -------------------------------------------------------------
>
> Key: JBIDE-19328
> URL: https://issues.redhat.com/browse/JBIDE-19328
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Reporter: Rob Stryker
> Priority: Major
> Fix For: 4.16.0.AM1
>
>
> 1) Start with a clean wf8.2
> {code}
> rm -rf wildfly-8.2.0.Final.zip.expanded/
> cd ../zipped
> ls -1 wildfly-8.2.0.Final.zip | ./unzipAndMove.sh
> cd ../unzipped/wildfly-8.2.0.Final.zip.expanded/bin/
> ./add-user.sh
> {code}
> 2) Start server in eclipse. filesystem + rse, defaults, localhost, no changes, all standard
> Process command line appears to be as follows:
> 22608 pts/1 Sl+ 0:10 java -Dprogram.name=JBossTools: WildFly 8.x -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/log/boot.log -Dlogging.configuration=file:/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/configuration/logging.properties -Djboss.home.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded -Dorg.jboss.logmanager.nocolor=true -jar /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/jboss-modules.jar -mp /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b 0.0.0.0 --server-config=standalone.xml -Djboss.server.base.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone
> 3) Copy a simple exploded web project into your deployments folder with a cp -R command. Then, touch WebProjectName.war.dodeploy to ensure it is picked up by server
> 4) Observe following sysout from server:
> 07:23:49,973 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
> 07:23:53,921 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
> 07:23:54,990 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "WebApp1.war" (runtime-name: "WebApp1.war")
> 07:23:55,295 INFO [org.wildfly.extension.undertow] (MSC service thread 1-16) JBAS017534: Registered web context: /WebApp1
> 07:23:55,347 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "WebApp1.war" (runtime-name : "WebApp1.war")
> 07:24:00,366 INFO [org.wildfly.extension.undertow] (MSC service thread 1-10) JBAS017535: Unregistered web context: /WebApp1
> 07:24:00,381 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-14) HV000001: Hibernate Validator 5.1.3.Final
> 07:24:00,413 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment WebApp1.war (runtime-name: WebApp1.war) in 51ms
> 07:24:00,448 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "WebApp1.war" (runtime-name: "WebApp1.war")
> 07:24:05,451 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found WebApp1.war in deployment directory. To trigger deployment create a file called WebApp1.war.dodeploy
> If we repeat but instead of starting from eclipse, we start from cmd line (standalone.sh) it seems to work, which may indicate a problem in how we're launching (?). Process details when started via standalone are as follows:
> 23536 pts/3 Sl+ 0:10 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/log/server.log -Dlogging.configuration=file:/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone/configuration/logging.properties -jar /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/jboss-modules.jar -mp /home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/modules org.jboss.as.standalone -Djboss.home.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded -Djboss.server.base.dir=/home/rob/apps/jboss/unzipped/wildfly-8.2.0.Final.zip.expanded/standalone
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months