IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Create and display error!

  • 1.  Create and display error!

    Posted Wed April 24, 2002 04:53 PM

    X-Application Version: 3.1.2
    Tamino Version : 3.1.1.1
    Platform : Win2k
    WebContainer : Tomcat 3.3.1
    JDK Version : 1.3.1

    Dear all

    The first page comes up wonderfull.
    If I put search the only one document displays ->ok. (tomcat 3.3.1 and 4.0.3)


    But if I put details, the folowing error occurs:
    In tomcat 3.3.1:

    Error message: 999: Application Error! Please contact the X-Application-Team.
    Help message: Please send a copy of the stack trace and of the error page to the development team in order to solve this problem immediately.
    Exception Type: ApplicationException
    Stacktrace:


    ApplicationException: 999: Application Error! Please contact the X-Application-Team.
    com.softwareag.xtools.xapplication.common.AssertionFailed
    sequence node '/Speditionsauftrag/xapp:occ(1)/xapp:seq(1) must return an element node with name ‘Nachrichtenfunktion’
    at com.softwareag.xtools.xapplication.businessdocument.Path.switchToNextElement(Path.java:327)
    at com.softwareag.xtools.xapplication.businessdocument.Path.walk(Path.java:236)
    at com.softwareag.xtools.xapplication.businessdocument.BusinessNodeImpl.getDescendant(BusinessNodeImpl.java:273)
    at com.softwareag.xtools.xapplication.jsp.taglib.ContextTag.getElementValue(ContextTag.java:225)
    at com.softwareag.xtools.xapplication.jsp.taglib.FieldTag.doStartTagCore(FieldTag.java:104)
    at com.softwareag.xtools.xapplication.jsp.JspTag.doStartTag(JspTag.java:120)
    at view_1._jspService(view_1.java:526)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java)
    at org.apache.tomcat.facade.ServletHandler.doService(ServletHandler.java:574)
    at org.apache.tomcat.core.Handler.invoke(Handler.java:322)
    at org.apache.tomcat.core.Handler.service(Handler.java:235)
    at org.apache.tomcat.facade.ServletHandler.service(ServletHandler.java:485)
    at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:917)
    at org.apache.tomcat.core.ContextManager.service(ContextManager.java:833)
    at org.apache.tomcat.modules.server.Http10Interceptor.processConnection(Http10Interceptor.java:176)
    at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:494)
    at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:516)
    at java.lang.Thread.run(Thread.java:484)

    ############################################

    If I put create, tomcat 3.3.1 crashs!

    ############################################


    If I put details on tomcat 4.0.3, the folowing error occurs:

    ApplicationException: 999: Application Error! Please contact the X-Application-Team.
    com.softwareag.xtools.xapplication.common.AssertionFailed
    sequence node '/Speditionsauftrag/xapp:occ(1)/xapp:seq(1) must return an element node with name ‘Nachrichtenfunktion’
    at com.softwareag.xtools.xapplication.businessdocument.Path.switchToNextElement(Path.java:327)
    at com.softwareag.xtools.xapplication.businessdocument.Path.walk(Path.java:236)
    at com.softwareag.xtools.xapplication.businessdocument.BusinessNodeImpl.getDescendant(BusinessNodeImpl.java:273)
    at com.softwareag.xtools.xapplication.jsp.taglib.ContextTag.getElementValue(ContextTag.java:225)
    at com.softwareag.xtools.xapplication.jsp.taglib.FieldTag.doStartTagCore(FieldTag.java:104)
    at com.softwareag.xtools.xapplication.jsp.JspTag.doStartTag(JspTag.java:120)
    at org.apache.jsp.view$jsp._jspService(view$jsp.java:322)
    at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
    at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
    at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
    at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
    at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
    at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012)
    at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
    at java.lang.Thread.run(Unknown Source)

    ############################################

    If I put create, tomcat 4.0.3 occours the same error above!

    Please help!
    I attached the schema to this message

    [This message was edited by Christian Freytag on 26 Jul 2002 at 09:42.]
    speditionsauftrag.tsd (12.9 KB)


    #Tamino
    #webMethods
    #API-Management


  • 2.  RE: Create and display error!

    Posted Fri April 26, 2002 04:13 PM

    Hello Marco,

    I changed the icon of your topic to ?Bug? since the path evaluation of X-Application for your schema produces an error.

    This error occurs if you have an optional field (in your case Nachrichtenfunktion?) is part of an sequence with multiplicity ( of ?Speditionsauftrag?).

    A workaround for this situation could be the introduction of another element for the anonymous sequence. I changed your schema and used ?Austragsposition? to define the sequence of the Speditionsauftrag.

    The advantage:


    • it works with X-Application.
    • the addressing of sequences via XPath is easier than before with regard to the element Nachrichtenfunktion. If you want to address the Nachrichtenfunktion of the third sequence, you have to know if the first and second sequence have an element Nachrichtenfunktion or you have to use XPath expressions with more complex navigation terms than ?/? .


    Nevertheless, we will try to fix the bug. If it is fixed we will make a post with the source code of classes which have to be replaced.

    Can you live with change within your schema or is it a customer schema which you cannot touch?

    Bye,
    Christian.
    speditionsauftrag_pos.tsd (13 KB)


    #Tamino
    #API-Management
    #webMethods


  • 3.  RE: Create and display error!

    Posted Fri July 26, 2002 01:16 PM

    the problem is solved for X-Application 3.1.3.


    #Tamino
    #API-Management
    #webMethods