StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19013524
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-25T19:26:39.193
FavoriteCount
0
LastActivityDate
2013-09-25T19:39:10.617
LastEditDate
2013-09-25T19:39:10.617
LastEditorUserId
1185559
OwnerUserId
1185559
ParentId
18970861
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
I got it working. In jboss in addition to modules which we can exclude there is another jar that’s at the root C:\jboss-eap-6.0\jboss-modules.jar. Inside this jar there is folder called “__redirected” with a class __TransformerFactory.class with following code. <pre><code>Class clazz = __RedirectedUtils.loadProvider(id, javax/xml/transform/TransformerFactory, loader); </code></pre> This forces the “org.apache.xalan.processor.TransformerFactoryImpl” to be loaded from C:\jboss-eap-6.0/jboss-modules.jar However this is not a module so I can’t exclude it using jboss-deployment-structure.xml, though I had exclude the following jboss modules for Xalan, Xercel and XML api . As we have a specific jars in the EAR lib to satisfy this. jboss-deployment-structure.xml <pre><code><jboss-deployment-structure xmlns:p="urn:jboss:deployment-structure:1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <deployment> <exclusions> <module name="org.apache.xerces" /> <module name="org.apache.xalan" /> <module name="org.apache.xml-resolver" /> </exclusions> </deployment> </code></pre> So I commented the following code <pre><code> stfactory = (SAXTransformerFactory) TransformerFactory.newInstance(); </code></pre> and added <pre><code> Class clazz = Class.forName("org.apache.xalan.processor.TransformerFactoryImpl"); stfactory = (SAXTransformerFactory) clazz.newInstance(); </code></pre> Now I see that <ul> <li>org.apache.xalan.processor.TransformerFactoryImpl is getting loaded from C:/jboss-eap-6.0/standalone/deployments/TST.ear/lib/xalan-2.7.0.jar</li> <li>The call stfactory.newTransformerHandler(streamSource) returns “org.apache.xalan.transformer.TransformerHandlerImpl” and not “org.apache.xalan.transformer.TransformerIdentityImpl”</li> </ul> So I believe that the jar “C:\jboss-eap-6.0\jboss-modules.jar” is part of class loader and above the EAR class loader. So it was not using Xalan.2.7.0.jar for “org.apache.xalan.processor.TransformerFactoryImpl”. However when we call stfactory.newTransformerHandler(streamSource) it would return “org.apache.xalan.transformer.TransformerIdentityImpl” . May be there is something buried in C:\jboss-eap-6.0\jboss-modules.jar for this behavior. What I don’t understand was in one of tests I did use Xalan.2.7.0.jar and added that in java.endorsed.dir it was still using C:\jboss-eap-6.0\jboss-modules.jar which is little surprising as I thought the jars in endorsed will be loaded even before C:\jboss-eap-6.0\jboss-modules.jar. But anyway the current fix resolves the problem and it happens only on Jboss application server 7. The code works without any changes in Webspshere 7.0 and also when I run it as standalone java program.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POXSL FO failing XSLT translation in JBOSS AS 7
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USReddymails
UserOwnerUserId
1. USReddymails
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.