RDBMSRealm ACL why if in deployment descriptors?

I was planning on using deployment descriptors for my ACL. I have users and
groups in my database and this maps just fine for the RDBMS schema. Why then
do I need ACLs in the schema? I have them in my deployment descriptors! I'm
getting errors like column not found, etc when it tries to load my realm
(obviously, I don't have ACL set up in database). Is there a way around
this?
thanks,
Mike Lee
Architect
AfterBOT
[email protected]
Just remove nospam_ to email me

You can not do this. Per J2EE is exactly how WLS works under the hood for
ACL deployment descriptors. It does not use container managed ACL through
RDBMSRealm for anything that a deployment descriptor can do (ie: ejb-jar.xml
and web.xlm security-contraint)
Michael Lee
"Michael Lee" <[email protected]> wrote in message
news:3d6d0765$[email protected]..
It turns out that it just wants an entry in the schema in the RDBMS setup.I
created a table that mapped to it just to be safe. If there are no entries
in the ACL table then thats ok, it just means that there are no ACL
constraints (outside of what you put on deployment descriptors of course).
This is all working now! Yay!
Now I'm looking at taking the ACL information out of the deployment
descriptors (web.xml and ejb-jar.xml) and putting them in the ACL_ENTRIESin
the RDBMSRealm. I don't know if this can be done but if it can it would be
very nice for configurability. I could then write JSPs for the customer to
change the security of the system.
Michael Lee
"Michael Lee" <[email protected]> wrote in message
news:[email protected]..
I was planning on using deployment descriptors for my ACL. I have usersand
groups in my database and this maps just fine for the RDBMS schema. Whythen
do I need ACLs in the schema? I have them in my deployment descriptors!I'm
getting errors like column not found, etc when it tries to load my realm
(obviously, I don't have ACL set up in database). Is there a way around
this?
thanks,
Mike Lee
Architect
AfterBOT
[email protected]
Just remove nospam_ to email me

Similar Messages

  • How to do JAAS and J2EE Deployment Descriptor ACL in WLS

    The examples on this website and shipped with WLS stink. Does there exist a GOOD
    example of how to
    Log in with a form
    authenticate (I guess using j_security_check to hook into the web.xml security)
    then pull a user from a database and use the roles defined there for authorization
    in the rest of the system?
    The weblogic examples are from java clients to RMI (ya, thats handy). They also
    sit alone. They dont say how to hook them into weblogic. They say to use JAAS
    but they have just JAAS examples! No hooking of it into an EJB, servlet, etc!
    They also dont show how to hook that code into WLS to use it as your security
    module!
    Help, I'm at a loss.
    They recommend using JAAS but their documentation and examples of doing so suck
    or are non existant. We have a complex real world product and need examples of
    the same. Stupid, stand alone examples that teach nothing do no help.
    frustrated at BEA for their poor documentation and support,
    Mike

    Also, I use struts....
    In struts you have to extend the Action class which then calls the perform()
    method on your servlet.
    So to call an EJB I have to have my servlet implement PrivilegedAction?
    If so, then this wants a run() method. Struts calls perform so that means
    I'm going to have to make another class to call from my servlet with a run
    method()? Or I'm going to have my servlet implement PrivledgedAction and
    call Security.runAs()?
    What if I just want to call the EJB from my servlet and put my security
    credentials in the JNDI lookup? I want the container to use the roles of the
    user in the JNDI lookup to authorize methods based on the deployment
    descriptors.
    thanks,
    Mike
    "Vimala Ranganathan" <[email protected]> wrote in message
    news:[email protected]...
    Hi Micheal,
    Attached is an exmaple of JAAS login and invoking an EJB.
    Let me know if this turns out to be useful.
    Regarding the form based authentication, Could you be more clear on whatissue you are
    facing?
    Just as note, when you use form based login, WLS would authenticate theuser against
    the realm
    WLS is setup for, which could be a file Realm, or a RDBMS realm (in whichcase users
    and groups are from database)
    Roles cannot be defined at the database level. This needs to be atapplication level
    which you can define in web.xml or
    console(in 7.0)
    If you need any specific help or more information please let me know.
    Vimala
    Michael Lee wrote:
    The examples on this website and shipped with WLS stink. Does there
    exist a GOOD
    example of how to
    Log in with a form
    authenticate (I guess using j_security_check to hook into the web.xmlsecurity)
    then pull a user from a database and use the roles defined there forauthorization
    in the rest of the system?
    The weblogic examples are from java clients to RMI (ya, thats handy).They also
    sit alone. They dont say how to hook them into weblogic. They say to useJAAS
    but they have just JAAS examples! No hooking of it into an EJB, servlet,etc!
    They also dont show how to hook that code into WLS to use it as yoursecurity
    module!
    Help, I'm at a loss.
    They recommend using JAAS but their documentation and examples of doingso suck
    or are non existant. We have a complex real world product and needexamples of
    the same. Stupid, stand alone examples that teach nothing do no help.
    frustrated at BEA for their poor documentation and support,
    Mike

  • Error in Sun XML schema for servlet2.4 deployment descriptor?

    Hi,
    I'm including the new XML schema for version 2.4 of the servlet standard in my web.xml deployment descriptor, using http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd
    When I try to save the XML file, XMLSpy reports an error in the schema file itself: "Undefined schema component 'base' encountered - simpleContext can not have a base that is a complexType with complexContent"
    This error is on line 744, and is caused by the snippet:
    <xsd:simpleContent>
    <xsd:extension base="j2ee:nonEmptyStringType"/>
    </xsd:simpleContent>
    Can anyone explain why I'm getting a validation failure on this schema? Surely someone else must have experienced the same thing, but I can't track down any reference to it anywhere. Help!

    XMLSpy is known to be flawed. From my own experience of implementing
    validators and data-binding tools, and from my experience of working in the
    W3C Schema working group, I can tell you that there are countless cases
    where XMLSpy violates the schema specification.
    I checked the corresponding part of the schema, but it looks correct to me.
    So I suspect that this is another bug in XMLSpy.
    Try Xerces. That's probably the best in terms of conformance to the spec.

  • The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing

    Hello,
    I want to create web service from ejb but everytime I want to do it, I get the following error:
    I'm using NWDS 7.2 and JDK 1.6
    [004]Deployment aborted
    Settings
    SDM host : XXX
    SDM port : 50118
    URL to deploy : file:/C:/DOCUME1/XXXX/LOCALS1/Temp/temp3760382784932063822XXXWSProjectEar.ear
    Result
    => deployment aborted : file:/C:/DOCUME1/XXX/LOCALS1/Temp/temp3760382784932063822XXX/WSProjectEar.ear
    Aborted: development component 'XXXWSProjectEar'/'sap.com'/'localhost'/'2011.01.06.15.48.31'/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Cannot deploy application sap.com/XXXWSProjectEar.. Reason: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing. ; nested exception is:      com.sap.engine.services.ejb.exceptions.deployment.EJBXMLParserException: The DOCTYPE declaration in the ejb-jar.xml deployment descriptor is missing.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Deployment exception : The deployment of at least one item aborted
    Can anyone tell me why am I getting this error.
    Thnx for your help.
    Best regards.

    Hello Decio Junior,
    Actually yes, I resolved my problem.
    I'm developing an EJB 3.0 project. I'm using NWDS 7.2 and JDK 1.6 as I said.
    The problem is that my server was using JDK 1.4 and that was the problem.
    EJB 1.1 and 2.1 need ejb-jar.xml but EJB 3.0 use the annotations instead.
    Check your server JDK Version. It should be JDK 1.5 or higher.
    Something else that you should check, in your project properties :
    In the Build PATH : Use JDK 1.5
    In the Java Compiler : Set the java compiler compliance level to 1.6 and check use default compliance settings
    Hope it would help.
    If you need more explanations, I'm here
    Good luck.

  • XML deployment descriptor generation

    How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
    By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
    Thanks.

    How to let OC4J automatically generate ejb-jar.xml, orion-ejb-jar.xml, web.xml for me? It is a nightmare to write these deployment descriptor by hand.
    By the way, I know that JDeveloper can generate this for us, but I am not using JDeveloper 9i. Can we just let OC4J generate these files for us?
    Thanks. Hi,
    there is no way (so far as I know) that an J2EE Application server (what oc4j is) makes the deployment descriptors, that's why they are called deployment descriptors, without them you can't deploy on any Application server.
    I personally use JDeveloper, but most current JAVA IDE's support generation of deployment descriptors.
    Basically my approach is to define the architecture within Rational Rose, which generates for me the stubs for the classes and for every ejb a deployment descriptor, later I copy all of them into one ejb-jar.xml and open the whole bunch with JDeveloper, it works fine with 903 preview, although there are some problems with the 902 version of JDeveloper.
    Which IDE are you using?
    --hery                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • How to edit web.xml deployment descriptor from console in weblogic 8.1?

    In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
    console, but on weblogic 8.1 I can't find a way to do so.
    Is this function taken out? Why is it taken out? Do I have an alternative to edit
    it without unpacking and packing the EAR or WAR?
    Thanks in advance.
    Bill

    In weblogic 7.0, deployment descriptor such as web.xml can be edited from the admin
    console, but on weblogic 8.1 I can't find a way to do so.
    Is this function taken out? Why is it taken out? Do I have an alternative to edit
    it without unpacking and packing the EAR or WAR?
    Thanks in advance.
    Bill

  • Deployment descriptor

    hi,
    what is the difference betwwen application server and web server?
    why we need a deployment descriptor?

    hi,
    what is the difference betwwen application server and
    web server?often, nothing. "application server" is a fairly broad term
    why we need a deployment descriptor?so that the container knows what your application consists of, and how to configure it

  • J2EE:160043]Missing deployment descriptor "WEB-INF/web.xml"

    Hi ,
    When I try to deploy using admin console i get the following error msg.
    J2EE:160043]Missing deployment descriptor "WEB-INF/web.xml"
    The war file has web.xml.
    Can some give me the reason for the above error.
    LOG content:
    weblogic.management.ApplicationException: [J2EE:160043]Missing deployment descriptor
    "WEB-INF/web.xml" at "C:\bea8\user_projects\domains\eConnect\applications\myEconnect.war"
         at weblogic.j2ee.J2EEApplicationContainerFactory.handleError(J2EEApplicationContainerFactory.java:729)
         at weblogic.j2ee.J2EEApplicationContainerFactory.initializeDeployment(J2EEApplicationContainerFactory.java:470)
         at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:833)
         at weblogic.management.deploy.DeployerRuntime.access$000(DeployerRuntime.java:63)
         at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:1499)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:1490)
         at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:186)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.runtime.DeployerRuntimeMBean_Stub.activate(DeployerRuntimeMBean_Stub.java:1064)
         at weblogic.management.console.actions.mbean.WebAppComponentDeployAction.prePerform(WebAppComponentDeployAction.java:141)
         at weblogic.management.console.actions.mbean.DoMBeanWizardAction.perform(DoMBeanWizardAction.java:215)
         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
         at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

    You'll have to at least show me the out contents of that WAR file.
    -- Rob
    Sowjanya wrote:
    Suppose the directory structure of the appl is c:\myroot\webapp\...
    then we need to go to webapp and then build the war file.
    C:\myroot\webapp>jar -cvf abc.war *
    then copy the war file and paste it in applicaitons folder.
    "sowjanya" <[email protected]> wrote:
    Hi ,
    When I try to deploy using admin console i get the following error msg.
    J2EE:160043]Missing deployment descriptor "WEB-INF/web.xml"
    The war file has web.xml.
    Can some give me the reason for the above error.
    LOG content:
    weblogic.management.ApplicationException: [J2EE:160043]Missing deployment
    descriptor
    "WEB-INF/web.xml" at "C:\bea8\user_projects\domains\eConnect\applications\myEconnect.war"
         at weblogic.j2ee.J2EEApplicationContainerFactory.handleError(J2EEApplicationContainerFactory.java:729)
         at weblogic.j2ee.J2EEApplicationContainerFactory.initializeDeployment(J2EEApplicationContainerFactory.java:470)
         at weblogic.management.deploy.DeployerRuntime.unprotectedActivate(DeployerRuntime.java:833)
         at weblogic.management.deploy.DeployerRuntime.access$000(DeployerRuntime.java:63)
         at weblogic.management.deploy.DeployerRuntime$1.run(DeployerRuntime.java:1499)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.management.deploy.DeployerRuntime.checkAndPerformDeployerActions(DeployerRuntime.java:1490)
         at weblogic.management.deploy.DeployerRuntime.activate(DeployerRuntime.java:186)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
         at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
         at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
         at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
         at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
         at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
         at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
         at weblogic.management.runtime.DeployerRuntimeMBean_Stub.activate(DeployerRuntimeMBean_Stub.java:1064)
         at weblogic.management.console.actions.mbean.WebAppComponentDeployAction.prePerform(WebAppComponentDeployAction.java:141)
         at weblogic.management.console.actions.mbean.DoMBeanWizardAction.perform(DoMBeanWizardAction.java:215)
         at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:173)
         at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
         at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

  • Deployment Descriptor Overwritten?

    Hey everyone thanks in advance for any help. I'm currently working on a newer EJB project in my company and I've seem to have run into a bit of an issue. Is there any reason why my Deployment Descriptors IE. orion-application.xml, orion-ejb-jar.xml and orion-application-client.xml are all over written at deployment time. we have just recently made the change from 9.0.4 to 10.1.2 and I'm wondering if the DTD headers on the .xml files can be causing this over write? The over written files show the 2 EJB previously defined but the new additions are missing?
    Thanks in Advance

    This is normal behaviour during deployment. You can include the vendor-specific deployment descriptors in your EAR file and OC4J/Oracle AS considers them during deployment. The more you specify the more will taken into account.
    To be on the save side during deployment an undeploy/deploy cycle is a good way.
    If you're lucky and can use JDeveloper you can test your complete application before deploying the first time...
    --olaf                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • Deployment descriptor file(portalapp.xml)

    Hi All,
    Can you tell me why portalapp.xml is a xml file why cannot it be a .txt or any other ?

    In java enterprise edition deployment descriptor denotes how the web or enterprise application should be deployed. It is a directive to the deployment tool regarding the specific configuration requirements that a deployer must fulfill.
    XML allows developers to set standards,helps in defining the configurations and the required information  and the sequence as well and easy to parse also.
    portalapp.xml ,the deployment descriptor of a PAR file  defines the components and services contained in the PAR, including the initial configuration and the parameters that can be modified by administrators and users. The descriptor also contains configuration information for the entire application.
    So considering the close relationship between java and xml,it makes sense to have the deployment descriptors, be it portalapp or ejb-jar.xml or any other deployment descriptor, as xml , as
    these parameters and sequence becomes rather unlikely to be maintained as a text file as there has always been a .

  • No option to create toplink-deployment-descriptor

    I originally started a TopLink project that allowed me to generate a toplink-deployment-descriptor.xml by right clicking on the project's mapping file.
    However, this option has recently been replaced with an option to generate toplink-ejb-jar.xml instead. There is no longer an option for toplink-deployment-descriptor.xml, yet the project will bomb if it's not there...
    Apparently the two files are the same thing (although one goes to META-INF and the other goes to a subfolder under META-INF) because if I rename toplink-ejb-jar.xml to toplink-deployment-descriptor.xml, the project runs fine.
    Can anyone explain why this is? I did add an EJB to the project (an MDB)... could that have messed something up?

    Adding an ejb, hence presence of an ejb-jar.xml, to the jdev project will cause this.
    This is a known issue and will be addressed in future releases.
    Hope this helps.

  • Error while deploying an application on weblogic 12c. An error occurred while reading the deployment descriptor. The error was: Error processing annotations

    Anyone please help me solve this error. I am trying to deploy an application on weblogic 12c  i am getting an error but the same application gets successfully deployed on weblogic 11g. The error is
    An error occurred during activation of changes, please see the log for details.
    Exception preparing module: EJBModule(gsCallbackAdapterLGTX-ejb.jar) An error occurred while reading the deployment descriptor. The error was: Error processing annotations: .
    [EJB:015001]Unable to link class com.aep.gridsmart.adapters.lgtx.buslogic.deliver.xform.AdapterTransfomerDeliverSession in Jar /appl/oracle/middleware/WLS/12.1.1.0/user_projects/domains/Gridsmart/servers/ManagedServer1/tmp/_WL_user/gsCallbackAdapterLGTX/34vz4d/gsCallbackAdapterLGTX-ejb.jar : java.lang.NoClassDefFoundError: com/aep/gridsmart/adapter/deliver/CommonAdapterDeliverBean

    Cotton please let me know what is the mistake i am
    doingThe following path does not exist.
    C:\Sun\AppServer7\domains\domain1\server1\
    applications\j2ee-modules\task_1\WEB-INF\web.xml

  • Deployment descriptor error for an EJB 3.0 entity bean module

    Hi all,
    i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
    The application is composed as follows:
    WASEnterprise.ear
    |-META-INF
    |-application.xml
    |-WAS.jar
    |-META-INF
    |-persistence.xml
    In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
    <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
    The persistence.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence>
    <persistence-unit name="CNT4">
    <non-jta-data-source>cnt5ds</non-jta-data-source>
    <class>it.eni.italgas.was.db.entity.AsiDisco</class>
    <class>it.eni.italgas.was.db.entity.AsiErrori</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
    <class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
    </persistence-unit>
    </persistence>
    and the application.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
    <display-name>WASEnterprise</display-name>
    <module id="myeclipse.1188512259959">
    <ejb>WAS.jar</ejb>
    </module>
    </application>
    I don't use any other weblogic specific deployment descriptor.
    Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
    Thanks inadvance.
    Denis Maggiorotto

    Hi all,
    i'm facing an error deploying an EJB 3.0 entity bean module wrapped in an enterprise application on WebLogic 10.
    The application is composed as follows:
    WASEnterprise.ear
    |-META-INF
    |-application.xml
    |-WAS.jar
    |-META-INF
    |-persistence.xml
    In other words the application server is unable to load persistence.xml deployment descriptor and,during deployment, it throws an error message like this:
    <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\bea\user_projects\domains\base_domain\autodeploy\WASEnterprise\WAS/META-INF/persistence.xml of module WAS. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed
    I suppose that the persistence.xml is correct since i can deploy the application on jboss without any problem.
    The persistence.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence>
    <persistence-unit name="CNT4">
    <non-jta-data-source>cnt5ds</non-jta-data-source>
    <class>it.eni.italgas.was.db.entity.AsiDisco</class>
    <class>it.eni.italgas.was.db.entity.AsiErrori</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRouting</class>
    <class>it.eni.italgas.was.db.entity.WasAsiRoutingId</class>
    <class>it.eni.italgas.was.db.entity.WasAsiSchemas</class>
    </persistence-unit>
    </persistence>
    and the application.xml deployment descriptor is:
    <?xml version="1.0" encoding="UTF-8"?>
    <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd">
    <display-name>WASEnterprise</display-name>
    <module id="myeclipse.1188512259959">
    <ejb>WAS.jar</ejb>
    </module>
    </application>
    I don't use any other weblogic specific deployment descriptor.
    Have you ever experienced such a strange behaviour? Can you suggest something to solve the problem?
    Thanks inadvance.
    Denis Maggiorotto

  • Challenges in deployment descriptors

    We currently have an EJB (called CD) that is contacted "remotely" by a web service
    (called CA) for some processing. The two (CD and CA) are deployed on different
    WLS8.1SP1 domains. CD is currently deployed as an EJB jar file (cd.jar) whereas
    CA is part of an EAR file and is deployed as an application. We ran into the necessity
    of making CD as part of EAR (much like CA). However, as part of the CA package,
    there is currently an initialization class (we're using a servlet) that saves
    some entries in JNDI for both CA and CD. We want to mimic the functionality of
    that class in CD when we create the ear for it.
    I just ran into some settings that could be made in the weblogic-application.xml
    deployment descriptor as follows:
    <startup-class>startup class name</startup-class>
    We're hoping this can help us mimic CA's init process. However, we need to pass
    that class some parameters upon load (which in the case of CA was done by using
    the <init-param> in its web.xml). We came across the following tag:
    <application-param>
         <param-name>someparam</param-name>
         </param-value>somevalue</param-value>
    </application-param
    However, we have the following questions:
    1. How do we make the startup class fetch those param values at load time? (for
    CA, the servlet was using the appPropLoc = getInitParameter("someparam") in its
    init method
    2. We needed to perform the remote lookup from CA to CD. Would enclosing CD in
    an EAR affect our ability to do so? If so, then how do we go about doing that?
    Thanks much,
    Sami

    Hi sami,
    Enclosing the EJB (CD) in an EAR file is not going to stop you from Remotely accessing
    it.
    As CD and CA are in different application package and moreover in different JVM,
    you have to package the interface classes as client jar with in CA for type casting.
    Joe
    "sami titi" <[email protected]> wrote:
    >
    We have resolved the first part of this problem by using a startup servlet
    much
    like we do in CA. However, we still face the issue of question number
    2 below.
    Please provide some feedback.
    Thanks,
    Samir
    "sami titi" <[email protected]> wrote:
    We currently have an EJB (called CD) that is contacted "remotely" by
    a web service
    (called CA) for some processing. The two (CD and CA) are deployed on
    different
    WLS8.1SP1 domains. CD is currently deployed as an EJB jar file (cd.jar)
    whereas
    CA is part of an EAR file and is deployed as an application. We raninto
    the necessity
    of making CD as part of EAR (much like CA). However, as part of the
    CA package,
    there is currently an initialization class (we're using a servlet) that
    saves
    some entries in JNDI for both CA and CD. We want to mimic the functionality
    of
    that class in CD when we create the ear for it.
    I just ran into some settings that could be made in the weblogic-application.xml
    deployment descriptor as follows:
    <startup-class>startup class name</startup-class>
    We're hoping this can help us mimic CA's init process. However, weneed
    to pass
    that class some parameters upon load (which in the case of CA was done
    by using
    the <init-param> in its web.xml). We came across the following tag:
    <application-param>
         <param-name>someparam</param-name>
         </param-value>somevalue</param-value>
    </application-param
    However, we have the following questions:
    1. How do we make the startup class fetch those param values at load
    time? (for
    CA, the servlet was using the appPropLoc = getInitParameter("someparam")
    in its
    init method
    2. We needed to perform the remote lookup from CA to CD. Would enclosing
    CD in
    an EAR affect our ability to do so? If so, then how do we go about doing
    that?
    Thanks much,
    Sami

  • How to edit deployment descriptor in weblogic 9.0?

    Hi ,
    I need to edit the values of certain environment variables mentioned in the deployment descriptor of a ejb module.
    In weblogic 7,its a straight forward method in which we have the option to edit the deployment descriptor in weblogic console.
    But I'm not sure how the same can be done in weblogic 9.0.
    Please guide me..!!! its urgent...
    Thanks,
    Smita

    If you want to edit the actual deployment descriptor (ie as a developer) than using any text editor or using an IDE like WebLogic Workshop/Eclipse etc would be the way to go.
    If you're trying to change values in an already deployed application, then configuration and tunables can be changed in the admin console. These write the changes to a separate file called a deployment plan. It allows you to change performance and environment settings without disturbing the original EAR file.
    -- Rob
    WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Maybe you are looking for

  • Make new custom tag in A2

    Good evening, I'm trying to add a custom tag to an image in Aperture 2.0. I've looked all over the internet and find no examples what so ever of AS and Aperture 2.0. I have a few guesses that produce one of two different errors - but no idea how to a

  • How do i defragment my hard drive

    Im new to Macs and i'm just wondering how you go about cleaning your computer up and defragging etc.

  • How set resultout for external java function

    Hi, i am working on workflow with java, any body know how to set resultout in java class in excute method (like return if that is custom look type) and my work flow making the status defferd even i am runing the background process. Thanks srinivas ch

  • After installing mountain lion facebook will not load on iMac

    Any helpers Please !!

  • Left - Right Balance

    I run iTunes with an external sound card (actually Tascam 428 surface controller), on which two active monitors. So I cannot fine tune the left-right balance with the system pref panel for sound, because it's not in use. The software controlling audi