Davanum Srinivas wrote:
Folks,
I've moved the dom stuff out of the way and made the saaj build
optional. Now looking at test failures in JDK1.5
thanks,
-- dims
Hey thanks, this is really good.
I've been using Java 1.5 for a while and most things work, with some caveats
-StringBuffer.toStrin
Steve,
You should be all set now.
Steps:
- Fetch latest SVN
- Create a project.properties in root directory
-
optional.includes=
-
- Drop latest
Folks,
I've moved the dom stuff out of the way and made the saaj build
optional. Now looking at test failures in JDK1.5
thanks,
-- dims
On 10/28/05, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
> Hi all, Ruchith ;-) ,
>
>
> Ruchith Fernando wrote:
> Hi All,
>
> The DOM impl that we have in the x
Hi all, Ruchith ;-) ,
Ruchith Fernando wrote:
Hi All,
The DOM impl that we have in the xml module implements the OM
interfaces. Therefore I included it under
org.apache.axis2.om.impl.dom.*
And I expected this to be used the same way we would use the llom
implementation of OM. (The linked
Hi All,
The DOM impl that we have in the xml module implements the OM
interfaces. Therefore I included it under
org.apache.axis2.om.impl.dom.*
And I expected this to be used the same way we would use the llom
implementation of OM. (The linked list implementation of OM goes under
org.apache.axis2.o
Steve Loughran wrote:
> Davanum Srinivas wrote:
>
>> Should we break out the DOM2/DOM3 stuff from xml module? just like we
>> did for saaj?
>>
>
> well, the issue is that both the OMElement and the SAAJ stuff declare
> that they implement the dom interfaces, and you cannot build them on
> java1.
Since SAAJ 1.3 implements DOM3, i feel we should just move this stuff
to SAAJ module. What do you think?
-- dims
On 10/28/05, Steve Loughran <[EMAIL PROTECTED]> wrote:
> Davanum Srinivas wrote:
> > Steve,
> >
> > all org.w3c imports are ONLY in org.apache.axis2.om.impl.dom.*
> > package. This can
Davanum Srinivas wrote:
Steve,
all org.w3c imports are ONLY in org.apache.axis2.om.impl.dom.*
package. This can be ripped out w/o affecting xml module.
I'm checking. OK, the files that changed there were
AttrImpl, DocumentImpl, DOMImplementationImpl, NodeImpl, ParentNode,
TextImpl
and in
Steve,
all org.w3c imports are ONLY in org.apache.axis2.om.impl.dom.*
package. This can be ripped out w/o affecting xml module.
-- dims
On 10/28/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> that's wrong...OMElement should not depend on DOM2...let me check.
>
> -- dims
>
> On 10/28/05, Steve
that's wrong...OMElement should not depend on DOM2...let me check.
-- dims
On 10/28/05, Steve Loughran <[EMAIL PROTECTED]> wrote:
> Davanum Srinivas wrote:
> > Should we break out the DOM2/DOM3 stuff from xml module? just like we
> > did for saaj?
> >
>
> well, the issue is that both the OMElemen
Davanum Srinivas wrote:
Should we break out the DOM2/DOM3 stuff from xml module? just like we
did for saaj?
well, the issue is that both the OMElement and the SAAJ stuff declare
that they implement the dom interfaces, and you cannot build them on
java1.5 without marking every impl class as a
Should we break out the DOM2/DOM3 stuff from xml module? just like we
did for saaj?
+1 from me.
-- dims
On 10/28/05, Steve Loughran <[EMAIL PROTECTED]> wrote:
> Davanum Srinivas wrote:
> > Steve,
> >
> > could we do a branch make the updates there to get a clearer picture?
> > - build against do
Davanum Srinivas wrote:
Steve,
could we do a branch make the updates there to get a clearer picture?
- build against dom3
- try support dom2 at runtime
- update both the SAAJ and DOMImpl (to SAAJ 1.3 and DOM3)
once we have stuff working we can merge back to trunk.
would make sense. I havent p
AIL PROTECTED]> wrote:
>
> I have axis2 building under java1.5, and DOM 3. The extra methods in the
> interfaces are just stubs, but it compiles.
>
> Trouble is, I can't check this stuff in without 1.4 builds breaking,
> because one of the new methods uses a datatype that is
I have axis2 building under java1.5, and DOM 3. The extra methods in the
interfaces are just stubs, but it compiles.
Trouble is, I can't check this stuff in without 1.4 builds breaking,
because one of the new methods uses a datatype that is only in dom3.
Otherwise we could stick the
15 matches
Mail list logo