Ejb-jar files directory in WLS console

Hi , Everyone
I 'll like to know that's the meaning of "\.\" in the following directory
which found in Weblogic 7 console.
I just clicked: mydomain | delplyment | EJB | a4b2.jar
D:\bea\user_projects\mydomain\.\myserver\upload\a4\a4b2.jar

Hi , Everyone
I 'll like to know that's the meaning of "\.\" in the following directory
which found in Weblogic 7 console.
I just clicked: mydomain | delplyment | EJB | a4b2.jar
D:\bea\user_projects\mydomain\.\myserver\upload\a4\a4b2.jar

Similar Messages

  • Updating an EJB jar file on WL7.0

    Hi
    Iam attempting to update an EBJ jar file without taking down my WL7.0 server.
    When I copy the jar file to the applications directory, I see the server accepting
    the update but when I run my client the update is not visible! Iseem to be still
    accessing the old ejb.
    From my understanding, if the server is running in development mode I should be
    able to copy the jar file with my update directly to the applications directory(
    overwriting old jar file) and be able to access the udated ejb.

    Hello Ron,
    An alternative would be to modify a REDEPLOY file if your application is deployed
    in exploded directory format. However, updating the EJB JAR should also do the
    trick. Try going into the Admin console and explicity redeploying the EJB JAR
    file after copying over the new JAR file. Let us know if any errors appear.
    Best regards,
    Ryan LeCompte
    [email protected]
    http://www.louisiana.edu/~rml7669
    "Ron Turner" <[email protected]> wrote:
    >
    Hi
    Iam attempting to update an EBJ jar file without taking down my WL7.0
    server.
    When I copy the jar file to the applications directory, I see the server
    accepting
    the update but when I run my client the update is not visible! Iseem
    to be still
    accessing the old ejb.
    From my understanding, if the server is running in development mode I
    should be
    able to copy the jar file with my update directly to the applications
    directory(
    overwriting old jar file) and be able to access the udated ejb.

  • How to deploy EJB jar file in Weblogic 8.1

    Hi,
    I have created the EJB jar file, bearing home,remote,ejb and client class aling with the META-INF folder containing ejb-jar.xml and weblogic-ejb-jar.xml.
    After all this I am confused where to put this EJB jar file so that the container could deploy it.
    I am putting it in application folder of my own created Domain.
    Suggest me...

    Put it anywhere you like. You can always deploy it using the administrator console. There usually is an auto-deployment directory for the domain. You could find all that information in the Weblogic documentation.

  • No EJBs found in the ejb-jar file

    Hello all, we are thinking about migrating from JBoss to WebLogic server, so as a proof of concept I am trying to migrate a JBoss Seam web application to WebLogic server.
    I have followed all the instructions here: http://docs.jboss.org/seam/2.0.2.SP1/reference/en-US/html/weblogic.html and I have set up ebvryhting that is needed in order to start the server (JMS queues, datasources, etc) but when the server starts and tries to load the web application I got the following error message
    <29 ═Ύί 2010 4:34:51 ΉΉ EET> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'myapplication-ear' due to error weblogic.application.ModuleException: Exception preparing module
    : EJBModule(MyApplication.jar)
    [EJB:011023]An error occurred while reading the deployment descriptor. The error was:
    No EJBs found in the ejb-jar file 'MyApplication.jar'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with t
    he @Stateless, @Stateful or @MessageDriven EJB annotation...
    weblogic.application.ModuleException: Exception preparing module: EJBModule(MyApplication.jar)
    [EJB:011023]An error occurred while reading the deployment descriptor. The error was:
    No EJBs found in the ejb-jar file 'MyApplication.jar'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with t
    he @Stateless, @Stateful or @MessageDriven EJB annotation..
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:467)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:507)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:149)
    Truncated. see log file for complete stacktrace
    Caused By: java.io.IOException: No EJBs found in the ejb-jar file 'MyApplication.jar'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at l
    east one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
    at weblogic.ejb.container.dd.xml.EjbDescriptorReaderImpl.createReadOnlyDescriptorFromJarFile(EjbDescriptorReaderImpl.java:219)
    at weblogic.ejb.spi.EjbDescriptorFactory.createReadOnlyDescriptorFromJarFile(EjbDescriptorFactory.java:93)
    at weblogic.ejb.container.deployer.EJBModule.loadEJBDescriptor(EJBModule.java:1242)
    at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:395)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
    Truncated. see log file for complete stacktrace
    The MyApplication.jar is where we keep all the models and we are using an exploded folder for the ear file. We have declared all the classes to be entities by using the @Entity and @Table annotations and we have also defined an interceptor in the ejb-jar.xml file (shown below).
    <?xml version="1.0" encoding="UTF-8"?>
    <ejb-jar xmlns="http://java.sun.com/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"
    version="3.0">
    <interceptors>
    <interceptor>
    <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>
    </interceptor>
    </interceptors>
    <assembly-descriptor>
    <interceptor-binding>
    <ejb-name>*</ejb-name>
    <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>
    </interceptor-binding>
    </assembly-descriptor>
    </ejb-jar>
    I have tried to compile everythign from scratch by using weblogic.appc but I am getting the same error: No EJBs found in the ejb-jar file 'ejbModule'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
    Any ideas what is going on and how I can resolve the issue?
    Regards
    Panos
    Edited by: 816483 on 29 Νοε 2010 6:53 πμ

    Hi John,
    I am working on development an enterprise application using EJB 3.0 on Weblogic 10.
    While developing, I am keeping all my classes (from ejb's as well as web) into APP-INF/classes directory. It is working fine for Web and ejb 2.0 packages, but ejb 3.0 packages, I get the following error when I keep my ejb 3.0 beans classes in APP-INF/classes directory.
    No EJBs found in the ejb-jar file 'customer'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
    One solution is to keep the classes under customer ejb directory, but I wan tto keep all the classes in APP-INF/classes directory so that when using Eclipse IDE I can output all compiled sources into APP-INF/classes directory.
    Has anyone faced this situation? Any suggestions to fix this issue?

  • 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"

  • ClassNotFoundException if ejb jar file is not placed in the server's classpath

    Hi,
    My ejb jar file contains some non-weblogic generated files and is placed in
    the applications directory. When client is executed, I get the ClassNotFoundException
    on the server when my bean makes a reference to the generated class. The problem
    gets resolved if I put the ejb jar in the server's classpath.
    This problem happens in weblogic server version 6.1. It was not happening in
    the previous releases of weblogic server(6.0).

    Well
    I follow your instruction
    I am pasting the command prompt operation
    Coding is same above
    My all three files (.java )is resides in javath folder
    command prompt code
    Z:\javath>javac -d . sa.java
    Z:\javath>javac -d . sb.java
    Z:\javath>jar -cvf p1.jar p1/*.class
    added manifest
    adding: p1/sa.class(in = 687) (out= 423)(deflated 38%)
    adding: p1/sb.class(in = 185) (out= 153)(deflated 17%)
    Z:\javath>javac demopack.java
    demopack.java:4: cannot access sb
    bad class file: .\sb.java
    file does not contain class sb
    Please remove or make sure it appears in the correct subdirectory of the classpa
    th.
    public class demopack implements sb
                                     ^
    1 error
    Z:\javath>------------------------------------------------------------
    in demopack.java file i want to access class files which are resides in
    jar files
    Actually when we are writing import java.io.*;
    we can access all the class file from that io package
    Same thing i am trying to implement for user defined package
    I hope you understand my question
    regards

  • Do I need to add to add a new jar file to the WLS ?

    I am new to java development and would like to know if I were to use a new jar
    file developed by another party in my EJB development, do I need to have this
    jar file available in WLS when I deploy the EJB to it ?
    I think this is not required but just need a confirmation.
    Thanks

    Hi,
    I take this to mean you are using java classes from the 3rd party jar in your
    EJB bean class. If that is the case, then you need the jar file in your classpath
    when you compile the EJB classes.
    Also, you will need the jar file to be in the classpath when the EJB is used.
    You can do this in a variety of ways. If the 3rd party jar is going to change
    infrequently, then you can put it in the system CLASSPATH in your startWebLogic
    script. Or you can add all the classes of the jar file in the root level of the
    EJB (Yuck!!).
    Perhaps the best answer is to create an enterprise application (EAR). Then you
    place the jar file in the root level of the EAR. In the META-INF\MANIFEST.MF
    file of the EJB place
    Class-Path: filename.jar
    Then when you build the .ear file use:
    jar -cvfm ..\commuterLog.jar META-INF\MANIFEST.MF *
    hope this helps,
    pat
    "John" <[email protected]> wrote:
    >
    I am new to java development and would like to know if I were to use
    a new jar
    file developed by another party in my EJB development, do I need to have
    this
    jar file available in WLS when I deploy the EJB to it ?
    I think this is not required but just need a confirmation.
    Thanks

  • 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

  • Deployment error 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.

    Hello,
    Thanks for the response. I have got both Local and Remote EJB References, but for the JAR (where the ejbc compiler stopped) that I have an error, it is the local reference.

  • EJB relation mappings between different ejb jar files.

    I have two local entity EJBs but they are in different ejb jar files. I'd like to make a relationship mapping (one-to-one, one-to-many or whatever) between them. Is it possible? To do that, I need <ejb-name> reference tag each other in both ejb-jar.xml, but how can I refer to ejb-name defined in different ejb jar files? Or as long as you make EJB relationship mappings, all EJBs must be in the same ejb jar file?
    thanks,
    -tom

    Refer to
    http://www.onjava.com/pub/a/onjava/2001/06/26/ejb.html?page=2&x-showcontent=text

  • 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

  • Unable to create ejb.jar file.

    how do we create an ejb.jar file in j2ee explorer.
    I am not able to see the option <i>Build Ejb.jar</i>
    in the context menu when i click on my ejb project
    Regards
    Naresh Garg

    hi Naresh,
    There is option called EJB Archive this option builds your EJB. if your trying to create Web Module Project you can only create WAR file .
    Venkat

  • How to create a deployable ejb(.jar file) when we use Oracle application sever?

    Hi,
    In case if we use Weblogic we give following command on console to create a deployable ejb, while weblogic.jar is in classpath.
    java weblogic.ejbc temp.jar StudentBean.jar
    1)What are the classes or jar files we have to set in classpath,
    2)What console based command(like what I mentioned above for weblogic) can we use,
    so that we can create a deployable jar file in case if we are using Oracle application server.
    thanks,
    Milind

    You can discover the origins of a loaded class programatically. You want to print:
    TheClass.class.getProtectionDomain().getCodeSource().getLocation().toString();

  • Import a ejb jar file created for Oracle OAS ?

    Hi,
    I have a jar file with some ejbs created to run on OAS. I need to import them
    into the Workshop and deploy them to WebLogic 8.1. I've tried to use the function
    Import ejb from jar (my jar file contains a weblogic-ejb-jar.xml file), but it
    fails badly. The stack trace I get:
    java.lang.InternalError: jzentry == 0,
    jzfile = 413124120,
    total = 175,
    name = C:\projects\xxxBEA\deploy\deploy\xxx_ejb.jar,
    i = 32,
    message = invalid LOC header (bad signature)
         at java.util.zip.ZipFile$2.nextElement(ZipFile.java:321)
         at java.util.jar.JarFile$1.nextElement(JarFile.java:201)
         at weblogic.utils.jars.JarFileDelegate$1.next(JarFileDelegate.java:54)
         at com.bea.wls.revejbgen.Main.loadAllClassNames(Main.java:102)
         at com.bea.wls.revejbgen.Main.init(Main.java:79)
         at com.bea.wls.revejbgen.Main.<init>(Main.java:52)
         at com.bea.wls.ejb.importer.ImportWizard.loadJarFile(ImportWizard.java:121)
         at com.bea.wls.ejb.importer.FileStep.onNext(FileStep.java:96)
         at com.bea.ide.ui.wizard.WizardDialog.next(WizardDialog.java:286)
         at com.bea.ide.ui.wizard.WizardDialog.access$1000(WizardDialog.java:42)
         at com.bea.ide.ui.wizard.WizardDialog$6.actionPerformed(WizardDialog.java:387)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1764)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1817)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:419)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:257)
         at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:245)
         at workshop.core.plaf.JbButtonUI$JbButtonListener.mouseReleased(JbButtonUI.java:1009)
         at java.awt.Component.processMouseEvent(Component.java:5134)
         at java.awt.Component.processEvent(Component.java:4931)
         at java.awt.Container.processEvent(Container.java:1566)
         at java.awt.Component.dispatchEventImpl(Component.java:3639)
         at java.awt.Container.dispatchEventImpl(Container.java:1623)
         at java.awt.Component.dispatchEvent(Component.java:3480)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3450)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3165)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3095)
         at java.awt.Container.dispatchEventImpl(Container.java:1609)
         at java.awt.Window.dispatchEventImpl(Window.java:1590)
         at java.awt.Component.dispatchEvent(Component.java:3480)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:450)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:140)
         at java.awt.Dialog.show(Dialog.java:551)
         at com.bea.ide.ui.wizard.WizardDialog.show(WizardDialog.java:130)
         at com.bea.wls.ejb.importer.ImportAction.showWizard(ImportAction.java:42)
         at com.bea.wls.ejb.importer.ImportAction.actionPerformed(ImportAction.java:32)
         at workshop.shell.commands.CmdActionDefinition.actionPerformed(CmdActionDefinition.java:217)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1764)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1817)
         at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:419)
         at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:257)
         at javax.swing.AbstractButton.doClick(AbstractButton.java:289)
         at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1113)
         at workshop.core.plaf.JbMenuItemUI.doClick(JbMenuItemUI.java:640)
         at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(BasicMenuItemUI.java:943)
         at java.awt.Component.processMouseEvent(Component.java:5134)
         at java.awt.Component.processEvent(Component.java:4931)
         at java.awt.Container.processEvent(Container.java:1566)
         at java.awt.Component.dispatchEventImpl(Component.java:3639)
         at java.awt.Container.dispatchEventImpl(Container.java:1623)
         at java.awt.Component.dispatchEvent(Component.java:3480)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3450)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3165)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3095)
         at java.awt.Container.dispatchEventImpl(Container.java:1609)
         at java.awt.Window.dispatchEventImpl(Window.java:1590)
         at java.awt.Component.dispatchEvent(Component.java:3480)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:450)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:144)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)
    Any help is appreciated. Thank you.

    Hi,
    >>>>We have to send the original xml-payload and the generated (over XSL-FO) pdf-file as attachments in one mail.
    Could this be realized with this solution?
    then don't set it as constant
    use getContextData method to get the xsl filename
    from one of the folders:
    moduleContext.getContextData("dirName");
    then you only have to add <b>dirName </b> parameter
    in the mail adapter configuration (modules tab)
    and specify the path to your xsl over there
    this way you're adapter module will be reusable
    and you'll have both XML-payload and the XSL
    (so you'll be able to generate PDF)
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

  • Problem accessing Application Ejb Jar files from Apache Axis jars

    I have deployed an EAR application, with a structure as shown below,
    MyApp.ear
    |____ MyApp_Ejb.jar
    |____ axis.war
    |_____ WEB-INF
    |_____ lib (This contains all axis specific jars)
    The application deploys just fine. But when i goto happyaxis.jsp and try to view all the web services that have been deployed. I get an exception "No provider type matches QName '{http://xml.apache.org/axis/wsdd/providers/java}SDL".
    Here SDL is a custom provider that i have written and all the required files for the provider are available in MyApp_Ejb.jar.
    I do not get as to why the axis.jar is not able to find classes in MyApp_Ejb.ear, when both these are in the same ear.
    Now i know i can add a utility jar to a war files classpath by adding a classpath line in the War file MANIFEST.MF. But since MyApp_Ejb.jar is defined as a Web Module this solution too doesnt help.
    Separating the provider related files from MyApp_Ejb.jar is not possible since there is too much dependance of other files within that jar.
    So i am looking for a solution where in i can continue to have MyApp_Ejb.jar as my ejb module as well as the axis related jars can find the required classes within MyApp_Ejb.jar. some way of sharing the ejb jar across to axis jars.
    Thanks in advance.
    Vicky

    I have deployed an EAR application, with a structure as shown below,
    MyApp.ear
    |____ MyApp_Ejb.jar
    |____ axis.war
    |_____ WEB-INF
    |_____ lib (This contains all axis specific jars)
    The application deploys just fine. But when i goto happyaxis.jsp and try to view all the web services that have been deployed. I get an exception "No provider type matches QName '{http://xml.apache.org/axis/wsdd/providers/java}SDL".
    Here SDL is a custom provider that i have written and all the required files for the provider are available in MyApp_Ejb.jar.
    I do not get as to why the axis.jar is not able to find classes in MyApp_Ejb.ear, when both these are in the same ear.
    Now i know i can add a utility jar to a war files classpath by adding a classpath line in the War file MANIFEST.MF. But since MyApp_Ejb.jar is defined as a Web Module this solution too doesnt help.
    Separating the provider related files from MyApp_Ejb.jar is not possible since there is too much dependance of other files within that jar.
    So i am looking for a solution where in i can continue to have MyApp_Ejb.jar as my ejb module as well as the axis related jars can find the required classes within MyApp_Ejb.jar. some way of sharing the ejb jar across to axis jars.
    Thanks in advance.
    Vicky

Maybe you are looking for