Weblogic XML Registry and Entity Resolution

Hi,
I have configure Weblogic XML Registry as described in
http://e-docs.bea.com/wls/docs81/ConsoleHelp/xml.html. I have a directory
where my dtds reside (%WLDOMAIN%/xml/registries/MyRegistry/). I using JAXP
(the BEA recommended API which should automatically make use of the registry
for entity resolution). But somehow it seems that it is looking in the root
of the weblogic domain for the entities and not in the registry entities
directory.
A sample doctype in one of my doc looks like <!DOCTYPE substance_id PUBLIC
"-//CAS//DTD substance_id//EN" "substance_id.dtd">
The registry is configured as follows
Public ID System ID
Entity URI When To Cache Cache Timeout Interval
============================================================================
===============
-//CAS//ENTITY CMD Defined Entities//EN CMSents.dtd CMSents.dtd
defer-to-registry-setting -1
-//CAS//DTD control//EN control.dtd
control.dtd defer-to-registry-setting -1
-//CAS//DTD substance_id//EN substance_id.dtd
substance_id.dtd defer-to-registry-setting -1
Below is the exception from the server log. Any help would be greatly
appreaciated.
####<Dec 12, 2003 11:09:32 AM EST> <Debug> <org.cas.felix.util.XML>
<PC81227> <myserver> <ExecuteThread: '13' for queue:
'weblogic.kernel.Default'> <<anonymous>> <BEA1-0009897C74118C32D0F4>
<000000> <exception parsing document <?xml version="1.0"?>
<!DOCTYPE substance_id PUBLIC "-//CAS//DTD substance_id//EN"
"substance_id.dt ... (4869)
java.io.FileNotFoundException: D:\wls_domains\felix\substance_id.dtd (The
system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:6
9)
at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection
.java:156)
at java.net.URL.openStream(URL.java:960)
at
weblogic.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.ja
va:836)
at
weblogic.apache.xerces.impl.XMLEntityManager.startDTDEntity(XMLEntityManager
.java:796)
at
weblogic.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerIm
pl.java:275)
at
weblogic.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XM
LDocumentScannerImpl.java:841)
at
weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLD
ocumentFragmentScannerImpl.java:329)
at
weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:
525)
at
weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:
581)
at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at
weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.jav
a:1175)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:138)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
at org.cas.felix.util.XML.validate(XML.java:88)
at org.cas.felix.util.XML.validate(XML.java:69)
at org.cas.felix.si.master.MasterDocument.<init>(MasterDocument.java:94)
at org.cas.felix.si.master.MasterDocument.<init>(MasterDocument.java:139)
at
org.cas.felix.si.j2ee.processing.FelixSIProcessorBean.processRecord(Unknown
Source)
at org.cas.felix.si.j2ee.processing.FelixSIProcessorBean.onMessage(Unknown
Source)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:374)
at
weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:30
8)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:273)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2550)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2470)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)

Hi Brian,
In your config.xml, in the <XMLRegistry> section, what does the
EntityURI look like? I believe it should be a relative entry, something
like %WLDOMAIN%/xml/registries/MyRegistry
If this is not the issue, I would encourage you to provide this
information with your config.xml to our outstanding support team to
resolve this issue.
Thanks,
Bruce
Brian Sam-Bodden wrote:
>
Hi,
I have configure Weblogic XML Registry as described in
http://e-docs.bea.com/wls/docs81/ConsoleHelp/xml.html. I have a directory
where my dtds reside (%WLDOMAIN%/xml/registries/MyRegistry/). I using JAXP
(the BEA recommended API which should automatically make use of the registry
for entity resolution). But somehow it seems that it is looking in the root
of the weblogic domain for the entities and not in the registry entities
directory.
A sample doctype in one of my doc looks like <!DOCTYPE substance_id PUBLIC
"-//CAS//DTD substance_id//EN" "substance_id.dtd">
The registry is configured as follows
Public ID System ID
Entity URI When To Cache Cache Timeout Interval
============================================================================
===============
-//CAS//ENTITY CMD Defined Entities//EN CMSents.dtd CMSents.dtd
defer-to-registry-setting -1
-//CAS//DTD control//EN control.dtd
control.dtd defer-to-registry-setting -1
-//CAS//DTD substance_id//EN substance_id.dtd
substance_id.dtd defer-to-registry-setting -1
Below is the exception from the server log. Any help would be greatly
appreaciated.
####<Dec 12, 2003 11:09:32 AM EST> <Debug> <org.cas.felix.util.XML>
<PC81227> <myserver> <ExecuteThread: '13' for queue:
'weblogic.kernel.Default'> <<anonymous>> <BEA1-0009897C74118C32D0F4>
<000000> <exception parsing document <?xml version="1.0"?>
<!DOCTYPE substance_id PUBLIC "-//CAS//DTD substance_id//EN"
"substance_id.dt ... (4869)
java.io.FileNotFoundException: D:\wls_domains\felix\substance_id.dtd (The
system cannot find the file specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at
sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:6
9)
at
sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection
.java:156)
at java.net.URL.openStream(URL.java:960)
at
weblogic.apache.xerces.impl.XMLEntityManager.startEntity(XMLEntityManager.ja
va:836)
at
weblogic.apache.xerces.impl.XMLEntityManager.startDTDEntity(XMLEntityManager
.java:796)
at
weblogic.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(XMLDTDScannerIm
pl.java:275)
at
weblogic.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XM
LDocumentScannerImpl.java:841)
at
weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLD
ocumentFragmentScannerImpl.java:329)
at
weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:
525)
at
weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:
581)
at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at
weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.jav
a:1175)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:138)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)
at org.cas.felix.util.XML.validate(XML.java:88)
at org.cas.felix.util.XML.validate(XML.java:69)
at org.cas.felix.si.master.MasterDocument.<init>(MasterDocument.java:94)
at org.cas.felix.si.master.MasterDocument.<init>(MasterDocument.java:139)
at
org.cas.felix.si.j2ee.processing.FelixSIProcessorBean.processRecord(Unknown
Source)
at org.cas.felix.si.j2ee.processing.FelixSIProcessorBean.onMessage(Unknown
Source)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:374)
at
weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:30
8)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:273)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2550)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2470)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)

