September 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3233) jbossws/services web view shows wrong port

by Steve Cassidy (JIRA)

jbossws/services web view shows wrong port ------------------------------------------ Key: JBWS-3233 URL: https://issues.jboss.org/browse/JBWS-3233 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss 4.3.0 CP08 running on RHEL 5 (5.6) - kernel version 2.6.18-238.1.1.el5 Reporter: Steve Cassidy Priority: Minor We have a JBoss installation where we have disabled port 8080 for security reasons (in jboss-web.deployer/server.xml). We listen on port 8443 on SSL and 8009 for AJP. However if I look at the web view of Web services (jbossws/services context path in a web browser) this shows the WSDLs of the services but the links are still showing ":8080" as the listening port (even though JBoss is not listening on port 8080). I undersdtand that it is possible to have JBoss listeing on multiple ports so hence it would not be clear what would be put here instead but for a simple example where Jboss is listening on port 8443 and not 8080 it seems wrong that 8080 is shown and not 8443. I understand that this is not the highetst priority issue ever but to make the product consistent could you please look at this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBWS-3288) Double slash in published endpoint address

by Alessio Soldano (JIRA)

Double slash in published endpoint address ------------------------------------------ Key: JBWS-3288 URL: https://issues.jboss.org/browse/JBWS-3288 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.1 Reporter: Alessio Soldano http://community.jboss.org/message/603293 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBWS-3268) REPLACE_WITH_ACTUAL_URL does not work for more than one Port in a WSDL

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3268?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3268: ---------------------------------- Component/s: (was: ws-addressing) > REPLACE_WITH_ACTUAL_URL does not work for more than one Port in a WSDL > ---------------------------------------------------------------------- > > Key: JBWS-3268 > URL: https://issues.jboss.org/browse/JBWS-3268 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Mustafa Musaji > > If you have a WSDL that contains more than one port and want the wsdl address location to be changed as per the jboss-beans.xml file this does not work. Only the first port will have it's location changed. The second will remain as REPLACE_WITH_ACTUAL_URL value and no error displayed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3259) Unbale to deploy WAR+VDB into JBoss AS 5.1.0

by Hilal Mushtaque (JIRA)

Unbale to deploy WAR+VDB into JBoss AS 5.1.0 -------------------------------------------- Key: JBWS-3259 URL: https://issues.jboss.org/browse/JBWS-3259 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Hilal Mushtaque Attachments: TestWS.zip Hi I am getting below given exception when I tried to deploy the generated war into JbossAS 5.1.0 along with the VDB file. I am using Teiid Designer 7.3.0 to generate war, I created a project having a single table with three fields of string type and generated the input/output xsd's, view and xmi's. Then I created a vdb configured it using the translator/jndi and generated the war & deployed the war. Then I deployed the war and vdb both on to the Jboss AS. (attached the project as well) ############################## org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/D:/jboss-5.1.0.GA/server/default/deploy/TestVDB.war/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.RuntimeException: Cannot publish wsdl to: D:\jboss-5.1.0.GA\server\default\data\wsdl\TestVDB.war\TestVDB.wsdl at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:104) at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.publishContractToFilesystem(EndpointImpl.java:84) at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:66) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:238) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:481) at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:112) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:110) at org.jboss.webservices.integration.deployers.WSDeploymentAspectDeployer.internalDeploy(WSDeploymentAspectDeployer.java:107) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) ... 29 more Caused by: java.io.IOException: Could not find WEB-INF/wsdl/EPCSchema_Input.xsd in the additional metadatafiles! at org.jboss.wsf.framework.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:121) at org.jboss.ws.core.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:181) at org.jboss.ws.core.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:208) at org.jboss.ws.core.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:208) at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:91) ... 38 more 07:13:54,681 INFO [TomcatDeployment] deploy, ctxPath=/jbossws 07:13:54,806 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console 07:13:56,869 INFO [PROCESSOR] Clearing prepared plan cache 07:13:56,869 INFO [PROCESSOR] Clearing the resultset cache for vdb EPC1372VDB.1 07:13:56,900 INFO [RUNTIME] VDB "EPC1372VDB.1[DataPersistor[], EPCSchema[EPCSchema/oracle/dcorp], GetXml[GetXML/file/epcfile]]" deployed in active state. 07:13:56,916 INFO [PROCESSOR] Clearing prepared plan cache 07:13:56,916 INFO [PROCESSOR] Clearing the resultset cache for vdb EPC1373VDB.1 07:13:56,916 INFO [RUNTIME] VDB "EPC1373VDB.1[DataPersistor[], TRUNC_MY_SCHEMA[TRUNC_MY_SCHEMA/oracle/dcorp], EPCSchema[EPCSchema/oracle/dcorp], GetXml[GetXml/file/epcfile]]" deployed in active state. 07:13:56,916 INFO [PROCESSOR] Clearing prepared plan cache 07:13:56,916 INFO [PROCESSOR] Clearing the resultset cache for vdb EPC1374VDB.1 07:13:56,916 INFO [RUNTIME] VDB "EPC1374VDB.1[DataPersistor[], TRUNC_MY_SCHEMA[TRUNC_MY_SCHEMA/oracle/dcorp], GetXml[GetXml/file/epcfile], EPCSchema[EPCSchema/oracle/dcorp]]" deployed in active state. 07:13:56,931 INFO [PROCESSOR] Clearing prepared plan cache 07:13:56,931 INFO [PROCESSOR] Clearing the resultset cache for vdb TestVDB.1 07:13:56,931 INFO [RUNTIME] VDB "TestVDB.1[EPCSchema_Output_View[], EPCSchema[EPCSchema/oracle/dcorp], EPCSchema_Input[], EPCSchema_WS[], EPCSchema_Output[]]" deployed in active state. 07:13:57,072 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS IN ERROR: Deployment "vfszip:/D:/jboss-5.1.0.GA/server/default/deploy/TestVDB.war/" is in error due to the following reason(s): java.io.IOException: Could not find WEB-INF/wsdl/EPCSchema_Input.xsd in the additional metadatafiles! ############################## Kindly revert ASAP -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-3358) Restore @EJB & @Resource injection on JAXWS components on AS7

