Framework Configuration Registry Web Framework

Table 58. Task Attributes Required Description Attribute yes Unique string used to call a task from controls or directly using http URL; the URI must start with a forward slash character. URI no task description to be displayed, for example as page title caption yes Name of task root component component Table 59. Subelement Required Description Element no Additional parameters to be passed to the root component; each parameter is specified as name-value pair. param Data Type Contains the definition of the data types. Table 60. Data Type Attributes Required Description Attribute yes Unique name of the data type; this name is used to reference a data type, for example from the syswf:input tag. typeName yes Name of data type implementation class className Page 558 Data Type Other Configuration Table 61. Configuration Elements Description Element First part of the URL used to access Oracle Service Registry without encryption plain HTTP; this part should contain the http protocol prefix, hostname, and port. url First part of the URL used to access Oracle Service Registry using encryption. This part should contain https protocol prefix, hostname and port. secureUrl Context part of the URL, used to access Oracle Service Registry tasks; the default value is uddiweb for standalone registries and registryuddiweb for registries ported to an application server. context Context part of the URL, used to access Oracle Service Registrys static content, for example, images and cascading style sheets. The default value is uddiwebdata for standalone registries and registryuddiwebdata for registries ported to an application server. dataContext Default timeout of server-side sessions measured in seconds. serverSessionTimeout Directory used to store temporary files during the upload process; this path should be relative to service context directory. uploadTempDir Maximum size of uploaded files; larger files are rejected. maxUploadSize Directory with JSP pages; the path should be relative to service context directory. jspDir Contains JSP engine initialization parameters and the compilation classpath. A complete list of available Jasper initialization parameters can be found below. jspEngine Page 559 Other Configuration Jasper Configuration Table 62. Jasper init Configuration Parameters Description Default value Parameter name If the development parameter is false and reloading parameter is true, background compiles are enabled. checkInterval is the time in seconds between checks to see if a JSP page needs to be recompiled. 300 checkInterval Which compiler Ant should be used to compile JSP pages. See the Ant documentation for more information. javac compiler Indicates whether the class file should be compiled with debugging information true classdebuginfo Indicates whether Jasper is used in development mode; checks for JSP modification on every access. true development Determines whether tag handler pooling is enabled true enablePooling The class-id value sent to Internet Explorer when using jsp:plugin tags. clsid:8AD9C840-044E-11D1- B3E9-00805F499D93 ieClassId Tells Ant to fork compiles of JSP pages so that a separate JVM is used for JSP page compiles from the JVM in which Tomcat is running. true fork Java file encoding to use for generating java source files. UTF8 javaEncoding Indicates whether generated Java source code for each page is kept or deleted. true keepgenerated The level of detailed messages to be produced by this servlet. Increasing levels cause the generation of more messages. Valid values are FATAL, ERROR, WARNING, INFORMATION, and DEBUG. WARNING logVerbosityLevel Indicates whether the static content is generated with one print statement per input line, to ease debugging. false mappedfile Indicates whether Jasper checks for modified JSPs. true reloading

3.7.4. syswf JSP tag library

A JSP page using the syswf tag library must include this header taglib prefix=syswf uri=http:systinet.comjspsyswf syswf:component Includes the component with specified parameters. Table 63. syswf:component Attributes Required Description Attribute yes All parameter names in component will be prefixed with this prefix; the prefix must be unique within each JSP page. prefix yes Name of component, as written in the config file. name Page 560 syswf:component Table 64. syswf:component Subelements Required Description Element optional When this parameter value is passed into a component, it will be accessible in the request scope in the component Java class and in the JSP page. param The value of the parameter should be specified in two ways: As a value attribute or as a content of the value tag. Example 19. Component Parameters syswf:component prefix=names name=nameList syswf:param name=color1 value=white syswf:param name=color2blacksyswf:param syswf:component syswf:page Creates an HTML page form with all required internal fields. This must be the root element of all components used as tasks. Table 65. syswf:page Attributes Required Description Attribute yes The filename of the JSP page containing the page header, this file is designed to create elements required for framework functionality. Note that there should be no graphic design. headerTemplate yes The filename of the JSP page containing the page footer, this file is designed to create elements required for framework functionality. Note that there should be no graphic design. footerTemplate syswf:wrap This tag helps you to separate page functionality from its design. It includes specified header and footer templates before and after the body element. Header and footer templates should be parametrized using syswf:param tags. Table 66. syswf:wrap Attributes Required Description Attribute no File name of JSP page containing the header. headerTemplate no File name of JSP page containing the footer. footerTemplate Table 67. syswf:wrap Subelements Required Description Element no When you pass the parameter value into a component, this parameter will be accessible in the request scope in the component Java class and JSP page. param Page 561 syswf:wrap