EJB JAR building by ANT problem

I have this task in my build file:
[code]
<target name="build"
     depends="compile">
        <ejbjar srcdir="$"
          descriptordir="META-INF"
          destdir="$"
          >
     </ejbjar>
</target> 
[/code]
which is generating this error message:
build:
      [ejbjar] Unable to load dependency analyzer: org.apache.tools.ant.util.depend.bcel.AncestorAnalyzer - dependent class not found: org/apache/bcel/classfile/ClassParser
      [ejbjar] BUILD FAILED: file:d:/my projects/MyApp/Bean/build.xml:82: SAXException while parsing 'ejb-j2ee-engine.xml'. This probably indicates badly-formed XML.  Details: Relative URI "ejb-j2ee-engine.dtd"; can not be resolved without a base URI.

Well, for the time being this is my solution:
[code]
<target name="build"
     depends="compile">
   <zip destfile="${ant.project.name}.jar">
     <fileset dir="$" />
     <fileset dir="$"
            includes="META-INF/**"/>
   </zip>
</target> 
[/code]
The resulting jar file has the same contents as the jar which is produced by the Netw. Dev. Studio

Similar Messages

  • Problem Building a Deployable EJB Jar

    I have a situation where I have compiled and jarred an EJB's Implementation and interfaces, along with some supporting code -- prior to running ejbc.
    I would like to distribute this jar along with a build.xml so that a developer can provide some simple implementation classes (not EJB implementations) along with the ejb-jar.xml and weblogic-ejb-jar.xml and create a deployable EJB jar. I would prefer not to package this as an ear so that the jar could then be neatly added to an ear or deployed separately, at the developers discretion.
    I have everything set up but am struggling to get this to work with some sample code.
    I am using Weblogic 8.1sp4, and can be sure that the developers will be using this level or higher. In my build.xml, I compile the sample code and package the deployable jar together ok. I then run the wlappc task on the jar.
    It took me several iterations to get wlappc to work, and I had to use the following layout for the deployable jar:
    /META-INF/myejbimplclasses.jar
    /META-INF/log4j.jar
    /META-INF/ejb-jar.xml
    /META-INF/weblogic-ejb-jar.xml
    /META-INF/Manifest.mf
    /com... sample compiled class files
    And the Manifest.mf contents look like:
    Manifest-Version: 1.0
    Class-Path: myejbimplclasses.jar;log4j.jar
    Created-By: 1.4.1_05-b01 (Sun Microsystems Inc.)
    Ant-Version: Apache Ant 1.5.3
    I thought it was strange that I needed to put the .jars under META-INF, but this was the only way that I could get the wlappc task to work. I also had to put a semicolon in between the two jars in the Class-Path line (I don't know why).
    Once I put it together this way, wlappc works. However, when I try to deploy the resulting jar, it does not work. It reports an error as follows:
    weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-
    jar.xml: com.dcbls.svc.ComponentManagerEJB
    Note that this .class file is available within myejbimplclasses.jar, along with all the other classes it relies on (except the log4j stuff.)
    Is there a simple problem that I can fix with this setup, or do I need to completely revamp my approach? If so, does anyone have a suggested
    approach?
    Thanks,
    ken clark

    OK -- I will concede that this cannot be done, at least not elegantly.
    I have started down the path of reorganizing this EJB such that it can be easily built and included in an Ear. However, I am now running into some ant build problems, primarily -- I think -- with wlappc.
    I set up the build.xml so that it first compiles the developer's local code, using a classpathref that refers to the EJB code I have previously developed and packaged in a jar, as in:
    <path id="compile.classpath">
    <pathelement location="../dcblsfw.jar"/>
    </path>
    <target name="compile_ejb" depends="init">
    <javac srcdir="${source}/src" destdir="${build}" debug="true" classpathref="compile.classpath"/>
    </target>
    Then I jar the output up with the META-INF stuff in the appropriate places. I also want to put the Manifest.mf together to refer to my jar as at the root (where I can have the Ear locate the jar file.)
    However, when I set up this manifest, and then run wlappc, also with the same classpathref, as in:
    <target name="appc" depends="jar.ejb">
    <wlappc debug="${debug}"
    source="${dist}/${jar.name}"
    classpathref="compile.classpath"/>
    </target>
    The appc throws all sorts of exceptions. It seems that the skeleton code it builds does not really match up well with the actual EJB code, and the compiler then complains when trying to compile the skeleton code. For example:
    [wlappc] C:\DOCUME~1\clarkk03\LOCALS~1\Temp\appcgen\com\pfizer\dcbls\svc\SampleEJBComponentManager_nrpnna_Impl.java:67: ejbActivate() in com.pfizer.dcbls.svc
    .SampleEJBComponentManager_nrpnna_Impl cannot override ejbActivate() in com.pfizer.dcbls.svc.ComponentManagerEJB; overridden method does not throw java.rmi.RemoteException
    [wlappc] public void ejbActivate()
    Now, when I remove the Class-Path entry in the Manifest.mf, wlappc works fine.
    For reference, the jar building task (with manifest entry included,) is:
    <target name="jar.ejb" depends="compile_ejb">
    <jar jarfile="${dist}/${jar.name}"
    basedir="${build}"
    update="yes">
    <manifest>
    <attribute name="Class-Path" value="dcblsfw.jar"/>
    </manifest>
    </jar>
    </target>
    Is this a bug with appc/wlappc? Is there a better way to do this, or a workaround to make it work?
    It seems odd that if the Class-Path in Manifest.mf is not to refer to anything internal to the jar, that it affects appc the way it does.
    Thanks,
    ken

  • Problem building EJB jar file using Eclipse

    Hi,
    Here's my file sturcture.
    ejb\x\y\z\test\
    ejb\x\y\z\test1\
    'ejb' is the root directory.
    The java source files under 'test' have a package name x.y.z.test.
    The java source files under 'test1' have a package name x.y.z.test1.
    I want to build a EJB jar file for 'test' and 'test1' separately. In eclipse when I create an EJB project, I specify the root folder as the source in the java build path settings. So the project explorer in Eclipse shows both the packages since they are under the same root folder. When I try to do 'Export - EJB Jar File', it includes both the 'test' and 'test1' in the .jar. Is there a way to build them separately ?
    Thanks,

    As far as I know, there is no way in Eclipse to specify a package prefix for a source folder. Assuming that you are not using an operating system with support for symbolic links at FS-level, the only way I can think of solving your problem is via linked folders and includes/excludes.
    1. Create two ejb projects in your workspace. Specify locations somewhere independent of where the root of your source tree is located.
    2. Right click on proj1 and select Properties / Java Build Path / Source.
    3. Click Link Source and specify the location to your source root on disk. Click Next.
    4. In the inclusion patterns section, add a pattern that captures classes appropriate for that module. Click Finish.
    5. Delete the original source directory that was created during project creation before leaving Build Path configuration dialog.
    6. Repeat steps 2-5 on the second project, except specify a different inclusion pattern.
    This should produce a project structure that Eclipse will be happy with, but you have to be a little bit careful. Even though you filtered out classes from the view of the java compiler for a particular project, you will still see them listed in the various navigational views (such as Package Explorer or Project Explorer). Don't modify these filtered out files. The project that is supposed to be building them will not react to changes in the other project. You will have to manually refresh (right click on project and select refresh) the other project before the java compiler will see changes.
    Hope this will help you out.
    - Konstantin

  • Build EJB in Workshop that can build in Ant outside of EAR

    In a project I work on, we have a directory structure that contains individual
    components with their own build scripts. Some of these components construct ejb
    jars as their output. We also have a separate component that uses the WLS Ant
    tasks to construct an ear, pulling in the ejb-jars and other components built
    from the other directories.
    One person attempted to use Workshop to define the EJB classes to compose the
    component. We were intending to use the WLS Ant tasks to compile those classes
    into an ejb jar. What they found (and I'm afraid I don't know the particular
    problems they had) was that the components buildable in Workshop have to be inside
    an EAR directory structure. Apparently the WLS Ant tasks can't work outside of
    that structure.
    Has anyone else noticed this? Are there strategies for dealing with this?

    Check this URL : http://edocs.bea.com/wls/docs81/webserv/anttasks.html i found
    there the way to do the ant task whit workshop.
    Viviana
    "David Karr" <[email protected]> wrote:
    >
    In a project I work on, we have a directory structure that contains individual
    components with their own build scripts. Some of these components construct
    ejb
    jars as their output. We also have a separate component that uses the
    WLS Ant
    tasks to construct an ear, pulling in the ejb-jars and other components
    built
    from the other directories.
    One person attempted to use Workshop to define the EJB classes to compose
    the
    component. We were intending to use the WLS Ant tasks to compile those
    classes
    into an ejb jar. What they found (and I'm afraid I don't know the particular
    problems they had) was that the components buildable in Workshop have
    to be inside
    an EAR directory structure. Apparently the WLS Ant tasks can't work
    outside of
    that structure.
    Has anyone else noticed this? Are there strategies for dealing with
    this?

  • Problem with ejb-jar.xml created with ejbgen.

    Hi! ,
    I m using ejbgen for creating interfaces for my bean nut i m facing a problem which is suppose i have beans in different folders and i m using ejbgen for each folder containing beans.Now the problem is i m using ejbgen under one target in build.xml so wht happens is when ejb-jar.xml is generated it contains entry for the last folder beans and overrides other beans entry in different folder . i need some way so tht ejb-jar.xml keeps appending for every ejbgen is called.
    Thanks in advance....... :-)
    warm regards,
    Sourabh Singh

    My temporary workaround is copy all beans from different directory trees to one temporary directory, and create one FileSet in Ant.
    z.

  • Problem deploying connector: META-INF/ejb-jar.xml not found in jar file

              Has anyone seen this problem:
              I built Sun's Blackbox implementation and packaged
              it identical to the BlackBoxNoTx.rar included with
              Weblogic's 'jconnector' sample (even using the same
              ra.xml and weblogic-ra.xml). When I try to deploy
              it, the server reports:
              java.io.FileNotFoundException:
              META-INF/ejb-jar.xml not found in jar file
              I have no idea why the server thinks my connector
              is an EJB. If I deploy the BlackBoxNoTx.rar included
              with the sample, everything works without a hitch.
              The only variable that I'm changing in my BlackBoxNoTx.rar
              is that I build the Blackbox classes myself--otherwise,
              the RAR packagings are identical. Any assistance is
              greatly appreciated since I'm banging my head against
              a wall...
              Thanks,
              -jason
              

              I was finally able to resolve this one. On the odd chance that someone else encounters
              the same problem, here's what went wrong:
              My RAR file had two directories: 'META-INF' and 'meta-inf'. The first was created
              by the jar tool and contained the manifest.mf file. The second I created manually
              and it contained my ra.xml and weblogic-ra.xml. When I examined the RAR using
              any tools or I extracted the contents, it looked like it only contained one directory:
              META-INF (because NT is case-insensitive).
              "Jason L" <[email protected]> wrote:
              >
              >Has anyone seen this problem:
              >
              >I built Sun's Blackbox implementation and packaged
              >it identical to the BlackBoxNoTx.rar included with
              >Weblogic's 'jconnector' sample (even using the same
              >ra.xml and weblogic-ra.xml). When I try to deploy
              >it, the server reports:
              >
              >java.io.FileNotFoundException:
              >META-INF/ejb-jar.xml not found in jar file
              >
              >I have no idea why the server thinks my connector
              >is an EJB. If I deploy the BlackBoxNoTx.rar included
              >with the sample, everything works without a hitch.
              >The only variable that I'm changing in my BlackBoxNoTx.rar
              >is that I build the Blackbox classes myself--otherwise,
              >the RAR packagings are identical. Any assistance is
              >greatly appreciated since I'm banging my head against
              >a wall...
              >
              >Thanks,
              >
              >-jason
              

  • How to configure maven to build EJB Jar?

    Hi!
    I would like to know how you setup Maven2 or alternatively Ant to build an EJB Jar.
    I have managed to do this in Maven by adding required jars to my local repository and added dependencies in the pom.xml file. This, however, do not seem like a good solution. I would like set some kind of classpath for maven to look for all libraries included in my application server.
    Could you please help me to solve this and I will be most grateful?!
    /Leo

    Hi,
    this is not an Eclipse forum but JDeveloper and ADF. Please try StackOverflow
    http://stackoverflow.com/questions/tagged/eclipse
    (Before I would search on StackOverflow if this question has been ansered before)
    Frank

  • Cannot build EJB jar file in NWDS

    hello,
    I changed java beans file, and tried to build jar file again, then the "build EJB archive" context menu is disabled so I can not make EJB jar file!
    So frustrated.. NWDS recognizes the changes in the java files , right? How come there 's no Build menu..
    Is there any pre-requisite to enable the menu?
    I have no idea how I can build jar file..
    Please give me a advice.. Thanks~!

    You might check the weblogic.developer.interest.ejb.tools new group.
    Make sure that the tool doesn't leave this ejbcgen directory around. It
    should delete
    that temp dir. When it doesn't it keeps all the old generated stuff around
    and your changes won't be
    reflected in the new jar.
    Rodrigo Ruiz Aguayo <[email protected]> wrote in message
    news:[email protected]..
    Hi,
    I have a problem with the EJBDeployerTool. When I want to update
    a class file (for example, because I corrected any problem), the
    deployer tool doesn't update the file correctly. It keeps the
    old version of the class file.
    In order to update a jar I have to copy the newer version in the
    .ejbdeployer/provider-projects directory by hand. Is it a bug?
    Is there any other way to do this? We are wasting too much time
    in this task, instead of programming :_(
    Thanks in advance,
    José Rodrigo Ruiz Aguayo e-mail : [email protected]
    I.T. en Informática de Sistemas webpage : ---------------------
    "Simulation is perfect, whenever we're not talking about reality"

  • External Entity Problem w/ ejb-jar.xml

    I cannot figure out nor find how to have the ejb-jar.xml refer to external entities
    so that it doesn't get overly large and unmanageable. Note: our "shared-ejb-jar.xml"
    gets converted into "ejb-jar.xml" inside of a deployed shared.jar file.
    The shared-ejb-jar.xml file contains:
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans
    2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'
    <!ENTITY SatelliteExt SYSTEM "satellite-ext.xml">
    ]>
    ........XML code.........
    &SatelliteExt;
    ........XML code.........
    The satellite-ext.xml file is in the same directory and contains the XML to describe
    a single <entity>...</entity>.
    I use ant to compile and receive this error:
    C:\jist\bin\build.xml:74: SAXException while parsing 'shared-ejb-jar.xml'. This
    probably indicates badly-formed XML. Details: Relative URI "satellite-ext.xml";
    can not be resolved without a document URI.
    Any help will be most appreciated.
    -- Guy

    Problem is resolved. Thanks for looking over this thread.
    Regards
    Karthik

  • Adding ejb.jars using ant

    I am trying to write an ant build.xml file that adds some ejb.jar files to the classpath.
    <project name="PRIMA Monitor" default="final stage" basedir=".">
         <!-- Init some path variables -->
         <target name="init">
              <echo message="Building PRIMA Monitor on ${os.name}" />
              <property name="src" location="ie/nuigalway/primamonitor"/>
              <property name="build" location="build"/>
              <property name="jars" location=" ./include/ejbBanHub.jar;include/kunststoff.jar;./include/jbcl.jar;.include/ejbPatient.jar;./include/ejbWearer.jar;./include/jbossall-client.jar"/>
              <property name="docs" location="docs"/>
              <property name="deploy" location="deploy"/>
         </target>
         <!-- Try and compile the source (in $src), dumping class files in the $build dir -->
         <target name="build" depends="init">
         <mkdir dir="${build}" />
              <javac srcdir="${src}"
                   destdir="${build}"
                   debug="true"
                   classpath="${jars}"
                   includes="**/*.java" />
         </target>
    when i run the build.xml i get some compilation errors associated with the ejb jar files(which i dont get when i manually javac the files). Am i adding the jar files correctly in the build.xml.

    typo error (";include/kunststoff.jar" or should be ";./include/kunststoff.jar") ?

  • Weblogic 7 SP2 - problem in ejb-jar.xml

    Hi,
    I have a problem when trying to move from Weblogic 7 to 7 SP2. In some of our
    ejb-jar.xml descriptors we have something like the following:
    <!ENTITY ENTITY_PROP SYSTEM "Config/entity_config.txt">
    then used this later on in the descriptor:
    <env-entry-value>&ENTITY_PROP;</env-entry-value>
    In all previous versions this would work fine with the Config directory sat in
    the domain directory but when we are trying to move to SP2 the ejb's are failing
    at deployment time with errors like:
    weblogic.xml.process.XMLParsingException: File "zip://C/bea/user_projects/mydomain/myserver/.wlnotdelete/ScanServer/MkpCodeServerEJB.jar!/META-INF/Config/entity_config.txt"
    not found. - with nested exception:
    [org.xml.sax.SAXParseException: File "zip://C/bea/user_projects/mydomain/myserver/.wlnotdelete/ScanServer/MkpCodeServerEJB.jar!/META-INF/Config/entity_config.txt"
    not found.].....
    What has changed? What can I do to solve the problem?
    thank you,
    Ian

    Hi,
    Please ignore the previous post. it is a bug in 10.3. Please contact the support and get the patch. The bug no is 8180493. thanks.
    -Albert
    Edited by: zhao.yong on 2009-6-22 下午11:17

  • Problem regarding Deployment of EJB jar file

    I am getting the following problem when i am trying to deploy my EJB on to the Weblogic 8.1 using the EjbModules option.
    Please help me
    Exception:weblogic.management.ApplicationException: prepare failed for mybank Module: mybank Error: Exception preparing module: EJBModule(mybank,status=NEW) Unable to deploy EJB: E:\OnlineBanking\mybank\mybank.jar from mybank.jar: weblogic.ejb20.deployer.DeploymentDescriptorException: Unable to load a class specified in your ejb-jar.xml: Class bytes found but defineClass()failed for: 'mybankEJB' at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Lweblogic.utils.classloaders.GenericClassLoader;)V(MBeanDeploymentInfoImpl.java:550) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Lweblogic.utils.classloaders.GenericClassLoader;Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;Lweblogic.utils.jars.VirtualJarFile;)V(MBeanDeploymentInfoImpl.java:232) at weblogic.ejb20.deployer.EJBDeployer.prepare(Lweblogic.utils.jars.VirtualJarFile;Ljava.lang.ClassLoader;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;Ljava.util.Map;)V(EJBDeployer.java:1302) at weblogic.ejb20.deployer.EJBModule.prepare(Ljava.lang.ClassLoader;)V(EJBModule.java:498) at weblogic.j2ee.J2EEApplicationContainer.prepareModule(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.j2ee.J2EEApplicationContainer$Component;Z)V(J2EEApplicationContainer.java:3101) at weblogic.j2ee.J2EEApplicationContainer.prepareModules([Lweblogic.j2ee.J2EEApplicationContainer$Component;Ljava.lang.String;Z)V(J2EEApplicationContainer.java:1560) at weblogic.j2ee.J2EEApplicationContainer.prepare([Lweblogic.j2ee.J2EEApplicationContainer$Component;[Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(J2EEApplicationContainer.java:1208) at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.management.configuration.ComponentMBean;[Ljava.lang.String;)V(J2EEApplicationContainer.java:1051) at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer()V(SlaveDeployer.java:2444) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2394) at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2310) at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866) at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594) at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508) at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25) at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219) at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178) at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

    In addition to the JavaEE Tutorial link above, Sun Java System Application Server 9.0 Documentation is here:
    http://docs.sun.com/app/docs/coll/1343.3
    -cheng

  • I have a problem when i open the ejb-jar.xml

    Hi All,
    I have a problem when i open the ejb-jar.xml.....
    It shows some problem like .....
    when Invoking  Code plug-in problem :Org.eclipse.jface.
    After updating my nwds 3 to 11.
    How can i solve this any body help me.
    regards
    BHI

    Maybe try hosting your image on a free image hosting site.

  • Deployment Plan / weblogic-ejb-jar.xml:  Problem

    Hello,
    I am trying to use a deployment plan to override the principal name in the weblogic-ejb-jar.xml.
    The deployment-plan looks like this (showing only the important sections)
    <variable-definition>
    <variable>
    <name>SecurityRoleAssignment_ejbRole_PrincipalNames_1</name>
    <value>MY PRINCIPAL 1</value>
    </variable>
    </variable-definition>
    <variable-assignment>
    <name>SecurityRoleAssignment_ejbRole_PrincipalNames_1</name>
    <xpath>/weblogic-ejb-jar/security-role-assignment/[role-name="View-Role"]/externally-defined</xpath>
    <operation>replace</operation>
    </variable-assignment>
    The security-role assignment in the weblogic-ejb-jar.xml looks like this:
    <security-role-assignment>
    <role-name>View-Role</role-name>
         <externally-defined/>
    </security-role-assignment>
    I 've tried to override the element-value of <externally-defined> (a valid tag in the weblogic-ejb-jar.xml ) with help of a deployment-plan.
    When trying to deploy my application (which is organised in the directory-structure: inst_dir/APP inst_dir/PLAN
    the following error occurs:
    VALIDATION PROBLEMS WERE FOUND problem: cvc-complex-type.2.4a: Expected element 'principal-name@http://www.bea.com/ns/weblogic/10.0' instead of 'externally-defined@http://www.bea.com/ns/weblogic/10.0' here in element security-role-assignment@http://www.bea.com/ns/weblogic/10.0:
    This has surprised me, as externally-defined is (according to the documentation) a valid tag.
    I have tried to replace <externally-defined> with an empty <principal-name> tag (which works fine when deploying the application), but causes a security exception, when trying to use the EJB.
    Has anybody an idea if there is a workaround for this problem?
    IMHO the Validatio Problem is not justified at this place then why should an otherwise valid weblogic-ejb-jar.xml (when not using a deployment-plan) suddenly become invalid when a deployment plan is used?
    Thanx a lot in advance!
    Edited by: user10672779 on 02.12.2008 04:09

    Hi again,
    I tried it with the weblogic 10 Namespace Declaration but got then this error:
    failed to load java type corresponding to e=weblogic-ejb-jar@http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd
    and following Exception:
    <02.12.2008 20.00 Uhr CET> <Error> <J2EE> <BEA-160197> <Unable to load descriptor D:\exportapps\tb.ear\app\tb_flowcontrol.jar/META-INF/weblogic-ejb-jar.xml of module tb_flowcontrol.jar. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:152)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
    at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:774)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:395)
    at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:745)
    Caused by: com.bea.xml.XmlException: failed to load java type corresponding to e=weblogic-ejb-jar@http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd
    at com.bea.staxb.runtime.internal.UnmarshalResult.getPojoBindingType(UnmarshalResult.java:329)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:296)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineTypeForGlobalElement(UnmarshalResult.java:306)
    at com.bea.staxb.runtime.internal.UnmarshalResult.determineRootType(UnmarshalResult.java:287)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:153)
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
    at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:141)
    Searching the net couldn't supply me with another answer as to use the 90 Namespace Declaration again...
    I think I forgot to mention I am using an exploded directory.
    This all seems very strange.
    cheers.

  • Deployment problems when using several ejb-jar files

    Hello All,
    I am having problems with deployment of my J2EE application. My EAR file has several EJB-JARs, one for each entity bean. However I refer to the other EJBs in one EJB. Hence I included the <ejb-ref> element in the deployment descriptor of the entity bean. But I am getting the deployment error that "the bundle does not contain the bean name". I tried to change the <ejb-name> value (within the <ejb-ref> element) to the JNDI name of the EJB I am referring to, and also added the <ejb-link> tag specifying the location of the JAR file that has the EJB. None of the attempts worked.
    Can someone help me out on how I am supposed to go about when I have several ejb-jar files as opposed to a single one? I am deploying my app on Sun ONE AS 7.0.
    Thank you,
    PS: I am posting this message on several forum topics. Please disregard this message if you have seen/answered this message. Thanks.

    Hi ,
    It would help if you could post the relevant snippets of your
    ejb-jar.xml. In general, you definitely shouldn't use jndi-name
    for any of the linking information. jndi-name is not part of the
    standard deployment descriptor. The syntax for the ejb-link is
    [ejb-jar uri]#ejb-name
    K

