March 2011 - jbossws-issues - Jboss List Archives

[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-3125) SOAP over JMS 1.0 support

by Alessio Soldano (JIRA)

SOAP over JMS 1.0 support ------------------------- Key: JBWS-3125 URL: https://jira.jboss.org/browse/JBWS-3125 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.4.1 Apache CXF 2.3 is coming with SOAP over JMS 1.0 support. We need to verify integration. See: http://cxf.apache.org/docs/soap-over-jms-10-support.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2709) Review JBossWS public api and provide online javadoc

by Alessio Soldano (JIRA)

Review JBossWS public api and provide online javadoc ---------------------------------------------------- Key: JBWS-2709 URL: https://jira.jboss.org/jira/browse/JBWS-2709 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 We should make the javadoc available online for api/spi meant to be public. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-3257) No class available with name 'org.jboss.security.plugins.JaasSecurityDomain'

by Richard Opalka (JIRA)

No class available with name 'org.jboss.security.plugins.JaasSecurityDomain' ---------------------------------------------------------------------------- Key: JBWS-3257 URL: https://issues.jboss.org/browse/JBWS-3257 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Fix For: jbossws-native-4.0 15:09:47,379 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."jaxws-jbws3182-service.sar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-jbws3182-service.sar".INSTALL: Failed to process phase INSTALL of deployment "jaxws-jbws3182-service.sar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_20] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] Caused by: java.lang.IllegalStateException: No class available with name 'org.jboss.security.plugins.JaasSecurityDomain' at org.jboss.msc.value.LookupClassValue.getValue(LookupClassValue.java:70) at org.jboss.msc.value.LookupClassValue.getValue(LookupClassValue.java:32) at org.jboss.msc.value.CachedValue.getValue(CachedValue.java:54) at org.jboss.msc.value.LookupConstructorValue.getValue(LookupConstructorValue.java:66) at org.jboss.msc.value.LookupConstructorValue.getValue(LookupConstructorValue.java:37) at org.jboss.msc.value.CachedValue.getValue(CachedValue.java:54) at org.jboss.msc.value.ConstructedValue.<init>(ConstructedValue.java:51) at org.jboss.as.service.ParsedServiceDeploymentProcessor.addService(ParsedServiceDeploymentProcessor.java:127) at org.jboss.as.service.ParsedServiceDeploymentProcessor.deploy(ParsedServiceDeploymentProcessor.java:102) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102) ... 4 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-3240) Rewrite tests relying on $JBOSS_HOME/server/default/tmp/jbossws folder existence

by Richard Opalka (JIRA)

Rewrite tests relying on $JBOSS_HOME/server/default/tmp/jbossws folder existence -------------------------------------------------------------------------------- Key: JBWS-3240 URL: https://issues.jboss.org/browse/JBWS-3240 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Fix For: jbossws-native-4.0 junit.framework.AssertionFailedError: Temp dir doesn't exist: /server/default/tmp/jbossws at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.test.ws.jaxws.samples.xop.doclit.XOPBase.testAttachmentpartSwap(XOPBase.java:157) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:23) at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:98) at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:107) at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:84) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2941) HTTP Proxy authentication for JBossWS-Native Web Service clients

by Thomas Lehmann (JIRA)

HTTP Proxy authentication for JBossWS-Native Web Service clients ---------------------------------------------------------------- Key: JBWS-2941 URL: https://jira.jboss.org/jira/browse/JBWS-2941 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Thomas Lehmann We need a possibility to access Web Service endpoints through an HTTP Proxy which needs client authentication. In our case it's BASIC authentication, but there are may other JBoss customers who want to have support for other authentication schemas like DIGEST or NTLM. There must be a way to set the Proxy settings, especially the Proxy credentials used for authentication (username, password), in some sort of meta data (using a Java API). See also support case https://support.redhat.com/jbossnetwork/restricted/caseDetail.html?caseId... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-3105) Review and fix AS IL maven dependencies

by Richard Opalka (JIRA)

Review and fix AS IL maven dependencies --------------------------------------- Key: JBWS-3105 URL: https://jira.jboss.org/browse/JBWS-3105 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-cxf-3.4.1, jbossws-native-3.4.1, jbossws-metro-3.4.1 I found some weirdness related to VirtualFile in AS IL. This blocked me to clean AS IL maven dependencies. We need to review AS IL dependencies and make them explicit i.e. to know which libraries we're exactly depending on. The result of this process should be VirtualFile weirdness fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-3199) AbstractServerConfig.toIPv6URLFormat throws java.net.UnknownHostException

by Alessio Soldano (JIRA)

AbstractServerConfig.toIPv6URLFormat throws java.net.UnknownHostException ------------------------------------------------------------------------- Key: JBWS-3199 URL: https://issues.jboss.org/browse/JBWS-3199 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Affects Versions: jbossws-native-3.4.1, jbossws-cxf-3.4.1 Reporter: Alessio Soldano Fix For: jbossws-native-4.0, jbossws-cxf-4.0 After applying the changes for IPv6 support, the AbstractServerConfig::toIPv6URLFormat method does a InetAddress.getByName(host) call that can throws UnknownHostException if the webserviceHost in the configuration can't be lookup. This needs to be changed or at least surrounded by a try-catch block as it's not robust (to be honest nothing even prevents the user from wanting a fancy hostname in there). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWS-3201) WSConsume does not generate operation fault in WSDL when the WS method throws java.lang.Exception.

by Marek Baluch (JIRA)

WSConsume does not generate operation fault in WSDL when the WS method throws java.lang.Exception. -------------------------------------------------------------------------------------------------- Key: JBWS-3201 URL: https://issues.jboss.org/browse/JBWS-3201 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.1.2 Reporter: Marek Baluch When we have the following WS: @WebService(name="BiddingService", targetNamespace="http://jboss.org/bidding") public class BiddingBackend { // ... @WebMethod(operationName = "makeBid") public Boolean makeBid(@WebParam(name = "itemName") String itemName, @WebParam(name = "offer") Integer offer) throws java.lang.Exception { // ... } } then the generated WSDL does not contain a fault in it's binding. It's as the method would not throw an Exception. If the method throws a descendant of java.lang.Exception then the resulting WSDL contains everything. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-3137) Support deploying http and jms endpoint in one deployment

by Jim Ma (JIRA)

Support deploying http and jms endpoint in one deployment --------------------------------------------------------- Key: JBWS-3137 URL: https://jira.jboss.org/browse/JBWS-3137 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.0.Beta2 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-3.4.1 When the jms endpoints is deployed with http endpoints in one war file, the WsTypeDeployer takes this deployment as "JAXWS_JSE" type . Hence the JMSDeploymentAspects will not be activated and process this mixed type deployment . JMSTransportTestCase is the test for this user case. The jms endpoints is not registered in registry so far. We can review our WSTypeDeployer and other JMSDAs to support this mixed type deployment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues March 2011