[jboss-dev-forums] [JBoss AS 7 Development] - Jboss 7.1.1 as having problems with Picketlink 2.0.3-Final for CXF endpoints

biswa mishra [https://community.jboss.org/people/mishra900] created the discussion "Jboss 7.1.1 as having problems with Picketlink 2.0.3-Final for CXF endpoints" To view the discussion, visit: https://community.jboss.org/message/779019#779019 -------------------------------------------------------------- I am trying to develop  apache CXF web service endpoints  using Picketlink 2.0.3-Final.jar   and deploying in Jboss 7.1.1 AS. I have updated Jboss 7.1.1 As   org.picketlink  modules with Picketlink 2.0.3-Final.jars as mentioned in some of the links in forum . all the examples are getting deployed and working as expected . I am planning to deploy my CXF web services as  .war file in Jboss Standalone deployment .  i have added  <extension module="org.picketlink"/> in the standalone.xml So it means , if i will deploy *.war file , i donot need to add picketlink 2.0.3-final related jars in to web-inf\lib folder , but looks like WAR file got deployed but not started .... Hence i have added picketlink 2.0.3-final related jars in to web-inf\lib folder , and redeployed , now WAR file got deployed and started also and i am able to see  CXF endpoints started also like below :   21:30:41,029 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service id=org.picketlink.identity.federation.core.wstrust.PicketLinkSTS address=http://localhost:8080/security-token-service/PicketLinkSTS implementor=org.picketlink.identity.federation.core.wstrust.PicketLinkSTS invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker serviceName={urn:picketlink:identity-federation:sts}PicketLinkSTS portName={urn:picketlink:identity-federation:sts}PicketLinkSTSPort wsdlLocation=null mtomEnabled=false 21:30:41,044 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service id=org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP address=http://localhost:8080/security-token-service/SOAPSAMLXACMLPDP implementor=org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker serviceName={urn:picketlink:identity-federation:pdp}SOAPSAMLXACMLPDP portName={urn:picketlink:identity-federation:pdp}SOAPSAMLXACMLPort wsdlLocation=null mtomEnabled=false *But Immediately it got failed throwing  the below exception like PL00075: File could not be located :policyConfig.xml* 09:31:43,712 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {urn:picketlink:identity-federation:sts}PicketLinkSTS from WSDL: WEB-INF/wsdl/PicketLinkSTS.wsdl 09:31:50,163 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/security-token-service/PicketLinkSTS 09:31:52,303 INFO  [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/C:/jboss/jboss-as-7.1.0.Final/standalone/data/wsdl/security-token-service.war/PicketLinkSTS.wsdl 09:31:53,358 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."security-token-service.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."security-token-service.war".INSTALL: Failed to process phase INSTALL of deployment "security-token-service.war"        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_29]        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_29]        at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_29] Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: PL00075: File could not be located :policyConfig.xml        at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.newInstance(NonSpringBusHolder.java:174)        at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:96)        at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:113)        at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:66)        at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:81)        at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]        ... 5 more Caused by: java.lang.IllegalStateException: PL00075: File could not be located :policyConfig.xml        at org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP.getPDP(SOAPSAMLXACMLPDP.java:115)        at org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP.<init>(SOAPSAMLXACMLPDP.java:75)        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.6.0_29]        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [rt.jar:1.6.0_29]        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [rt.jar:1.6.0_29]        at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [rt.jar:1.6.0_29]        at java.lang.Class.newInstance0(Class.java:355) [rt.jar:1.6.0_29]        at java.lang.Class.newInstance(Class.java:308) [rt.jar:1.6.0_29]        at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.newInstance(NonSpringBusHolder.java:170)        ... 10 more   This looks to me more on support issues with jboss 7.1.1 AS with Picketlink using CXF endpoints ... , any tips from the Jboss Security team will be really helpful ..  Even i have tried with Jboss 7.1.0 As  using Picketlink 2.0.2 -final build , same issue persists  Thanks, Biswa -------------------------------------------------------------- Reply to this message by going to Community [https://community.jboss.org/message/779019#779019] Start a new discussion in JBoss AS 7 Development at Community [https://community.jboss.org/choose-container!input.jspa?contentType=1&...]