axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivan <xhh...@gmail.com>
Subject Re: Is there possible for 1.7.0 release ?
Date Thu, 28 Jul 2011 08:09:56 GMT
Hi, we got a good testing result for the 1.6.1-SNAPSHOT + listed revision
changes. So, is there a plan for 1.6.1 release ?
Thanks.

2011/7/26 Ivan <xhhsld@gmail.com>

> Hi, Geronimo is trying to switch to use 1.6.1-SNAPSHOT, while it looks that
> some codes are also required to merge from trunk, Could you help to merge
> the changes to 1.6.1-SNAPSHOT ? Thanks
>
> --->
> Revision: 1068985
> AXIS2-4952
> Scope dynamic ports to the instance of the service that did the
> addPort(...).  Add TDD Unit test and flag to revert to previous behavior of
> sharing dynamic ports across services.
>
> Revision: 1069659
> Message:
> AXIS2-4938
> Patch submitted by Katherine Sanders.  BindingProvider.getEndpointReference
> should put reference parameters from WSDL in returned EPR.
>
> Revision: 1069898
> AXIS2-4948
> Patch contributed by Katherine Sanders.  Wrong WSDL location returned by
> BindingProvider; was using the local filesystem path instead of the endpoint
> URL.
>
> Revision: 1075057
> Prevent index out of bounds exception, or any exception, from attempting to
> log.  Add TDD/UT for same.
>
> Revision: 1096530
> On JAX-WS Client, treat local exceptions (e.g. ConnectException) as a
> SOAPFault, driving the JAX-WS handler handleFault methods and throwing a
> SOAPFAultException back through the client invocation.  Also provide a
> property to revert to previous behavior of creating an empty message,
> driving the JAX-WS handler handleMessage methods, and throwing a
> WebServiceException back through the client invocation.
>
> Revision: 1096557
> Two changes in JAX-WS Endpoint implementation (1) Override
> setEndpointContext method, (2) Add logic to throw an exception if endpoint
> publishing is disabled by a property (publishing is enabled by default); per
> JSR-109 5.3.3 dynamically publishing endpoints in a server environment is
> non portable and should be disabled.  A server runtime can use the property
> to disabled dynamically publishing JAX-WS endpoints via Endpoint.publish
> methods.
>
> Revision: 1103336
> AXIS2-5021: Committed patch provided by Ivan (xuhaihong).
>
> Revision: 1136177
> AXIS2-5067: Committed patch provided by Ivan (xuhaihong), with minor
> changes. This implements the saveChanges method and calculates the correct
> content type for a SOAPMessage.
>
>
>
> 2011/7/13 Ivan <xhhsld@gmail.com>
>
>> Hi, devs, I just uploaded a patch for AXIS2-5023<https://issues.apache.org/jira/browse/AXIS2-5023>.
>> If possible, please help to review it first, as I am not quite confident for
>> the changes for this jira, although it seems to work now.
>> Thanks.
>>
>> 2011/7/12 Ivan <xhhsld@gmail.com>
>>
>>> OK, I forget to reply to Axis2 mail list again ...
>>>
>>>
>>> 2011/7/12 Ivan <xhhsld@gmail.com>
>>>
>>>>
>>>>
>>>> 2011/7/12 Andreas Veithen <andreas.veithen@gmail.com>
>>>>
>>>>> The changes for Neethi 3.0.x (including the three changes mentioned in
>>>>> your mail) should now be included in the latest 1.6.1-SNAPSHOT build.
>>>>> The release vote for Neethi 3.0.1 has started a couple of hours ago.
>>>>> Once that release is complete, we can switch to the Neethi 3.0.1
>>>>> release version on the 1.6 branch and Axis2 1.6.1 will be ready for
>>>>> release.
>>>>>
>>>>>    Thanks, Andreas, I will try to switch to Axis2 1.6.1-SNAPSHOT soon.
>>>>
>>>>
>>>>> Regarding the list of JIRA issues, if I understand this correctly, the
>>>>> Geronimo project has a sort of patching mechanism so that they are not
>>>>> on the critical path for the Geronimo release, which means that we
>>>>> have the time to review them properly and first apply them to the
>>>>> trunk, without delaying any Geronimo release. Can you confirm this?
>>>>>
>>>>
>>>>    Hmm, I would say that the patching mechanism used now is somewhat a
>>>> 'temporary' solution, and it is not expected to do that. Geronimo needs to
>>>> bundle the axis2 components, that gave us a chance to modify codes.
>>>>    We do hope that those patches could be reviewed and included in Axis2
>>>> code base. And yes, they work well now,  but it is better to have your Axis2
>>>> experts' view for them. Also, from other sides, most of them are related
to
>>>> JAX-WS 2.2 support. I guess that they are also important for Axis2 ;-)
>>>>    Anyway, it depends on your schedule, and your guys really helped us a
>>>> lot in the past.
>>>>    Thanks.
>>>>
>>>>>
>>>>> Andreas
>>>>>
>>>>> On Sun, Jul 10, 2011 at 15:58, Ivan <xhhsld@gmail.com> wrote:
>>>>> > Hi, Axis2 devs, any thought to port those listed changes to 1.6
>>>>> branch ?
>>>>> > Thanks.
>>>>> >
>>>>> > 2011/7/8 Ivan <xhhsld@gmail.com>
>>>>> >>
>>>>> >> Just add the geronimo mail address.
>>>>> >>
>>>>> >> 2011/7/8 Ivan <xhhsld@gmail.com>
>>>>> >>>
>>>>> >>> Hi, the initial reason for moving to 1.7.0-SNAPSHOT is for
the
>>>>> Policy
>>>>> >>> support, the changes are list below. If they could be ported
to 1.6
>>>>> branch,
>>>>> >>> we are fine to try to turn to 1.6 branch.
>>>>> >>> Also, understand that you guys are busy with some other
stuffs,
>>>>> will be
>>>>> >>> very appreciated if those web services patches could be
reviewed
>>>>> and
>>>>> >>> included in the 1.6 branch.  I pasted the Jira list in the
end of
>>>>> the mail.
>>>>> >>> The initial thread could be found
>>>>> >>> http://www.mail-archive.com/java-dev@axis.apache.org/msg06438.html
>>>>> >>> Thanks.
>>>>> >>> --->
>>>>> >>> Revision: 1090457
>>>>> >>> Author: veithen
>>>>> >>> Date: 5:36:59 AM, Saturday, April 09, 2011
>>>>> >>> Message:
>>>>> >>> Exclude the transitive Woodstox dependency from Neethi.
Otherwise
>>>>> we will
>>>>> >>> end up with two versions of Woodstox.
>>>>> >>> ----
>>>>> >>> Modified : /axis/axis2/java/core/trunk/modules/parent/pom.xml
>>>>> >>> Revision: 1090429
>>>>> >>> Author: veithen
>>>>> >>> Date: 4:19:38 AM, Saturday, April 09, 2011
>>>>> >>> Message:
>>>>> >>> Neethi now supports DOM elements. Therefore we don't need
to
>>>>> convert DOM
>>>>> >>> elements to stream any more. Alos, DOM2Writer seems to have
a bug
>>>>> that
>>>>> >>> causes processing of some policies to fail.
>>>>> >>> ----
>>>>> >>> Modified :
>>>>> >>>
>>>>> /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/util/PolicyUtil.java
>>>>> >>> Revision: 1089989
>>>>> >>> Author: veithen
>>>>> >>> Date: 4:27:37 AM, Friday, April 08, 2011
>>>>> >>> Message:
>>>>> >>> Updated Neethi dependency and fixed PolicyUtil such that
it
>>>>> supports all
>>>>> >>> WS-Policy namespaces supported by Neethi.
>>>>> >>> ----
>>>>> >>> Modified :
>>>>> >>>
>>>>> /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/util/PolicyUtil.java
>>>>> >>> Modified : /axis/axis2/java/core/trunk/modules/parent/pom.xml
>>>>> >>> <---
>>>>> >>> Jira list:
>>>>> >>>         (AXIS2-5062) Connection is not released while using
JAXWS
>>>>> client
>>>>> >>> API
>>>>> >>> (AXIS2-5039) Override the SOAPAction from the SOAPMessage
MIME
>>>>> header if
>>>>> >>> it is explicitly configured later
>>>>> >>> (AXIS2-5023) Ambigious use of isElementData in the Block
interface
>>>>> >>> (AXIS2-5022) Support addressing meta data with policy 1.5
framework
>>>>> >>> (AXIS2-5040) Ignore the methods while no webmethod annotation
and
>>>>> no
>>>>> >>> webservice annotation on the declaring class
>>>>> >>> (AXIS2-5034) Incorrect exception name is used for fault
message
>>>>> while
>>>>> >>> creating AxisService from WSDL
>>>>> >>> (AXIS2-5001) SOAPMessage.getSOAPHeaders() return null while
no
>>>>> headers in
>>>>> >>> the soap envelope
>>>>> >>> (AXIS2-4996) Exclude content-length header while chunked
is enabled
>>>>> >>> 2011/7/8 Andreas Veithen <andreas.veithen@gmail.com>
>>>>> >>>>
>>>>> >>>> Ivan,
>>>>> >>>>
>>>>> >>>> There are no plans for a 1.7.0 release, but we can do
a 1.6.1
>>>>> >>>> maintenance release. For that you need to let us know
which
>>>>> changes
>>>>> >>>> you want to see included in that release, so that we
can merge
>>>>> them to
>>>>> >>>> the 1.6 branch. The goal is to make Geronimo work with
>>>>> 1.6.1-SNAPSHOT.
>>>>> >>>> Once that is done, we can create the 1.6.1 release anytime
you
>>>>> want.
>>>>> >>>>
>>>>> >>>> Andreas
>>>>> >>>>
>>>>> >>>> On Fri, Jul 8, 2011 at 04:31, Ivan <xhhsld@gmail.com>
wrote:
>>>>> >>>> > Hi, Axis2 devs,
>>>>> >>>> >     Geronimo bundles the some Axis2 components
of
>>>>> 1.7.0-SNAPSHOT, and
>>>>> >>>> > it is
>>>>> >>>> > obviously that we could not release these bundles
with snapshot.
>>>>> I am
>>>>> >>>> > wondering that whether Axis2 could have chance
to have a 1.7.0
>>>>> >>>> > release, or
>>>>> >>>> > maybe a milestone release ?
>>>>> >>>> > thanks.
>>>>> >>>> > --
>>>>> >>>> > Ivan
>>>>> >>>> >
>>>>> >>>>
>>>>> >>>>
>>>>> ---------------------------------------------------------------------
>>>>> >>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>>>> >>>> For additional commands, e-mail: java-dev-help@axis.apache.org
>>>>> >>>>
>>>>> >>>
>>>>> >>>
>>>>> >>>
>>>>> >>> --
>>>>> >>> Ivan
>>>>> >>
>>>>> >>
>>>>> >>
>>>>> >> --
>>>>> >> Ivan
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Ivan
>>>>> >
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Ivan
>>>>
>>>
>>>
>>>
>>> --
>>> Ivan
>>>
>>
>>
>>
>> --
>> Ivan
>>
>
>
>
> --
> Ivan
>



-- 
Ivan

Mime
View raw message