June 2011 - jbossws-issues - Jboss List Archives

[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] 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-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-3211) Enable AS7 version checks in our test suite

by Richard Opalka (JIRA)

Enable AS7 version checks in our test suite ------------------------------------------- Key: JBWS-3211 URL: https://issues.jboss.org/browse/JBWS-3211 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-3234) JNDI over RMI not supported on AS7 yet

by Richard Opalka (JIRA)

JNDI over RMI not supported on AS7 yet -------------------------------------- Key: JBWS-3234 URL: https://issues.jboss.org/browse/JBWS-3234 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 <opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :( <opalka> wolfc, dmlloyd in the config I see the following ports defined <opalka> --- <opalka> <socket-binding name="jndi" port="1099"/> <opalka> <socket-binding name="jmx-connector-registry" port="1090"/> <opalka> <socket-binding name="jmx-connector-server" port="1091"/> <opalka> --- <dmlloyd> we don't do JNDI over RMI anymore <dmlloyd> that listing is an error <opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to? <opalka> dmlloyd, or we'll be doing JNDI over different binary protocol? <dmlloyd> no, we will be able to, it'll just work somewhat differently <opalka> dmlloyd, ok, I'm excluding the tests then ... <opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment? <dmlloyd> not that I'm aware of, it's just an outstanding task <dmlloyd> remote invocation is not planned to be covered in next months' beta release <opalka> dmlloyd, ok, thx for info ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-3316) i18n logging message

by Jim Ma (JIRA)

i18n logging message -------------------- Key: JBWS-3316 URL: https://issues.jboss.org/browse/JBWS-3316 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 Internationalize logging message with jboss logging 3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-3324) Implement service-ref/wsdl-override parsing

by Richard Opalka (JIRA)

Implement service-ref/wsdl-override parsing ------------------------------------------- Key: JBWS-3324 URL: https://issues.jboss.org/browse/JBWS-3324 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[22,5] Message: Unexpected element 'wsdl-override' encountered at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109) at org.jboss.metadata.parser.ee.ServiceReferenceMetaDataParser.parse(ServiceReferenceMetaDataParser.java:127) at org.jboss.metadata.parser.ee.EnvironmentRefsGroupMetaDataParser.parse(EnvironmentRefsGroupMetaDataParser.java:81) at org.jboss.metadata.parser.jbossweb.JBossWebMetaDataParser.parse(JBossWebMetaDataParser.java:108) at org.jboss.as.web.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:64) ... 6 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-3323) Get rid of WebServiceDeclaration & WebServiceDeployment spi abstractions

by Richard Opalka (JIRA)

Get rid of WebServiceDeclaration & WebServiceDeployment spi abstractions ------------------------------------------------------------------------ Key: JBWS-3323 URL: https://issues.jboss.org/browse/JBWS-3323 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.0, jbossws-cxf-4.0 We need to remove the following 2 abstractions from our SPI: org.jboss.wsf.spi.deployment.integration.WebServiceDeclaration org.jboss.wsf.spi.deployment.integration.WebServiceDeployment because it's just used in ASIL side source code. The abstractions should move to ASIL instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3284) Add WS-SecurityPolicy testcases without Spring descriptors

by Alessio Soldano (JIRA)

Add WS-SecurityPolicy testcases without Spring descriptors ---------------------------------------------------------- Key: JBWS-3284 URL: https://issues.jboss.org/browse/JBWS-3284 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0.0.Beta1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3302) Enable WS-Security UT JAAS integration for policy-first scenarios

by Alessio Soldano (JIRA)

Enable WS-Security UT JAAS integration for policy-first scenarios ----------------------------------------------------------------- Key: JBWS-3302 URL: https://issues.jboss.org/browse/JBWS-3302 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-4.0 With JBWS-3284 we now have WS-Security Policy samples working without Spring descriptors. Now, we need to extend the JAAS username token integration to the policy-first / non-spring scenarios. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues June 2011