-
1. Re: WSRP error
julien1 Aug 2, 2006 11:35 AM (in response to danny_hon)Hi Danny, check you have portal-wsrp.sar in jboss-portal.sar
-
2. Re: WSRP error
danny_hon Aug 2, 2006 12:15 PM (in response to danny_hon)Interestingly the portal-wsrp.sar is not in the jboss-portal.sar. I built the code from source. I can see that portal-wsrp.sar was generated in the output/lib, but not include it in the final jboss-portal.sar. How can I include it in the final sar file?
-
3. Re: WSRP error
danny_hon Aug 2, 2006 1:39 PM (in response to danny_hon)I looked at the build scripts from JBoss_Portal_2_4_CR2. The scripts may be old, as they don't have any code that includes the portal-wsrp.sar.
Ok, instead of building it from source, I downloaded the one from JBoss site. However, it gives me deployment error:
12:27:19,310 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@e020f888 { url=file:/C:/jboss/jboss-4.0.4.GA/server/jbptest-download/deploy/apps/jbo
ss-portal.sar/portal-wsrp.sar/portal-wsrp.jse }
deployer: org.jboss.ws.server.WebServiceDeployerNestedJSE@834af6
status: Deployment FAILED reason: Could not create deployment: file:/C:/jboss/jboss-4.0.4.GA/server/jbptest-download/t
mp/deploy/portal-wsrp.war; - nested throwable: (org.jboss.ws.metadata.wsdl.WSDLException: WSDLException (at /wsdl:defini
tions/import/wsdl:definitions/import/wsdl:definitions/wsdl:types/schema/schema): faultCode=OTHER_ERROR: An error occurre
d trying to resolve schema referenced at 'http://www.w3.org/2001/xml.xsd', relative to 'file:/C:/jboss/jboss-4.0.4.GA/se
rver/jbptest-download/tmp/deploy/portal-wsrp-exp.war/WEB-INF/wsdl/wsrp_v1_types.xsd'.: Cannot access imported wsdl [http
://www.w3.org/2001/xml.xsd], Server returned HTTP response code: 503 for URL: http://www.w3.org/2001/xml.xsd: java.lang.
RuntimeException: Cannot access imported wsdl [http://www.w3.org/2001/xml.xsd], Server returned HTTP response code: 503
for URL: http://www.w3.org/2001/xml.xsd
at org.jboss.ws.metadata.wsdl.WSDLDefinitionsFactory$WSDLLocatorImpl.getImportInputSource(WSDLDefinitionsFactory
.java:310)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:740)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:830)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(WSDLReaderImpl.java:620)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseTypes(WSDLReaderImpl.java:583)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(WSDLReaderImpl.java:302)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2133)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(WSDLReaderImpl.java:450)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(WSDLReaderImpl.java:294)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2133)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseImport(WSDLReaderImpl.java:450)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(WSDLReaderImpl.java:294)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2133)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2125)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2150)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2171)
at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2201)
at org.jboss.ws.metadata.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:144)
at org.jboss.ws.metadata.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:273)
at org.jboss.ws.metadata.JSR109ServerMetaDataBuilder.buildMetaData(JSR109ServerMetaDataBuilder.java:111)
at org.jboss.ws.server.WebServiceDeployerJSE.createWebServicesMetaData(WebServiceDeployerJSE.java:189)
at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:103)
at org.jboss.ws.server.WebServiceDeployerJSE.create(WebServiceDeployerJSE.java:66)
........
I am behind a firewall, but it doesn't work even if I specified http.proxyHost in the JAVA_OPTS. Any ideas how can I get pass this issue? -
4. Re: WSRP error
claprun Aug 2, 2006 2:05 PM (in response to danny_hon)You can build and deploy the WSRP service from the source distribution:
cd wsrp; ant deploy;
The other issue arises because you are not connected to the internet or behind a firewall/proxy. This is a known issue with JBoss WS. To fix the issue, please upgrade to JBoss WS 1.0.2.GA or later.
See http://wiki.jboss.org/wiki/Wiki.jsp?page=WSRP_UpdateJBossWS on our wiki for more details. -
5. Re: WSRP error
danny_hon Aug 2, 2006 4:53 PM (in response to danny_hon)Thank you. Both the build and the WSRP are working now.
-
6. Re: WSRP error
danny_hon Aug 4, 2006 11:26 AM (in response to danny_hon)I just checked out 2.4.0 CR3 code. The main build was successful, and created the jboss-portal.sar. However, the WSRP build failed. Here is the error.
$ build.sh deploy
build.sh: *WARNING* Ignoring environment value for $ANT_HOME
build.sh: Executing: /cygdrive/d/opensource/jboss-portal-2.4-CR3/jboss-portal-2.4/tools/bin/ant -logger org.apache.tools.ant.NoBannerLogger deploy
Buildfile: build.xml
_buildmagic:init:
Trying to override old definition of task property
configure:
Overriding previous definition of reference to jboss.test.classpath
Overriding previous definition of reference to apache.ant.classpath
BUILD FAILED
D:\opensource\jboss-portal-2.4-CR3\jboss-portal-2.4\wsrp\build.xml:267: org.codehaus.cargo.container.ContainerException: Failed to deploy to [http://localhost:8080/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=undeploy&argType=java.net.URL&arg0=file:D%3A%5Copensource%5Cjboss-portal-2.4-CR3%5Cjboss-portal-2.4%5Cwsrp%5Coutput%5Clib%5Cportal-wsrp.sar]
Total time: 3 seconds
Any ideas why? -
7. Re: WSRP error
claprun Aug 4, 2006 11:48 AM (in response to danny_hon)Did you checked out the code from CVS or downloaded the source release?
-
8. Re: WSRP error
danny_hon Aug 4, 2006 11:59 AM (in response to danny_hon)I checked out from CVS, tag is "JBoss_Portal_2_4_0_CR3".
-
9. Re: WSRP error
claprun Aug 4, 2006 12:25 PM (in response to danny_hon)There is indeed an error in the WSRP build. This has now been fixed in CVS. Thanks for catching it.