[seam-dev] [jbosstools-dev] JBAS 7.1 asking me to create a file called <app>.war.dodeploy for app created in JBT

Mon May 21 00:01:10 EDT 2012

This is the normal method of triggering a deployment in AS7. If you use
JBoss Tools or the JBoss AS7 Maven Plugin (you can use Forge to install and
use this easily), this would have happened automatically, but if you are
doing a deployment by hand then you'll need to create the necessart files.

On Wed, May 16, 2012 at 1:19 PM, Max Rydahl Andersen <
max.andersen at redhat.com> wrote:

> Yes, if you are using our AS 7.x server adapter it will create this file
> automatically.
>
> How did you deploy it ?
>
> /max
>
> On May 16, 2012, at 19:01 , Alexey Kazakov wrote:
>
> > I guess such a file should be created by JBoss AS Tools.
> > Rob, Max?
> >
> >
> > On 05/16/2012 07:06 AM, Daniel Hinojosa wrote:
> >> Hey Alexey,
> >>
> >> When deploying and testing from JBT to JBAS7.1.1 I get the message:
> >>
> >> 07:53:09,039 INFO  [org.jboss.as.server.deployment.scanner]
> (DeploymentScanner-threads - 1) JBAS015003: Found test-seam.war in
> deployment directory. To trigger deployment create a file called
> test-seam.war.dodeploy
> >>
> >> What is responsible for this file? seam-gen or JBT?
> >>
> >> Thanks, Alexey.
> >>
> >> CC:ed relevant groups for public disclosure, bringing "open" to "open
> source" ;)
> >>
> >>
> >>
> >> 07:53:00,223 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
> >> 07:53:01,164 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
> >> 07:53:01,442 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
> "Brontes" starting
> >> 07:53:04,993 INFO  [org.xnio] XNIO Version 3.0.3.GA
> >> 07:53:05,007 INFO  [org.jboss.as.server] JBAS015888: Creating http
> management service using socket-binding (management-http)
> >> 07:53:05,045 INFO  [org.xnio.nio] XNIO NIO Implementation Version
> 3.0.3.GA
> >> 07:53:05,087 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
> >> 07:53:05,240 INFO  [org.jboss.as.logging] JBAS011502: Removing
> bootstrap log handlers
> >> 07:53:05,285 INFO  [org.jboss.as.configadmin] (ServerService Thread
> Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
> >> 07:53:05,371 INFO  [org.jboss.as.naming] (ServerService Thread Pool --
> 38) JBAS011800: Activating Naming Subsystem
> >> 07:53:05,383 INFO  [org.jboss.as.osgi] (ServerService Thread Pool --
> 39) JBAS011940: Activating OSGi Subsystem
> >> 07:53:05,330 INFO  [org.jboss.as.clustering.infinispan] (ServerService
> Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
> >> 07:53:05,440 INFO  [org.jboss.as.security] (ServerService Thread Pool
> -- 44) JBAS013101: Activating Security Subsystem
> >> 07:53:05,584 INFO  [org.jboss.as.webservices] (ServerService Thread
> Pool -- 48) JBAS015537: Activating WebServices Extension
> >> 07:53:05,777 INFO  [org.jboss.as.security] (MSC service thread 1-5)
> JBAS013100: Current PicketBox version=4.0.7.Final
> >> 07:53:05,853 INFO  [org.jboss.as.naming] (MSC service thread 1-8)
> JBAS011802: Starting Naming Service
> >> 07:53:05,906 INFO  [org.jboss.as.connector] (MSC service thread 1-8)
> JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
> >>
> >>
> >> 07:53:06,075 INFO  [org.jboss.as.mail.extension] (MSC service thread
> 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
> >> 07:53:06,171 INFO  [org.jboss.as.connector.subsystems.datasources]
> (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant
> driver class org.h2.Driver (version 1.3)
> >> 07:53:06,925 INFO
>  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread
> 1-7) JBoss Web Services - Stack CXF Server 4.0.2.GA
> >> 07:53:07,190 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC
> service thread 1-3) Starting Coyote HTTP/1.1 on
> http-localhost-127.0.0.1-8080
> >> 07:53:08,661 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC
> service thread 1-7) JBAS010400: Bound data source
> [java:jboss/datasources/ExampleDS]
> >> 07:53:09,017 INFO  [org.jboss.as.server.deployment.scanner] (MSC
> service thread 1-5) JBAS015012: Started FileSystemDeploymentService for
> directory /home/danno/java/jboss-as-7.1.1.Final/standalone/deployments
> >> 07:53:09,026 INFO  [org.jboss.as.remoting] (MSC service thread 1-6)
> JBAS017100: Listening on /127.0.0.1:9999
> >> 07:53:09,026 INFO  [org.jboss.as.remoting] (MSC service thread 1-8)
> JBAS017100: Listening on localhost/127.0.0.1:4447
> >> 07:53:09,039 INFO  [org.jboss.as.server.deployment.scanner]
> (DeploymentScanner-threads - 1) JBAS015003: Found test-seam.war in
> deployment directory. To trigger deployment create a file called
> test-seam.war.dodeploy
> >> 07:53:09,322 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951:
> Admin console listening on http://127.0.0.1:9990
> >> 07:53:09,324 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874:
> JBoss AS 7.1.1.Final "Brontes" started in 10309ms - Started 133 of 208
> services (74 services are passive or on-demand)
> >> 07:53:09,363 INFO  [org.jboss.as.server.deployment] (MSC service thread
> 1-2) JBAS015876: Starting deployment of "test-seam-ds.xml"
> >> 07:53:09,363 INFO  [org.jboss.as.server.deployment] (MSC service thread
> 1-1) JBAS015876: Starting deployment of "hsqldb-2.2.4.jar"
> >
> > _______________________________________________
> > jbosstools-dev mailing list
> > jbosstools-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/seam-dev
>

-- 
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20120521/604e19ed/attachment.html 