JSF2 on Netweaver 7.3

[Former Member]

Hi experts,

I'm currently trying to get JSF2 working on a Netweaver 7.3 AS Java. I want to integrate Apache myfaces and another jsf library called primefaces.

I add the two myfaces libraries myfaces-impl.jar and myfaces-api.jar (and also the primefaces.jar) to the JEE Module dependencies of my EAR project (name: TestEAR) and checked the "In Lib Dir" option.

In my "Dynamic Web Project" (name: Test) I added a file called test.xhtml (containing simple jsf script) to the web-inf folder and also adjusted the web.xml for JSF usage.

The builded EAR file looks good, it contains the selected libraries as well as the dynamic web project. The deployment to the SAP AS Java also finishes with status OK. When I open the application using the context root I get an error message that goes like "File [test.jsp] is not found in application root of alias [Test] of Java EE application [.../TestEAR]."

The message suggests, that JSF 1.2 is used instead of the bundled JSF2 libraries (I cross-checked this assumption deleting the included jsf libraries => that leads to the same error message, so the application server doesn't care about my libs).

What am I missing here? Is there a possiblity to have the server use the bundled libraries instead of the default ones? (I have in mind the jboss web.xml parameter org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL). How can I achieve the usage of JSF2?

Thanks in advance!

Kind regards,

Helmut

[Former Member · Accepted solution]

Ah, that's interesting!

I have an other project that bundles eclipselink as persistency provider within the ear project and runs fine, so I thought the same approach should be sufficient for JSF2.0.

[Former Member · Accepted solution]

Finally after weeks of desperation...

The solution (if you know it) is quite simple:

One has to depoly an own SDA which acts as a library, containing the JSF2 libs.

In my case this looks as follows:

jsf-libs.sda
\_lib
   |- jsf-api.2.0.9.jar
   |- jsf-impl.2.0.9.jar
\_server
   |- provider.xml
\_META-INF
   |- MANIFEST.MF
   |- SAP_MANIFEST.MF
   |- primary-lib-dd.xml

the files looking like this:

provider.xml

<?xml version="1.0"?>
<provider-descriptor>
<display-name>ec/java/fake/jsf/api</display-name>
<component-name>ec~java~fake~jsf~api</component-name>
<provider-name>sap.com</provider-name>
<references>
<reference type="library" strength="strong" provider-name="sap.com">servlet</reference>
</references>
<jars>
<jar-name>lib/jsf-api.2.0.9.jar</jar-name>
<jar-name>lib/jsf-impl.2.0.9.jar</jar-name>
</jars>
</provider-descriptor>

MANIFEST.MF

Manifest-Version: 1.0
Implementation-Title: ec~java~fake~jsf~api
Implementation-Version: 20120312101820
Implementation-Vendor-Id: test.burda.com
Specification-Vendor: SAP AG

SAP_MANIFEST.MF

Manifest-Version: 1.0
Ext-SDM-SDA-Comp-Version: 1
softwaretype: primary-library
JarSAP-Standalone-Version: 20090803.1000
JarSAPProcessing-Version: 20090907.1000
dtr-workspace: XXXXX
deployfile: primary-lib-dd.xml
archivetype: DC
JarSAP-Version: 20090803.1000
keyname: ec~java~fake~jsf~api
keyvendor: test.com
keylocation: localDevelopment
keycounter: 20120312101820
componentelement: <componentelement  name="ec~java~fake~jsf~api" vendor="test.com" componenttype="DC" subsystem="NO_SUBSYS" location="localDevelopment"
counter="20120312101820" scvendor="test.burda.com" scname="MyComponents" deltaversion
="F" updateversion="LB-20120312111821" componentprovider="localDevelopment" servertype="DTR" sourceserver="xxxxxxxx" archivetype="DC"/>
JarSL-Version: 20100616.1800
compress: true

primary-lib-dd.xml

<?xml version="1.0" ?>
<SDA>
<SoftwareType>primary-library</SoftwareType>
<engine-deployment-descriptor version="2.0"/>
</SDA>

These files are packed in a zip-archive and then I renamed the zip to "jsf-libs.sda" and deploed it to the server.

Afterwards I created my web-project for the JSF things.

The faces-config.xml for the WAR is changed manually to version 2.0

<faces-config xmlns="http://java.sun.com/xml/ns/javaee"
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-facesconfig_2_0.xsd"
version="2.0">

Finally the application-j2ee-engine.xml in the EAR is changed to:

<?xml version="1.0" encoding="UTF-8"?>

<application-j2ee-engine xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="application-j2ee-engine.xsd">

<reference reference-type="hard" prepend="true">
     <reference-target target-type="library">ec~java~fake~jsf~api</reference-target>
</reference>
<reference reference-type="hard" prepend="false">
     <reference-target provider-name="sap.com" target-type="library">engine.jee5.facade</reference-target></reference>
</application-j2ee-engine>

I wanted to use Primefaces as well and just put the primefaces-3.2.jar into the  WebContent/WEB-INF/lib

Only issue now is, that the server seems to call somewhere and is waiting for an timeout (60sec) before I can use the Primefaces-UI. Bisides of that everything is running so far.

Greething

Ingo

[Former Member · Accepted solution]

Hi Ingo,

thanks for this great post! We've the same problem with slow access to css and js (~60 seconds timeout) you described. Did you find a solution yet?

cheers

christopher

[Former Member · Accepted solution]

We found out, that the timeout was somehow related to the gzip-compression of the AS.

In the NWA you can find in Configuration -> Infrastructure -> Java-Systemproperties the Tab Services:

Search here for: "HTTP Providers" there you find a Property "CompressOthers" this has to be false. Afterwards I guess you have to restart the AS.

Currently I have no AS 7.3 running so I am not able to check the correct steps and I've written this post just with what's on my mind. It is also possible that we set some other values but everything was set in "HTTP Providers" thats for sure.

I can remember that we have had some trouble after setting the value to false since some parts worked well and others remain the same but after a restart everthing worked like expected.

[Former Member · Accepted solution]

Hi Ingo,

thanks for this hint! With this it works like a charme! And no matter with gzip compression, we've a reverse proxy instance in front of our application server which will compress the content for the customer.

thanks a lot!

cheers

christopher

[Former Member · Accepted solution]

Hi Ingo,

I am trying to deploy JSF2 + RichFaces 4 application on NW 7.3 SP7.

I tried to create JSF2 SDA as you explained, with the only modification i have 'javax.faces-2.1.7.jar' instead of two jars api&impl. I have also tried the instructions @ http://scn.sap.com/community/open-source/blog/2012/05/02/nw-73-spring-31-jsf-20-and-primefaces-part-..., but my SDA is always deployed as 'application'. I can deploy my EAR if i change 'reference-type' from "library" to "application" in the application-j2ee-engine.xml, but NW's own JSF1.2 seems still first on the class path.

How do you deploy the JSF2 SDA you create?

I am using deploy.bat script. Could you possibly share with me the exact SDA file you use?

Can  you undeploy such SDA or application EAR somehow?

Best regards,

Piotr

[Former Member · Accepted solution]

Hi,

I've got a working SDA (Mojarra 2.1.16) on dropbox, just message me your email address.

The META_INF.. data posted by Ingo S. above didn't work for me out of the box. Eventually I downloaded a standard SDA from my 7.30 system (tc~je~ejb~client~730.sda), copied the META-INF and server folders to my working folder and changed the component information (display and component name, jar name and so on).

After deployment in the EAR's application-j2ee-engine.xml just add:

<reference reference-type="hard" prepend="true">

     <reference-target target-type="library">demo.ecenta.com~javax~faces~2.1.16</reference-target>

</reference>

Before I found this post I tried the following with no luck:

a) Deploying a EAR DC that is using a public part (assembly) of a Library DC (refer to http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/006a6229-b1ed-2e10-0c8c-cc5673cf2...)

