Ejbs in workshop

Hi, I'm developing some EJBs using workshop/ejbgen. I have an MDB working and now want to refer another local-ejb within it. Basically I have one application (top-level folder) in workshop with two EJB projects under it. One is the MDB and the other is a stateful session bean that I want to be invoked by the MDB. A couple of questions:
1) I attempted to use the ejbgen:ejb-local-ref tag as follows:
"* @ejbgen:ejb-local-ref link="anXMLParserUtil""
When I try to build the project I get an error message:
anMDB.java:21: [ejb-local-ref name = ejb/anXMLParserUtil link=anXMLParserUtil] must have either 'link' or all of 'name', 'type', 'home', 'remote|local' attributes specified.
However, when I look at the property editor and the ejbgen tags all I have set is link... so where is it getting this name attribute from???
2) More of a general workshop question really... if my two separate ejb projects both ahve the same package structure should they be able to see each others classes without having to import anything?
Thanks a lot for the help!!!

OK - so I decided to attempt a different approach while awaiting a response here. Originally, I had the MDB and the session EJB in two separate projects - therefore two separate .jar files being generated by workshop. I have since moved them both into the same project and was able to build and deploy my .ear to the server. However, now when I publish a message to the topic using a separate test program, the MDB throws an exception when executing the lookup:
public void ejbCreate()
try {
javax.naming.Context ic = new InitialContext();
xmlParser = (MyParserBeanLocalHome)ic.lookup("java:/comp/env/ejb/MyParserBean");
The error I get is:
javax.naming.NameNotFoundException: While trying to lookup /comp/env/ejb/MyParserBean in /app/ejb/MyJarFileContainingBothMDBandEJB.jar#SomeName.; remaining name /comp/env/ejb/MyParserBean
I googled and found a lot of instances of this problem but none of them had answers...
I'd greatly appreciate any feedback anyone can give me.
Thanks.

Similar Messages

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

  • Creating Web Services From EJBs In WorkShop

    Is there a way to create webservices by exposing local stateless session jbs from
    within Workshop 8.1? I have read BEA documentation that states that you should
    use the ant task to do this. I find this rather inconvenient that I had to run
    an additional ant build file outside of the one generated by Workshop (along with
    another ant script I had to write in order to get javadocs to look somewhat readable
    by excluding the weblogic generated classes.)
    What is the best solution path to take when I want to expose a few stateless session
    ejbs via webservices for a .NET client application?

    You're right. More expert them I am I guess. :) I should have gone through the
    workshop help guide in more detail.
    Thanks
    Pete <[email protected]> wrote:
    I may have misunderstood as I'm not an expert, but don't you just
    create an ejb control in workshop, which exposes the methods in the
    ejb. Then that ejb control can be dropped into the web service?
    Pete

  • Why JavaControls are not supported in EJBs?

    It's weird that JCs cannot be used in EJBs in Workshop? Is there any good reason
    why is it so?
    Thank you,
    Miklos

    Ask Apple to include that font: http://www.apple.com/feedback/ipodnano.html

  • Error during JNDI lookup Accessing Remote EJB (access to web service restricted using declarative security model)

    Hello everyone,
    I developed a Web Service prototype accessing remote EJB using the EJB
    control with special syntax in the jndi-name attribute: @jws:ejb
    home-jndi-name="t3://10.10.245.70:7131/AccountDelegatorEJB"
    Everything works fine, but I get an error when I restrict access to my web
    service with a declarative security model by implementing steps provided in
    help doc:
    - Define the web resource you wish to protect
    - Define which security role is required to access the web resource
    - Define which users are granted the required security role
    - Configure WebLogic Server security for my web service(Compatibility
    Security/Users)
    I launch the service by entering the address in a web browser. When prompted
    to accept the digital certificate, click Yes, when prompted for network
    authentication information, enter username and password, navigate to the
    Test Form tab of Test View, invoke the method by clicking the button and I
    get the following exception:
    <error>
    <faultcode>JWSError</faultcode>
    <faultstring>Error during JNDI lookup from
    jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed for
    name:t3://10.10.245.70:7131/AccountDelegatorEJB]</faultstring>
    <detail>
    <jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
    lookup from jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed
    for name:t3://10.10.245.70:7131/AccountDelegatorEJB] at
    weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
    8) at
    weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
    .java:220) at
    weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
    ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
    ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64) </jwErrorDetail>
    </detail>
    </error>
    I have a simple Hello method as well in my WebService (which is also
    restricted) and it works fine, but remote EJB access doesn't. I tested my
    prototype on Weblogic 7.2 and 8.1 platforms - same result.
    Is that a bug or I am missing some additional configuration in order to get
    that working. Has anyone seen similar behavior? Is there a known resolution?
    Or a suggested way to work around the problem?
    Thank you.
    Andre

    Andre,
    It would be best if this issue is handled as an Eval Support case. Please
    BEA Customer Support at http://support.beasys.com along with the required
    files, and request that an Eval support case be created for this issue.
    Thanks
    Raj Alagumalai
    WebLogic Workshop Support
    "Andre Shergin" <[email protected]> wrote in message
    news:[email protected]...
    Anurag,
    I removed "t3", still get an error but a different one (Unable to create
    InitialContext:null):
    <error>
    <faultcode>JWSError</faultcode>
    <faultstring>Error during JNDI lookup from
    jndi://secuser1:[email protected]:7131/AccountDelegatorEJB[Unable to
    create InitialContext:null]</faultstring>
    <detail>
    <jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
    lookup from
    jndi://secuser1:[email protected]:7131/AccountDelegatorEJB[Unable to
    create InitialContext:null] at
    weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
    8) at
    weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
    .java:220) at
    weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
    ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
    ibas.GetVisaHistoryTransactions.getVisaHistoryTxn(GetVisaHistoryTransactions
    .jws:67) </jwErrorDetail>
    </detail>
    </error>
    Note: inter-domain communication is configured properly. The Web Service to
    remote EJB works fine without a declarative security.
    Any other ideas?
    Thank you for your help.
    Andre
    "Anurag" <[email protected]> wrote in message
    news:[email protected]...
    Andre,
    It seems you are using the URL
    jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB
    whereas you should not be specifying the "t3:" protocol.
    The URL should be like
    jndi://secuser1:[email protected]:7131/AccountDelegatorEJB
    Please do let me know if you see any issues with this.
    Note that this will only allow you to access remote EJBs in the same WLS
    domain. For accessing EJBs on another domain, you need to configure
    inter-domain communication by
    following a few simple steps as mentioned at
    http://e-docs.bea.com/wls/docs81/ConsoleHelp/jta.html#1106135. This link has
    been provided in the EJB Control Workshop documentation.
    Regards,
    Anurag
    "Andre Shergin" <[email protected]> wrote in message
    news:[email protected]...
    Raj,
    I tried that before, it didn't help. I got similar error message:
    <error>
    <faultcode>JWSError</faultcode>
    <faultstring>Error during JNDI lookup from
    jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB[Lookup
    failed for
    name:t3://secuser1:[email protected]:7131/AccountDelegatorEJB]</faultstr
    ing>
    <detail>
    <jwErrorDetail> weblogic.jws.control.ControlException: Error during JNDI
    lookup from
    jndi:t3://secuser1:[email protected]:7131/AccountDelegatorEJB[Lookup
    failed for
    name:t3://secuser1:[email protected]:7131/AccountDelegatorEJB] at
    weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
    8) at
    weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
    .java:220) at
    weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260) at
    ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
    ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64) </jwErrorDetail>
    </detail>
    </error>
    Anything else should I try?
    P.S. AccountDelegatorEJB, the remote EJB my Web Service calls is NOTaccess
    restricted.
    I hope there is a solution.
    Thanks,
    Andre
    "Raj Alagumalai" <[email protected]> wrote in message
    news:[email protected]...
    Andre,
    Can you try using the following url with username and password
    jndi://username:password@host:7001/my.resource.jndi.object ?
    once you add webapp level security, the authenticated is the user who
    invokes the EJB.
    http://e-docs.bea.com/workshop/docs81/doc/en/workshop/guide/controls/ejb/con
    CreatingANewEJBControl.html?skipReload=true
    has more info on using remote EJB's.
    Hope this helps.
    Thanks
    Raj Alagumalai
    WebLogic Workshop Support
    "Alla Resnik" <[email protected]> wrote in message
    news:[email protected]...
    Hello everyone,
    I developed a Web Service prototype accessing remote EJB using the EJB
    control with special syntax in the jndi-name attribute: @jws:ejb
    home-jndi-name="t3://10.10.245.70:7131/AccountDelegatorEJB"
    Everything works fine, but I get an error when I restrict access to my
    web
    service with a declarative security model by implementing steps
    provided
    in
    help doc:
    - Define the web resource you wish to protect
    - Define which security role is required to access the web resource
    - Define which users are granted the required security role
    - Configure WebLogic Server security for my web service(Compatibility
    Security/Users)
    I launch the service by entering the address in a web browser. Whenprompted
    to accept the digital certificate, click Yes, when prompted for
    network
    authentication information, enter username and password, navigate tothe
    Test Form tab of Test View, invoke the method by clicking the buttonand
    I
    get the following exception:
    <error>
    <faultcode>JWSError</faultcode>
    <faultstring>Error during JNDI lookup from
    jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookup failed for
    name:t3://10.10.245.70:7131/AccountDelegatorEJB]</faultstring>
    <detail>
    <jwErrorDetail> weblogic.jws.control.ControlException: Error during
    JNDI
    lookup from jndi:t3://10.10.245.70:7131/AccountDelegatorEJB[Lookupfailed
    for name:t3://10.10.245.70:7131/AccountDelegatorEJB] at
    weblogic.knex.control.EJBControlImpl.acquireResources(EJBControlImpl.java:27
    8) at
    weblogic.knex.context.JwsInternalContext.acquireResources(JwsInternalContext
    .java:220) at
    weblogic.knex.control.ControlHandler.invoke(ControlHandler.java:260)at
    ibas.AccountControl.getTransactionHistory(AccountControl.ctrl) at
    ibas.GetSecure.retrieveVisaHistoryTxn(GetSecure.jws:64)</jwErrorDetail>
    </detail>
    </error>
    I have a simple Hello method as well in my WebService (which is also
    restricted) and it works fine, but remote EJB access doesn't. I testedmy
    prototype on Weblogic 7.2 and 8.1 platforms - same result.
    Is that a bug or I am missing some additional configuration in order
    to
    get
    that working. Has anyone seen similar behavior? Is there a knownresolution?
    Or a suggested way to work around the problem?
    Thank you.
    Andre

  • Using a JMS control from an EJB project

    I'm developing an EJB in Workshop and my EJB is expected to send messages to a JMS queue. How can I use a JMS control (JCX) from my EJB?

    If you're talking about making an executable jar file that will work with the bouncycastle jar:
    (1) Make a jar as usual with your classes in it
    (2) Include a manifest file that specifies the class containing your app's main() method
    (3) In that same manifest, make sure that the bouncycastle jar is included in the Class-Path
    Details are in Sun's Tutorial: [Packaging Programs in JAR Files|http://java.sun.com/docs/books/tutorial/deployment/jar/index.html] and specifically [http://java.sun.com/docs/books/tutorial/deployment/jar/downman.html|http://java.sun.com/docs/books/tutorial/deployment/jar/downman.html] for the business of having your app recognise the other jar file's classes at runtime.
    Doubtless this can all be done from the comfort of your IDE, but I don't know how. There will be documentation on NetBeans site I suppose.
    Edited by: pbrockway2 on Jul 23, 2008 8:59 PM

  • Using external interface for ejbs in WLWS 8.1

    (Weblogic 8.1 / Workshop)
    Hi there,
    I need to create a session ejb within workshop, implementing externaly defined interface. How can this be done?
    greetings
    Heiner

    Hi,
    I am having same problem. Did you find any solution?.
    Thank You.

  • EJB control question

    Hello,
    To put it shortly, can I access remote EJBs from Workshop
    EJB control? For example, I have WLS 6.1 production cluster and
    separate WLS 7.0 webservice server. Now I want to access
    those 6.1 beans from 7.0 webservice EJB control. Is it possible?
    I used Workshop to create EJB controls and it seemed to me that
    Workshop only specifies JNDI names in JWS file, but no
    machine/port information ...
    best regards,
    Ago Meister

    have a kind of similar problem, deployed an SLSB with local home interface.
    Deployed SLSB with jndi name myapp/ejb/localSLSB. I checked that the SLSB
    is listed in the JNDI tree of the server but lookup with
    jndi://localhost:7001/myapp/ejb/localSLSB from EJB Ctrl failed.
    With username and password exposes another error:
    Error: jndi://usr@pwd:localhost:7001/myapp/ejb/localSLSB is not a valid JNDI
    URL[java.lang.NumberFormatException: localhost:7001]
    Torsten Friebe
    "Ago Meister" <[email protected]> schrieb im Newsbeitrag
    news:[email protected]..
    >
    I already solved problem, it is actually described
    in Workshop tutorial. To access remote EJBs, you
    have to use format
    jndi://username@password:host:7001/my.resource.jndi.object
    when accessing beans.
    bstrgds,
    Ago Meister
    "Ago Meister" <[email protected]> wrote:
    Hello,
    To put it shortly, can I access remote EJBs from Workshop
    EJB control? For example, I have WLS 6.1 production cluster and
    separate WLS 7.0 webservice server. Now I want to access
    those 6.1 beans from 7.0 webservice EJB control. Is it possible?
    I used Workshop to create EJB controls and it seemed to me that
    Workshop only specifies JNDI names in JWS file, but no
    machine/port information ...
    best regards,
    Ago Meister

  • Weblogic 10.0 error java.lang.NoClassDefFoundError:

    Hi,
    I am using weblogic 10.0 and trying to upload the EAR which is build using Weblogic Workshop 8.1 SP4. i am gettign the following error:
    ####<Feb 13, 2010 2:36:48 AM IST> <Error> <Deployer> <STPLT1005> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1266008808529> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1266008804528' for task '0'. Error is: 'java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/AsyncDispatcherBean : weblogic/ejb20/interfaces/JmsMessageDrivenBean'
    java.lang.NoClassDefFoundError: com/bea/wlw/runtime/core/bean/AsyncDispatcherBean : weblogic/ejb20/interfaces/JmsMessageDrivenBean
         at java.lang.ClassLoader.defineClass1(Native Method)
         at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
         at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
         at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
         at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
         at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)

    Hello,
    I have not seen this particular error before, but if you can re-build the EJB using Workshop 10.0 I bet it will fix your problem. The old Workshop is running an old version of appc which the 10.0 version of WLS is probably not expecting.
    Kevin

  • Issue while upgrading weblogic portal 8.1 to 9.2

    Hi All,
    I am upgrading my weblogic portal 8.1 application to 9.2. While following the process give at following link.
    http://download.oracle.com/docs/cd/E13214_01/wli/docs92/upgradetutorial/chap2.html
    I am getting following error in the update tab. Any suggestion would be greatful.
    weblogic.DDConverter failed to convert the EAR, weblogic-application.xml will not be
    upgraded :
    [DDConverter] START Converting EAR BEA[DDConverter] START Converting EJB-JAR
    .workshop/<App_name>/EJB/GenericStateless[DDConverter] END Converting EJB-JAR
    .workshop/<App_name>/EJB/GenericStateless[DDConverter] START Converting EJB-JAR
    content.jar[DDConverter] END Converting EJB-JAR content.jar[DDConverter] START Converting
    EJB-JAR content_repo.jar[DDConverter] END Converting EJB-JAR content_repo.jar[DDConverter]
    START Converting EJB-JAR netuix.jar[DDConverter] END Converting EJB-JAR
    netuix.jar[DDConverter] START Converting EJB-JAR p13n_ejb.jar[DDConverter] END Converting
    EJB-JAR p13n_ejb.jar[DDConverter] START Converting EJB-JAR prefs.jar[DDConverter] END
    Converting EJB-JAR prefs.jar[DDConverter] START Converting EJB-JAR wps.jar[DDConverter] END
    Converting EJB-JAR wps.jar[DDConverter] START Converting EJB-JAR
    .workshop/<App_name>/EJB/ProjectBeans[DDConverter] END Converting EJB-JAR
    .workshop/<App_name>/EJB/ProjectBeans[DDConverter] START Converting WAR
    adminPortal.war[DDConverter] END Converting WAR adminPortal.war[DDConverter] START
    Converting WAR datasync.war<May 4, 2010 5:16:20 PM PDT> <Info> <J2EE> <BEA-160192> <While
    upgrading weblogic.xml, encountered "debug" param "jsp-param". This param is unknown and
    will be removed> [DDConverter] END Converting WAR datasync.war[DDConverter] START Converting
    WAR wps-toolSupport.war[DDConverter] END Converting WAR wps-toolSupport.war[DDConverter]
    START Converting WAR <App_name><May 4, 2010 5:16:20 PM PDT> <Error> <J2EE> <BEA-160197>
    <Unable to load descriptor
    weblogic.application.ddconvert.ConvertCtx$VJarResourceLoader@b16f5f finder:
    weblogic.utils.classloaders.CodeGenClassFinder@106def2 annotation: /WEB-INF/web.xml of
    module null. The error is weblogic.descriptor.DescriptorException: Unmarshaller failed     at
    weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:147
    )     at
    weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)     at
    weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:248)     at
    weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(Abstra
    ctDescriptorLoader2.java:749)     at
    weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescr
    iptorLoader2.java:376)     at
    weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(Abst
    ractDescriptorLoader2.java:720)     at
    weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescrip
    torLoader2.java:729)     at
    weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:134)     at
    weblogic.application.ddconvert.WarConverter.convertDDs(WarConverter.java:60)     at
    weblogic.application.ddconvert.EarConverter.convertModules(EarConverter.java:125)     at
    weblogic.application.ddconvert.EarConverter.convertDDs(EarConverter.java:84)     at
    weblogic.application.ddconvert.DDConverter.runBody(DDConverter.java:157)     at
    weblogic.utils.compiler.Tool.run(Tool.java:158)     at
    weblogic.utils.compiler.Tool.run(Tool.java:115)     at
    weblogic.application.ddconvert.DDConverter.main(DDConverter.java:177)     at
    weblogic.DDConverter.main(DDConverter.java:10)Caused by: com.bea.xml.XmlException:
    weblogic.descriptor.BeanAlreadyExistsException: Bean already exists:
    "weblogic.j2ee.descriptor.ListenerBeanImpl@788e8862(/Listeners[com.bea.wlw.runtime.core.serv
    let.WebappContextListener])"     at
    com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:54)     
    at
    com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindin
    gType.java:483)     at
    com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollecti
    on(AttributeRuntimeBindingType.java:385)     at
    com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)     
    at
    com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(At
    tributeRuntimeBindingType.java:145)     at
    com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:185
    )     at
    com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:154)     
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)     at
    weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:136
    )     ... 15 moreCaused by: weblogic.descriptor.BeanAlreadyExistsException: Bean already
    exists:
    "weblogic.j2ee.descriptor.ListenerBeanImpl@788e8862(/Listeners[com.bea.wlw.runtime.core.serv
    let.WebappContextListener])"     at
    weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:207)     at
    weblogic.j2ee.descriptor.WebAppBeanImpl.setListeners(WebAppBeanImpl.java:965)     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:585)     at
    com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)     
    ... 23 more.> weblogic.application.ddconvert.DDConvertException:
    weblogic.descriptor.DescriptorException: Unmarshaller failed     at
    weblogic.application.ddconvert.WarConverter.convertDDs(WarConverter.java:79)     at
    weblogic.application.ddconvert.EarConverter.convertModules(EarConverter.java:125)     at
    weblogic.application.ddconvert.EarConverter.convertDDs(EarConverter.java:84)     at
    weblogic.application.ddconvert.DDConverter.runBody(DDConverter.java:157)     at
    weblogic.utils.compiler.Tool.run(Tool.java:158)     at
    weblogic.utils.compiler.Tool.run(Tool.java:115)     at
    weblogic.application.ddconvert.DDConverter.main(DDConverter.java:177)     at
    weblogic.DDConverter.main(DDConverter.java:10)Caused by:
    weblogic.descriptor.DescriptorException: Unmarshaller failed     at
    weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:147
    )     at
    weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:280)     at
    weblogic.descriptor.DescriptorManager.createDescriptor(DescriptorManager.java:248)     at
    weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(Abstra
    ctDescriptorLoader2.java:749)     at
    weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescr
    iptorLoader2.java:376)     at
    weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(Abst
    ractDescriptorLoader2.java:720)     at
    weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescrip
    torLoader2.java:729)     at
    weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescriptor.java:134)     at
    weblogic.application.ddconvert.WarConverter.convertDDs(WarConverter.java:60)     ... 7
    moreCaused by: com.bea.xml.XmlException: weblogic.descriptor.BeanAlreadyExistsException:
    Bean already exists:
    "weblogic.j2ee.descriptor.ListenerBeanImpl@788e8862(/Listeners[com.bea.wlw.runtime.core.serv
    let.WebappContextListener])"     at
    com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:54)     
    at
    com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindin
    gType.java:483)     at
    com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollecti
    on(AttributeRuntimeBindingType.java:385)     at
    com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)     
    at
    com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(At
    tributeRuntimeBindingType.java:145)     at
    com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:185
    )     at
    com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:154)     
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)     at
    weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:136
    )     ... 15 moreCaused by: weblogic.descriptor.BeanAlreadyExistsException: Bean already
    exists:
    "weblogic.j2ee.descriptor.ListenerBeanImpl@788e8862(/Listeners[com.bea.wlw.runtime.core.serv
    let.WebappContextListener])"     at
    weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:207)     at
    weblogic.j2ee.descriptor.WebAppBeanImpl.setListeners(WebAppBeanImpl.java:965)     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:585)     at
    com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)     
    ... 23 moreweblogic.descriptor.DescriptorException: Unmarshaller failed
    Thanks in advance.
    Regards,
    Sandeep K

    Hi,
    Upgrade report is giving me following warning. Is my above problem is due to this warning?
    The project <Application Name> references netui-pageflow.jar, which contains an 8.1 WLS XMLBean, com.bea.wlw.netui.pageflow.schema.webapp23.EjbLinkDocument. Regenerate the JAR to use Apache XMLBeans.
    If yes then how to resolve this issue. Any suggestion guys.
    Thanks in advance.
    Regards,
    SandeepK

  • Weblogic 10.0 webservice java to wsdl

    can i use JAXB annotations in my web service for which im using weblogic 10.0 to deploy the service.
    Does weblogic 10.0 supports JAXB annotations..

    Hello,
    I have not seen this particular error before, but if you can re-build the EJB using Workshop 10.0 I bet it will fix your problem. The old Workshop is running an old version of appc which the 10.0 version of WLS is probably not expecting.
    Kevin

  • Richfaces 4 and weblogic 10.0: error deploying

    When i tried to deploy an example application,
    I have this error:
    Unable to set the activation state to true for the application 'TestJSF'.
    weblogic.application.ModuleException:
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:975)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    javax.xml.bind.JAXBException: ClassCastException: attempting to cast jar:file:/C:/XXXXXXX/BEA_weblogic/modules/javax.xml.bind_2.0.jar!/javax/xml/bind/JAXBContext.class to zip:C:/XXXXXXX/BEA_weblogic/user_projects/domains/mare_domain/servers/AdminServer/tmp/_WL_user/TestJSF/96q78q/war/WEB-INF/lib/jaxb-api.jar!/javax/xml/bind/JAXBContext.class. Please make sure that you are specifying the proper ClassLoader.
    at javax.xml.bind.ContextFinder.handleClassCastException(ContextFinder.java:96)
    at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:214)
    at javax.xml.bind.ContextFinder.find(ContextFinder.java:372)
    at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
    at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)
    at javax.xml.bind.JAXB$Cache.<init>(JAXB.java:87)
    at javax.xml.bind.JAXB.getContext(JAXB.java:114)
    at javax.xml.bind.JAXB.unmarshal(JAXB.java:143)
    at org.richfaces.javascript.ClientServiceConfigParser.parse(ClientServiceConfigParser.java:60)
    at org.richfaces.javascript.ClientServiceConfigParser.parseConfig(ClientServiceConfigParser.java:49)
    at org.richfaces.application.ValidatorModule.createClientScriptService(ValidatorModule.java:68)
    at org.richfaces.application.ValidatorModule.configure(ValidatorModule.java:62)
    at org.richfaces.application.ServicesFactoryImpl.init(ServicesFactoryImpl.java:28)
    at org.richfaces.application.InitializationListener.createFactory(InitializationListener.java:136)
    at org.richfaces.application.InitializationListener.onStart(InitializationListener.java:110)
    at org.richfaces.application.InitializationListener.processEvent(InitializationListener.java:152)
    at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106)
    at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2129)
    at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2105)
    at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:300)
    at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:603)
    at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:369)
    at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225)
    at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:458)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:168)
    at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1744)
    at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909)
    at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973)
    at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
    at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
    at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
    at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
    at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
    at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
    at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
    at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
    at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
    at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
    at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
    at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
    at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    Note that i have create and example application:
    TestJSF:
    lib
    common-annotations.jar
    commons-beanutils.jar
    commons-collections.jar
    commons-digester.jar
    commons-logging.jar
    guava-r08.jar
    jaxb-api.jar
    jhighlight-1.0.jar
    jsf-api.jar
    jsf-impl.jar
    jstl.jar
    richfaces-components-api-4.0.0.Final.jar
    richfaces-components-ui-4.0.0.Final.jar
    richfaces-core-api-4.0.0.Final.jar
    richfaces-core-impl-4.0.0.Final.jar
    standard.jar
    NOTE: before adding richfaces4 jars, i had jsf-api and jsf-impl of jsf 2 anche into weblogic.xml i specify to prefere application lib so,
    I tested a greeting application so it work fine !!
    The step after, i added richeface4 jars, and the application server gave me that error.
    Please !!
    hellp me!!
    a

    Hello,
    I have not seen this particular error before, but if you can re-build the EJB using Workshop 10.0 I bet it will fix your problem. The old Workshop is running an old version of appc which the 10.0 version of WLS is probably not expecting.
    Kevin

  • ProcessControl invocation failed - Process not found

    I have built and deplyed a small integration application. When I try to test this
    application I get the following run-time error:
    [WLI-Core:530214]ProcessControl invocation failed[Service at /TestWeb/process/AddProcess.jpd
    not found]
    caused by: : com.bea.wlw.runtime.core.dispatcher.ServiceHandleException: Service
    at /TestWeb/process/AddProcess.jpd not found
    I am pretty sure that this process is deplyed on the server. I can see the following
    modules deployed in the WebLogic console:
    .workshop/TestWeb/EJB/AddProcess_54emdkdnnj
    .workshop/TestWeb/EJB/AddProcessControl_54emdkdnnj
    The JNDI tree also has entries for /TestWeb/process/AddProcess and /TestWeb/process/AddProcessControl.
    Any idea what is going on?
    Thanks.

    Well, I cannot reproduce the problem anymore. I don't know what changed!
    Steven Ostrowski <[email protected]> wrote:
    And does the WLI Console show AddProcess under the Process Instance Monitor?
    Naresh Bhatia wrote:
    I have built and deplyed a small integration application. When I tryto test this
    application I get the following run-time error:
    [WLI-Core:530214]ProcessControl invocation failed[Service at /TestWeb/process/AddProcess.jpd
    not found]
    caused by: : com.bea.wlw.runtime.core.dispatcher.ServiceHandleException:Service
    at /TestWeb/process/AddProcess.jpd not found
    I am pretty sure that this process is deplyed on the server. I cansee the following
    modules deployed in the WebLogic console:
    .workshop/TestWeb/EJB/AddProcess_54emdkdnnj
    .workshop/TestWeb/EJB/AddProcessControl_54emdkdnnj
    The JNDI tree also has entries for /TestWeb/process/AddProcess and/TestWeb/process/AddProcessControl.
    Any idea what is going on?
    Thanks.

  • How to develop EJB 3.0  Session Beans under WL Workshop 10.3?

    Hi there,
    I know the theory about EJB, no problem there, but I've been trying to develop some EJB's on WLW, and I'd like to ask you two things:
    1. Is there any guide to follow? I found this web page, but I feel it's not quite enough.
    2. How do you do to make code-completion working for the EJB (or any other) annotations? I write @javax. CTRL-Space and it starts completing, but it does not add the founded class to the class' imports.
    Thanks in advance for any tip!
    Andrés

    Hi,
    You may have better luck posting this question to the Workshop forum: Workshop
    - Matt

  • Publishing EJBs takes more time in Oracle Weblogic 10.3 workshop

    Hi,
    We recently migrated from Weblogic 9.2 to Oracle Weblogic 10.3 workshop.
    I have a ejb project which has more than 30 ejb's(both entity and session ejbs).
    The problem is: whenever I modify the code inside a method and save, it builds the project automatically. After that when I try to publish the module, it takes around 5 - 10 minutes for publishing.
    Points to note are : The ejb I am modifying has reference to other (10 - 20) ejbs. Hence it takes more time for even for single ejb change.
    however, when i modify an ejb which has no reference to ejb, takes less time to publish.
    My question is : is there a way to reduce the publishing time in this scenario.
    Thanks in advance!

    There is a special forum for Workshop issues:
    Workshop
    Try there.

