Loading...

XML

Word

Printable

Type: Task
Resolution: Done
Priority: Critical
Fix Version/s: jbossws-native-3.2.0
Affects Version/s: None
Component/s: jbossws-integration, jbossws-native
Labels:
None

Forum Reference:
http://community.jboss.org/message/285648#285648

Remoting 2.x is going away, possibly for the forthcoming JBossAS 5.1 release; Remoting 3 will not have an equivalent generic HTTP abstraction. Anything depending on Remoting 2 will break if it is not ported to some other situation.

blocks

JBWS-2739 Make OneWay operation non-blocking (client side)

Closed

JBWS-2679 Add support for compression for endpoints and clients

Closed

JBWS-2674 Restore implementation of javax.xml.ws.Endpoint

Closed

relates to

JBWS-2672 Make the JBoss Remoting property 'socketFactoryClassName' available to allow clients to specify the SocketFactory

Closed

Assignee:: Alessio Soldano

Reporter:: David Lloyd

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2009/02/24 2:21 PM

Updated:: 2020/09/14 5:21 AM

Resolved:: 2009/07/16 5:33 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates