March 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9108) Base64 outputstream not flushed

by Heiko Braun (JIRA)

Base64 outputstream not flushed ------------------------------- Key: JBAS-9108 URL: https://issues.jboss.org/browse/JBAS-9108 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Affects Versions: 7.0.0.Beta1 Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.0.0.Beta2 ${subject} leads to missing padding characters. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBJCA-537) AdminObject must be considered when activating

by Jesper Pedersen (JIRA)

AdminObject must be considered when activating ---------------------------------------------- Key: JBJCA-537 URL: https://issues.jboss.org/browse/JBJCA-537 Project: IronJacamar Issue Type: Bug Components: Standalone Affects Versions: 1.0.0.Beta4 Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta5 Consider admin objects in addition to connection factory when activating a deployment -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9166) modifySOAPAddress = true ends up rewriting WSDLS for WebServiceClient code as well

by borfnorton22 borfnorton22 (JIRA)

modifySOAPAddress = true ends up rewriting WSDLS for WebServiceClient code as well ---------------------------------------------------------------------------------- Key: JBAS-9166 URL: https://issues.jboss.org/browse/JBAS-9166 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 6.0.0.Final Environment: Linux x64, Java 6 Reporter: borfnorton22 borfnorton22 Assignee: Alessio Soldano Fix For: 6.1.0 We recent upgraded from Jboss 4.22 to Jboss 6. The code I am describing below works fine on 4.2.2. a) We have a JAX-WS generated client b) The generated client code is configured to talk to a remote webservice and it calls a method on it as follows. URL url = new URL("http://bass01.stage.fishing89k41.com:80/Netter/NetterSyncQ.nsf/NetterWS?O..."); NetterService netterService = new NetterService(url); netterService.getNetterServicePort().isNetAvailable("someNetName"); The remote web-services WSDL exposes its service endpoint address as follows: <service name="NetterService"> <port binding="impl:NetterServicePortSoapBinding" name="NetterServicePort"> <wsdlsoap:address location="http://bass01.stage.fishing89k41.com:80/Netter/NetterSyncQ.nsf/NetterWS?O..."/> </port> </service> c) When this is running on Jboss 4.2.2 it works fine and has for quite some time. When the code executes on our JB6 server we see this is the logs which is absolutely bizzarre! Something in JB6 (cxf AddressRewritingEndpointInfo) is re-writing the hostname portion of the endpoint out client needs to talk to to a different host. This totally fails as when it trys to make a call we get a 404. 11:02:38,377 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] Creating Service {urn:DefaultNamespace}NetterService from WSDL: http://bass01.stage.fishing89k41.com:80/Netter/NetterSyncQ.nsf/NetterWS?O... 11:02:38,378 INFO [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] Setting new service endpoint address in wsdl: http://ws-stage.fishing89k41.com/Netter/NetterSyncQ.nsf/NetterWS 11:02:38,394 INFO [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] Setting new service endpoint address in wsdl: http://ws-stage.fishing89k41.com/Netter/NetterSyncQ.nsf/NetterWS 11:02:38,406 WARN [org.apache.cxf.phase.PhaseInterceptorChain] Interceptor for {urn:DefaultNamespace}NetterService#{urn:DefaultNamespace}isNetAvailable has thrown exception, unwinding now: org.apache.cxf.interceptor.Fault: Could not send Message. at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:64) [:2.3.1] at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255) [:2.3.1] at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:516) [:2.3.1] at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313) [:2.3.1] at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265) [:2.3.1] at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) [:2.3.1] at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124) [:2.3.1] at $Proxy302.isNetAvailable(Unknown Source) at some.service.SomeService. We edited this file: deployers/jbossws.deployer/META-INF/stack-agnostic-jboss-beans.xml and turned this OFF (rewrite to false) <property name="modifySOAPAddress">false</property> Once we did this the above rewrite went away, however isn't this a bug?? The documentation @ http://community.jboss.org/wiki/JBossWS-UserGuide under (Address Rewrite). It states this configuration is for deployed services. This is not a deployed service but a ws client. We are seeing this do rewrites for endpoints defined in remotely retrieved WSDLS for WebServiceClient code.....as shown above. @ see http://community.jboss.org/thread/164507 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-524) create a classloader spi for jdbc adapters

by Stefano Maestri (JIRA)

create a classloader spi for jdbc adapters ------------------------------------------ Key: JBJCA-524 URL: https://issues.jboss.org/browse/JBJCA-524 Project: IronJacamar Issue Type: Feature Request Components: JDBC Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 1.0.0.Beta5 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBJCA-536) Create a JMX view of a datasource

by Jesper Pedersen (JIRA)

Create a JMX view of a datasource --------------------------------- Key: JBJCA-536 URL: https://issues.jboss.org/browse/JBJCA-536 Project: IronJacamar Issue Type: Task Components: Deployer Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Beta5 Create a simple JMX view of a datasource -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-509) XA Recovery

by Jesper Pedersen (JIRA)

XA Recovery ----------- Key: JBJCA-509 URL: https://issues.jboss.org/browse/JBJCA-509 Project: IronJacamar Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Stefano Maestri Fix For: 1.0.0.Beta5 Implement XA recovery based on the existing implementation described at https://community.jboss.org/wiki/XARecoveryinJCA -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-6519) JCA / XAResourceRecovery

by Jesper Pedersen (JIRA)

JCA / XAResourceRecovery ------------------------ Key: JBAS-6519 URL: https://jira.jboss.org/jira/browse/JBAS-6519 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: JBossAS-5.1.0.Beta1 Add support for org.jboss.tm.XAResourceRecovery in the JCA layer -- 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

15 years, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (JBJCA-535) Only activate enabled datasources

by Jesper Pedersen (JIRA)

Only activate enabled datasources --------------------------------- Key: JBJCA-535 URL: https://issues.jboss.org/browse/JBJCA-535 Project: IronJacamar Issue Type: Bug Components: Deployer Affects Versions: 1.0.0.Beta4 Reporter: Jesper Pedersen Assignee: Jesper Pedersen Priority: Minor Fix For: 1.0.0.Beta5 Only enabled datasources should be activated -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-515) code generation improvement

by Jeff Zhang (JIRA)

code generation improvement ---------------------------- Key: JBJCA-515 URL: https://issues.jboss.org/browse/JBJCA-515 Project: IronJacamar Issue Type: Task Components: Code Generator Affects Versions: 1.0.0.Beta4 Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Beta5 update the template for ConnectionFactoryImpl to include ManagedConnectionFactory And use the ConnectionManager to get connections. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBJCA-530) define a ConnectionFactory class in the management api package

by Jeff Zhang (JIRA)

define a ConnectionFactory class in the management api package --------------------------------------------------------------- Key: JBJCA-530 URL: https://issues.jboss.org/browse/JBJCA-530 Project: IronJacamar Issue Type: Task Components: Management Affects Versions: 1.0.0.Beta4 Reporter: Jeff Zhang Assignee: Jeff Zhang Fix For: 1.0.0.Beta5 A ManagedConnectionFactory doesn't have a JNDI name. Will put JNDI name into ConnectionFactory Plus the Pool / PoolConfiguration also belongs to the ConnectionFactory, so CF - MCF - Pool - PoolConfiguration Also will refactor rhq plugin code to match it -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2011