Maybe you are looking for

  • Can not focus or edit on JTextField on SuSe Linux 9.1

    Hi, I am trying to debug a strange problem with JTextField on SuSe Linux 9.1. The problem is that the mouse click can not gain focus to the JTextField in a very high frequency. Once problem occurs, the keyboard tab also does not work. The problem doe

  • Macbook Late 2011 and Dell UltraSharp 29"

    Hi! I have a Macbook 13" Late 2011 and i'm about to buy a Dell UltraSharp 29" (http://www.pcmag.com/article2/0,2817,2414974,00.asp). I would like to know if my Macbook will be able to support the maximum resolution 2560x1080. Anyone knows if the Mini

  • HT6093 Thunderbolt firmware 1.2 - applied but not working

    I have tried to install the thunderbolt firmware 1.2 update. It said it succeeded but I still have blackout issues with my apple display and the firmware reported in the system report for my macbook pro is 23.4 instead of 26.2 (port micro version is

  • How to query objects on variable one-to-one relationship

    Hi, I have a situation here: Application (APPLICATION table) has many payoffs (Payoff table); Primary key of application is the foreign key of payoff. Payoff has disbursement, such as check(check table), directDeposit(directDeposit table) or Wire(wir

  • Uploading Photoshop CS5 and LR4 to new MacBook Pro

    I have LR4 and Photoshop CS5 on my old MacBook Pro. They were installed via a disc. And later I upgraded from LR3 to LR4. I have just bought a new MacBook Pro with no DVD player. I transferred my Adobe files to an external drive and uploaded them ont