by Richard Opalka (JIRA)

Restore @EJB & @Resource injection on JAXWS components on AS7 ------------------------------------------------------------- Key: JBWS-3358 URL: https://issues.jboss.org/browse/JBWS-3358 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3352) Refactor and enable related tests

by Jim Ma (JIRA)

Refactor and enable related tests ---------------------------------- Key: JBWS-3352 URL: https://issues.jboss.org/browse/JBWS-3352 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Jim Ma Assignee: Jim Ma -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3346) Add EndpointType and remove the context root from service

by Jim Ma (JIRA)

Add EndpointType and remove the context root from service ---------------------------------------------------------- Key: JBWS-3346 URL: https://issues.jboss.org/browse/JBWS-3346 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-3349) Remove checkers which relies on DeplymentType in stack agnostic DAs

by Jim Ma (JIRA)

Remove checkers which relies on DeplymentType in stack agnostic DAs --------------------------------------------------------------------- Key: JBWS-3349 URL: https://issues.jboss.org/browse/JBWS-3349 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3215) Review the way testsuite is run using Maven

by Alessio Soldano (JIRA)

Review the way testsuite is run using Maven ------------------------------------------- Key: JBWS-3215 URL: https://issues.jboss.org/browse/JBWS-3215 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-cxf-4.0 Instead of requiring us/users to do what follows to run the testsuite > mvn -Ptestsuite,jbossXYZ -DjbossXYZ.home=.. test we should probably be able to support something like: > mvn -DjbossXYZ.home=.. integration-test The move of non-unit tests to integration-test phase is being done as part of JBWS-3210, the rest is probably a matter of implicitly getting the target container from the jbossXYZ.home defined in the env and removing the testsuite profile / automatically enabling the testsuite modules, which just have integration tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
7
0 / 0

[JBoss JIRA] Created: (JBWS-3355) Launch of *.sh scripts from path with space does not work

by Alessio Soldano (JIRA)

Launch of *.sh scripts from path with space does not work --------------------------------------------------------- Key: JBWS-3355 URL: https://issues.jboss.org/browse/JBWS-3355 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-cxf-4.0 See https://issues.jboss.org/browse/AS7-1740 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues September 2011