Similar Messages

ClassCastException: weblogic.xml.jaxp.WebLogicTransformerFactory

I am running Weblogic 6.1 on a Solaris 7 machine.
I have added the following runtime properties in my startWebLogic.sh to handle
Weblogic 6.1
transformation bugs.
-Djavax.xml.parsers.DocumentBuilderFactory=weblogic.xml.jaxp.WebLogicDocumentBuilderFactory
-Djavax.xml.transform.TransformerFactory=weblogic.xml.jaxp.WebLogicTransformerFactory
-Djavax.xml.parsers.SAXParserFactory=weblogic.xml.jaxp.WebLogicSAXParserFactory
After adding these parameters, my servlet (which is loaded on startup and creates
a Transformer
Template during its init function for future XSL transformations) was working
fine.
Now, however, I need to create an XML Registry in order to perform entity resolution.
When I created an XML Registry and entered the above values in the Registry, my
servlet now
throws the following exception:
java.lang.ClassCastException: weblogic.xml.jaxp.WebLogicTransformerFactory
at weblogic.xml.jaxp.RegistrySAXTransformerFactory.<init>(RegistrySAXTransformerFactory.java:48)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:237)
at javax.xml.transform.TransformerFactory.newInstance(TransformerFactory.java:119)
at com.nokia.imessage.AlertServlet.loadStylesheets(AlertServlet.java:549)
at com.nokia.imessage.AlertServlet.init(AlertServlet.java:59)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:698)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:641)
My XML Registry is the following:
<XMLRegistry
DocumentBuilderFactory="weblogic.xml.jaxp.WebLogicDocumentBuilderFactory"
Name="MyXMLRegistry"
SAXParserFactory="weblogic.xml.jaxp.WebLogicSAXParserFactory"
TransformerFactory="weblogic.xml.jaxp.WebLogicTransformerFactory"
WhenToCache="cache-on-reference">
<XMLEntitySpecRegistryEntry EntityURI="dtds/pap_1.0.dtd"
Name="XMLEntitySpecRegistryEntry-1000329224935"
PublicId="-//WAPFORUM//DTD PAP 1.0//EN"
SystemId="http://www.wapforum.org/DTD/pap_1.0.dtd" WhenToCache="cache-at-initialization"/>
</XMLRegistry>
Why do the runtime parameters work but the XML Registry (with the same information)
don't?
Am I doing something wrong or is there a solution/workaround for this problem?
Thank you!
Samantha

Hello,
I have the answer, thanks for BEAs customer support, there is a bug from WL
6.1, and it should be fixed with sp2 (scheduled for the middle of December).
So here is the answer from BEA:
-----------------answer-from-Gareth Chapman--------------------
When I tried the code you send I did not receive the ClassCastException but
a ClassNotFoundException, I think the root problem could be the same though.
There looks to be two parts of a bug that's stopping this code from working
correctly:
(CR 055082)
To work around the ClassNotFoundException (hopefully in your case the
ClassCastException) add this line of code before calling the
XSLTProcessorFactory.getProcessor():
System.setProperty("javax.xml.transform.TransformerFactory",
"weblogic.apache.xalan.processor.TransformerFactoryImpl");
Secondly I received the error:
SystemId Unknown; Line 0; Column 0; SystemId Unknown; Line 0; Column 0;
javax.xml.transform.TransformerException: SAX Exception
Which looks to be part of the same bug, in order to fix this you will need
to:
Extract org/apache/xalan/res/XSLTInfo.properties from
$WL_HOME/lib/weblogic.jar change the path to
weblogic/apache/xalan/res/XSLTInfo.properties and then add it to
$WL_HOME/lib/weblogic.jar
Steps to do this:
WL_HOME is the directory where weblogic is installed....e.g.
e:\bea6.1\wlserver6.1
1) Make a backup copy of %WL_HOME%\lib\weblogic.jar
2) jar xvf %WL_HOME%\lib\weblogic.jar
org/apache/xalan/res/XSLTInfo.properties
3) move org weblogic
4) jar uvf %WL_HOME%\lib\weblogic.jar weblogic
-----------------answer-from-Gareth Chapman--------------------
My case the path of XSLTInfo.properties was correct, so I did not have to
make any chances from it.
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
Hi Jouni,
Could you post full text of the exception here?It is (was) the full Exception!
Regards,
Slava Imeshev
"Jouni Koistinen" <[email protected]> wrote in message
news:[email protected]...
I have (allmost) same problem.
I get exception from XSLTProcessor.process() when running code above:
java.lang.ClassCastException:
weblogic.xml.jaxp.RegistrySAXTransformerFactory
My code works fine when I use WL 6.0 sp2, but WL 6.1 sp1 gives that
exception. If I let XSLTInputSource:s empty, WL 6.0 sp2 gives another
exception: weblogic.apache.xalan.xslt.XSLProcessorException: File "null"not
found, but WL 6.1 sp1 gives still the same exception, so prosessor noteven
try to found those files.
If I put xalan.jar (version 2.0.1) to my CLASSPATH and then run class
like
Samantha, then it works fine, but without xalan.jar, even if I run itlike
this, its not working:
java -Djavax.xml.parsers.DocumentBuilderFactory=weblogic.xml.jaxp.WebLogicDo
>>
>
cumentBuilderFactory -Djavax.xml.transform.TransformerFactory=weblogic.xml.j
>>
>
axp.WebLogicTransformerFactory -Djavax.xml.parsers.SAXParserFactory=weblogic
.xml.jaxp.WebLogicSAXParserFactory xalanTest
We are going to update our servers to 6.1sp1 from 6.0sp2, but I need toget
system working first, I have not tested this yet from servlet but I
think
its working just like from console.
What can I do with this?
xalanTest.java:
import weblogic.apache.xalan.xslt.XSLTProcessorFactory;
import weblogic.apache.xalan.xslt.XSLTInputSource;
import weblogic.apache.xalan.xslt.XSLTResultTarget;
import weblogic.apache.xalan.xslt.XSLTProcessor;
public class xalanTest {
public static void main(String[] args) {
try {
XSLTProcessor processor = XSLTProcessorFactory.getProcessor();
XSLTInputSource inXML = new XSLTInputSource("atom.xml");
XSLTInputSource inXSL = new XSLTInputSource("atom.xsl");
XSLTResultTarget out = new XSLTResultTarget(System.out);
System.out.println("Start parsing ...\n");
processor.process(inXML,inXSL,out);
System.out.println("\n... Parsing ok");
}catch (Exception e){
System.out.println(e);
atom.xml:
<?xml version="1.0"?>
<?xml-stylesheet type="text/xml" href="17-2.xsl"?>
<PERIODIC_TABLE>
<ATOM STATE="GAS">
<NAME>Hydrogen</NAME>
<SYMBOL>H</SYMBOL>
</ATOM>
</PERIODIC_TABLE>
atom.xsl:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="PERIODIC_TABLE">
<html>
<xsl:apply-templates/>
</html>
</xsl:template>
<xsl:template match="ATOM">
<P>
<xsl:apply-templates/>
</P>
</xsl:template>
</xsl:stylesheet>
Thanks
-Jouni Koistinen-

Using Axis2 webservices in WebLogic 10.3 - weblogic.xml

Hi,
I am facing an issue while trying the following:
I am using a webservices webapp in WebLogic 10.3. The web-app uses Axis2 for the webservices. To fix a logging issue, I had to add the following to my weblogic.xml:
<weblogic-web-app>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>
After adding this change to the weblogic.xml- I am now getting an error in weblogic server log files, which is as follows -
]] Root cause of ServletException.
java.lang.LinkageError: loader constraint violation: when resolving interface method "org.apache.xmlbeans.SchemaTypeLoader.parse(Ljavax/xml/stream/XMLStreamReader;Lorg/apache/xmlbeans/SchemaType;Lorg/apache/xmlbeans/XmlOptions;)Lorg/apache/xmlbeans/XmlObject;"
the class loader (instance of org/apache/axis2/deployment/DeploymentClassLoader) of the current class, com/arcot/schemas/regfort/v2/types/GetArcotIdDocument$Factory, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for resolved class, org/apache/xmlbeans/SchemaTypeLoader, have different Class objects for the type javax/xml/stream/XMLStreamReader used in the signature
I have tried over 6 hours of debugging but to no avail. If there are any suggestions anyone came make- as to the possible cause of this problem, it would be much appreciated!
thank you,
ronak

hi david,
thank you for the suggestion. The interesting thing is the error goes away as soon as I remove the weblogic.xml entry- and everything works fine. Except, when I dont have the prefer-web-inf-classes I get a log4j issue where my logs from different apps merge into a single file. That problem got resolved by adding the weblogic.xml change, but now it is this error.
Do you think there is anything that can be done in the weblogic-application.xml <prefer-application-packages> that might help in solving this problem?
thank you

WL 6.1 and Configuring External Entity Resolution with XML Registry

I have an XML document that uses a DTD with an http:// URL (specifically, my configuration
file for Struts). It works fine if the machine on which WebLogic is running has
an internet connection, but doesn't work when that machine (for security reasons)
is not connected.
I found in the "Administering WebLogic server XML" document the "External Entity
Configuration Tasks" section which seemed that it would solve my problem by specifying
a local file when encountering an external entity. I followed the directions,
but it didn't seem to make a difference.
Am I interpreting the documentation correctly (and if so, would the XMLRegistry
section below do what I think it should do), or do I need to do something completely
different (i.e., modify the Struts code) to have it not look for the http-based
DTD?
Any help is appreciated.
;ted
The XMLRegistry section of the config.xml file:
<XMLRegistry Name="Struts">
<XMLEntitySpecRegistryEntry CacheTimeoutInterval="-1" EntityURI="file:c:/struts-config_1_1.dtd"
Name="XMLEntitySpecRegistryEntry-1003533562502" PublicId="-//Apache Software Foundation//DTD
Struts Configuration 1.1//EN" WhenToCache="cache-at-initialization" />
<XMLEntitySpecRegistryEntry EntityURI="file:c:/struts-config_1_1.dtd" Name="XMLEntitySpecRegistryEntry-1003525690002"
SystemId="http://jakarta.apache.org/struts/dtds/struts-config_1_1.dtd" />
</XMLRegistry>
A copy of the struts-config_1_1.dtd file is in the C:\ directory.

