Trouble deploying endeca studio application in weblogic: endeca-portal-weblogic-3.1.14220.ear

Hello,
I'm trying to install Endeca Studio on weblogic and I'm seeing a class not found error during the "install" step.
The CPU spikes up during the deploy and no progress is made. The error is seen below. Any insight would
be appreciated.
I have installed Endeca Server 7.6 with no issues and have seen the ws running at
http://localhost:7001/endeca-server/ws/manage?WSDL
Thanks!
<Nov 20, 2013 6:13:26 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element application in the deployment descriptor in D:\Orac
le\Middleware\user_projects\domains\endecastudio_domain\servers\AdminServer\tmp\
.appmergegen_1384989205678_endeca-portal-weblogic-3.1.14220.ear/META-INF/applica
tion.xml. A version attribute is required, but this version of the Weblogic Serv
er will assume that the JEE5 is used. Future versions of the Weblogic Server wil
l reject descriptors that do not specify the JEE version.>
<Nov 20, 2013 6:15:55 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element application in the deployment descriptor in D:\Orac
le\Middleware\user_projects\domains\endeca-portal-weblogic-3.1.14220.ear/META-IN
F/application.xml. A version attribute is required, but this version of the Webl
ogic Server will assume that the JEE5 is used. Future versions of the Weblogic S
erver will reject descriptors that do not specify the JEE version.>
<Nov 20, 2013 6:15:58 PM EST> <Warning> <Munger> <BEA-2156203> <A version attrib
ute was not found in element application in the deployment descriptor in D:\Orac
le\Middleware\user_projects\domains\endecastudio_domain\servers\AdminServer\tmp\
_WL_user\endeca-portal-weblogic-3\diq5s7/META-INF/application.xml. A version att
ribute is required, but this version of the Weblogic Server will assume that the
JEE5 is used. Future versions of the Weblogic Server will reject descriptors th
at do not specify the JEE version.>
When processing WebService module 'endeca-dataset-manager-portlet.war'.  Failed
to load servlet Class: com.endeca.portlet.datasetmanager.upload.EnrichmentsUploa
dServlet
Ignoring: unable to load class:java.lang.ClassNotFoundException: com.endeca.port
let.datasetmanager.upload.EnrichmentsUploadServlet at: weblogic.xml.schema.bindi
ng.util.ClassUtil.loadClass(ClassUtil.java:76)
When processing WebService module 'endeca-dataset-manager-portlet.war'.  Failed
to load servlet Class: com.endeca.portlet.datasetmanager.upload.EnrichmentsUploa
dServlet
Ignoring: unable to load class:java.lang.ClassNotFoundException: com.endeca.port
let.datasetmanager.upload.EnrichmentsUploadServlet at: weblogic.xml.schema.bindi
ng.util.ClassUtil.loadClass(ClassUtil.java:76)
Loading zip:D:/Oracle/Middleware/user_projects/domains/endecastudio_domain/serve
rs/AdminServer/tmp/_WL_user/endeca-portal-weblogic-3/gaidjs/war/WEB-INF/lib/port
al-impl.jar!/system.properties
Nov 20, 2013 6:17:52 PM com.liferay.portal.kernel.log.Jdk14LogImpl info
INFO: Platform default Studio home: 'D:/Oracle/Middleware/user_projects/domains/
endecastudio_domain/eid/studio'
log4j:WARN No appenders could be found for logger (org.apache.commons.configurat
ion.PropertiesConfiguration).
log4j:WARN Please initialize the log4j system properly.
Loading zip:D:/Oracle/Middleware/user_projects/domains/endecastudio_domain/serve
rs/AdminServer/tmp/_WL_user/endeca-portal-weblogic-3/gaidjs/war/WEB-INF/lib/port
al-impl.jar!/portal.properties
Nov 20, 2013 6:17:53 PM com.liferay.portal.kernel.log.Jdk14LogImpl info
INFO: Studio home directory path: 'D:\Oracle\Middleware\user_projects\domains\en
decastudio_domain\eid\studio'
Nov 20, 2013 6:17:53 PM com.liferay.portal.kernel.log.Jdk14LogImpl info
INFO: Created home directory: 'D:\Oracle\Middleware\user_projects\domains\endeca
studio_domain\eid\studio'

Interestingly enough I killed the server after 5 min of high CPU usage and restarted it.
It looks as if the application deployed and is showing as  "healthy".
I was able to see the application http://localhost:port/eid