In telnet the Lib EAR was found in the classpath but the JSF 2 classes are not loaded. I assume the fact that the JSF jars are not exposed directly in the EAR (but within an assembly JAR) is the reason.

Nevertheless when working with DC's you will need the compliation public parts in order to build the web module.

b) Adding the JAR's to WEB-INF/lib

For some reason the AS always falls back the JSF 1.2 libs on Java AS.

I almost spend 2 days to get this working, hope that the SDA file can speed the project setup up for others.

In a NWDI development scenario b) still seems the most logical to me to avoid the manual SDA deployment in all landscapes and use the CMS transport instead. Hope to still get it working.

Best Regards

Ingo

[steffen_spahr2]

Hi Ingo,

have you ever tried to use "Shared Libraries" instead of the SDA that acts as a library?

See:   "http://help.sap.com/saphelp_nw73/helpdata/en/4a/5f913b0fe452f6e10000000a42189c/content.htm

For myself I am using the MyFaces 1.2 - Implementation of JSF 1.2 in one of my projects. I separated the JAR-Files (myfaces-api.1.2.12.jar and myfaces-impl-1.2.12.jar,..) in a Shared Library Porject (In NW 7.3 it is an EAR-Project with Module Dependencies (Bundled Libraries)).

For using the MyFaces-Shared-Libraries, I defined in my Web-Application-EAR-Project a Reference to the Shared Library:

