XMLBeans / Xquery with Workshop 9.2

Hi there,
We're developing an app in workshop 9.2 that's using xmlbeans and xquery. According to what we've read, weblogic 9.2 supports both and we don't need to add any additional libraries. However, we're getting the follwoing exception:
java.lang.RuntimeException: No query engine found
at org.apache.xmlbeans.impl.store.Query.getCompiledQuery(Query.java:120)
at org.apache.xmlbeans.impl.store.Query.getCompiledQuery(Query.java:53)
at org.apache.xmlbeans.impl.store.Query.objectExecQuery(Query.java:43)
at org.apache.xmlbeans.impl.store.Xobj.exec_query(Xobj.java:2503)
at org.apache.xmlbeans.impl.values.XmlObjectBase.execQuery(XmlObjectBase.java:480)
at org.apache.xmlbeans.impl.values.XmlObjectBase.execQuery(XmlObjectBase.java:462)
at domain.RecFileManager.fillRuleSetActionMappings(RecFileManager.java:346)
at domain.RecFileManager.getRuleSets(RecFileManager.java:175)
at Controller.selectVersion(Controller.java:110)
at jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Object ;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
        at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)Ljava.lang.Object;(Unknown Source)
        at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:869)
        at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:808)
        at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:477)
        at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:305)
        at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:335)
        at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:51)
        at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:419)
        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:95)
        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2042)
        at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:90)
        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2114)
        at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:224)
        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:554)
        at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:851)
        at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:630)
        at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:157)
        at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
Can anybody point us in the right direction to fix this?
Thxs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

To enable XQuery you need to make sure some jars are on the server classpath. The Jars:
xquery.jar
binxml.jar
wlxbean.jar
apachexmlbeansutil.jar
xqrl.jar;
can be added to the classpath easily by setting an environment variable or changing one of the domain start scripts to something like:
set
POST_CLASSPATH=%POST_CLASSPATH%;%DATABASE_CLASSPATH%;%ARDIR%\xquery.jar;%ARDIR%\binxml.jar;%ARDIR%\wlxbean.jar;%ARDIR%\apachexmlbeansutil.jar;%ARDIR%\xqrl.jar;"
Hope this helps, let us know if you continue to have any problems,
-jacobd

