RE: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar
When I manually change the name of the artifact like so mv dsc-ear-1.0.ear dsc-ear.ear Now I get this. [EMAIL PROTECTED]:target]$ cd .. [EMAIL PROTECTED]:ear]$ mvn weblogic:deploy [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'weblogic'. [INFO] [INFO] Building DSC:: Enterprise Application [INFO]task-segment: [weblogic:deploy] [INFO] [INFO] Preparing weblogic:deploy [INFO] [ear:generate-application-xml] [INFO] Generating application.xml [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [ear:ear] [INFO] Copying artifact[jar:net.myco.dsc:dsc-ejb:1.0] to[dsc-ejb-1.0.jar] [INFO] Could not find manifest file: /opt/app/devtp/username/builds/dsc/vobs/opus_dev/earpackaging/ear/src/ma in/application/META-INF/MANIFEST.MF - Generating one [INFO] Building jar: /opt/app/devtp/username/builds/dsc/vobs/opus_dev/earpackaging/ear/target /dsc-ear-1.0.ear Downloading: http://corprepo.edc.myco.net:4321/repository/weblogic/webservices/8.1/we bservices-8.1.pom [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [weblogic:deploy] [INFO] Weblogic Deployment beginning weblogic.management.DeploymentException: Error while loading descriptors: Error processing file 'META-INF/application.xml'. weblogic.xml.process.XMLProcessingException: XML document does not appear to contain a properly formed DOCTYPE header - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] weblogic.management.ApplicationException: weblogic.management.DeploymentException: Error while loading descriptors: Error processing file 'META-INF/application.xml'. weblogic.xml.process.XMLProcessingException: XML document does not appear to contain a properly formed DOCTYPE header - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] - with nested exception: [weblogic.xml.process.ProcessorFactoryException: XML document does not appear to contain a properly formed DOCTYPE header] I think Weblogic is not happy with the application descriptor being generated by mvn because there is no DOCTYPE header. How can I instruct maven to add a DOCTYPE Header to the application.xml? Can I create or modify the application.xml manually? [EMAIL PROTECTED]:target]$ cat application.xml ?xml version=1.0 encoding=UTF-8? application xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd; version=1.4 descriptionDSC/description display-nameDSC Enterprise Application/display-name module javadsc-ejb-1.0.jar/java /module /application -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 26, 2006 11:13 AM To: user@mojo.codehaus.org Subject: Re: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar I actually don't use Weblogic much these days, just trying to help Bryan out. ;-) Bryan, let us know how it goes... Wayne On 7/26/06, Scott Ryan [EMAIL PROTECTED] wrote: Yes that will work to change the object that is being sought. you can also use the same structure for deploying the ejb.jar target/dsc-ejb-1.0.jar. I am really trying to get the defaults to work for you guys but in the mean time the overrides will work for you. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 26, 2006 12:31 AM To: user@mojo.codehaus.org Subject: Re: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar Give this a try, it might work (??)... Obviously I'm not positive of all the details, but I think you can figure it out. build plugins plugin groupIdo.a.m.p artifactIdweblogic... configuration objectPathtarget/dsc-ear-1.0.ear/objectPath /configuration ... Wayne - To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar
According to the weblogic documentation.. http://e-docs.bea.com/wls/docs81/programming/app_xml.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar
The only place I specify ejb is in the packagingejb/packaging element of the projects pom. I can not change this and get maven 2.0.4 to generate the ejb-client jars. Why would the weblogic deployer assume a .ejb extension unless maven was somehow passing this to the deployer? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, July 21, 2006 4:32 PM To: user@mojo.codehaus.org Subject: Re: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar If you grok the entire log, you'll find: [INFO] Building ejb dsc-ejb-1.0 [INFO] Building jar: /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb-1.0.jar ... [INFO] Building ejb client dsc-ejb-1.0-client [INFO] Building jar: /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb-1.0-client.jar ... [INFO] Weblogic Deployment parameters [-deploy, -adminurl, http://devbox.wdc.myco.net:32030, -username, guido, -password, something, -name, dsc-ejb, -targets, myapp-frontend-server, -remote, -nostage, -sourcerootforupload, /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb.ejb] weblogic.Deployer$DeployerException: The source file /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb.ejb does not exist and cannot be deployed. So basically you are building a .jar file and then the Weblogic deployer is looking for a .ejb file. Change one or the other and its bound to work, I'd expect. Wayne On 7/21/06, Pauquette, Bryan [EMAIL PROTECTED] wrote: To: 'user@mojo.codehaus.org' Trying to deploy a simple ejb-jar using the weblogic 8.1 plugin. I think I followed all of the instructions correctly but alas I am getting the following. (Sensitive information has been changed in the post). It seems the name of the artifact is not correctly updated to .jar a .ejb extension is being used. I already posted on the maven users list regarding a similar issue a few days ago. Is this a bug? Thanks mvn -e -X weblogic:deploy + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/opt/app/devbox/username/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/opt/app/devbox/myappbuild/.gnu/maven-2.0.4/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Searching for parent-POM: net.myco.dsc:dsc::1.0 of project: null:dsc-ejb:ejb:null in relative path: ../pom.xml [DEBUG] Parent-POM: net.myco.dsc:dsc::1.0 not found in relative path: ../pom.xml [DEBUG] Retrieving parent-POM: net.myco.dsc:dsc::1.0 for project: null:dsc-ejb:ejb:null from the repository. [INFO] Searching repository for plugin with prefix: 'weblogic'. [DEBUG] Skipping disabled repository Maven Snapshots [DEBUG] Skipping disabled repository Maven Snapshots [DEBUG] Skipping disabled repository Maven Snapshots [DEBUG] maven-ejb-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugin-parent::2.0 for project: null:maven-ejb-plugin:maven-plugin:2.0 from the repository. [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] weblogic-maven-plugin: resolved to version 2.8.0-20060304.202223-1 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-sandbox::2-SNAPSHOT for project: null:weblogic-maven-plugin:maven-plugin:2.8.0-20060304.202223-1 from the repository. [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] mojo-sandbox: resolved to version 2-20060213.034901-2 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::7 for project: null:mojo-sandbox:pom:2-SNAPSHOT from the repository. [DEBUG] weblogic-maven-plugin: resolved to version 2.8.0-20060304.202223-1 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-extensions::0.8 for project: null:cargo-maven2-plugin:maven-plugin:0.2 from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo::0.8 for project: null:cargo-extensions:pom:null from the repository. [DEBUG] weblogic-maven-plugin: resolved to version 2.8.0-20060304.202223-1 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-sandbox::2-SNAPSHOT for project: null:weblogic-maven-plugin:maven-plugin:2.8.0-20060304.202223-1 from the repository. [DEBUG] mojo-sandbox: resolved to version 2-20060213.034901-2 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::7 for project: null:mojo-sandbox:pom:2-SNAPSHOT from the repository. [DEBUG] weblogic-maven-plugin: resolved to version 2.8.0-20060304.202223-1 from repository Maven Snapshots [INFO]
RE: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar
THe packaging attribute is used to determine what type of object you are trying to deploy. In weblogic the only types of objects that can actually be deployed are ears and wars so I am not sure why you are running deploy in an ejb project since it will not deploy without being contained inside an EAR. Scott Ryan Chief Technology Officer Soaring Eagle L.L.C. [EMAIL PROTECTED] www.soaringeagleco.com (303) 263-3044 -Original Message- From: Pauquette, Bryan [mailto:[EMAIL PROTECTED] Sent: Friday, July 21, 2006 3:11 PM To: user@mojo.codehaus.org; Maven Users List Subject: RE: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar The only place I specify ejb is in the packagingejb/packaging element of the projects pom. I can not change this and get maven 2.0.4 to generate the ejb-client jars. Why would the weblogic deployer assume a .ejb extension unless maven was somehow passing this to the deployer? -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, July 21, 2006 4:32 PM To: user@mojo.codehaus.org Subject: Re: [mojo-user] Unable to use the weblogic-8.1 plugin to deploy a simple ejb jar If you grok the entire log, you'll find: [INFO] Building ejb dsc-ejb-1.0 [INFO] Building jar: /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb-1.0.jar ... [INFO] Building ejb client dsc-ejb-1.0-client [INFO] Building jar: /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb-1.0-client.jar ... [INFO] Weblogic Deployment parameters [-deploy, -adminurl, http://devbox.wdc.myco.net:32030, -username, guido, -password, something, -name, dsc-ejb, -targets, myapp-frontend-server, -remote, -nostage, -sourcerootforupload, /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb.ejb] weblogic.Deployer$DeployerException: The source file /opt/app/devbox/username/builds/myapp_ssk_dsc_1.0.1/vobs/pos_dev/dsc-pro file-services/target/dsc-ejb.ejb does not exist and cannot be deployed. So basically you are building a .jar file and then the Weblogic deployer is looking for a .ejb file. Change one or the other and its bound to work, I'd expect. Wayne On 7/21/06, Pauquette, Bryan [EMAIL PROTECTED] wrote: To: 'user@mojo.codehaus.org' Trying to deploy a simple ejb-jar using the weblogic 8.1 plugin. I think I followed all of the instructions correctly but alas I am getting the following. (Sensitive information has been changed in the post). It seems the name of the artifact is not correctly updated to .jar a .ejb extension is being used. I already posted on the maven users list regarding a similar issue a few days ago. Is this a bug? Thanks mvn -e -X weblogic:deploy + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: '/opt/app/devbox/username/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/opt/app/devbox/myappbuild/.gnu/maven-2.0.4/conf/plugin-registry.xml' [INFO] Scanning for projects... [DEBUG] Searching for parent-POM: net.myco.dsc:dsc::1.0 of project: null:dsc-ejb:ejb:null in relative path: ../pom.xml [DEBUG] Parent-POM: net.myco.dsc:dsc::1.0 not found in relative path: ../pom.xml [DEBUG] Retrieving parent-POM: net.myco.dsc:dsc::1.0 for project: null:dsc-ejb:ejb:null from the repository. [INFO] Searching repository for plugin with prefix: 'weblogic'. [DEBUG] Skipping disabled repository Maven Snapshots [DEBUG] Skipping disabled repository Maven Snapshots [DEBUG] Skipping disabled repository Maven Snapshots [DEBUG] maven-ejb-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugin-parent::2.0 for project: null:maven-ejb-plugin:maven-plugin:2.0 from the repository. [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] weblogic-maven-plugin: resolved to version 2.8.0-20060304.202223-1 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-sandbox::2-SNAPSHOT for project: null:weblogic-maven-plugin:maven-plugin:2.8.0-20060304.202223-1 from the repository. [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] mojo-sandbox: resolved to version 2-20060213.034901-2 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::7 for project: null:mojo-sandbox:pom:2-SNAPSHOT from the repository. [DEBUG] weblogic-maven-plugin: resolved to version 2.8.0-20060304.202223-1 from repository Maven Snapshots [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo-extensions::0.8 for project: null:cargo-maven2-plugin:maven-plugin:0.2 from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.cargo:cargo::0.8 for project: null:cargo-extensions:pom:null from the repository.