Maybe you are looking for

  • When is Apple going to provide sRGB on the iPad Retina mini?

    I was looking forward for months for the iPad mini Retina.  I'm extremely disappointed at the restricted colour gamut which is clear, even without comparing it directly with an Air.  When alternative tablets are much cheaper, have both the resolution

  • Ctrl alt F1 problem in X

    Has anything changed recently that would prevent switching to virtual consoles with ctrl alt F1? It has suddenly stopped working for me.  The xorg.conf file (below) hasn't been changed in over a month.  Have kept up to date with pacman -Syu.  Only ot

  • Daily Show comes in after the free Web version online, why is that?

    Bought pass for Daily Show and Colbert Report, first 2 came in fine but now they are a day late. I can watch for free on the Comedy Central site right away. Seems a waste since its a current affairs show, why pay if it's downloading late?

  • HTTP/1.1 100 Continue from PTWC 3.0

    Hi all We are getting the string "HTTP/1.1 100 Continue" appearing every so often after a PTWC 3.0 postback .. it doesn't seem to have any detrimental affect on the app but it's a little confusing to end users. Has anyone else experienced this? We'd

  • Help with vidieo? Premiere Elements

    I created a slide show in organizer. Now in Premier Elements I have added a narritive and sound track. Hve burnt a dvd in hvchd and it works fine on my dvd players at home but will not work on some other dvd players I have tried. Also when I down loa