application-j2ee-engine.xml:

<?xml version="1.0" encoding="UTF-8"?>

<application-j2ee-engine xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

    xsi:noNamespaceSchemaLocation="application-j2ee-engine.xsd">

    <reference reference-type="hard">

        <reference-target target-type="application"

            provider-name="bit.de">MyFaces12Libraries</reference-target>

    </reference>

    <provider-name>bit.de</provider-name>

</application-j2ee-engine>

Greetings

Steffen

[steffen_spahr2]

Hi Ingo,

I was wrong.

I believed I was using the MyFaces 1.2 Implementation of JSF 1.2 by defining a reference to the Shared Library Projekt. But in reality, my application always used tm SAP JSF 1.2 implementation.

I another project I used the JSF 2.x Mojarra-Implementation.

Referencing this implemenation via a "heavy reference" to a Shared Library application didn't work:

<reference reference-type="hard" prepend="true">

     <reference-target target-type="application"

            provider-name="oevbs.de">Mojarra21xEAR</reference-target>

</reference>

I had to define a library-project in the way you explained and to define a heavy reference (using prepend="true") to this library:

<reference reference-type="hard" prepend="true" >

     <reference-target provider-name="local.j2ee"

            target-type="library">javax~faces~2.1.x</reference-target>

</reference>

Regards Steffen

[Former Member]

Hey everybody,

for reasons of completeness in this place should be mentioned that George Ushakov did a great job in writing all necessary things together here:

http://scn.sap.com/community/open-source/blog/2012/05/02/nw-73-spring-31-jsf-20-and-primefaces-part-...

One further question from my side has to been asked:

Am I the only one experiencing a delay while deploying Primefaces-Applications?

It is roughly 10min per deploy where the server has no load at all. Our guess currently is, that it is a timeout while validating some xml since our NW has no access to the Internet. But we can't find anything that is pointing us into the right direction.

Cheers

Ingo

[Former Member]

Yes!  I've seen the exact same thing, but weirdly, only when I'm in the office.  My local server is running on a virtual machine, and when I'm at home, there is no timeout.  When in my office, I see the 10 min issue...  I too have always been suspicious of the XML/XSD schema validation process.

I did a dump of the deploy process during one of these delays while in the office...  I do think this is the issue as seen below in RED.  Any ideas how to turn off the schema validation as a part of deploy?

