Where is weblogic application.xml located

Specifies a SQL query that automatically runs when a connection is created. Controls whether a connection is removed from the pool when the application asks for the underlying vendor connection object. Enabling this attribute has an impact on performance; it essentially disables the pooling of connections as connections are removed from the pool and replaced with new connections. The following table describes the elements you can define within a driver-params element. Table A driver-params Elements.

Defines the driver-params statement. Contains the following optional element: profiling-enabled. Enables the running of JDBC prepared statement cache profiling. When enabled, prepared statement cache profiles are stored in external storage for further analysis.

This is a resource-consuming feature, so it is recommended that you turn it off on a production server. The cache-profiling-threshold element defines a number of statement requests after which the state of the prepared statement cache is logged.

This element minimizes the output volume. The cache-size element returns the size of the prepared statement cache. During SQL roundtrip profiling it is possible to store values of prepared statement parameters. The parameter-logging-enabled element enables the storing of statement parameters. This is a resource-consuming feature, so you should limit the length of data for a parameter to reduce the output volume.

When an external client accesses a database using JDBC through Weblogic Server, row prefetching improves performance by fetching multiple rows from the server to the client in one server access.

The optimal value depends on the particulars of the query. In general, increasing this number increases performance, until a particular value is reached. At that point further increases do not result in any significant increase in performance. Note: Typically you will not see any increase in performance after rows. The default value should be adequate for most situations.

Specifies the data chunk size for streaming data types, which are pulled from WebLogic Server to the client as needed. The following table describes the elements you can define within a security element. Table A security Elements. Names a security realm to be used by the application.

If none is specified, the system default realm is used. Declares a mapping between an application-wide security role and one or more WebLogic Server principals. The following table describes the elements you can define within a application-param element. Table A application-param Elements. The following table describes the elements you can define within a classloader-structure element.

Table A classloader-structure Elements. The following list describes the elements you can define within a module-ref element:. Allows for arbitrary nesting of classloader structures for an application. However, for this version of WebLogic Server, the depth is restricted to three levels. The following table describes the elements you can define within a listener element.

Table A listener Elements. If you do not specify the listener-uri , it is assumed that the class is visible to the application. Specific a user identity to startup and shutdown application lifecycle events. The identity specified here should be a valid user name in the system.

If run-as-principal-name is not specified, the deployment initiator user identity will be used as the run-as identity for the execution of the application lifecycle listener. Note: If the run-as-principal-name identity defined for the application lifecycle listener is an administrator, the application deployer must have administrator privileges; otherwise, deployment will fail. The following table describes the elements you can define within a singleton-service element. Table A singleton-service Elements.

If singleton-uri is not defined, then its assumed that the class is visible to the application. Application-scoped startup and shutdown classes have been deprecated as of release 9. Table A startup Elements. If startup-uri is not defined, then its assumed that the class is visible to the application.

The following table describes the elements you can define within a shutdown element. Table A shutdown Elements. If you do not define the shutdown-uri element, it is assumed that the class is visible to the application.

Table A work-manager Elements. Used to specify a Stuck Thread Work Manager component that can shut down the Work Manager in response to stuck threads. Specifies whether the Work Manager should ignore stuck threads and never shut down even if threads become stuck.

Table A session-descriptor Elements. Specifies the name of the cookie that holds the attribute name and values when using cookie -based session persistence. Specifies the name of the directory when using file -based session persistence.

The directory is relative to the temporary directory defined for the Web application. Specifies the name of the JDBC connection pool when using jdbc -based session persistence.

Required for certain databases that do not support long column names. Default value is true , which means that the header is NOT added. Set this element to false if you want the header added to the response. Used to tag runtime information for different sessions. For example, set this element to username if you have a username attribute that is guaranteed to be unique. The following table describes the elements you can define within a library-ref element.

Table A library Elements. Specifies whether there must be an exact match between the specification and implementation version that is specified and that of the referenced library.

The following table describes the elements you can define within a library-context-root-override element to override context-root elements within a referenced EAR library. See library-ref. Table A library-context-root-override Elements. Overrides the context-root elements declared in libraries. In the absence of this element, the library's context-root is used. Only a referencing application for example, a user application can override the context-root elements declared in its libraries.

Specifies the value of the library-context-root-override element when overriding the context-root elements declared in libraries. In the absence of these elements, the library's context-root is used. The following table describes the elements you can define within a fast-swap element. Table A fast-swap Elements. Subsequent HTTP requests arriving within the refresh-interval seconds will not trigger a check for changes.

The first HTTP request arriving after the refresh-interval seconds have passed, will cause FastSwap to perform a class-change check again. FastSwap class redefinitions are performed asynchronously by redefinition tasks.

They can be controlled and inspected using JMX interfaces. Specifies the number of redefinition tasks that will be retained by the FastSwap system. If the number of tasks exceeds this limit, older tasks are automatically removed. For more information about application. Table A-1 weblogic-application Elements Element Required?

Specifies an application-scoped JDBC connection pool. Used to register user-defined startup classes. Used to register user defined shutdown classes. This element has the following child elements: name —The name of the module. The name used in this example ejb1 is the ejb-ref-name defined in the ejb-ref element of the web. The ClasspathServlet is useful for applications that use applets or RMI clients and require access to server-side classes. The ClasspathServlet is implicitly registered and available from any application.

The ClasspathServlet is always enabled by default. In this case, the resource is located in the following directory, relative to the root of the Web application:. The class name for the CGIServlet is weblogic. You do not need to package this class in your Web application. Register the following initialization attributes for the CGIServlet by defining the following init-param elements:. If you do not specify cgiDir , the directory defaults to a directory named cgi-bin under the Web application root.

When scripts produce binary data, the stream may become corrupted due to character encoding. Use the useByteStream parameter to keep the stream from becoming corrupted. Using this parameter for ascii output also improves performance.

If the script does not require an executable, this initialization attribute may be omitted. The param-value contains the path to the interpreter or executable that runs the script. If any configuration information for an enterprise bean is not specified in the glassfish-ejb-jar. The sun-cmp-mappings. The glassfish-application-client. The sun-acc.

The glassfish-resources. GlassFish Server offers limited support for the weblogic-application. The only element in weblogic-application. The equivalent element in the glassfish-application. The elements of weblogic. The elements of weblogic-webservices. Ok, then i make a client project where i put the generated clienteBB. I make this project twice 1 communicates to a testMethod to test custom exception and the other one calling 2 method with structure data.

The problem is that when im running the project for the testMethod call in the WS all looks ok! But when i run the other project to call others method same web service i have a crash like this. Unknown Source at com. ClassCastException: com. XmlTokenImpl at weblogic. Apart from that i have few more questions here: 1. Are u using clientgen task to generate the Client Artifacts or some other similar tool. By any chance have u upgraded your webservice from any previous version of weblogic?

From My openion this kind of issues happens because of the Classpath Settings…If you are using the Same Jars in Both the Projects …though…it is always possible that…some of the Jar is getting loaded in a different order in the Classpath in another project.

So please try to manually edit the classpath build path as the Working project. I use JWSC task i tried to post the build.