Alternate deployment descriptor for an exploded war (web.xml/weblogic.xml)

Hi.
I believe this is a simple question: Am i able to deploy an exploded war directory using an alternate deployment descriptor (web.xml outside the directory structure of my application)? According to the docs, I can do it for an ear, but I'm not sure if it can be done for an war.
http://download.oracle.com/docs/cd/E13222_01/wls/docs81b/deployment/concepts.html#1001945
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/config_xml/Application.html#AltDescriptorPath
Thanks in advance.
Best regards,
Daniel.

Or should i use a deployment plan?
http://download.oracle.com/docs/cd/E13222_01/wls/docs103/deployment/config.html#wp1057141

Similar Messages

Failed to save deployment descriptor for: EEdnc cause: null

I am getting nowhere fast trying to deploy an ear with 1 EJB jar and a war file.
The war deploys by itself ok. So the EJB jar has 2 stateless beans and an MDB
configured for mqseries. I deployed a sample with some EJBs so the configuration
must be ok. It verifies with no errors, compiles with ejbc, javac and rmi ok. then I get
this error...
I was wondering if anyone has run into this before or if an expert knows what it is.
I have been using the admin console to deploy as well as asadmin.
\j2ee-apps\EEdnc\com\boeing\bca\ednc\ejbcontainer\services\imsaccess\_IMSAccess_Stub.class
[24/Sep/2003:10:47:33] INFO ( 1564): DPL5110: EJBC - END of EJBC for [EEdnc]
[24/Sep/2003:10:47:33] FINE ( 1564): [Application]uid: 69758199598546944
[24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: BoltsReceiver
[24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546944
[24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: IMSAccess
[24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546945
[24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc name: JmsEjb
[24/Sep/2003:10:47:33] FINE ( 1564): [Application]desc id: 69758199598546946
[24/Sep/2003:10:47:33] FINE ( 1564): Saving the app descriptor....................
[24/Sep/2003:10:47:33] WARNING ( 1564): DPL5035:Error while running ejbc
com.iplanet.ias.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: EEdnc
cause: null
     at com.iplanet.ias.deployment.backend.EJBCompiler.wrapException(EJBCompiler.java:589)
     at com.iplanet.ias.deployment.backend.EJBCompiler.compile(EJBCompiler.java:186)
     at com.iplanet.ias.deployment.backend.AppDeployer.runEJBC(AppDeployer.java:215)
     at com.iplanet.ias.deployment.backend.AppDeployer.deploy(AppDeployer.java:98)
     at com.iplanet.ias.deployment.backend.AppDeployer.doRequest(AppDeployer.java:50)
     at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplicationArchiveOrDirectory(ManagedServerInstance.java:745)
     at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployJ2EEApplication(ManagedServerInstance.java:667)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.iplanet.ias.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:188)
     at com.iplanet.ias.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:137)
     at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:222)
     at com.iplanet.ias.admin.servermodel.controllers.SOMRequestDispatcher.invoke(SOMRequestDispatcher.java:88)
     at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.doDeploy(AppServerInstanceController.java:2244)
     at com.iplanet.ias.admin.servermodel.controllers.AppServerInstanceController.deployApplication(AppServerInstanceController.java:1099)
     at com.iplanet.ias.admin.servermodel.AppServerInstance.deployApplication(AppServerInstance.java:249)
     at com.iplanet.ias.admin.server.gui.jato.DeployEARApplicationViewBean.add(DeployEARApplicationViewBean.java:111)
     at com.iplanet.ias.admin.server.gui.jato.IASViewBean.handleOkRequest(IASViewBean.java:235)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.iplanet.jato.view.command.DefaultRequestHandlingCommand.execute(DefaultRequestHandlingCommand.java:183)
     at com.iplanet.jato.view.RequestHandlingViewBase.handleRequest(RequestHandlingViewBase.java:299)
     at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:811)
     at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:749)
     at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandler(ViewBeanBase.java:596)
     at com.iplanet.jato.ApplicationServletBase.dispatchRequest(ApplicationServletBase.java:772)
     at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:446)
     at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:324)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
     at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
     at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
     at org.apache.catalina.core.StandardHostValve.invoke(Standar
[24/Sep/2003:10:47:34] WARNING ( 1564): Deployment Error
com.iplanet.ias.deployment.backend.IASDeploymentException: Error while running ejbc -- Fatal Error from EJB Compiler -- -- Failed to save deployment descriptor for: EEdnc
cause: null

I don't remember exactly what it was, but I think it was a JNDI name. I resolved it by using
<ejb-link></ejb-link> in the ejb-local-ref in the ejb-jar.xml. I made the ejb-link match the
ejb-name in the same descriptor. This seemed to work better than changing the jndi-name in the sun-ejb-jar.xml.
One thing you can do is set the logging for server1 to finest, then bounce the server and deploy.
Shut down the server and look at the log with wordpad. Start at the bottom and work your
way up looking for stack traces. They get more and more detailed as you go up and may
point you to the exact problem. Works most of the time.

Weblogic Deployment Descriptor for CMP EJB

Hi all,
Am new to EJB, CMP. Pls help me how to write deployment descriptors for the CMP EJB for Weblogic.
Give me the list of the Deployment descriptors needed and also pls give me some samples
thanks in advance
rgds
Ravi Bharathi

The easiest way is to go through some tutorial or refer the code samples. If you have installed weblogic, there are examples provided in the weblogic installation folder itself for each type of bean. Basically for cmp you have to provide the table names and mapping between the class variables to db fields in weblogic_cmp_rdbms.xml deployment descriptor.

Plugin to migrate deployment descriptors for J2EE apps

I was told there is a JDev 10g plugin that deals with migration of deployment descriptors for different kinds of J2EE application servers.
If it is true, what is the plugin name? Is it already contained within JDev or we are supposed to download and install it?
Regards,
Eduardo Gouvea.

Have a look at the deployment desriptor category in the JDeveloper new gallery - you'll see support for OC4J, JBoss, and Weblogic built-in.

Weblogic 10 jaas and login.jsp and web.xml/weblogic.xml security constaints

Hello,
I struggled through and got the examples.security.jaas.SampleCallbackHandler.java and examples.common.utils.ExampleUtils.java/ExampleConstants.java into eclipse where they compile. A bean I made can call SambleCallbackHandler like such:
mybean.logmein(username,password,url). I can then do a mybean.getStatus() or even a mybean.returnCode(). It does seem to correctly identlify that it is authenticating me (I see in stdout logs that it shows success or failures. The problem I have is I do not know how to apply this weblogic and web.xml/weblogic.xml so that if authentication works it redirects me to the page requiring the authentication. In web.xml I have the following set up:
<security-role>
     <role-name>Admins</role-name>
</security-role>
<login-config>
     <auth-method>FORM</auth-method>
     <realm-name>default</realm-name>
     <form-login-config>
          <form-login-page>/login.jsp</form-login-page>
          <form-error-page>/badlogin.html</form-error-page>
     </form-login-config>
</login-config>
<security-constraint>
     <web-resource-collection>
          <web-resource-name>empower</web-resource-name>
          <description>These pages are only accessible by authorized users.</description>
          <url-pattern>/admin/*</url-pattern>
          <http-method>GET</http-method>
          <http-method>POST</http-method>
     </web-resource-collection>
<auth-constraint>
<description>These are the roles who have access</description>
<role-name>Administrators</role-name>
</auth-constraint>
     <user-data-constraint>
     <description>This is how the user data must be transmitted</description>
     <transport-guarantee>NONE</transport-guarantee>
     </user-data-constraint>
</security-constraint>
My weblogic.xml has:
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
<wls:security-role-assignment>
<wls:role-name>Admins</wls:role-name>
<wls:principal-name>Administrators</wls:principal-name>
<wls:principal-name>dashap</wls:principal-name>
</wls:security-role-assignment>
</wls:weblogic-web-app>
With this set up, if I try to go to a page in /admin folder in my application, it correctly pops up the login page. The jaas in the bean is doing a loginContext.login(), which I thought does authentication too, but it never goes back to the /admin page I was going to that needed the authentication. With jaas, can I not use the web.xml FORM security option? Do I Need to use j_security in the login.jsp's form's action= option and j_username and j_password for the input type names? How do I use j_username/j_password things if I am using jaas? I could just ignore using the web.xml security stuff and put something in the pages that need authentication, but it would be easier if I could use jaas with the security featurs without doing all that. Note that my code above is using a realm called default just because that was what was in the example I got from the web. Does that need to be something else?

Hi John,
I would like magic of course. However, in this case I want something special: my authentication provider uses special means and contents of headers, cookies and service from external identity management systems to determine the user's identity.
I do not want the application to present the login dialog! I want to derive the identity and the fact that the user is logged in from whatever the authentication provider returns in terms of Subject.
Ideally, the flow is something like:
- user accesses an unprotected resource - resource is shown, no interaction with authentication provider
- user presses a link or button that takes him/her to a protected resource
- the authentication provider is contacted to work with the identity asserter to establish the identity of the current user and create a subject object for this user
- the application can access the subject and principals
- ADF Security recognizes the identity and the roles (based on the principals) and coordinates access based on this.
the authentication method is client certificate. presumably this prompts WebLogic/OPS to use an identity asserter to work with custom headers and cookies ("... when you configure a web application to use CLIENT-CERT authentication. In this case, WebLogic can perform identity assertion based on values from request headers and cookies. If the header name or cookie name matches the active token type for the provider, the value is passed to the provider."). No login form should be presented to the user, as all information required to perform the authentication is already available.
I am trying to understand what I must do to have the ADF application adopt the subject set by the authentication provider - if anything?!
If you more ideas to share - I would love to hear them.
best regards,
Lucas

Refreshing JSP file for an exploded WAR without undeploying the WAR - 7210

The weblogic.Deployer utility with -activate option does redeploy my application. How do I prevent redeployment while refreshing. I'm using Weblogic 7.0.0.0.
          Thanks
          Senthil Kumar.S


Thanks mbg for your response.
          Our production environment does not support the option a. We use the
          option b approach.
          My config.xml looks like this for the webapplication
          <Application Deployed="true" Name="oas"
          Path="/tmp/senthil/oas3.7.1.5"
          StagedTargets="DOAS_MT_021_20501" TwoPhase="true">
          <WebAppComponent Name="oas" Targets="DOAS_MT_CLUSTER_1"
          URI="oas"/>
          </Application>
          I performed the following steps..
          1) Modified the following jsp file on the admin.
          /tmp/senthil/oas3.7.1.5/oas/customercare/contactus.jsp
          2) Ran the following command on the admin
          java weblogic.Deployer -adminurl t3://n.n.n.n:20501 -user system
          -password weblogic -name oas -activate customercare/contactus.jsp
          after running the command,
          I was able to identify the corresponding jsp file immediately updated
          on the managed instance under the stage folder. But the class file on
          the stage folder was not updated and neither the class file on the
          .wlnotdelete folder. I was using the pagecheckseconds on the
          weblogic.xml as -1.
          I stopped both the admin and manage, modified the pagecheckseconds to
          1 Hour and when I performed same steps as before, I was able to see
          the jsp file updated and also getting compiled (when accessed) and
          serving the updated content. Also the user session was kept intact.
          i.e. no interruption to the session. This was what I was expecting
          for. The strange thing is, it didn't wait for one hour to compile. It
          was compiling immediately when I accessed the modified jsp file. I'm
          not sure whether it would behave the same way if I put that value as 1
          day or some very big +ve value.
          I'm not sure whether I'm doing the right way. i.e. changing the
          pagecheckseconds to ve value. Also I'm not sure whether the ve value
          for the pagecheckseconds would create impact on performance.
          Thanks for your time.
          Senthil Kumar.S
          "Mark Griffith" <[email protected]> wrote in message news:<[email protected]>...
          > Ahh clarity. :D
          >
          > You can:
          >
          > a) deploy your exploded web app with -nostage option. Meaning nocopy, or in
          > otherwords "WLS when you deploy this Application to each server in the
          > cluster, don't copy the bits to each server, just deploy from this src".
          > What that means is that the path that maps to the directory of your webapp
          > must be accessible, or resolvable on each server that it is deployed to.
          >
          > java weblogic.Deploy .... -nostage -activate -source /myapps/mywebapp
          >
          > so that /myapps/mywebapp must be resolvable on each server that it is
          > deployed to. You can accomplish this via a shared network directory for
          > /myapps or you can copy and create /myapps your self on each of the
          > machines.
          >
          > b) deploy your exploded web app with -stage option. Meaning copy, or in
          > otherwords "WLS when you deploy this Application to each server in the
          > cluster, do copy the bits from my "source" to each server" In this case,
          > you will have to use refresh
          >
          > What command did you execute on with weblogic.Deployer
          >
          > Cheers
          > mbg
          >
          >
          >
          > "Senthil Kumar S" <[email protected]> wrote in
          > message news:[email protected]...
          > > Let me rephrase my requirement..
          > > My production environment is Weblogic 7.0.1 with a clustered environment
          > with exploded WAR.
          > > How do I refresh my jsp files with out undeploying my web application?
          > >
          > > When I tried by modifying the jsp file on the exploded directory on the
          > admin and ran the weblogic.Deployer utility, it successfully updated the
          > copy on the managed instance (I verified by checking the stage directory).
          > But the jsp was never recompiled on the managed instance and it was serving
          > old content.
          > >
          > > Thanks
          > > Senthil Kumar.S

Deployment Descriptor for SOA-SAR files on weblogic?

Hi,
i want to access a shared library (that i deployed separately) from within a SOA Project with an SCA composite that is deployed as a SOA-SAR.
I am using JDeveloper 11.1.1.3 along with the according Weblogic Server and SOA Suite.
My shared library is deployed correctly, because i can access it from e.g. other web applications. These are deployed as war files and therefore i have a weblogic.xml file, where i define my library-refs. The problem is, that weblogic.xml as well as weblogic-application.xml seem not to be processed when deploying the SOA-SAR file. Is there another descriptor for that, or is it just not possible to access shared libraries from within a SOA Project deployed as SOA-SAR?
For some more background information, i have my entities deployed as a shared library in weblogic (deployed as a web application(war file)). Now i want to create an SCA composite with a Spring component. A Bean defined in the Spring context shall access the entities from within the shared library.
I hope someone has a solution for this, because i already spent a lot of time on searching for a solution and did not even get close to one. The closest solution i found was deploying the SCA composite as a web application using in Spring the sca:service tag. In that case i have the problem that i want to use the SCA composite from within another SCA composite and i want it to use a local call, not a SOAP request for performance reasons. So this solution unfortunately doesn't fit my requirements.

Please ask this in the SOA Suite forum:
SOA Suite
You might also find the answer in the SOA Suite 11g docs:
http://download.oracle.com/docs/cd/E12839_01/soa.htm

How To Define Security in the deployment descriptor for an ejb

Hi All
Pls help!
I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
Thanks
Yours in Java

Hi All
Pls help!
I am trying to call a remote ejb running on JBOSS in a remote server. Typically inside my code I would include a System.setSecurityManager() = new RMISecurityManager () etc. and specify a security policy file to use when running my client.
But since I am running inside the application server where many other applications are running, I cannot use system.abc() it breaks everyone's application.
Can someone please refer me to how to specify security manager policy inside the ejb-jar.xml deployment descriptor or how I can resolve the above issue. O am using OC4J to run my ejbs.
Thanks
Yours in Java

Web.xml / weblogic.xml security

Let's say I define security constraints in the web.xml file for my web application
using the security-constraint,auth-constraint, and security-role tags. Does this
mean that in order to add a new user I must modify weblogic.xml and specify a
new security-role-assignment? Can I specify a group name as a principal, or is
there a way to programatically add new users? Any help would be greatly appreciated.
Thank you.

yes, you can use groups as principals in weblogic.xml. then permissions are
managed through the user-group relationship.
"Leonard Pham" <[email protected]> wrote in message
news:3b657f8a$[email protected]..
>
Let's say I define security constraints in the web.xml file for my webapplication
using the security-constraint,auth-constraint, and security-role tags.Does this
mean that in order to add a new user I must modify weblogic.xml andspecify a
new security-role-assignment? Can I specify a group name as a principal,or is
there a way to programatically add new users? Any help would be greatlyappreciated.
Thank you.

Directory Structure ?s for an Exploded Web Application

We have an application that consists only of JSPs and Servlets, no
EJBs. I am researching whether or not it's worthwhile to start using
EJBs. We're also migrating from Weblogic 5 to 6.1. I've managed to
migrate our application fine and have it up and running on WLS 6.1.
I'm confused about the exploded directory structure, the
application.xml file, where to put the EJBs and whether or not I have
to jar them. Here's our current directory structure:
DefaultWebApp/               JSPs here
DefaultWebApp/WEB-INF          web.xml and weblogic.xml here
DefaultWebApp/WEB-INF/classes     Servlets and other classes here
DefaultWebApp/WEB-INF/lib     do my un-jar-ed EJBs go here?
I've been reading a lot of BEA's documentation, particularly
‘Deploying an Exploded J2EE Application' and a ‘Web Application PDF',
and looking for relevant threads on the weblogic.developer.interest
groups. It looks like the application.xml should go in a new
DefaultWebApp/META-INF directory. But where do the EJBs go?
I also see some directory structures with another /web directory
that's confusing me.
Oh, I've also managed to compile and jar up a trial Stateless Session
EJB. Then I think I ‘auto-deployed' it into the /applications
directory, and Weblogic seems to recognize it. But when I tried to
reference it in a JSP, I got an error message ‘class x is public,
should be declared in a file named x.java'. I'm assuming this is
related to the application.xml, where I need to define the ejb
directory.
Thanks.

To deploy your web app together with your EJBs, you need to create
an "EAR" structure. Both your webapp and your EJB jars will be within
this new structure, at the same level. You may jar up your EJBs, or you
may explode their structure, it's up to you.
The resulting structure should look something like below:
EnterpriseApp/ <-- new top level
EnterpriseApp/META-INF/
EnterpriseApp/META-INF/application.xml
EnterpriseApp/lib/ <-- shared libraries (if any)
EnterpriseApp/EJB/ <-- ejbs go here
EnterpriseApp/EJB/META-INF/ejb-jar.xml
EnterpriseApp/EJB/META-INF/weblogic-ejb-jar.xml
EnterpriseApp/EJB/com/your/ejb/classes/here
EnterpriseApp/WebApp/ <-- move your current app here
EnterpriseApp/WebApp/index.jsp <-- JSPs goes here
EnterpriseApp/WebApp/other.jsp
EnterpriseApp/WebApp/WEB-INF/web.xml
EnterpriseApp/WebApp/WEB-INF/weblogic.xml
EnterpriseApp/WebApp/WEB-INF/lib <-- ui libraries go here
EnterpriseApp/WebApp/WEB-INF/classes <-- servlets go here
The above structure is identical to the structure to an EAR file, only "exploded"
as actual files and directories instead of being "jarred" into a single EAR file.
Your application.xml in this case would specify something like:
<application>
<display-name>EnterpriseApp</display-name>
<description>My Enterprise Application</display-name>
<module>
<ejb>EJB</ejb>
</module>
<module>
<web>
<web-uri>WebApp</web-uri>
<context-root>/yourAppRoot</context-root>
</web>
</module>
</application>
And in config.xml you would have an entry similar to:
<Application Deployed="true" Name="EnterpriseApp"
Path=".\config\mydomain\applications\EnterpriseApp">
<WebAppComponent Name="ui" Targets="myserver" URI="WebApp"/>
<EJBComponent Name="ejb" Targets="myserver" URI="EJB"/>
</Application>
regards,
-Ade

After deployment of war/exploded war modified files are not reflected

Dear All,
I have done the application deployment(war/exploded war) successfully in weblogic 10.3.5.0 version But After deployment js/jsp files to get updated through the scheduler in the following path Weblogic/user_projects/domains/domain/servers/my_server/tmp/_WL_user/myapp/7i4bde/war/
The files are getting updated successfully with updated values in above specified path.
But it is not getting reflected, when we are accessing the application.
Kindly help for the same..
Thanks in Advance
Vijay Jetti

Hi Vijay,
When your doing a deployment,
Stop the Managed server,
Rename the folders "tmp" and "cache" to tmp_04012013 and cache_04012013 inside Weblogic/user_projects/domains/domain/servers/my_server/
(This is for clearing the Cache)
After Deployment-->Start the managed server.
On starting the services,new directory tmp and cache will be created and All the changes will be automatically be reflected.
As you have said,
After deployment js/jsp files to get updated through the scheduler in the following path
Weblogic/user_projects/domains/domain/servers/my_server/tmp/_WL_user/myapp/7i4bde/war/Make a point to restart the managed server once the scheduled job is complete(No need to clear the cache).
Assume your scheduler is set at 6.00,then restart the services around 6.30
Hope this helps.
Regards
Fabian

Deployment Descriptor defaults for clustering

          If stateless session EJB is deployed in a cluster, and cluster properties are not explicitly set, what are their defaults?
          Darko Bohinc
          Synergy International Limited
          www.synergy.co.nz


          Darko,
          All EJB "homes" are clusterable by default (a request for a home interface can be routed to any server in the cluster).
          In the case of stateless session beans, you also achieve load-balancing by default (method calls can be sent to any server in the cluster). Failover is achieved by default only BETWEEN method calls and not DURING method calls. In other words, the stub will retry a method call on another server in the cluster only if the stub is absolutely sure that the method call did not reach the server in the cluster during the first try. If the stub cannot determine this, it will not retry by default and you should eventually get an error. If you would like the server to retry all method calls even if the server failed in the middle of a call, then you need to write your EJB methods to be idempotent (calling any method in the EJB many times with the same parameters should achieve the same result with no side effects such as duplicate inserts in the database etc). You will then have to explicitly set the "stateless-bean-methods-are-idempotent" element in the deployment descriptor for the EJB to let WL know that all methods can be retried without any worries.
          Please see the following link for additional information:
          http://www.weblogic.com/docs51/classdocs/API_ejb/EJB_environment.html#1046391
          Hope this answers your questions.
          Giri
          "Darko Bohinc" <[email protected]> wrote:
          >
          >If stateless session EJB is deployed in a cluster, and cluster properties are not explicitly set, what are their defaults?
          >
          >Darko Bohinc
          >Synergy International Limited
          >www.synergy.co.nz

Deploying war files to weblogic 10.3.4

I have a weblogic domain 10.3.4 and a war file (smap.war). I can deploy this war file using weblogic console (10.3.4).
However, I cannot using ant (wldeploy 11.1.1.4) to deploy this war file. It shows error as follow.
This war file and weblogic domain is in the same machine.
------------------error---------------------------
[wldeploy] Task 27 failed: [Deployer:149026]deploy application smap.war on AdminServer.
[wldeploy] Target state: deploy failed on Server AdminServer
[wldeploy] weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
[wldeploy] problem: cvc-complex-type.2.4a: Expected element 'servlet-name@http://java.sun.com/xml/ns/javaee' instead of 'description@http://www.w3.org/2001/XMLSchema-instance' here in element servlet@http://java.sun.com/xml/ns/javaee:<null>
[wldeploy] problem: cvc-complex-type.2.4a: Expected element 'servlet-name@http://java.sun.com/xml/ns/javaee' instead of 'display-name@http://www.w3.org/2001/XMLSchema-instance' here in element servlet@http://java.sun.com/xml/ns/javaee:<null>
[wldeploy]      at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:245)
[wldeploy]      at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:231)
---------------------------build.xml------------------------
<?xml version="1.0" encoding="UTF-8" ?>


<project default="init">
<target name="init">
<tstamp/>
</target>
<property name="wls.username" value="weblogic" />
<property name="wls.password" value="welcome1" />
<property name="wls.hostname" value="localhost" />
<property name="wls.port" value="7001" />
<property name="admin.server.name" value="AdminServer" />
<property name="deploy.target" value="AdminServer" />

<property name="deploy.name" value="smap.war" />
<property name="deploy.source" value="E:\SVN_Root\smap_Build" />
<taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy">
<classpath>
<pathelement location="D:\Oracle\Middleware\wlserver_10.3\server\lib\weblogic.jar"/>
</classpath>
</taskdef>
<target name="szmap" depends="init" >
<war destfile="${deploy.source}\smap.war"
webxml="${deploy.source}\smap\WebContent\WEB-INF\web.xml" >
<fileset dir="${deploy.source}\smap\WebContent"/>
<classes dir="${deploy.source}\smap\build\classes"/>
</war>
</target>
<target name="deployX" depends="init">
<echo message="27 deploy.source=${deploy.source}"/>
<echo message="28 deploy.name=${deploy.name}"/>
<wldeploy action="deploy"
name="${deploy.name}"
source="${deploy.source}\${deploy.name}"
user="${wls.username}"
nostage="true"
password="${wls.password}"
verbose="true"
adminurl="t3://${wls.hostname}:${wls.port}" targets="${deploy.target}"
debug="true"
/>
</target>

<target name="redeploy">
<wldeploy action="redeploy"
name="${deploy.name}"
user="${wls.username}"
nostage="true"
password="${wls.password}"
verbose="true"
adminurl="t3://${wls.hostname}:${wls.port}" targets="${deploy.target}" />
</target>

<target name="undeployX">
<wldeploy action="undeploy"
name="szmap"
failonerror="false"
user="${wls.username}"
password="${wls.password}"
verbose="true"
adminurl="t3://${wls.hostname}:${wls.port}" targets="${deploy.target}" />
</target>
<target name="all" depends="init, deployX"/>
</project>

In szmap.war\WEB-INF\lib, I can find spring-beans-2.0.8.jar, spring-context-2.0.8.jar, spring-core-2.0.8.jar, spring-web-2.0.8.jar.
I change weblogic.xml as follows. Then, I get new errors.
<?xml version = '1.0' encoding = 'UTF-8'?>
<weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd"
xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app">
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
<library-ref>
<library-name>spring-beans-2.0.8.jar</library-name>
</library-ref>
<library-ref>
<library-name>spring-context-2.0.8.jar</library-name>
</library-ref>
<library-ref>
<library-name>spring-core-2.0.8.jar</library-name>
</library-ref>
<library-ref>
<library-name>spring-web-2.0.8.jar</library-name>
</library-ref>
<library-ref>
<library-name>cxf-2.2.5.jar</library-name>
</library-ref>
<library-ref>
<library-name>wsdl4j-1.6.2.jar</library-name>
</library-ref>
</weblogic-web-app>
----------------------------error-------------------------------------
Buildfile: E:\CI_Build\szmap\ANT\ANTszmap\ANT_szmap\build_szmap.xml
init:
deployX:
[echo] 27 deploy.source=E:\SVN_Root\szmap_Build
[echo] 28 deploy.name=szmap.war
[wldeploy] weblogic.Deployer -debug -nostage -verbose -noexit -name szmap.war -source E:\SVN_Root\szmap_Build\szmap.war -targets AdminServer -adminurl t3://localhost:7001 -user weblogic -password ******** -deploy
[wldeploy] weblogic.Deployer invoked with options: -debug -nostage -verbose -noexit -name szmap.war -source E:\SVN_Root\szmap_Build\szmap.war -targets AdminServer -adminurl t3://localhost:7001 -user weblogic -deploy
[wldeploy] [WebLogicDeploymentManagerImpl.<init>():115] : Constructing DeploymentManager for J2EE version V1_4 deployments
[wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():158] : Connecting to admin server at localhost:7001, as user weblogic
[wldeploy] [ServerConnectionImpl.getEnvironment():286] : setting environment
[wldeploy] [ServerConnectionImpl.getEnvironment():289] : getting context using t3://localhost:7001
[wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://localhost:7001/jndi/weblogic.management.mbeanservers.domainruntime
[wldeploy] [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://localhost:7001/jndi/weblogic.management.mbeanservers.runtime
[wldeploy] [DomainManager.resetDomain():36] : Getting new domain
[wldeploy] [DomainManager.resetDomain():39] : Using pending domain: true
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@4406cef4
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@4406cef4
[wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@8429c19
[wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@8429c19
[wldeploy] [ServerConnectionImpl.initialize():169] : Connected to WLS domain: sunzmap_domain
[wldeploy] [ServerConnectionImpl.init():159] : Initializing ServerConnection : [email protected]3969
[wldeploy] [BasicOperation.dumpTmids():713] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():715] : {Target=AdminServer, WebLogicTargetType=server, Name=szmap.war}, targeted=true
[wldeploy] [BasicOperation.deriveAppName():141] : appname established as: szmap.war
[wldeploy] <2011-3-15 下午03时48分03秒 CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, szmap.war [archive: E:\SVN_Root\szmap_Build\szmap.war], to AdminServer .>
[wldeploy] [BasicOperation.dumpTmids():713] : Incoming tmids:
[wldeploy] [BasicOperation.dumpTmids():715] : {Target=AdminServer, WebLogicTargetType=server, Name=szmap.war}, targeted=true
[wldeploy] [BasicOperation.loadGeneralOptions():628] : Delete Files:false
[wldeploy] Timeout :3600000
[wldeploy] Targets:
[wldeploy] AdminServer
[wldeploy] ModuleTargets={}
[wldeploy] SubModuleTargets={}
[wldeploy] }
[wldeploy] Files:
[wldeploy] null
[wldeploy] Deployment Plan: null
[wldeploy] App root: C:\Users\ADMINI~1\AppData\Local\Temp\2\Administrator\.\config\deployments\szmap.war
[wldeploy] App config: C:\Users\ADMINI~1\AppData\Local\Temp\2\Administrator\.\config\deployments\szmap.war\plan
[wldeploy] Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=nostage,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=szmap.war,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0,deploymentPrincipalName=null,useExpiredLock=false}
[wldeploy]
[wldeploy] [BasicOperation.execute():445] : Initiating deploy operation for app, szmap.war, on targets:
[wldeploy] [BasicOperation.execute():447] : AdminServer
[wldeploy] Task 33 initiated: [Deployer:149026]deploy application szmap.war on AdminServer.
[wldeploy] dumping Exception stack
[wldeploy] Task 33 failed: [Deployer:149026]deploy application szmap.war on AdminServer.
[wldeploy] Target state: deploy failed on Server AdminServer
[wldeploy] java.lang.NoSuchMethodException: oracle.j2ee.ws.wsdl.extensions.soap.SOAPBindingImpl.getElementType()
[wldeploy]      at java.lang.Class.getDeclaredMethod(Class.java:1937)
[wldeploy]      at org.apache.cxf.tools.common.ExtensionInvocationHandler.invoke(ExtensionInvocationHandler.java:41)
[wldeploy]      at $Proxy325.getElementType(Unknown Source)
[wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.hasUsingAddressing(JaxWsEndpointImpl.java:201)
[wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.extractWsdlExtensibilities(JaxWsEndpointImpl.java:184)
[wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.<init>(JaxWsEndpointImpl.java:174)
[wldeploy]      at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.createEndpoint(JaxWsServiceFactoryBean.java:206)
[wldeploy]      at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:165)
[wldeploy]      at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:105)
[wldeploy]      at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:167)
[wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:346)
[wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:259)
[wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:209)
[wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:404)
[wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1414)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1375)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
[wldeploy]      at java.security.AccessController.doPrivileged(Native Method)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
[wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
[wldeploy]      at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
[wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
[wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
[wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
[wldeploy]      at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
[wldeploy]      at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
[wldeploy]      at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
[wldeploy]      at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
[wldeploy]      at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
[wldeploy]      at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
[wldeploy]      at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
[wldeploy]      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
[wldeploy]      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
[wldeploy]      at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
[wldeploy]      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
[wldeploy]      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
[wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
[wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
[wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
[wldeploy]      at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
[wldeploy]      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
[wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
[wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
[wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
[wldeploy]      at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
[wldeploy]      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
[wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
[wldeploy]      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
[wldeploy]      at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
[wldeploy]      at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
[wldeploy]      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
[wldeploy]      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
[wldeploy]      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
[wldeploy]      at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
[wldeploy]
[wldeploy]
[wldeploy] Target Assignments:
[wldeploy] + szmap.war AdminServer
[wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Task 33 failed: [Deployer:149026]deploy application szmap.war on AdminServer.
[wldeploy] Target state: deploy failed on Server AdminServer
[wldeploy] java.lang.NoSuchMethodException: oracle.j2ee.ws.wsdl.extensions.soap.SOAPBindingImpl.getElementType()
[wldeploy]      at java.lang.Class.getDeclaredMethod(Class.java:1937)
[wldeploy]      at org.apache.cxf.tools.common.ExtensionInvocationHandler.invoke(ExtensionInvocationHandler.java:41)
[wldeploy]      at $Proxy325.getElementType(Unknown Source)
[wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.hasUsingAddressing(JaxWsEndpointImpl.java:201)
[wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.extractWsdlExtensibilities(JaxWsEndpointImpl.java:184)
[wldeploy]      at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.<init>(JaxWsEndpointImpl.java:174)
[wldeploy]      at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.createEndpoint(JaxWsServiceFactoryBean.java:206)
[wldeploy]      at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:165)
[wldeploy]      at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:105)
[wldeploy]      at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:167)
[wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:346)
[wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:259)
[wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:209)
[wldeploy]      at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:404)
[wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1414)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1375)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
[wldeploy]      at java.security.AccessController.doPrivileged(Native Method)
[wldeploy]      at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
[wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
[wldeploy]      at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
[wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
[wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
[wldeploy]      at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
[wldeploy]      at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
[wldeploy]      at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
[wldeploy]      at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
[wldeploy]      at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
[wldeploy]      at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
[wldeploy]      at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
[wldeploy]      at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
[wldeploy]      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
[wldeploy]      at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
[wldeploy]      at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
[wldeploy]      at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
[wldeploy]      at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
[wldeploy]      at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
[wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
[wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
[wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
[wldeploy]      at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
[wldeploy]      at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
[wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
[wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
[wldeploy]      at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
[wldeploy]      at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
[wldeploy]      at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
[wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
[wldeploy]      at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
[wldeploy]      at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
[wldeploy]      at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
[wldeploy]      at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
[wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
[wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
[wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
[wldeploy]      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
[wldeploy]      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
[wldeploy]      at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
[wldeploy]
[wldeploy]
[wldeploy]
[wldeploy]      at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:542)
[wldeploy]      at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
[wldeploy]      at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
[wldeploy]      at weblogic.utils.compiler.Tool.run(Tool.java:158)
[wldeploy]      at weblogic.utils.compiler.Tool.run(Tool.java:115)
[wldeploy]      at weblogic.Deployer.run(Deployer.java:70)
[wldeploy]      at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
[wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
[wldeploy]      at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
[wldeploy]      at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
[wldeploy]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
[wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy]      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wldeploy]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wldeploy]      at java.lang.reflect.Method.invoke(Method.java:597)
[wldeploy]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[wldeploy]      at org.apache.tools.ant.Task.perform(Task.java:348)
[wldeploy]      at org.apache.tools.ant.Target.execute(Target.java:357)
[wldeploy]      at org.apache.tools.ant.Target.performTasks(Target.java:385)
[wldeploy]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
[wldeploy]      at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
[wldeploy]      at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[wldeploy]      at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
[wldeploy]      at org.apache.tools.ant.Main.runBuild(Main.java:758)
[wldeploy]      at org.apache.tools.ant.Main.startAnt(Main.java:217)
[wldeploy]      at org.apache.tools.ant.Main.start(Main.java:179)
[wldeploy]      at org.apache.tools.ant.Main.main(Main.java:268)
[wldeploy] [ServerConnectionImpl.close():332] : Closing DM connection
[wldeploy] [ServerConnectionImpl.close():352] : Unregistered all listeners
[wldeploy] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection
BUILD FAILED
weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 33 failed: [Deployer:149026]deploy application szmap.war on AdminServer.
Target state: deploy failed on Server AdminServer
java.lang.NoSuchMethodException: oracle.j2ee.ws.wsdl.extensions.soap.SOAPBindingImpl.getElementType()
     at java.lang.Class.getDeclaredMethod(Class.java:1937)
     at org.apache.cxf.tools.common.ExtensionInvocationHandler.invoke(ExtensionInvocationHandler.java:41)
     at $Proxy325.getElementType(Unknown Source)
     at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.hasUsingAddressing(JaxWsEndpointImpl.java:201)
     at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.extractWsdlExtensibilities(JaxWsEndpointImpl.java:184)
     at org.apache.cxf.jaxws.support.JaxWsEndpointImpl.<init>(JaxWsEndpointImpl.java:174)
     at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.createEndpoint(JaxWsServiceFactoryBean.java:206)
     at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:165)
     at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:105)
     at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:167)
     at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:346)
     at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:259)
     at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:209)
     at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:404)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1414)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1375)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
     at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
     at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
     at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
     at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
     at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
     at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
     at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
     at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
     at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
     at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.Ev

Deployment Error - failed to load deployment descriptor

I'm getting the following error when I try to deploy an ear file for my application. I am able to successfully deploy the associated war and ejb jar files as separate modules, but when I try to deploy the application as an ear I get the error:
Deployment Error -- Error while running ejbc -- Fatal Error from EJB Compiler --
-- Failed to load deployment descriptor for: pta
cause: I/O error while reading web xml into object representation

What was the solution for this problem?
Because I have the same error and I tried 920 and 910 100 doe not seem to exist.
I am using WLS 10.
Help would be appreciated.
Thanks

Document type declaration for root element type "web-app" must end with ' '

I am attempting to deploy an application (.war file) using the Sun Access Manager Agent installed, (Reference http://docs.sun.com/app/docs/doc/819-3201/6n5eht3k4?a=view -near the bottom) and I get this error:
Error loading deployment descriptors for ajacs Line 3 Column 19 -- The document type declaration for root element type "web-app" must end with '>'.
Here is the relavent code:
<!DOCTYPE web-app version="2.4" 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/web-app_2_4.xsd">
<web-app>
<filter>
<filter-name>Agent</filter-name>
<filter-class> com.sun.identity.agents.filter.AmAgentFilter </filter-class>
</filter>
<filter-mapping>
<filter-name>Agent</filter-name>
<url-pattern>/*</url-pattern>
<dispatcher>REQUEST</dispatcher>
<dispatcher>INCLUDE</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>ERROR</dispatcher>
</filter-mapping>
<display-name>AJACS</display-name>
<welcome-file-list>
<welcome-file>frameSet.jsp</welcome-file>
</welcome-file-list>
etc...
Now, when I remove the parts that http://docs.sun.com/app/docs/doc/819-3201/6n5eht3k4?a=view said to add, it deploys just like it used to deploy- just fine with no errors. However, I add that code and it breaks.
Note: The code was a straight copy/paste, so if there is any error in the code, it is because it's written incorrectly on the Sun doc website.
Any help would be MUCH appreciated. Thanks!

Well, if that was pasted on one line, it would be:
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
So it's supposed to be that way. I just tried it with the extra quotes, and no dice...

Alternate deployment descriptor for an exploded war (web.xml/weblogic.xml)

Similar Messages

Maybe you are looking for