Firstly, ensure that your XML Registry is targeted at a server. I know that's stating the obvious but you never know.
Secondly the xml/registries/??? directory belongs in the config/domain directory and not one level higher in the applications directory.
I'm been experincing problems resolving to an XML Schema. Resolution to a DTD works fine. Let me know how you get along

Weblogic 10 jaas and login.jsp and web.xml/weblogic.xml security constaints

Hello,
I struggled through and got the examples.security.jaas.SampleCallbackHandler.java and examples.common.utils.ExampleUtils.java/ExampleConstants.java into eclipse where they compile. A bean I made can call SambleCallbackHandler like such:
mybean.logmein(username,password,url). I can then do a mybean.getStatus() or even a mybean.returnCode(). It does seem to correctly identlify that it is authenticating me (I see in stdout logs that it shows success or failures. The problem I have is I do not know how to apply this weblogic and web.xml/weblogic.xml so that if authentication works it redirects me to the page requiring the authentication. In web.xml I have the following set up:
<security-role>
     <role-name>Admins</role-name>
</security-role>
<login-config>
     <auth-method>FORM</auth-method>
     <realm-name>default</realm-name>
     <form-login-config>
          <form-login-page>/login.jsp</form-login-page>
          <form-error-page>/badlogin.html</form-error-page>
     </form-login-config>
</login-config>
<security-constraint>
     <web-resource-collection>
          <web-resource-name>empower</web-resource-name>
          <description>These pages are only accessible by authorized users.</description>
          <url-pattern>/admin/*</url-pattern>
          <http-method>GET</http-method>
          <http-method>POST</http-method>
     </web-resource-collection>
<auth-constraint>
<description>These are the roles who have access</description>
<role-name>Administrators</role-name>
</auth-constraint>
     <user-data-constraint>
     <description>This is how the user data must be transmitted</description>
     <transport-guarantee>NONE</transport-guarantee>
     </user-data-constraint>
</security-constraint>
My weblogic.xml has:
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-web-app.xsd">
<wls:security-role-assignment>
<wls:role-name>Admins</wls:role-name>
<wls:principal-name>Administrators</wls:principal-name>
<wls:principal-name>dashap</wls:principal-name>
</wls:security-role-assignment>
</wls:weblogic-web-app>
With this set up, if I try to go to a page in /admin folder in my application, it correctly pops up the login page. The jaas in the bean is doing a loginContext.login(), which I thought does authentication too, but it never goes back to the /admin page I was going to that needed the authentication. With jaas, can I not use the web.xml FORM security option? Do I Need to use j_security in the login.jsp's form's action= option and j_username and j_password for the input type names? How do I use j_username/j_password things if I am using jaas? I could just ignore using the web.xml security stuff and put something in the pages that need authentication, but it would be easier if I could use jaas with the security featurs without doing all that. Note that my code above is using a realm called default just because that was what was in the example I got from the web. Does that need to be something else?

Hi John,
I would like magic of course. However, in this case I want something special: my authentication provider uses special means and contents of headers, cookies and service from external identity management systems to determine the user's identity.
I do not want the application to present the login dialog! I want to derive the identity and the fact that the user is logged in from whatever the authentication provider returns in terms of Subject.
Ideally, the flow is something like:
- user accesses an unprotected resource - resource is shown, no interaction with authentication provider
- user presses a link or button that takes him/her to a protected resource
- the authentication provider is contacted to work with the identity asserter to establish the identity of the current user and create a subject object for this user
- the application can access the subject and principals
- ADF Security recognizes the identity and the roles (based on the principals) and coordinates access based on this.
the authentication method is client certificate. presumably this prompts WebLogic/OPS to use an identity asserter to work with custom headers and cookies ("... when you configure a web application to use CLIENT-CERT authentication. In this case, WebLogic can perform identity assertion based on values from request headers and cookies. If the header name or cookie name matches the active token type for the provider, the value is passed to the provider."). No login form should be presented to the user, as all information required to perform the authentication is already available.
I am trying to understand what I must do to have the ADF application adopt the subject set by the authentication provider - if anything?!
If you more ideas to share - I would love to hear them.
best regards,
Lucas

Weblogic does not recognize the XML Registry settings!!!!

Dear colleagues,
We use Weblogic Server 6.0 sp2 and we would like to run an XML application with
following settings:
DocumentBuilderFactory: "org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"SAXParserFactory:
"org.apache.xerces.jaxp.SAXParserFactoryImpl"
Problem is:
weblogic shows this settings in the console, but at the runtime XML application
gets always the following parser:
javax.xml.parsers.SAXParserFactory = weblogic.xml.jaxp.RegistrySAXParserFactory
and the weblogic.log has also this parameters as a java system property.
How can we solve this problem in order to use the right parser inside the weblogic?
I appreciate your cooperation
thanx,
Metin

Can you show me what the error looks like. Also are you deploying the war to the other server? If the war worked on one server it should work on the other server too.
-- Nagesh

Weblogic 6.0sp2, problems useing new XML Registry

I'm trying to configure a parser other than the Built-In Parser, but WLS seems
to still us its default.
I follow the documentation at http://edocs.bea.com/wls/docs60/xml/xml_admin.html#1055027,
and use xerces 1.4.3, also creating a new server that is targeted.
I have attached a java file that I set as a startup class, targeted to myserver.
It shows the classname of saxparsers.
I allways get the following printout:
parserFactory: weblogic.xml.jaxp.RegistrySAXParserFactory
saxParser: weblogic.xml.jaxp.RegistrySAXParser
parser: weblogic.xml.jaxp.RegistryParser
But if I run the program from the command prompt, with xerces in the classpath
I get the following:
parserFactory: org.apache.xerces.jaxp.SAXParserFactoryImpl
saxParser: org.apache.xerces.jaxp.SAXParserImpl
parser: org.xml.sax.helpers.XMLReaderAdapter
Anyone now anything about this, seems like a bug?
-perotto
The parser
[PrintParserInfo.java]

hi,
try keeping the xerces.jar file before the weblogic.jar in the classpath of the
server script...
cuz' weblogic.jar file includes weblogic xerces parser..
but weblogic does not support all the features that xerces 1.4.3 version support.and
they(BEA) does not recommend to use other versions...
hope it will help you..
Vijay
"Per Otto Christensen" <[email protected]> wrote:
>
>
>
I'm trying to configure a parser other than the Built-In Parser, but
WLS seems
to still us its default.
I follow the documentation at http://edocs.bea.com/wls/docs60/xml/xml_admin.html#1055027,
and use xerces 1.4.3, also creating a new server that is targeted.
I have attached a java file that I set as a startup class, targeted to
myserver.
It shows the classname of saxparsers.
I allways get the following printout:
parserFactory: weblogic.xml.jaxp.RegistrySAXParserFactory
saxParser: weblogic.xml.jaxp.RegistrySAXParser
parser: weblogic.xml.jaxp.RegistryParser
But if I run the program from the command prompt, with xerces in the
classpath
I get the following:
parserFactory: org.apache.xerces.jaxp.SAXParserFactoryImpl
saxParser: org.apache.xerces.jaxp.SAXParserImpl
parser: org.xml.sax.helpers.XMLReaderAdapter
Anyone now anything about this, seems like a bug?
-perotto
The parser

Difference between prefer-application-packages in weblogic.xml and weblogic-application.xml?

Hi!
When deploying a WAR to WebLogic 10.3.5, what is the difference between the prefer-application-packages element in the files weblogic.xml and weblogic-application.xml?
In my WARs WEB-INF/lib/ I have a JAR that contains classes that are already provided by the container (but older versions).
If I do not use prefer-application-packages then my app gets the classes provided by the container.
If I use prefer-application-packages in weblogic.xml then I get the classes from WAR/WEB-INF/lib which is expected.
But if I use prefer-application-packages in weblogic-application.xml then I get the container versions. Why?
Is there a difference between those two options?
The exact data I use is:
(foo.bar.* is the conflicting package; I add or remove the linex marked with XXXX)
WEB-INF/weblogic.xml :
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-web-app
    xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-web-app"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd http://xmlns.oracle.com/weblogic/weblogic-web-app http://xmlns.oracle.com/weblogic/weblogic-web-app/1.2/weblogic-web-app.xsd">
    <wls:container-descriptor>
        <wls:show-archived-real-path-enabled>true</wls:show-archived-real-path-enabled>
        <wls:prefer-application-packages> 
            <wls:package-name>foo.bar.*</wls:package-name> 
        </wls:prefer-application-packages> 
        <wls:prefer-application-resources>
            <wls:resource-name>META-INF/services/some....</wls:resource-name>
            <wls:resource-name>META-INF/services/unrelated...</wls:resource-name>
            <wls:resource-name>META-INF/services/stuff...</wls:resource-name>
        </wls:prefer-application-resources>
    </wls:container-descriptor>
    <wls:jsp-descriptor>
        <wls:page-check-seconds>-1</wls:page-check-seconds>
        <wls:precompile>true</wls:precompile>
        <wls:precompile-continue>true</wls:precompile-continue>
        <wls:keepgenerated>true</wls:keepgenerated>
    </wls:jsp-descriptor>
    <wls:session-descriptor>
        <wls:persistent-store-type>replicated_if_clustered</wls:persistent-store-type>
    </wls:session-descriptor>
</wls:weblogic-web-app>
META-INF/weblogic-application.xml :
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-application
    xmlns="http://xmlns.oracle.com/weblogic/weblogic-application"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.2/weblogic-application.xsd">
    <application-param>
        <param-name>webapp.encoding.default</param-name>
        <param-value>UTF-8</param-value>
    </application-param>
    <xml>
        <parser-factory>
            <saxparser-factory>
                org.apache.xerces.jaxp.SAXParserFactoryImpl
            </saxparser-factory>
            <document-builder-factory>
                org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
            </document-builder-factory>
            <transformer-factory>
                org.apache.xalan.processor.TransformerFactoryImpl
            </transformer-factory>
        </parser-factory>
    </xml>
    <prefer-application-packages>
        <package-name>foo.bar.*</package-name> 
        <package-name>javax.jws.*</package-name>
        <package-name>javax.xml.ws.*</package-name>
        <package-name>org.apache.cxf.*</package-name>
        <package-name>antlr.*</package-name>
        <package-name>org.xmlsoap.schemas.wsdl.*</package-name>
    </prefer-application-packages>
</weblogic-application>

weblogic-application.xml has no meaning in WARs, it is only used in EARs.

Discrepancy between weblogic-ejb-jar.xml DTD and documentation

There seems to be a discrepancy between the DTD for the weblogic-ejb-jar.xml file
and the WLS7 documentation: Which source of information should I treat as
For example, the WLS7 documentation contains no information on the <idempotent-methods>
element (and its child elements)
(There is also a (larger) discrepancy between the weblogic-application.xml DTD and
the docs - I will post that Q under application deployment)
Regards,
Nick

Yep, I noticed it too. I used DTD, of course.
"Nick Minutello" <[email protected]> wrote
in message news:[email protected]..
>
>
There seems to be a discrepancy between the DTD for theweblogic-ejb-jar.xml file
and the WLS7 documentation: Which source of information should I treat as
For example, the WLS7 documentation contains no information on the<idempotent-methods>
element (and its child elements)
(There is also a (larger) discrepancy between the weblogic-application.xmlDTD and
the docs - I will post that Q under application deployment)
Regards,
Nick

WebLogic 9.2 MP1 - NoClassDefFoundError: weblogic/xml/domimpl/Saver

Hello,
I'm currently experiencing the following error in our production WebLogic environment. Curiously, the same WAR file deploys and works fine on our QA and STAGE servers. I must admit that my debugging knowledge of WebLogic is limited, but I have checked the obvious things (same version of WebLogic on all servers, same JAR files present on all, etc).
The error occurs when trying to generate a WSDL for a web service. The error is as follows:
####<Oct 16, 2008 6:46:59 PM BST> <Error> <HTTP> <lxxxxxxxxx.xxxxx.com> <xxxxxx_16621_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1224179219556> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@5ebaa3 - appName: 'AJPServices', name: 'AJPServices.war', context-path: '/AJP/AJPServices'] Root cause of ServletException.
java.lang.NoClassDefFoundError: weblogic/xml/domimpl/Saver
at weblogic.wsee.wsdl.WsdlDefinitions.write(WsdlDefinitions.java:581)
at weblogic.wsee.wsdl.WsdlDefinitions.write(WsdlDefinitions.java:569)
at weblogic.wsee.server.servlet.WsdlRequestProcessor.writeWsdl(WsdlRequestProcessor.java:146)
at weblogic.wsee.server.servlet.WsdlRequestProcessor.process(WsdlRequestProcessor.java:81)
at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:173)
at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:92)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:176)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3245)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Any suggestions would be most appreciated.
Thanks,
Sam
Edited by: user3634124 on 17-Oct-2008 04:41 (Fixed typos)

Hey Sam,
Are you using the same kinda startup means ?
(NodeManager / Regular Scripts)
If you created your application the same way on all environments, you could try to use the script from QA to production (means you'll have to do it by night :) ) or in the other way : try your production startup script in the QA env.
Else, the good old-fashioned way : compare both config.xml with WinCompare or BeyondCompare or anything that does the job.
Make also sure you don't have any XML Registry declared and that your domain/lib directories look alike.
Hope this helps.

Using XML registry FactoryConfigurationError

Hi I have been trying to use the XML registry to parse an XML doc, using weblogic6.0.
I generated a custom parser from the dtd for the said xml doc.
I have attached the config window (reg1) for the registry, the SAX and Document
builder factories are the default.
I have also attached a portion of the code used to the JAXP to call the custom
generated parser class
When I try to run this I get the error specified below.
Running on a windows NT machine.
Any advice or pointers would be greatly appreciated.
Thanks,
Brian
<Apr 17, 2001 4:09:13 PM PDT> <Error> <HTTP> <[WebAppServletContext(5163124,subs
)] Servlet failed with Exception
javax.xml.parsers.FactoryConfigurationError: weblogicx.xml.objects.SubscriberPar
ser
at weblogic.xml.jaxp.RegistryParser.getCustomParser(RegistryParser.java:
247)
at weblogic.xml.jaxp.RegistryParser.getParser(RegistryParser.java:172)
at weblogic.xml.jaxp.RegistryParser.parse(RegistryParser.java:103)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:155)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:100)
at JAXPSubscriberParser.<init>(JAXPSubscriberParser.java:40)
at jsp_servlet._jaxpsubscriberparser._jspService(_jaxpsubscriberparser.j
ava:94)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:213)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:1265)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:1622)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
[subs.doc]

Hi Rothrock, thanks for your reply...
Flash Version: 8, but the swf was published to be 7+
compatible.
The font is Meta Normal, it is embedded, and it does include
the character.
I am retrieving the xml by using this script in the html
page:
<script type="text/javascript">
// <![CDATA[
var fo = new FlashObject("/templates/flash/index.swf" +
cKiller, "ad-flash", "710", "351", "7", "#FFFFFF");
fo.addVariable("xmlURL", "/flash_content/products.xml");
fo.write("ad");
// ]]>
</script>
I am creating the XML using Macromedia Homesite, with the
encoding declaration <?xml version="1.0" encoding="UTF-8" ?>
The XML is being read fine, only the special characters don't
show up... so it will cut off the word, or just have an empty space
where the character should be.
I am not sure how to specifiy Extended Latin charset in the
document... could you tell me how to do that?
Thanks

XML Registry problem in WLS 7.0

Hi,
I have created an XML Registry with SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl
because i want to use the latest saxparser in my webapplication. But when i invoke
this line of code in my webapplication: -
SAXParserFactory spf = SAXParserFactory.newInstance();
i get weblogic.xml.jaxp.RegistrySAXParserFactory instead of org.apache.xerces.jaxp.SAXParserFactoryImpl
I also get system property javax.xml.parsers.SAXParserFactory=weblogic.xml.jaxp.RegistrySAXParserFactory
in the WLS log file.
I have tried putting xercesImpl.jar in the classpath before weblogic.jar. I also
tried changing the system property in startWLS.cmd also, ..but all in vain.
Can someone help me out in figuring out who is setting this system property to
WLS's default SAXfactory and how can i use my parser work in a webapplication?
Any help would be greatly appreciated!!
thanks -
Manoj

First thing, most of BEA's forums are terrible as people rarely reply. I noticed your post through google searching for the same fix. You have likely done the same things as me and have learned that your Oracle JDBC Client driver has some bugs interacting with certain version of Oracle Server. For us, this problem occured when we migrated from Solaris to AIX. We were able to fix this by downloading the latest version of ojdbc14.zip from oracle's site. You can either replace the current ojdbc14 file in the bea installation or make sure it is visible in the classpath for WLS before the old version.
Here is a good link which describes the problem, good luck.
http://www.dbtalk.net/comp-databases-oracle-server/java-sql-sqlexception-bigger-type-289015.html

XML Registry

I'm still trying to run Xalan from the server side...
I tried to set up an XML Registry to use the org.apache.xerces.jaxp
classes. Though it is selected by the server on the XML Services tab,
and it is the only registry I have, I print out the factory and parser
classes that get created, and they are still
weblogic.xml.jaxp.RegistryBlahblahblah classes. The config.xml has the
right class names as shown on the console. Why aren't they used?
The other question I have is that since the Xerces classes that I want
to use have the same names as the ones included but are a different
version, how do I get the server to use the new classes and not the ones
bundled with WebLogic?
Any help would be greatly appreciated!
Michelle

Try to define XML Registry Entry for your specific DTD.
WL compares PublicId, SystemId and RootElement between XML and DTD to find
specific Parser class name for your XML. In this case you must create
xml/registry directory in your domain directory and put there your DTD file.
If it still not working - write this code:
public SAXParser getParser() {
// Return the parser we already created (if any)
if(parser!=null) {
return (parser);
// Create and return a new parser
try {
SAXParserFactory factory= new
org.apache.xerces.jaxp.SAXParserFactoryImpl();
factory.setNamespaceAware(false);
factory.setValidating(false);
parser=factory.newSAXParser();
return (parser);
} catch(Exception e) {
System.out.println("getParser: "+e.getMessage());
return (null);
"Michelle Baxter" <[email protected]> wrote in message
news:[email protected]...
Ok, thanks. I suspected it might be wrapping it, but I wasn't sure how
to tell. I have not figured out how to get the server to run as a
JBuilder run configuration to debug it. It's looking for ".\config",
even though I've given it weblogic.system.home. So I can't look at the
stack trace, at least not that way.
Whatever parser it's getting, it's still the wrong one because I still
get the AbstractMethodError. I don't see how it's possible to have the
wrong version with xmlx.jar out of the way. But I have to keep looking.
Thanks for all your help.
Sandeep Shrivastava wrote:
The parser is weblogic.xml.jaxp.RegistrySAXParser, but it wraps the
org.apache.xerces.parser.SAXParser. the actual parse will be done by the
xerces parser ( whatever is configured in the xml registry )
look at the stack trace in one of your sax callback methods to verify
this.
>>
sandeep
Michelle Baxter wrote in message <[email protected]>...
If that is true, then why when I print out the class name of a parser
that I created do I get weblogic.xml.jaxp.RegistrySAXParser instead of
org.apache.xerces.parsers.SAXParser, which is what is configured in the
config.xml file?
Sandeep Shrivastava wrote:
the weblogic.xml.jaxp package contains classes which implement JAXP
inside
weblogic server. The parser configured in the registry will be invoked
by
the server's jaxp implementation. You can verify this by examining thestack
trace inside one of your sax handler callback methods.
Michelle Baxter wrote in message <[email protected]>...
I'm trying to use Xalan 2J D05. The config.xml is attached.
Xalan is the first thing in my classpath when I run the server.
Xerces
is the second. I tried renaming xmlx.jar to something else, but it
doesn't make a difference.
Sandeep Shrivastava wrote:
Which version of Xalan are you trying to use?
Can you post the config.xml?
The weblogic 6.0 install contains Xerces 1.2 in
weblogic.apache.xerces.parsers package and Xalan 1.2 in the
weblogic.apache.xalan.xslt package ( These are the built-in sax and
dom
parser and xslt engine, bundled in weblogic.jar )
The install also includes Xerces 1.2 in theorg.apache.xerces.parsers
package and Xalan 1.2 in the org.apache.xalan.xslt package ( Theseare
>>>>>
the
XML module's parser and xslt engine, bundled in xmlx.jar )
If you want to use another version of xalan rename the xmlx.jar to
xmlx.jar.bak in the lib directory of the install. You may lose on
the
>>>>>
other
goodies that come with the XML module, i.e. the parser generator and
the
jsp
tag library though.
thanks
Sandeep
"Michelle Baxter" <[email protected]> wrote in message
news:[email protected]...
I'm still trying to run Xalan from the server side...
I tried to set up an XML Registry to use the org.apache.xerces.jaxp
classes. Though it is selected by the server on the XML Services
tab,
and it is the only registry I have, I print out the factory andparser
classes that get created, and they are still
weblogic.xml.jaxp.RegistryBlahblahblah classes. The config.xml hasthe
right class names as shown on the console. Why aren't they used?
The other question I have is that since the Xerces classes that Iwant
to use have the same names as the ones included but are a different
version, how do I get the server to use the new classes and not theones
bundled with WebLogic?
Any help would be greatly appreciated!
Michelle

Creation of Virtual Directory in weblogic.xml (OBIEE11 Weblogic)

We are using OBIEE 11.1.1.6.4, we want to create a Virtual directory mapping in weblogic server so that we can place our static image files to access from the application URL.
To do this activity, we have performed following steps -
1) Navigated to C:\OBIEE11G\Oracle_BI1\bifoundation\jee
2) Open analytics.ear file
3) Existing code in weblogic.xml is: (if weblogic.xml is not present we need to create the file with below code)
<?xml version = '1.0' encoding = 'US-ASCII'?>
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app">
<session-descriptor>
<cookie-path>/analytics</cookie-path>
</session-descriptor>
</weblogic-web-app>
4) We have added virtual-directory-mapping tag; After adding virtual directory mapping tag, the code in weblogic.xml is
<?xml version = '1.0' encoding = 'US-ASCII'?>
<weblogic-web-app xmlns="http://xmlns.oracle.com/weblogic/weblogic-web-app">
<session-descriptor>
<cookie-path>/analytics</cookie-path>
</session-descriptor>
<virtual-directory-mapping>
<local-path>D:/virtualdirectory</local-path>
<url-pattern>/images/*</url-pattern>
<url-pattern>*.jpeg</url-pattern>
</virtual-directory-mapping>
</weblogic-web-app>
5) We have created a folder virtualdirectory under D: drive. And then created a folder images within folder virtualdirectory.
6) Then we have placed an image (lets say) test.jpeg within image folder.
7) Restarted all BI services,
8) Now when we try to access URL http://localhost:9704/analytics/images/test.gif. Now we are able to see the image, it’s working perfectly fine.
If we paste the above URL in browser it will automatically displays the image without any authentication. So our requirement is, on pasting the URL in browser first it should redirect to OBIEE homepage and when authentication is done then it should display the image.
Request you to please advise with your inputs.

Why did you modify analytics.ear ?
Should'nt you make changes here : Middleware_Home>\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1
\analyticsRes\WEB_INF\web.xml
Follow this note : OBIEE 11g: How To Access Custom Files Through URL By Creating Virtual Directory In Weblogic Server? [ID 1408240.1]
And you should be able to deploy that virtual directory and access it after authentication.
HTH,
SVS

prefer-web-inf-classes in weblogic.xml doesn't work

When I try to use <prefer-web-inf-classes>true</prefer-web-inf-classes> it works fine with default classloaders structure. But after I changed classloaders hierarhy by means of <classloader-structure> in weblogic-application.xml classes from web app are ignored and classes from outside web app are loaded.
Here is classloaders structure I use
<weblogic-application>
<classloader-structure>
<module-ref>
<module-uri>mywar.war</module-uri>
</module-ref>
<classloader-structure>
<module-ref>
<module-uri>myejb.jar</module-uri>
</module-ref>
</classloader-structure>
</classloader-structure>
</weblogic-application>
Has anybody encountered this before?

Hi, Rob
Does it work in WL9.2?
It seems I do it exactly as the explained at http://edocs.bea.com/wls/docs81/programming/classloading.html - and it fails :o(.
I try to run my app.ear with WL9.2 There are 2 components in it: webapp and mdb. The webapp/WEB-INF contains weblogic.xml:
<weblogic-web-app>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
</weblogic-web-app>
Mdb is expected to run in the same mode, i.e. to prefer the webapp/WEB-INF/*.jar over the parent Weblogic classloader. To do so I add the weblogic-application.xml to the app.ear!/META-INF:
<weblogic-application>
<classloader-structure>
<module-ref>

<module-uri>webapp</module-uri>
</module-ref>
<classloader-structure>
<module-ref>
<module-uri>mdb.jar</module-uri>
</module-ref>
</classloader-structure>
</classloader-structure>
</weblogic-application>
Now, when classloader-structure specified, both webabb and mdb prefer the weblogic root loader as if prefer-web-inf-classes not defined at all.

Weblogic XML Registry and Entity Resolution

Similar Messages

Maybe you are looking for