Similar Messages

  • Unable to start WLS8.1sp4 after extended with Workshop& Integration Templat

    Hi,
    I have configured three domains of WLS8.1sp4 on
    unique ports namely 6001, 7001 & 8001 but
    only one domain can be started on the port 7001
    but there is a problem starting the other ports.
    All the three domains WLS were able to be started
    without any problem at all before the domains
    were being extended with Workshop and Integration
    Templates from the Basic Weblogic Server Domain
    in the Weblogic Configuration using the built-in Configuratino Wizard.
    Could someone please assist ?
    ./startWebLogic.sh
    JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=:/dev_app/bea/weblogic81/server/lib/weblogic_knex_patch.jar:/dev_app/bea/weblogic81/common/lib/log4j.jar:/dev_app/bea/weblogic81/server/lib/debugging.jar:/dev_app/bea/weblogic81/server/lib/knex.jar:/dev_app/bea/weblogic81/javelin/lib/javelin.jar:/dev_app/bea/weblogic81/server/lib/wlw-lang.jar:/dev_app/bea/jdk142_05/lib/tools.jar:/dev_app/bea/weblogic81/server/lib/weblogic_sp.jar:/dev_app/bea/weblogic81/server/lib/weblogic.jar:/dev_app/bea/weblogic81/server/lib/ant/ant.jar:/dev_app/bea/jdk142_05/jre/lib/rt.jar:::/dev_app/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/dev_app/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/dev_app/bea/weblogic81/server/lib/webserviceclient.jar:/dev_app/bea/weblogic81/server/lib/webserviceclient+ssl.jar:/dev_app/bea/weblogic81/server/lib/xbean.jar:/dev_app/bea/weblogic81/server/lib/wlxbean.jar:/dev_app/bea/weblogic81/server/lib/xqrl.jar:/dev_app/bea/weblogic81/server/lib/netui/netui-compiler.jar:/dev_app/bea/weblogic81/server/lib/wli.jar:/dev_app/bea/weblogic81/server/lib/fop.jar:/dev_app/bea/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
    PATH=/dev_app/bea/weblogic81/server/bin:/dev_app/bea/jdk142_05/jre/bin:/dev_app/bea/jdk142_05/bin:/usr/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/dt/bin:/usr/platform/SUNW,Sun-Fire-480R/sbin:/opt/sun/bin::/opt/SUNWexplo/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    Error [125] in bind() call!
    err:: Address already in use
    Socket transport failed to init.
    Transport dt_socket failed to initialize, rc = -1.
    FATAL ERROR in native method: No transports initialized
    Starting WLS with line:
    /dev_app/bea/jdk142_05/bin/java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -Dplatform.home=/dev_app/bea/weblogic81 -Dwls.home=/dev_app/bea/weblogic81/server -Dwli.home=/dev_app/bea/weblogic81/integration -Dlog4j.configuration=file:/dev_app/bea/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=myserver -Djava.security.policy=/dev_app/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
    === Debugging ===
    This window is necessary for debugging code using WebLogic Workshop
    Error [125] in bind() call!
    err:: Address already in use
    Socket transport failed to init.
    Transport dt_socket failed to initialize, rc = -1.
    FATAL ERROR in native method: No transports initialized
    Stopping the Weblogic Workshop debugger...
    ERROR: Proxy already running...
    weblogic.debugging.comm.SocketCommException
    at weblogic.debugging.comm.SocketComm.accept(SocketComm.java:53)
    at weblogic.debugging.comm.ServerSocketComm.accept(ServerSocketComm.java:53)
    at weblogic.debugging.engine.ProxyThread.run(ProxyThread.java:81)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: java.io.InterruptedIOException: operation interrupted
    at java.net.PlainSocketImpl.socketAccept(Native Method)
    at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353)
    at java.net.ServerSocket.implAccept(ServerSocket.java:448)
    at java.net.ServerSocket.accept(ServerSocket.java:419)
    at weblogic.debugging.comm.SocketComm.accept(SocketComm.java:47)
    ... 3 more
    Debugger Stopped.
    Stopping Pointbase server...
    Pointbase server stopped.

    Problem solved since default ports 8453 & 9093 were occupied
    But behaviour on Windows for debug is different from Unix which requires unique potr althought windows still works.

  • Works only with Workshop

    Hi,
    I have done some updates which work fine with Workshop, but when I try to deploy the application, I get :
    Errors found in E:\upload_RE7\PortalApplication\Portail\WEB-INF\src\com\xxxxxxx\xxxxxx\common\Constants.java:
    Error at line 3 column 8:
    Description: Package com.bea.p13n.entitlements.common contains no member type of this name.
    Line 3 is import com.bea.p13n.entitlements.common.EntitlementConstants;
    And i can't find this class in any jar or directory, neither on my local server (which works) nor on my deploiement server...
    Can I get a jar which contains this class anywhere?
    Greetings.
    Edited by herge89 at 04/28/2008 5:18 AM
    PS : I'm using WLP 8.1.6
    Edited by herge89 at 04/28/2008 8:04 AM

    p13n_system.jar under weblogic/p13n/lib/platform/lib/p13n/p13n_system.jar
    regards
    deepak

  • RPC/SOAP-Encoded Web Service with Workshop

    Is there anyway to create a RPC/SOAP-Encoded Web Service with Workshop ? There is an "encoding" attribute in the autotype ant task but no corresponding properties in Workshop.

    Hi,
    Thanks for the reference.
    I have checked both in the wsdl and the Soap message,
    rpc property effectively means rpc/encoded. Now that
    would say that RPC/Literal is not supported ?
    Here are what the messages looks like with rpc and
    document properties
    Thanks all for making this clear.
    document wlw property = Document/Literal
    <SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <ns:getEmployeeResponse xmlns:ns="http://www.openuri.org/">
    <ns:getEmployeeResult xmlns:ns="http://www.openuri.org/">
    <ns:Address xmlns:ns="http://www.openuri.org/">
    <ns:City xmlns:ns="http://www.openuri.org/">Luxembourg</ns:City>
    <ns:Country xmlns:ns="http://www.openuri.org/">LU</ns:Country>
    <ns:Number xmlns:ns="http://www.openuri.org/">2</ns:Number>
    <ns:PostCode xmlns:ns="http://www.openuri.org/">1000</ns:PostCode>
    <ns:Street xmlns:ns="http://www.openuri.org/">Bld. Royal</ns:Street>
    </ns:Address>
    <ns:Age xmlns:ns="http://www.openuri.org/">20</ns:Age>
    <ns:Name xmlns:ns="http://www.openuri.org/">Dupont</ns:Name>
    <ns:FirstNames xmlns:ns="http://www.openuri.org/">
    <ns:String xmlns:ns="http://www.openuri.org/">Jean</ns:String>
    <ns:String xmlns:ns="http://www.openuri.org/">Jacques</ns:String>
    </ns:FirstNames>
    </ns:getEmployeeResult>
    </ns:getEmployeeResponse>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    rpc wlw property = RPC/Soap-Encoded
    <SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <SOAP-ENV:Body SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <ns:getEmployeeResponse xmlns:ns="http://www.openuri.org/">
    <getEmployeeResult xmlns:s="http://www.openuri.org/encodedTypes" xsi:type="s:Employee">
    <Address xsi:type="s:Address">
    <City xsi:type="xsd:string">Luxembourg</City>
    <Country xsi:type="xsd:string">LU</Country>
    <Number xsi:type="xsd:int">2</Number>
    <PostCode xsi:type="xsd:string">1000</PostCode>
    <Street xsi:type="xsd:string">Bld. Royal</Street>
    </Address>
    <Age xsi:type="xsd:int">20</Age>
    <Name xsi:type="xsd:string">Dupont</Name>
    <FirstNames SOAP-ENC:arrayType="xsd:string[2]" xsi:type="SOAP-ENC:Array">
    <String xsi:type="xsd:string">Jean</String>
    <String xsi:type="xsd:string">Jacques</String>
    </FirstNames>
    </getEmployeeResult>
    </ns:getEmployeeResponse>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Message was edited by phcollignon at Aug 27, 2004 2:54 AM

  • Source control with Workshop

    What is the best source control solution when working with Workshop?
    thanks,
    Chad

    We use CVSNT as server and Tortoise as Client and these can be integrated very easliy with workshop. Works well..Try out.:-)

  • Clearcase integration with workshop

    Hi,
    Has anyone done clearcase integration with workshop? Any pointers highly appreciated?
    TIA,
    Amit

    Check out the Visual Studio Source Control Provider at
    http://dev2dev.bea.com/codelibrary/code/vsscp.jsp
    Josh
    Amit Bhutra wrote:
    Hi,
    Has anyone done clearcase integration with workshop? Any pointers highly appreciated?
    TIA,
    Amit

  • Creating Singleton with Workshop

    I am trying to create a Singleton with Workshop and am having some difficulties. When I try to add the <singleton-service> element to the weblogic-application.xml deployment descriptor, I get a schema error because the element is not defined in the supplied schema location of http://www.bea.com/ns/weblogic/90/weblogic-application.xsd. If I change the location to http://www.bea.com/ns/weblogic/920/weblogic-application.xsd (note the change from "90" to "920"), then the <singleton-service> element is defined, but this schema has two subelements defined as <singleton-class> and <singleton-uri>. According to the documentation (and oddly enough the comments in the schema itself), these elements should be <class-name> and <name> respectively.
    There is a weblogic-application.xsd file located in a eclipse plugins folder under workshop that is the same as the old version without the <singleton-service> element. I am assuming that some eclipse builder uses this schema and may be causing the problem. I tried updating this file, but that just causes eclipse to crash on startup.
    Anyone have any ideas on how to get an EAR project with a singleton to build successfully in Workshop?

    Hi Vimala,
    I tried your example and got the deployment problem as well. I don't think the way you have your schema defined is correct. By putting xmlns:xls="http://www.bea.com/ns/weblogic/90", you are associating all tags that begin with "wls:" with that namespace. By specifying the schemas location for http://www.bea.com/ns/weblogic/920, you are telling it where it can find the "920" schema, but it is never stated where you find the "90" schema. This effectively turns off schema checking for the "90" namespace. By not putting "wls:" in front of singleton-service, you are putting it at the default namespace which is not defined. This all seems to make Eclipse happy because it cannot fully validate the document.
    I did find a jar file in the weblogic install that contains the schemas that weblogic uses internally. The jar file is at \beahome\weblogic92\server\lib\schema\weblogic-container-binding.jar. The schema for weblogic-application.xml is in this jar and is different from either the "90" or "920" schemas that is online. I believe this is why there is an error when you try to deploy your app. It must validate against this schema.
    I have found as long as I match this schema, I can just leave the schemaLocation out of my weblogic-application.xml file and get it to build and deploy. I do get problems reported by eclipse that I need to define library references because it is needed by dependent projects. I believe this is because internally eclipse has its own copy of the schema which predates the <singleton-service> element. The builder is trying to validate the document against this schema and is failing because of the <singleton-service> element, so it cannot find the <library-ref> elements that are in the document. I did not get the same problem with your example application and I haven't figured out why yet. Funny thing, I can make a change to some other file in the project and save and all the reported problems disappear.
    I believe using this work-around, I am able to get a good EAR file to build and deploy. It just seems that after I deploy and define my singleton using the admin console that nothing happens. I get no indications that the singleton is working or not in the logs. This did cause me to try a little experiment in that I configured a singleton service using the admin console to a singleton that did not exist. It acts identically to the one that did exist. No warnings or errors at all. I would hope that if I configured a singleton that I would get an error if weblogic could not start it.
    Thanks for your efforts. Let me know if you find out anything else,
    Jeff

  • Creating a WebService with Workshop on NT and deploying to UNIX

    Are there any problems with a webservice (created with Workshop on NT) being deployed(
    as an ear file) on a WL 7.0 instance? Does the instance have to be a Workshop
    type domain or not?

    Hello Ron,
    The EAR file generated on a Win NT machine, can be deployed on a Workshop
    enabled server running on a UNIX machine.
    Please refer to the link provided by Anurag for steps on Workshop enabling a
    WebLogic Domain.
    http://e-docs/workshop/docs70/help/guide/howdoi/howWLW-enableExistingWLSDoma
    in.html
    For information on supported platform please refer to the following URL.
    http://e-docs/platform/docs70/support/index.html
    Thanks
    Raj Alagumalai
    WebLogic Workshop Support
    "Anurag Pareek" <[email protected]> wrote in message
    news:[email protected]..
    Ron,
    A Workshop webservice EAR file should only be deployed on a Workshopenabled
    domain.
    Please refer the Workshop docs for 'How to Workshop enable an existing
    WebLogic Server domain', or 'How to create a new Workshop domain'.
    Let me know if you have further questions.
    Thanks,
    Anurag
    "Ron" <[email protected]> wrote in message
    news:3e8d9480$[email protected]..
    Are there any problems with a webservice (created with Workshop on NT)being deployed(
    as an ear file) on a WL 7.0 instance? Does the instance have to be aWorkshop
    type domain or not?

  • Xquery with bind variable in OSB

    Hi,
    I have requirement to read XML file in Xquery as bind variable but it's giving error. I have included this file in OSB proejct but i dont know how to point this out using bind variable. I tried to read file using fn:doc and given file name but it's giving error.
    Any pointer here..
    Thanks

    a few other threads :
    How to use fn:doc() in ALSB
    Re: OSB: How read file xml that is into project OSB
    Caching XML Variable in OSB
    things you need to look at :
    xquery files aren't customizable
    xquery files itself are cached, the fn:foc function will be executed every time again
    so if you don't use the xml for other things, i would just registrate it as xquery file with the xml in it
    or you could use the synchronous file adapter to retrieve the data from the file

  • Execution of xquery with sql prompt(oracle 11g)

    Hi All I am executing the following query with squl prompt:
    SELECT XMLQuery('xquery version "1.0"; (: :)
    declare default element namespace "eNodeB"; (: :)
    for $m in ora:tokenize('oracle~','~')
    return ($m)'
    RETURNING CONTENT) AS RESULT
    FROM DUAL;
    But its giving the following exception
    for $m in ora:tokenize('deepa~','~')
    ERROR at line 3:
    ORA-19109: RETURNING keyword expected
    2) With the below mentioned query
    SELECT XMLQuery('xquery version "1.0"; (: :)
    declare default element namespace "eNodeB"; (: :)
    for $x in $eNodeBRef/eNodeBFile/eNodeB/eNodeBTop[eNodeBTopIndex='1']
    for $m in ora:tokenize('eNodeBTopAttr1~','~')
    let $r:=$x/following-sibling::*[local-name(.)=$m]
    where (exists($x/*[local-name(.)=$m]) or exists($r))
    return (
    if(exists($r) and not(exists($x/*[local-name(.)=$m]))) then
    element{local-name($r)}{data($r)} else(), if(exists($x/*[local-na
    me(.)=$m])) then element{local-name($x/*[local-name(.)=$m])}{data($x/*[local-name(.)=$m])} else()' PASSING p.OBJECT_VALUE AS
    "eNodeBRef"
    RETURNING CONTENT) AS RESULT
    FROM A_ENODEB p
    WHERE
    existsNode(p.OBJECT_VALUE,
    '/eNodeBFile/fileHeader[@fileName="eNodeB_inst_1.xml"]') =1;
    its giving the below error while executing through sql prompt
    *for $x in $eNodeBRef/eNodeBFile/eNodeB/eNodeBTop[eNodeBTopIndex='1']
    ERROR at line 3:
    ORA-19109: RETURNING keyword expected*

    Login to SQL Developer as the SYS user for Getting Started tutorial

  • XQuery with recuesive function and instance of operation gives problem

    Hi,
    << Using Oracle 11g .06. release >>
    I have an Xquery that has recursive functions and "instance of" operation.
    I facing the following problem
    "error raised during evaluation: oracle.xquery.XQException: XPTY0004: It is a type error if, during the static analysis phase, an expression is found to have a static type that is not appropriate for the context in which the expression occurs, or during the dynamic evaluation phase, the dynamic type of a value does not match a required type as specified by the matching rules in 2.5.4 SequenceType Matching.
    Detail: empty sequence encountered where a sequence of length one is expected
    The same xQuery works on Berkely DB, Altova XML and Oxygen. I could able to figure out the problem in oracle, where i need an help from you people.
    The below is the XQuery Function
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    SELECT XMLQuery('xquery version "1.0";
    declare default element namespace "WiMax_CAPC_XML";(: :)
    declare namespace HHP="HHP";(: :)
    declare namespace AtomicXQuery="AtomicXQuery";(: :)
    declare function AtomicXQuery:filter-modifier($element as element(), $attribute-name as xs:string*) {
    element {node-name($element)}
    for $child in $element/node()
    return if ($child instance of element())
    then (("deepa instance"),$child,"45",name($child),$attribute-name,
    if($child/node() instance of element())
    then ("it is an instance of element")
    else($child),
    AtomicXQuery:filter-modifier($child, $attribute-name))
    else $child
    let $i:= ora:view("NECB")/node()/child::*[2]/HHP:HHP/HHP:hapNe/HHP:maxCageCount
    let $m:=element HHP:deepa {element HHP:deepa1 {"deepa1"}} return AtomicXQuery:filter-modifier($m,"modifier")'
    RETURNING CONTENT) AS RESULT
    FROM DUAL;
    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    The XML data is available in XMLType table NECB.
    The XMLData is as follows
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    <?xml version="1.0" encoding="UTF-8"?>
    <ConfigDataFile xmlns="WiMax_CAPC_XML" xmlns:HHP="HHP" xmlns:SWM="SWM" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <fileHeader cfgMinorVersion="0" cfgSavedMinorVersion="0" cfgVersion="0" fileFormatVersion="CAPC_I1" fileName="NECB.xml" fileType="necb" senderName="CNEOMI" swVersion="D00.00.01.05" vendorName="Motorola"/>
    <configData dnPrefix="String">
    <HHP:HHP>
    <HHP:hapNe>
    <HHP:maxCageCount>3</HHP:maxCageCount>
    <HHP:minLogLevel>1</HHP:minLogLevel>
    </HHP:hapNe>
    <HHP:hapCageTable>
    <HHP:hapCageEntry cageId="1">
    <HHP:numOfModems>1</HHP:numOfModems>
    <HHP:numOfBackupModems>1</HHP:numOfBackupModems>
    <HHP:hapCagemaxModemCount>1</HHP:hapCagemaxModemCount>
    <HHP:minModemLogLevel>1</HHP:minModemLogLevel>
    <HHP:hapModemTable>
    <HHP:hapModemEntry cageId="1" modemId="1">
    <HHP:maxServiceTypeCount>1</HHP:maxServiceTypeCount>
    <HHP:hapModemLogLevel>1</HHP:hapModemLogLevel>
    <HHP:maxBlackboxCount>1</HHP:maxBlackboxCount>
    <HHP:minBlackboxLogLevel>1</HHP:minBlackboxLogLevel>
    <HHP:hapBlackboxTable>
    <HHP:hapBlackboxEntry cageId="1" modemId="1" blackboxId="1">
    <HHP:hapBlackboxLogLevel>1</HHP:hapBlackboxLogLevel>
    </HHP:hapBlackboxEntry>
    </HHP:hapBlackboxTable>
    </HHP:hapModemEntry>
    </HHP:hapModemTable>
    </HHP:hapCageEntry>
    </HHP:hapCageTable>
    <HHP:serviceTypeTable>
    <HHP:serviceTypeEntry serviceTypeId="1">
    <HHP:priority>1</HHP:priority>
    <HHP:serviceTypemaxModemCount>1</HHP:serviceTypemaxModemCount>
    </HHP:serviceTypeEntry>
    </HHP:serviceTypeTable>
    <HHP:serviceMappingTable>
    <HHP:serviceMappingEntry cageId="1" modemId="1" serviceTypeId="1">
    </HHP:serviceMappingEntry>
    </HHP:serviceMappingTable>
    </HHP:HHP>
         <SWM:SWM>
    <SWM:wmanIfBsPagingGroupTable>
    <SWM:wmanIfBsPagingGroupEntry ifIndex="1" wmanIfBsPagingGroupIndex="1">
    <SWM:wmanIfBsPagingGroupId>1</SWM:wmanIfBsPagingGroupId>
    <SWM:wmanIfBsPagingControllerId>9</SWM:wmanIfBsPagingControllerId>
    <SWM:wmanIfBsPagingCycle>100</SWM:wmanIfBsPagingCycle>
    <SWM:wmanIfBsPagingOffset>1</SWM:wmanIfBsPagingOffset>
    <SWM:wmanIfBsPagingRetryCount>3</SWM:wmanIfBsPagingRetryCount>
    <SWM:wmanIfBsPagingBcastRetryCount>3</SWM:wmanIfBsPagingBcastRetryCount>
    <SWM:wmanIfBsPagingControllerAddress>aabbccddeeffaabbccddeeffaabbccddeeffaabbccddeeffaabbccddeeffaabb</SWM:wmanIfBsPagingControllerAddress>
    <SWM:wmanIfBsPagingControllerAddressType>1</SWM:wmanIfBsPagingControllerAddressType>
    <SWM:wmanIfBsPagingControllerAsnMmId>aabbccddeeff</SWM:wmanIfBsPagingControllerAsnMmId>
    </SWM:wmanIfBsPagingGroupEntry>
    </SWM:wmanIfBsPagingGroupTable>
    <SWM:wmanIfAsnMmTable>
    <SWM:wmanIfAsnMmEntry ifIndex="1">
    <SWM:wmanIfAsnMmId>AAffFFAAAAFF</SWM:wmanIfAsnMmId>
    <SWM:wmanIfAsnMmId/>
    </SWM:wmanIfAsnMmEntry>
    </SWM:wmanIfAsnMmTable>
    <SWM:wmanIfNeighborAsnMmTable>
    <SWM:wmanIfNeighborAsnMmEntry ifIndex="1" wmanIfNbrAsnMmId="AAffFFAAAAFFFFFF">
    <SWM:wmanIfNbrAsnMmAddress>AAffFFAAAAFFFFFF</SWM:wmanIfNbrAsnMmAddress>
    <SWM:wmanIfNbrAsnMmAddressType>1</SWM:wmanIfNbrAsnMmAddressType>
    <SWM:wmanIfNbrAsnMmControlSecurityProtocol>1</SWM:wmanIfNbrAsnMmControlSecurityProtocol>
    </SWM:wmanIfNeighborAsnMmEntry>
    </SWM:wmanIfNeighborAsnMmTable>
    </SWM:SWM>
    </configData>
    <fileFooter dateTime="2007-11-07T09:30:47.0Z" update="2007-11-07T09:30:47.0Z"/>
    </ConfigDataFile>
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    The expected output XML is as follows
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    <HHP:deepa xmlns="WiMax_CAPC_XML" xmlns:HHP="HHP">deepa instance<HHP:deepa1>deepa1</HHP:deepa1>45 HHP:deepa1 modifier<HHP:deepa1>deepa1</HHP:deepa1>
         <HHP:deepa1>deepa1</HHP:deepa1>
    </HHP:deepa>
    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    Thanks in advance!

    Ashwin,
    Please try it with 11.1.0.7 instead and let us know if it works.
    Regards,
    Geoff

  • Problem with WorkShop 3.2 when lanching tomcat

    hi!I met a problem with debugging projects in WorkShop.
    I'm using tomcat 5.5.17 in WorkShop studio 3.2.All my server configurations are default!When debugging,I just right clicked on the project and chose "debug on server",then tomcat lanched.During that time,something weird happened.I found my project was deployed twice,and I also found that one was deployed as context "dms"(project's directory name),another as context "web"(project's real context).
    I tried all means to solve this problem.Finally I got one.I set two attributes of host tag to false from server.xml,deployOnStartup and autoDeploy.It works.But I don't think it is the best way.so my questions is: is this a workshop deploy bug?
    I guess it is.This is what I found from tomcat document.I think it may help us to slove this problem.
    "When using automatic deployment, the docBase defined by an XML Context file should be outside of the appBase directory. If this is not the case difficulties may be experienced deploying the web application or the application may be deployed twice.
    Finally, note that if you are defining contexts explicitly, you should probably turn off automatic application deployment. Otherwise, your context will be deployed twice each, and that may cause problems for your app. "
    Maybe workshop should use the web context name as project directory name when deploying and do not define the context explicitly in server.xml.

    hi, I just do the same thing as you do!The problem still exists!
    if you go to Tomcat Web Application Manager page and have a look at the applications you deployed. You will find your project is deployed twice with two different context(context root and project directory name as context root).
    note:if you don't have access to the manager page,you can try the following:
    -edit the settings for the server
    -find 'Run modules directly from the workspace(do not modify the Tomcat installation)' setting and uncheck the checkbox before it
    -then save your changes.
    Doing this you can deploy your project directly to the appbase of your tomcat server directory.Then you will have access to the manager page with the url "http://localhost:8080/manager/html".
    Also you may take a closer look at the output of your workshop console,you will find some output messages duplicated.
    This problem originally starts from workshop 3.1.There is no such issue before 3.0 and lower versions.
    Workshop studio was once an fatastic tool.But after integrated with WTP things have been changed.The biggest trouble is it costs too much memory.and some import features such as AJAX support,javascript debugger aren't available to us.I feel a little disappointed.:(
    Hope you guys will fix those defects.
    Regards!

  • Cannot use Spring 2.0 final with Workshop Studio 3.2_569

    It seems to be impossible to use Spring 2.0 final with the latest Studio. When attempting to define an alternate Spring library (the Studio download is still a CR release), you'll receive an error dialog complaining about a missing OJB jar file from the Spring distribution.
    This jar file is missing, but on purpose--it appears that with the 2.0 final release, support for Apache OJB was removed from the main Spring distribution and moved to the Spring modules project.
    Any chance we'll get a Studio update to resolve this issue, or provide a final Spring 2.0 version download within Workshop?

    The BEA Workshop release 3.2 & 3.2.1 (build 569 & 589 respectively), does not bundle Spring 2.0 final and is also not aware of this release.
    However, this should not stop you from manually importing the Spring 2.0 libraries into Workshop.
    Preferences | Workshop Studio Facet Libraries | Spring Library is used by the "New Web app" and "Project Facet" wizard to import the libraries on creation. Instead you can manually copy/overwrite Spring 2.0 libraries in your existing project.We will keep you posted on the Spring 2.0 support release.

  • OSB 10gr3 XQuery with CDATA - how to best do this?

    Hi There,
    I am writing an XQuery function to transform from one schema to another. My target schema has an attribute that is a string (xs:string), but the related protocol uses is for embedding another XML schema. Therefore I would like to treat the embedded value as an XML document using the CDATA command. I have tried using fn:concat and fn-bea:serialize but they do not work. There was an older thread :
    Returning CDATA using XQuery in ALSB
    in which the fn:inline is suggested, but this is not a valid function in the OSB10gR3 version.
    Can somebody provide me with an idea about how to use CDATA in an xquery ? Here is an example of the non-working fn:concat implementation:
    <ns0:abcRequest>
    <ns0:abcRequest>
    {fn:concat("<![CDATA[") }
    { $abcMessage/@* , $abcMessage/node() }
    {fn:concat("]]>") }
    </ns0:abcRequest>
    <ns0:abcEgmId>{ xs:string( $abcEgmId ) }</ns0:abcEgmId>
    <ns0:abcHostId>{ xs:int( $abcHostId ) }</ns0:abcHostId>
    </ns0:abcRequest>
    Any ideas for OSB 10g R3 would be much appreciated.
    Thanks,
    David.

    Hi Anuj,
    The serialize function does not escape the contents properly. It converts ">" to "Ambersand-G-T-Semicolon" (I had to spell them out since this forum had converted the characters back to the greater than symbol). I need to have the embedded CDATA and XML document untouched for subsequent processing on the side of the SOAP Provider (which I have no control over).
    So I want to achieve:
    <xmlElement>
    <innerElement><![CDATA[<myEmbeddedXML><nextedElement>....</myEmbeddedXML></nextedElement>]]>
    </xmlElement>
    Does this make sense ?
    Thanks,
    David.
    Edited by: user10313579 on Oct 27, 2010 9:30 PM

  • Ant with Workshop

    When I exported ant build script out of workshop (it creates exported_build.xml),
    and run the same script at command line I am getting the following error:
    UNCAUGHT EXCEPTION IN JAVELIN COMPILER!
    File a pri-1 bug on knex-compilerthread: Exclusive Thread error: com/bea/xml/marshall/SchemaTypeBuilder
    stack: java.lang.NoClassDefFoundError: com/bea/xml/marshal/SchemaTypeBuilder
    Any help is greatly appreciated.
    Thanks, Prasad

    The normal "exported_build.xml" file has two hardcoded paths, one for "weblogic.home", and one for "app.dir". If either one of these is invalid when checked out by CruiseControl, then the build will fail. From what you describe, it sounds like the "weblogic.home" value is invalid.
    Noting this, I set up a build process in a "build.xml" script that generates a "transformed_build.xml" file from an XSLT stylesheet, which replaces the "weblogic.home" value with the value of "env.BEA_HOME", and replaces "app.dir" with ".". The "build.xml" then runs the "build" target from the "transformed_build.xml" file.

Maybe you are looking for