Similar Messages

  • Trouble deploying a J2EE application using the J2EE 6.20 Deploy Tool

    I am having trouble deploying a J2EE application using the J2EE 6.20 Deploy Tool.
    I successfully create the WAR/EAR files, I then select deploy and the deploy process gets to 100% before displaying an error message.
    Can anybody help?
    Please see Deploy Tool log entry:
    01:39 -  **********************************************************
    05/01/17 10:19:16 -  Applying user role management mappings.
    05/01/17 10:19:16 -  Start updating EAR-file...D:\SAP_J2EEngine6.20_Cluster\deploying\carmodeller\carmodeller.ear
    05/01/17 10:19:27 -  Temp files deleted...
    05/01/17 10:19:27 -  Ear-file updated successfully for 11375ms.
    05/01/17 10:19:27 -  Start deploying ...
    05/01/17 10:20:15 -  Ear-file uploaded to server for 47297ms.
    05/01/17 10:21:47 -  ERROR: ID90506: NOT Deployed. ERROR returned from deploy service :
                         com.inqmy.services.deploy.container.DeploymentException: Can't init application carmodeller. com.inqmy.services.servlets_jsp.server.WebApplicationException: ID17110: Error in starting application carmodeller.java.lang.NullPointerException
                              at com.inqmy.services.servlets_jsp.server.ServletsAndJspImpl.deploy(ServletsAndJspImpl.java:482)
                              at com.inqmy.services.servlets_jsp.server.WebContainer.commitDeploy(WebContainer.java:256)
                              at com.inqmy.services.deploy.server.DeployServiceImpl.commit(DeployServiceImpl.java:2848)
                              at com.inqmy.services.deploy.server.DeployServiceImpl.deploy1(DeployServiceImpl.java:512)
                              at com.inqmy.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:140)
                              at com.inqmy.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:184)
                              at com.inqmy.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:157)
                              at com.inqmy.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:108)
                              at com.inqmy.core.service.context.container.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:36)
                              at com.inqmy.core.cluster.impl5.ParserRunner.run(ParserRunner.java:55)
                              at com.inqmy.core.thread.impl0.ActionObject.run(ActionObject.java:46)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.inqmy.core.thread.impl0.SingleThread.run(SingleThread.java:153)
    05/01/17 10:21:47 -  **********************************************************

    Hi, it looks like the app has trouble starting up:
    05/01/17 10:21:47 - ERROR: ID90506: NOT Deployed. ERROR returned from deploy service :
    com.inqmy.services.deploy.container.DeploymentException: Can't init application carmodeller. com.inqmy.services.servlets_jsp.server.WebApplicationException: ID17110: Error in starting application carmodeller.java.lang.NullPointerException
    Did you have any errors on the compile of the code?
    You also want to check if the app is deployed (if so you may want to remove it before re-deploying it)

  • Oracle endeca studio application creation issue

    I have installed oracle endeca 3.1 solution on my desktop but i am not able to create application using endeca studio from excel upload. It shows excel data in preview and fields as well. But it gets stuck in create application page. Please help in resolving this issue.

    Hi,
         I have had this before and sometimes it can be that the Excel spreadhseet has formula, split screen, colours or anything else odd, please copy and paste values and take any split screen or colour off and try again, it usually works for me.
    Regards John

  • How to deploy a portlet application on Sun One Portal Server?

    Hi all,
    I have developed a JSR168 helloworld portlet.
    how will i deploy that war file to Sun One Portal Server ?
    Thanks & Regards
    ~Neeraj.

    Thanks Shay! I was able to deploy the application per your instructions.
    [10:41:53 AM] Deploying Application...
    [10:42:10 AM] [Deployer:149192]Operation 'deploy' on application 'mobilesolution2 [Version=V2.0]' is in progress on 'AdminServer'
    [10:42:13 AM] [Deployer:149194]Operation 'deploy' on application 'mobilesolution2 [Version=V2.0]' has succeeded on 'AdminServer'
    [10:42:13 AM] Application Deployed Successfully.
    [10:42:13 AM] Elapsed time for deployment: 32 seconds
    [10:42:13 AM] ---- Deployment finished. ----

  • EPMA 11.1.1.3  deployment of ASO application to Essbase issue

    Hi,
    We are having trouble deploying an ASO application from EPMA to Essbase. When we deploy the application it validates okay and then completes 100% but the outline does not get loaded into Essbase. In the EPMA deployment message text is the following error
    *[Network Error: Cannot send Data, Loading new outline for database Failed]*
    NB: 1. we have two other applications: a planning application and a BSO application. Both can be successfully deployed from the same application library to the same Essbase server so i think the issue is specific to the ASO application.
    2. We successfully deployed the ASO application last Friday at 4pm prior to the change I am tryign to implement this week.
    3. The three applications share common dimensions from the shared library one of which is the Account dimension.
    4. The change I am trying to deploy is an alternate hierarchy in the account dimension (dynamic calc - containing shared members) - I have changed the storage type to Storedata in the ASO application.
    5. I have subsequently removed the alternate hierarchy and tried to deploy - still gettign the same issue.
    Any suggestions on where to look to solve this would be appreciated.
    Thanks in advance

    Restoring the whole driectory has still been unsuccessful.
    deployign the application from EPMA will start to build the otn file - very slowly - it took over an hour and then it just stops and never completes the deploy so we are left with an OTN and an OTL file and EPMA states that the application is deployed but out of sync with deployment.
    the error we are gettign in the application log file is
    [Thu Oct 04 09:20:27 2012]Local/FINASO///Error(1270005)
    Fatal error: invalid page encountered in aggregate storage file at location [0001.0001.00000002]
    [Thu Oct 04 09:20:27 2012]Local/FINASO///Error(1270071)
    Page ID [0000.0000.00000000] in the page header doesn't match page location [0001.0001.00000002]
    I have also tried building a replacement ASO application in EPMA and deploying it - we were able to complete this with an application with 3 local dimensions each with 1 member but this took over an hour. when we try to do it with the same build as our DEVELOPMENT equivalent for the ASO file (which works in dev) it starts to build it but then falls over and leaves just an otn in the database directory.
    any ideas on what else i should be lookign at?
    cheers
    Darren

  • Framework Settings for map in Endeca studio for getting started application

    Hi All,
    Can anybody tell me,what is the default framework setting for below fields when we installed endeca studio to make getting started application work especially map settings,
    df.mapviewer:???
    df.mapTileLayer:    ???
    df.mapViewer:     ???
    Due to change in configuration i cannot see the map in getting started application please help to solve the above problem.
    I m getting below error
    MapView service is not available, please contact your system administrator.

    Hello.
    df.mapTileLayer:    "elocation_mercator.world_map"
    df.mapViewer:     "http://elocation.oracle.com/mapviewer/"
    and i think you was asking also for:
    df.mapLocation:   "elocation.oracle.com"
    Let me know if this helped you
    EBrauerP

  • May I install Endeca Server 7.6 on an existing weblogic 10.3.6?

    I would like to install Endeca Server 7.6 on an existing weblogic 10.3.6 using JDK 1.6U45 based Window 2008 R2 SP1. I notice the install guide, just chose 3 options when install weblogic 10.3.6, while the existing weblogic 10.3.6 in real life was fully installed. So May I install Endeca Server 7.6 on this existing weblogic 10.3.6? Thanks!

    Hi,
    Yes you can install Endeca Server in an existing WebLogic 10.3.6, although it is preferable to dedicate a WebLogic domain to hosting only the Endeca Server application. See this topic about the Endeca Server and WebLogic integration, from the Endeca Server 7.6.0 doc.
    In it, it is stated:
    "Important: For performance and troubleshooting purposes, it is preferable to dedicate a WebLogic domain to hosting only the Endeca Server application. In this case, the endeca-server root context is used in the URL pointing to any of the WebLogic Server instances hosting the Endeca Server application."
    Additionally, the Endeca Server Installation Guide provides instructions for installing the generic version of the Oracle WebLogic 10.3.6. installer package, and not any other WebLogic packages. Specifically, it states:
    "This procedure relies on those components that are available in the WebLogic Server installation under the Oracle Restricted Use License. If your site already has access to the fuller version of the WebLogic Server, additional components may be available to you. However, the instructions in this topic do not guarantee that any other components of the WebLogic Server can be used with the Endeca Server. Additionally, certain components, such as the Enterprise Manager, are not discussed in this guide."
    Julia

  • Endeca Reference application issue

    Hi,
    I am getting below message while deploying discover reference application.
    Found version 6.1 of the Endeca IAP installed in directory
    D:\Endeca\PlatformServices\6.1.3. If either the version or location are
    incorrect, type 'Q' to quit and adjust your ENDECA_ROOT environment variable.
    Press enter to continue with these settings.
    **Does any one know why this is coming??.**
    I have cross checked Endeca root directory and Platform service location. Both are same.
    Thanks.

    The new properties will have to be added to product-sku-output-config.xml, which went under /atg/commerce/search in 10.1.0 (the location might have changed in 10.1.1). Check the ATG Endeca Integration guide for exact steps.
    HTH,
    Pankaj.

  • Consume Endeca Studio Page as a Portlet

    Hi,
    Is it possible to
    1) Consume the pages created in Endeca as portlets in our application??
    2) Consume the individual studio components as portlets in our transaction pages??
    If any of the above are possible, please provide steps/documentation/samples for the same. Also any documentation which could help us understand Endeca Studio page/component portlets is most welcome.
    Thanks,
    Leon.

    Hi Leon,
    Per #1, leveraging an IFRAME, you could certainly embed a Studio page in your application. For security and cross-application interactive purposes, you'll need to pay particularly close attention to your cross-domain javascript settings.
    Per #2, I will start off by saying that this is unintended and unsupported use of the product. That said, you can reference a Studio portlet/component by going to your component's "Configuration -> Sharing" and embedding the <script> HTML and javascript syntax it offers you for that component into your application. It goes without saying that there are a lot of unexpected and unintended corner cases that may arise from this. This isn't expected product use, so you're really off-roading at this point. Be sure to test it thoroughly to make sure you're comfortable with the behaviors. For example, for charts or tag clouds, what is the user going to expect when they click on the links offered by the components?
    Happy off-roading,
    Dan
    http://branchbird.com
    Edited by: Dan at Branchbird on Dec 12, 2012 7:16 AM

  • Deploy web application in jbuilder 9 with weblogic 7 problem

    when i create a web application and a servlet, and deploy it in jbuilder 9 with weblogic 7.0 ,jbuilder 9 showed me the error,please tell me why, when i choose "redeploy" ,it can be normally work..
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    Usage: java weblogic.Deployer [options] [-activate|-deactivate|-remove|-unprepare|-cancel|-list] [files]
    where options include:
    -help Print this help message.
    -version Print version information.
    -adminurl <https://<server>:<port>> The URL of the administration server: default
    http://localhost:7001
    -user <user> A user other than the default of
    "installadministrator"
    -password <password> Specifies the password on the command line.
    If this option is absent the user is
    prompted.
    -verbose Displays additional status during the
    deployment process, including notifications
    when the application is prepared and
    activated on each target.
    -debug Displays debug level messages to the standard
    output.
    -examples Display example usage of this tool.
    -upload Causes the specified source file(s) to be
    transferred to the adminstration server. This
    is used when the Deployer tools is not being
    used on the same machine as the adminstration
    server and the user does not otherwise have
    access to place the targeted files on the
    adminstration server.
    -delete_files Causes the server to remove the files that
    are specified in the file list and leave the
    application activated. This option is valid
    only for unarchived web applications.
    -remote Signals that the tools is not runnning on the
    same machine as the adminstration server and
    that the source path should be made passed
    through unchanged as it represents the path
    on the remote server.
    -nostage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged and the
    original source is be used.
    -external_stage Sets the stagingMethod attribute on the
    application mbean when it is created so that
    the application will not be staged but the
    value of the staging path will be used when
    preparing the application.
    -stage Sets the stagingMethod staging attribute on
    the application when it is created so that
    the application will always be staged. This
    value will override the stagingMethod
    attribute on any targeted servers.
    -nowait Once the action is initiated the tool will
    print the task id and exit. This is used to
    initiate multiple tasks and then monitor them
    later using the -list action.
    -timeout <seconds> The maximum time in seconds to wait for the
    completion of the deployment task. When the
    time expires the current status is printed
    and the program exits.
    -source <archive file or directory> Location of the file or directory that
    represents the enterprise component or
    application tha is being (re)activated. If
    the source file is relative it is relative to
    the current directory, unless the -remote
    option is used. To specify individual files
    within an application for reployment or
    addition list them at the end of the command
    line.
    -name <application name> The name of the application being deployed.
    -targets <<server 1>,...<component>@<server N>> A comma separated list of the server and/or
    cluster names. Each target may be qualified
    with a J2EE component name. This enables
    different components of the archive to
    deployed on different servers.
    -id <task identifier> Optional client supplied unique identifier
    for the deployment task. The id is first
    specified to -activate, -deactivate,
    -unprepare or -remove. It is then used later
    as an argument to -cancel or -list.
    -activate (Re)activates the <source> application on the
    <targets> with the <name>.
    -deactivate Deactivates the application <name> on the
    <targets> leaving an staged application files
    in a state where the may be quickly
    reactivated.
    -unprepare Deactivates and unloads classes for the
    application <name> on the <targets> leaving
    an staged application files in a state where
    the may be quickly reloaded.
    -remove Deactivates the application <name> on the
    <target> and removes any files that were
    staged for this application. If there are no
    longer any targets for the application, the
    associated configuration is completely
    removed.
    -cancel Atempts to cancel the task <id> if it is has
    not yet completed.
    -list Lists the target status of each task <id>
    -deploy a convenient alias for activate.
    -undeploy a convenient alias for unprepare.
    Optionally a list of the specific files in the archive that are to be
    redeployed may be specified. If a directory is specified the entire subtree is
    redeployed.
    Full documentation on this tool is available at:
    http://edocs.beasys.com/wls/docs70/adminguide/utils.html#1138475
    No actions was specified. Please specify one and only one of:
    -activate, -deactivate, -cancel, -remove, -unprepare, or -list.
    Type java weblogic.Deployer -examples for example usage.

    you use "deploy" under DOS-Mode to deploy your web application?
    i found some differences between "deploy" and "redeploy" function in jbuilder 9.
    when i choose "deploy" ,jbuilder shows me the commond below:
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -deploy -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility
    when i choose redeploy,it shows me: (the -deploy parameter has changed to -activate) ,maybe it's a bug.
    E:\bea\jdk131_02\bin\javaw -classpath E:\bea\weblogic700\server\lib\weblogic.jar;E:\bea\weblogic700\server\lib\webservices.jar;E:\bea\weblogic700\server\lib\weblogic_sp.jar; weblogic.Deployer -user system -adminurl http://localhost:7001 -password 12345678 -activate -name firstWebApp -upload -source E:/J2EE/servlet/firstWebApp.war -targets myserver
    WebLogic Application Deployment Utility

  • Problem in deploying Web Service Application on Weblogic Server

    Hi,
    I am trying to develop a web service application with eclipse, all things goes correct and wsdl also gets formed but the problem occurs when the EAR is deployed. It gives error in publishing the EAR file.
    Here is the error i am getting:
    Module named 'ftooldev1EAR' failed to deploy. See Error Log view for more detail.
    *weblogic.application.ModuleException: [HTTP:101064][WebAppModule(ftooldev1EAR:/ftooldev1)] Error parsing descriptor in Web appplication "D:\eclipse_wspace1\ftooldev1\build\jws\weboutput"*
    *com.bea.xml.XmlRuntimeException: invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
    *     at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)*
    *     at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)*
    *     at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)*
    *     at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)*
    *     at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)*
    *     at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)*
    *     at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)*
    *     at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)*
    *     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)*
    *     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)*
    *     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)*
    *     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)*
    *     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)*
    *     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)*
    *     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)*
    *     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)*
    *     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)*
    *     at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)*
    *     at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)*
    *     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)*
    *     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)*
    *     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)*
    *     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)*
    *     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)*
    *     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)*
    *     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)*
    *     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)*
    *     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)*
    *     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)*
    *     at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)*
    *     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)*
    *     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)*
    *     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)*
    *     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)*
    *     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)*
    *     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)*
    *     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)*
    *     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)*
    *     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)*
    *     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)*
    *     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)*
    *     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)*
    *     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)*
    *     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)*
    *     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)*
    *invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
    java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1566)
    at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:470)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1346)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:803)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:623)
    at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:516)
    at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
    at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
    at org.eclipse.wst.server.core.internal.Server.publish(Server.java:1075)
    at org.eclipse.jst.ws.internal.consumption.ui.command.StartServerCommand$1.run(StartServerCommand.java:132)
    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
    *Caused by: weblogic.application.ModuleException: [HTTP:101064][WebAppModule(ftooldev1EAR:/ftooldev1)] Error parsing descriptor in Web appplication "D:\eclipse_wspace1\ftooldev1\build\jws\weboutput"*
    *com.bea.xml.XmlRuntimeException: invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
    at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
    at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)
    at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    *invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
    at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
    at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)
    at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    at weblogic.servlet.internal.WebAppModule.createModuleException(WebAppModule.java:1511)
    at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1247)
    at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:346)
    at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:59)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:43)
    at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:1221)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
    at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:367)
    at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:54)
    at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:207)
    at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:98)
    at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
    at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
    at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
    at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    *Caused by: com.bea.xml.XmlRuntimeException: invalid ByNameBean java type: class [Ljava.lang.String; found in com.bea.staxb.buildtime.internal.bts.ByNameBean{com.bea.staxb.buildtime.internal.bts.ByNameBean[java.lang.String[]; t=url-patternType@http://java.sun.com/xml/ns/j2ee]-props=size:0[]}*
    at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.getRuntimeBindingType(RuntimeBindingType.java:624)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:148)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.unmarshalElementProperty(LiteralUnmarshalResult.java:184)
    at com.bea.staxb.runtime.internal.LiteralUnmarshalResult.extractAndFillElementProp(LiteralUnmarshalResult.java:156)
    at com.bea.staxb.runtime.internal.ByNameUnmarshaller.deserializeContents(ByNameUnmarshaller.java:51)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshalIntoIntermediary(AttributeUnmarshaller.java:47)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:199)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
    at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:141)
    at weblogic.servlet.internal.WebAppModule.loadDescriptor(WebAppModule.java:1216)
    Here is the web.xml of my application:
    *<?xml version="1.0" encoding="UTF-8"?>*
    *<web-app xmlns:j2ee="http://java.sun.com/xml/ns/j2ee"*
    xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:web="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd">
    *<servlet>*
    *<servlet-name>action</servlet-name>*
    *<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>*
    *<init-param/>*
    *</servlet>*
    *<servlet>*
    *<javaee:display-name>Apache-Axis Servlet</javaee:display-name>*
    *<servlet-name>AxisServlet</servlet-name>*
    *<servlet-class>org.apache.axis.transport.http.AxisServlet</servlet-class>*
    *</servlet>*
    *<servlet-mapping>*
    *<servlet-name>AxisServlet</servlet-name>*
    *<url-pattern>/servlet/AxisServlet</url-pattern>*
    *</servlet-mapping>*
    *<servlet-mapping>*
    *<servlet-name>AxisServlet</servlet-name>*
    *<url-pattern>*.jws</url-pattern>*
    *</servlet-mapping>*
    *<servlet-mapping>*
    *<servlet-name>AxisServlet</servlet-name>*
    *<url-pattern>/services/*</url-pattern>*
    *</servlet-mapping>*
    *<servlet>*
    *<javaee:display-name>Axis Admin Servlet</javaee:display-name>*
    *<servlet-name>AdminServlet</servlet-name>*
    *<servlet-class>org.apache.axis.transport.http.AdminServlet</servlet-class>*
    *<load-on-startup>100</load-on-startup>*
    *</servlet>*
    *<servlet-mapping>*
    *<servlet-name>AdminServlet</servlet-name>*
    *<url-pattern>/servlet/AdminServlet</url-pattern>*
    *</servlet-mapping>*
    *</web-app>*
    Edited by: 925692 on Apr 5, 2012 1:38 AM
    Edited by: 925692 on Apr 5, 2012 1:40 AM
    Edited by: 925692 on Apr 5, 2012 1:40 AM

    This behavior might be attributed to Axis inclusion.
    Web service actions and wizards supported by Weblogic can be found at:
    File->New->Other->Oracle->WebLogic->Web Services
    Can you provide more detail about your starting point wsdl? or JWS? and information around what generation actions you used?
    Thanks

  • Problem while deploying the ADF application in weblogic 10.3

    Hi,
    We did the application using ADF and EJB3.0 in JDeveloper11g relese and this application is working fine when i run in the JDeveloper release. When i try to deploy the same application in weblogic 10.3(Which I downloded and installed) i am getting following error.
    shared library "adf.oracle.domain" could not be found.
    Can any one tell me, what the problem is?
    Thanking you,
    NIRANJAN REDDY.

    person with many names,
    You need to configure the WLS domain for ADF.
    http://download.oracle.com/docs/cd/E12839_01/install.1111/e13666/toc.htm#wls_adf
    John

  • Failed to deploy a simple application on weblogic 10.3.3.0

    Hi All,
    I'am unable to deploy a very simple War file application by ant task (weblogic ant task weblogic.ant.taskdefs.management.WLDeploy).
    I find how to cause this problem,but I can't resolve it .
    In my war file ,include one file with chinese file name "测试.jsp" .
    the weblogic use the java.util.jar.JarFile to extract the war file.but is can't handle chinese file name corrently.
    so it get a wrong file name "²âÊÔ.js" ,and cause this problem.
    Thinks
    Jason
    exception:
    deployOnServer1:
    [echo] *********** Start deploying war file on SERVER1 ***********
    [wldeploy] weblogic.Deployer -debug -remote -verbose -upload -noexit -name yuidemo -source y:\sources\yuidemo\dist\yuidemo.war -targets AdminServer -adminurl http://10.99.76.58:7001 -user weblogic -password ******** -redeploy
    [wldeploy] weblogic.Deployer invoked with options: -debug -remote -verbose -upload -noexit -name yuidemo -source y:\sources\yuidemo\dist\yuidemo.war -targets AdminServer -adminurl http://10.99.76.58:7001 -user weblogic -redeploy
    [wldeploy] [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
    [wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at 10.99.76.58:7001, as user weblogic
    [wldeploy] [ServerConnectionImpl.getEnvironment():288] : setting environment
    [wldeploy] [ServerConnectionImpl.getEnvironment():291] : getting context using http://10.99.76.58:7001
    [wldeploy] [ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:http://10.99.76.58:7001/jndi/weblogic.management.mbeanservers.domainruntime
    [wldeploy] [ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:http://10.99.76.58:7001/jndi/weblogic.management.mbeanservers.runtime
    [wldeploy] [DomainManager.resetDomain():36] : Getting new domain
    [wldeploy] [DomainManager.resetDomain():39] : Using pending domain: false
    [wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@1041876
    [wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@1041876
    [wldeploy] [MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@34151f
    [wldeploy] [MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@34151f
    [wldeploy] [ServerConnectionImpl.initialize():171] : Connected to WLS domain: base_domain
    [wldeploy] [ServerConnectionImpl.setRemote():482] : Running in remote mode
    [wldeploy] [ServerConnectionImpl.init():161] : Initializing ServerConnection : [email protected]a99
    [wldeploy] [BasicOperation.dumpTmids():689] : Incoming tmids:
    [wldeploy] [BasicOperation.dumpTmids():691] : {Target=AdminServer, WebLogicTargetType=server, Name=yuidemo}, targeted=true
    [wldeploy] [RedeployOperation.setupPaths():86] : in place redeploy: false from moduleArchive: y:\sources\yuidemo\dist\yuidemo.war
    [wldeploy] [RedeployOperation.setupPaths():95] : redeploy src path: Y:\sources\yuidemo\dist\yuidemo.war
    [wldeploy] [BasicOperation.deriveAppName():140] : appname established as: yuidemo
    [wldeploy] <2013-2-6 上午10时16分36秒 CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, yuidemo [archive: y:\sources\yuidemo\dist\yuidemo.war], to AdminServer .>
    [wldeploy] [ServerConnectionImpl.upload():658] : Uploaded app to D:\TOOLS\DEVELOP\bea\user_projects\domains\base_domain\.\servers\AdminServer\upload\yuidemo
    [wldeploy] [BasicOperation.dumpTmids():689] : Incoming tmids:
    [wldeploy] [BasicOperation.dumpTmids():691] : {Target=AdminServer, WebLogicTargetType=server, Name=yuidemo}, targeted=true
    [wldeploy] [BasicOperation.loadGeneralOptions():606] : 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: D:\TOOLS\DEVELOP\bea\user_projects\domains\base_domain\.\servers\AdminServer\upload\yuidemo
    [wldeploy] App config: D:\TOOLS\DEVELOP\bea\user_projects\domains\base_domain\.\servers\AdminServer\upload\yuidemo\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=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=yuidemo,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0deploymentPrincipalName=null}
    [wldeploy]
    [wldeploy] [BasicOperation.execute():423] : Initiating redeploy operation for app, yuidemo, on targets:
    [wldeploy] [BasicOperation.execute():425] : AdminServer
    [wldeploy] [RedeployOperation.initializeTask():55] : Starting task with path: D:\TOOLS\DEVELOP\bea\user_projects\domains\base_domain\.\servers\AdminServer\upload\yuidemo\app\yuidemo.war
    [wldeploy] Task 3 initiated: [Deployer:149026]deploy application yuidemo on AdminServer.
    [wldeploy] dumping Exception stack
    [wldeploy] Task 3 failed: [Deployer:149026]deploy application yuidemo on AdminServer.
    [wldeploy] Target state: redeploy failed on Server AdminServer
    [wldeploy] java.lang.NullPointerException
    [wldeploy]      at weblogic.utils.jars.JarFileUtils.extract(JarFileUtils.java:287)
    [wldeploy]      at weblogic.application.io.ArchivedWar.expandWarFileIntoDirectory(ArchivedWar.java:131)
    [wldeploy]      at weblogic.application.io.ArchivedWar.extractWarFile(ArchivedWar.java:100)
    [wldeploy]      at weblogic.application.io.ArchivedWar.<init>(ArchivedWar.java:49)
    [wldeploy]      at weblogic.servlet.internal.War.makeExplodedJar(War.java:1019)
    [wldeploy]      at weblogic.servlet.internal.War.<init>(War.java:182)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.processDocroot(WebAppServletContext.java:2658)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:2552)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:388)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456)
    [wldeploy]      at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414)
    [wldeploy]      at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910)
    [wldeploy]      at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
    [wldeploy]      at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    [wldeploy]      at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    [wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
    [wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    [wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
    [wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
    [wldeploy]      at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
    [wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    [wldeploy]      at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    [wldeploy]      at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
    [wldeploy]      at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
    [wldeploy]      at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    [wldeploy]      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    [wldeploy]      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    [wldeploy]      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    [wldeploy]
    [wldeploy]
    [wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application yuidemo on AdminServer.
    [wldeploy] Target state: redeploy failed on Server AdminServer
    [wldeploy] java.lang.NullPointerException
    [wldeploy]      at weblogic.utils.jars.JarFileUtils.extract(JarFileUtils.java:287)
    [wldeploy]      at weblogic.application.io.ArchivedWar.expandWarFileIntoDirectory(ArchivedWar.java:131)
    [wldeploy]      at weblogic.application.io.ArchivedWar.extractWarFile(ArchivedWar.java:100)
    [wldeploy]      at weblogic.application.io.ArchivedWar.<init>(ArchivedWar.java:49)
    [wldeploy]      at weblogic.servlet.internal.War.makeExplodedJar(War.java:1019)
    [wldeploy]      at weblogic.servlet.internal.War.<init>(War.java:182)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.processDocroot(WebAppServletContext.java:2658)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:2552)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:388)
    [wldeploy]      at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:456)
    [wldeploy]      at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414)
    [wldeploy]      at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910)
    [wldeploy]      at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
    [wldeploy]      at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
    [wldeploy]      at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
    [wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
    [wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    [wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
    [wldeploy]      at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
    [wldeploy]      at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
    [wldeploy]      at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
    [wldeploy]      at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
    [wldeploy]      at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:16)
    [wldeploy]      at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
    [wldeploy]      at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
    [wldeploy]      at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
    [wldeploy]      at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
    [wldeploy]      at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
    [wldeploy]      at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
    [wldeploy]      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    [wldeploy]      at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    [wldeploy]
    [wldeploy]
    [wldeploy]
    [wldeploy]      at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:541)
    [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:291)
    [wldeploy]      at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
    [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:392)
    [wldeploy]      at org.apache.tools.ant.Target.performTasks(Target.java:413)
    [wldeploy]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
    [wldeploy]      at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
    [wldeploy]      at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    [wldeploy]      at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
    [wldeploy]      at org.apache.tools.ant.Main.runBuild(Main.java:811)
    [wldeploy]      at org.apache.tools.ant.Main.startAnt(Main.java:217)
    [wldeploy]      at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
    [wldeploy]      at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
    [wldeploy] [ServerConnectionImpl.close():334] : Closing DM connection
    [wldeploy] [ServerConnectionImpl.close():354] : Unregistered all listeners
    [wldeploy] [ServerConnectionImpl.closeJMX():374] : Closed JMX connection
    [wldeploy] [ServerConnectionImpl.closeJMX():386] : Closed Runtime JMX connection
    [wldeploy] [ServerConnectionImpl.closeJMX():398] : Closed Edit JMX connection

    Hi Jason,
    1. Log in to the WebLogic Administrative Console.
    2. Click Preference at the top of the right pane.
    3. Deselect Automatically acquire lock.
    4. Click Save to save the changes.
    5. On the left pane of Administrative Console, click Release Configuration.
    6. Re-run the ant build
    Regards,
    Kal

  • Steps to deploy an ejb application and running an ejb client in weblogic server6.1

    steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
    if the client is an simple java application and if the client is a servlet

    Hi.
    Check out the beanManaged example that ships with WLS and read the accompanying docs. This
    is a simple EJB with a servlet that invokes it.
    Michael
    shekhar sachdev wrote:
    steps to deploy an ejb application and steps to run an ejb client in weblogic server6.1
    if the client is an simple java application and if the client is a servlet--
    Michael Young
    Developer Relations Engineer
    BEA Support

  • Help required in endeca java application

    Hi,
    I am creating a java application of the endeca wine application. I am able to display the results but facing issue in creating the product links for individual products which we redirect me to the product detail page. How will the string query created append the R parameter to the query?
    Pls let me know.
    Thanks,
    Vineet

    There multiple ways you can do this
    1. As you mentioned using R (Record Query) - where you should pass the endeca record ID, not the product ID for this to work
    2. if you have unique product ids, you can use ntk param to look at only ID property and set ntt value as product id
    hope this helps.
    Ram

Maybe you are looking for