user="Administrator" isapplicationthread="true" prio=10 tid=0x00000000026f2800 nid=0x295b / 10587  pthread-id=139733963151104 runnable  [_thread_in_native (_at_safepoint), stack(0x00007f16591c9000,0x00007f16593ca000)] [0x00007f16593c6000]   java.lang.Thread.State: RUNNABLE at java.net.PlainSocketImpl.socketConnect(Ljava/net/InetAddress;II)V(Native Method) at java.net.PlainSocketImpl.doConnect(Ljava/net/InetAddress;II)V(PlainSocketImpl.java:351) - locked (a java.net.SocksSocketImpl) - additional info (remote: bigip-www-legacy-cms-ucf.oracle.com/156.151.59.19:80, local: localhost/127.0.0.1:0) at java.net.PlainSocketImpl.connectToAddress(Ljava/net/InetAddress;II)V(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(Ljava/net/SocketAddress;I)V(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(Ljava/net/SocketAddress;I)V(SocksSocketImpl.java:366) at java.net.Socket.connect(Ljava/net/SocketAddress;I)V(Socket.java:531) at java.net.Socket.connect(Ljava/net/SocketAddress;)V(Socket.java:478) at sun.net.NetworkClient.doConnect(Ljava/lang/String;I)Ljava/net/Socket;(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(Ljava/lang/String;I)V(HttpClient.java:413) at sun.net.www.http.HttpClient.openServer()V(HttpClient.java:527) - locked (a sun.net.www.http.HttpClient) at sun.net.www.http.HttpClient.(Ljava/net/URL;Ljava/net/Proxy;I)V(HttpClient.java:210) at sun.net.www.http.HttpClient.New(Ljava/net/URL;Ljava/net/Proxy;IZLsun/net/www/protocol/http/HttpURLConnection;)Lsun/net/www/http/HttpClient;(HttpClient.java:293) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Ljava/net/URL;Ljava/net/Proxy;IZ)Lsun/net/www/http/HttpClient;(HttpURLConnection.java:994) at sun.net.www.protocol.http.HttpURLConnection.plainConnect()V(HttpURLConnection.java:942) at sun.net.www.protocol.http.HttpURLConnection.connect()V(HttpURLConnection.java:841) at com.sap.engine.httpdsrclient.protocols.http.DSRHttpURLConnection.connect()V(DSRHttpURLConnection.java:103) at sun.net.www.protocol.http.HttpURLConnection.getInputStream()Ljava/io/InputStream;(HttpURLConnection.java:1195) - locked (a com.sap.engine.httpdsrclient.protocols.http.DSRHttpURLConnection) at com.sap.engine.httpdsrclient.protocols.http.DSRHttpURLConnection.getInputStream()Ljava/io/InputStream;(DSRHttpURLConnection.java:133) - locked (a com.sap.engine.httpdsrclient.protocols.http.DSRHttpURLConnection) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(Ljava/lang/String;Lcom/sun/org/apache/xerces/internal/xni/parser/XMLInputSource;ZZ)Ljava/lang/String;(XMLEntityManager.java:704) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(Ljava/lang/String;Lcom/sun/org/apache/xerces/internal/xni/parser/XMLInputSource;ZZ)V(XMLEntityManager.java:1342) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDocumentEntity(Lcom/sun/org/apache/xerces/internal/xni/parser/XMLInputSource;)V(XMLEntityManager.java:1294) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.setInputSource(Lcom/sun/org/apache/xerces/internal/xni/parser/XMLInputSource;)V(XMLDocumentScannerImpl.java:280) at com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaParsingConfig.parse(Z)Z(SchemaParsingConfig.java:409) at com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaParsingConfig.parse(Lcom/sun/org/apache/xerces/internal/xni/parser/XMLInputSource;)V(SchemaParsingConfig.java:491) at com.sun.org.apache.xerces.internal.impl.xs.opti.SchemaDOMParser.parse(Lcom/sun/org/apache/xerces/internal/xni/parser/XMLInputSource;)V(SchemaDOMParser.java:510) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getSchemaDocument(Ljava/lang/String;Lcom/sun/org/apache/xerces/internal/xni/parser/XMLInputSource;ZSLorg/w3c/dom/Element;)Lorg/w3c/dom/Element;(XSDHandler.java:1812) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(Lcom/sun/org/apache/xerces/internal/xni/parser/XMLInputSource;Lcom/sun/org/apache/xerces/internal/impl/xs/XSDDescription;Ljava/util/Hashtable;)Lcom/sun/org/apache/xerces/internal/impl/xs/SchemaGrammar;(XSDHandler.java:541) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(Lcom/sun/org/apache/xerces/internal/impl/xs/XSDDescription;Lcom/sun/org/apache/xerces/internal/xni/parser/XMLInputSource;Ljava/util/Hashtable;)Lcom/sun/org/apache/xerces/internal/impl/xs/SchemaGrammar;(XMLSchemaLoader.java:578) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.findSchemaGrammar(SLjava/lang/String;Lcom/sun/org/apache/xerces/internal/xni/QName;Lcom/sun/org/apache/xerces/internal/xni/QName;Lcom/sun/org/apache/xerces/internal/xni/XMLAttributes;)Lcom/sun/org/apache/xerces/internal/impl/xs/SchemaGrammar;(XMLSchemaValidator.java:2443) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(Lcom/sun/org/apache/xerces/internal/xni/QName;Lcom/sun/org/apache/xerces/internal/xni/XMLAttributes;Lcom/sun/org/apache/xerces/internal/xni/Augmentations;)Lcom/sun/org/apache/xerces/internal/xni/Augmentations;(XMLSchemaValidator.java:1788) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(Lcom/sun/org/apache/xerces/internal/xni/QName;Lcom/sun/org/apache/xerces/internal/xni/XMLAttributes;Lcom/sun/org/apache/xerces/internal/xni/Augmentations;)V(XMLSchemaValidator.java:711) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement()Z(XMLNSDocumentScannerImpl.java:400) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook()Z(XMLNSDocumentScannerImpl.java:626) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next()I(XMLDocumentFragmentScannerImpl.java:3104) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next()I(XMLDocumentScannerImpl.java:921) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next()I(XMLDocumentScannerImpl.java:647) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next()I(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Z)Z(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Z)Z(XML11Configuration.java:817) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Lcom/sun/org/apache/xerces/internal/xni/parser/XMLInputSource;)V(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Lcom/sun/org/apache/xerces/internal/xni/parser/XMLInputSource;)V(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Lorg/xml/sax/InputSource;)V(DOMParser.java:232) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Lorg/xml/sax/InputSource;)Lorg/w3c/dom/Document;(DocumentBuilderImpl.java:284) at com.sap.tc.jtools.jlinee.web.tests.JSFApplicationTest.parseSchemaValidating(Ljava/io/InputStream;Ljava/lang/String;)Lorg/w3c/dom/Document;(JSFApplicationTest.java:322) - locked (a com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl) at com.sap.tc.jtools.jlinee.web.tests.JSFApplicationTest.parseJSF(Ljava/lang/String;Ljava/io/InputStream;)Lcom/sap/engine/lib/descriptors5/webfacesconfig/FacesConfigType;(JSFApplicationTest.java:297) at com.sap.tc.jtools.jlinee.web.tests.JSFApplicationTest.getFacesConfigs()Ljava/util/HashMap;(JSFApplicationTest.java:197) at com.sap.tc.jtools.jlinee.web.tests.JSFApplicationTest.executeTests()Z(JSFApplicationTest.java:119) at com.sap.tc.jtools.jlinee.web.tests.JSFApplicationTest.execute()V(JSFApplicationTest.java:103) at com.sap.tc.jtools.jlinee.lib.AbstractJ2EETest.executeWithStatus()Z(AbstractJ2EETest.java:158) at com.sap.tc.jtools.jlinee.lib.framework.dependency.Node.execute()V(Node.java:212) at com.sap.tc.jtools.jlinee.lib.framework.JLinEETestProcessor.executeAll(Ljava/util/List;)V(JLinEETestProcessor.java:148) at com.sap.tc.jtools.jlinee.lib.framework.JLinEETestProcessor.execute()V(JLinEETestProcessor.java:118) at com.sap.engine.jlinee.lib.impl.TestManager.executeTestsForAppComponent(Lcom/sap/engine/jlinee/lib/ApplicationComponentInfo;Lcom/sap/engine/jlinee/lib/ApplicationInfo;Ljava/util/List;Ljava/util/List;)V(TestManager.java:154) at com.sap.engine.jlinee.lib.impl.TestManager.executeTests()Lcom/sap/engine/jlinee/lib/ResultsDescriptor;(TestManager.java:89) at com.sap.engine.jlinee.lib.JLinEEValidatorImpl.validateApplication(Lcom/sap/engine/jlinee/lib/ApplicationInfo;Lcom/sap/engine/lib/converter/ISubstVarResolver;[Ljava/lang/String;)Lcom/sap/engine/jlinee/lib/ResultsDescriptor;(JLinEEValidatorImpl.java:143) at com.sap.engine.services.deploy.server.validate.jlin.impl.JLinPluninImpl.exec(Lcom/sap/engine/services/deploy/server/validate/jlin/AppJLinInfo;)Ljava/util/Set;(JLinPluninImpl.java:99) at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.validateApplication(Lcom/sap/engine/services/deploy/container/ContainerDeploymentInfo;Ljava/util/Hashtable;)Lcom/sap/engine/services/deploy/container/ContainerDeploymentInfo;(DeployUtilTransaction.java:459) at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin()V(DeployUtilTransaction.java:174) at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin()V(DeploymentTransaction.java:203) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer()V(ApplicationTransaction.java:421) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases()V(ApplicationTransaction.java:473) at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(Lcom/sap/engine/services/deploy/server/DTransaction;Z)V(DeployServiceImpl.java:1832) at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(Lcom/sap/engine/services/deploy/server/application/DeploymentTransaction;Ljava/util/List;)[Ljava/lang/String;(DeployServiceImpl.java:360) at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(Ljava/lang/String;[Ljava/lang/String;Ljava/util/Properties;)[Ljava/lang/String;(DeployServiceImpl.java:313) at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(Lcom/sap/engine/services/dc/cm/deploy/DeploymentItem;ZLjava/lang/String;Ljava/util/Properties;)V(ApplicationDeployer.java:139) at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(Lcom/sap/engine/services/dc/cm/deploy/DeploymentItem;)V(InitialApplicationDeployer.java:138) at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(Lcom/sap/engine/services/dc/cm/deploy/DeploymentItem;)V(InitialGenericDeliveryImpl.java:57) at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(Lcom/sap/engine/services/dc/cm/deploy/DeploymentItem;Lcom/sap/engine/services/dc/cm/deploy/DeploymentData;)V(OnlineDeployProcessor.java:213) at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(Lcom/sap/engine/services/dc/cm/deploy/DeploymentItem;Lcom/sap/engine/services/dc/cm/deploy/DeploymentData;)V(BulkOnlineDeployProcessor.java:67) at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(Lcom/sap/engine/services/dc/cm/deploy/DeploymentItem;)V(AbstractDeployProcessor.java:282) at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(Lcom/sap/engine/services/dc/cm/deploy/DeploymentBatchItemVisitor;)V(DeploymentItemImpl.java:84) at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(Lcom/sap/engine/services/dc/cm/deploy/DeploymentBatchItem;Lcom/sap/engine/services/dc/cm/deploy/DeploymentData;Lcom/sap/engine/services/dc/cm/deploy/DeployListenersList;)V(AbstractDeployProcessor.java:100) at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run()V(DeployThread.java:39) at com.sap.engine.core.thread.execution.Executable.run(Z)V(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run()V(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run()V(CentralExecutor.java:328)   Locked ownable synchronizers: - None

[Former Member]

Hey Chris,

as soon as we configured the proxy on our NetWeaver this 10min delay was gone. We did not further dig into this topic since it was done for us.

Please don't ask where exactly the proxy was configured, it is quiet a while since we did that. I know it is somewhere in the NWA.

My guess is still that what is/was takeing so long is some XML-Validation.

[Former Member]

Hi Ingo,

I didn't get those log messages, so I guess you're one step further than me (or your server version is ;-).

Hopefully someone will enlighten us on our search.

Kind regards,

Helmut

[Former Member]

I've seen, that the difference in our approaches is, that I have bundled the jars in the Web Module (WebContent/WEB-INF/lib), not in that Web-Application which produces the EAR to deploy.

[Former Member]

Hey,

I'm trying exactly the same.

Further I was looking in the NWA for the Log-Files and found two interesting messages:

First is a WARING while deloyment:

[Server 01 13_0000000] (000) :Deploy Service's update operation has finished with warnings. CSN component of deployment item is [not available].
[
Warning occurred on server 0000000 during update of xxxxx.com/testear : JSF Application Test: schema_reference.4: Failed to read schema document 'http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>., file: xxxxx.com~test.war#faces-config.xml, column 16, line 6, severity: warning
CSN component of deployment item is not available]

So It seems, that my AS is not able to receive the xsd with the information how to process the JSF2.0.

Next to that WARNING I found an INFO:

Feb XX, XXXX X:XX:XX AM com.sun.faces.config.ConfigureListener contextInitialized
INFO: Initializing Mojarra (1.2_10) for context '/xxxxx.com~test'

My suggestion is that indeed there is a fallback to the build-in-implementation from SAP.

I haven't figured out yet how it is posible to let the AS find the 'http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd' nor how to force the AS to use the bundled jars.

Neither could I find out what is ment by "CSN component of deployment item is not available"

Greetings

Ingo