You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scout-dev@ws.apache.org by "David Jencks (JIRA)" <sc...@ws.apache.org> on 2007/04/12 08:45:32 UTC

[jira] Created: (SCOUT-28) XmlBeans conversion compiles but is non-functional

XmlBeans conversion compiles but is non-functional
--------------------------------------------------

                 Key: SCOUT-28
                 URL: https://issues.apache.org/jira/browse/SCOUT-28
             Project: Scout
          Issue Type: Bug
          Components: Scout Implementation
            Reporter: David Jencks
         Assigned To: Anil Saldhana


The code in RegistryImpl that converts from DOM responses to XmlObjects yields actual element XmlObjects, not Document objects. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


[jira] Commented: (SCOUT-28) XmlBeans conversion compiles but is non-functional

Posted by "Davanum Srinivas (JIRA)" <sc...@ws.apache.org>.
    [ https://issues.apache.org/jira/browse/SCOUT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488331 ] 

Davanum Srinivas commented on SCOUT-28:
---------------------------------------

Applied in svn revision 527885. need to close this issue.

thanks,
dims

> XmlBeans conversion compiles but is non-functional
> --------------------------------------------------
>
>                 Key: SCOUT-28
>                 URL: https://issues.apache.org/jira/browse/SCOUT-28
>             Project: Scout
>          Issue Type: Bug
>          Components: Scout Implementation
>            Reporter: David Jencks
>         Assigned To: Anil Saldhana
>         Attachments: SCOUT-28.patch
>
>
> The code in RegistryImpl that converts from DOM responses to XmlObjects yields actual element XmlObjects, not Document objects. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


[jira] Closed: (SCOUT-28) XmlBeans conversion compiles but is non-functional

Posted by "Kurt Stam (JIRA)" <sc...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/SCOUT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt Stam closed SCOUT-28.
--------------------------

       Resolution: Fixed
    Fix Version/s: 1.0rc1

> XmlBeans conversion compiles but is non-functional
> --------------------------------------------------
>
>                 Key: SCOUT-28
>                 URL: https://issues.apache.org/jira/browse/SCOUT-28
>             Project: Scout
>          Issue Type: Bug
>          Components: Scout Implementation
>            Reporter: David Jencks
>            Assignee: Anil Saldhana
>             Fix For: 1.0rc1
>
>         Attachments: SCOUT-28.patch
>
>
> The code in RegistryImpl that converts from DOM responses to XmlObjects yields actual element XmlObjects, not Document objects. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: XmlBeans and JAXB

Posted by Kurt T Stam <ks...@apache.org>.
Sounds good to me.

--Kurt

Davanum Srinivas wrote:
> Kurt,
>
> Let's not move to jaxb just yet maybe in another month or so. we are
> trying to get something out for Geronimo.
>
> thanks,
> dims
>
> On 4/12/07, Kurt T Stam <ks...@apache.org> wrote:
>> Now that Java6 contains JAXB it makes more sense to use JAXB. I know
>> most people can't use java6 yet, so
>> at least for a while we'd need to use JAXME (or SUN's JAXB
>> implementation), but I'd like to keep the number of dependencies low.
>> Does anyone know if XMLBeans is going to support JAXB, if so this
>> discussion is pointless :).
>>
>> Cheers,
>> --Kurt
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: XmlBeans and JAXB

Posted by Kurt T Stam <ks...@apache.org>.
So what is the status of the trunk right now?

I see that

1. with the latest checkin I can no longer run the unittests in scout.
2. The only working build is the maven1 build. The maven2 build is
giving me problems in eclipse, it complains about the parent pom.xml not
being found and it does not run the unittests.

It looks that one of the problems has to do with unmarshalling the
authorization token. I'm looking into this now.

thx,

--Kurt

p,s, Just for kicks I followed through converting to JAXB, which is
almost working. I have not checked in, but I'll keep on working it if I
find some spare cycles, and will wait with checking it in anyways till
next month or so, as per below.

Davanum Srinivas wrote:
> Kurt,
>
> Let's not move to jaxb just yet maybe in another month or so. we are
> trying to get something out for Geronimo.
>
> thanks,
> dims
>
> On 4/12/07, Kurt T Stam <ks...@apache.org> wrote:
>> Now that Java6 contains JAXB it makes more sense to use JAXB. I know
>> most people can't use java6 yet, so
>> at least for a while we'd need to use JAXME (or SUN's JAXB
>> implementation), but I'd like to keep the number of dependencies low.
>> Does anyone know if XMLBeans is going to support JAXB, if so this
>> discussion is pointless :).
>>
>> Cheers,
>> --Kurt
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


maven/mvn

Posted by Kurt T Stam <ks...@apache.org>.
The maven1 build works for me. It has 2 modules:

- jaxr-api, which use xmlbeans to generate to uddi bindings, which
proces the jax-api-1.0.kar
- scout which produces the scout-1.0.jar, this module contains unittests
that are run in the maven1 build.

Pretty simple, but the jar dependencies seem to always be broken. So
people end up having to manually download the jars.

1. What rules for making sure this does not happen. I'm starting to
believe that maven sucks. This worked at some point, but the
repositories seem very dynamic.

The maven2 does not work for me either. It does not run the unittests.
The unittests can be found in modules/scout/src/test

2. Is there a maven guru out there who can help straightening out the
build?

Thanks,

---Kurt







---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: XmlBeans and JAXB

Posted by Davanum Srinivas <da...@gmail.com>.
Kurt,

Let's not move to jaxb just yet maybe in another month or so. we are
trying to get something out for Geronimo.

thanks,
dims

On 4/12/07, Kurt T Stam <ks...@apache.org> wrote:
> Now that Java6 contains JAXB it makes more sense to use JAXB. I know
> most people can't use java6 yet, so
> at least for a while we'd need to use JAXME (or SUN's JAXB
> implementation), but I'd like to keep the number of dependencies low.
> Does anyone know if XMLBeans is going to support JAXB, if so this
> discussion is pointless :).
>
> Cheers,
> --Kurt
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: XmlBeans and JAXB

Posted by Davanum Srinivas <da...@gmail.com>.
Please see https://issues.apache.org/jira/browse/SCOUT-28

-- dims

On 4/12/07, Kurt T Stam <ks...@apache.org> wrote:
> What are the exact issues you are having? Certainly when using a local
> transport
> things seem to work ok for me.
>
> Davanum Srinivas wrote:
> > Too much work for the G release. Would you be able to help us clean up
> > the xmlbeans issues for now?
> >
> > thanks,
> > dims
> >
> > On 4/12/07, Anil Saldhana <an...@yahoo.com> wrote:
> >> XML binding issues in Scout only arrive at when the request is made to a
> >> registry and response is received. This has caused some issues in the
> >> various branches - trunk uses xmlbeans and one of the branches uses
> >> juddi.
> >> We can standardize on JAXB.
> >>
> >> Do you think it will be pragmatic to just abstract a layer out for
> >> binding
> >> and let users put in whatever binding layer they want? Just a
> >> thought. Not
> >> given too much thought into details.
> >>
> >> Kurt T Stam <ks...@apache.org> wrote:
> >>  Now that Java6 contains JAXB it makes more sense to use JAXB. I know
> >> most people can't use java6 yet, so
> >> at least for a while we'd need to use JAXME (or SUN's JAXB
> >> implementation), but I'd like to keep the number of dependencies low.
> >> Does anyone know if XMLBeans is going to support JAXB, if so this
> >> discussion is pointless :).
> >>
> >> Cheers,
> >> --Kurt
> >>
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: scout-dev-help@ws.apache.org
> >>
> >>
> >>
> >>
> >>  ________________________________
> >>  Get your own web address.
> >>  Have a HUGE year through Yahoo! Small Business.
> >>
> >>
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: XmlBeans and JAXB

Posted by Kurt T Stam <ks...@apache.org>.
What are the exact issues you are having? Certainly when using a local
transport
things seem to work ok for me.

Davanum Srinivas wrote:
> Too much work for the G release. Would you be able to help us clean up
> the xmlbeans issues for now?
>
> thanks,
> dims
>
> On 4/12/07, Anil Saldhana <an...@yahoo.com> wrote:
>> XML binding issues in Scout only arrive at when the request is made to a
>> registry and response is received. This has caused some issues in the
>> various branches - trunk uses xmlbeans and one of the branches uses
>> juddi.
>> We can standardize on JAXB.
>>
>> Do you think it will be pragmatic to just abstract a layer out for
>> binding
>> and let users put in whatever binding layer they want? Just a
>> thought. Not
>> given too much thought into details.
>>
>> Kurt T Stam <ks...@apache.org> wrote:
>>  Now that Java6 contains JAXB it makes more sense to use JAXB. I know
>> most people can't use java6 yet, so
>> at least for a while we'd need to use JAXME (or SUN's JAXB
>> implementation), but I'd like to keep the number of dependencies low.
>> Does anyone know if XMLBeans is going to support JAXB, if so this
>> discussion is pointless :).
>>
>> Cheers,
>> --Kurt
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: scout-dev-help@ws.apache.org
>>
>>
>>
>>
>>  ________________________________
>>  Get your own web address.
>>  Have a HUGE year through Yahoo! Small Business.
>>
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: XmlBeans and JAXB

Posted by Davanum Srinivas <da...@gmail.com>.
Too much work for the G release. Would you be able to help us clean up
the xmlbeans issues for now?

thanks,
dims

On 4/12/07, Anil Saldhana <an...@yahoo.com> wrote:
> XML binding issues in Scout only arrive at when the request is made to a
> registry and response is received. This has caused some issues in the
> various branches - trunk uses xmlbeans and one of the branches uses juddi.
> We can standardize on JAXB.
>
> Do you think it will be pragmatic to just abstract a layer out for binding
> and let users put in whatever binding layer they want? Just a thought. Not
> given too much thought into details.
>
> Kurt T Stam <ks...@apache.org> wrote:
>  Now that Java6 contains JAXB it makes more sense to use JAXB. I know
> most people can't use java6 yet, so
> at least for a while we'd need to use JAXME (or SUN's JAXB
> implementation), but I'd like to keep the number of dependencies low.
> Does anyone know if XMLBeans is going to support JAXB, if so this
> discussion is pointless :).
>
> Cheers,
> --Kurt
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: scout-dev-help@ws.apache.org
>
>
>
>
>  ________________________________
>  Get your own web address.
>  Have a HUGE year through Yahoo! Small Business.
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


Re: XmlBeans and JAXB

Posted by Anil Saldhana <an...@yahoo.com>.
XML binding issues in Scout only arrive at when the request is made to a registry and response is received. This has caused some issues in the various branches - trunk uses xmlbeans and one of the branches uses juddi.  We can standardize on JAXB.

Do you think it will be pragmatic to just abstract a layer out for binding and let users put in whatever binding layer they want? Just a thought. Not given too much thought into details.

Kurt T Stam <ks...@apache.org> wrote: Now that Java6 contains JAXB it makes more sense to use JAXB. I know
most people can't use java6 yet, so
at least for a while we'd need to use JAXME (or SUN's JAXB
implementation), but I'd like to keep the number of dependencies low.
Does anyone know if XMLBeans is going to support JAXB, if so this
discussion is pointless :).

Cheers,
--Kurt





---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org



       
---------------------------------
 Get your own web address.
 Have a HUGE year through Yahoo! Small Business.

XmlBeans and JAXB

Posted by Kurt T Stam <ks...@apache.org>.
Now that Java6 contains JAXB it makes more sense to use JAXB. I know
most people can't use java6 yet, so
at least for a while we'd need to use JAXME (or SUN's JAXB
implementation), but I'd like to keep the number of dependencies low.
Does anyone know if XMLBeans is going to support JAXB, if so this
discussion is pointless :).

Cheers,
--Kurt





---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


[jira] Resolved: (SCOUT-28) XmlBeans conversion compiles but is non-functional

Posted by "Davanum Srinivas (JIRA)" <sc...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/SCOUT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davanum Srinivas resolved SCOUT-28.
-----------------------------------

    Resolution: Fixed

> XmlBeans conversion compiles but is non-functional
> --------------------------------------------------
>
>                 Key: SCOUT-28
>                 URL: https://issues.apache.org/jira/browse/SCOUT-28
>             Project: Scout
>          Issue Type: Bug
>          Components: Scout Implementation
>            Reporter: David Jencks
>         Assigned To: Anil Saldhana
>         Attachments: SCOUT-28.patch
>
>
> The code in RegistryImpl that converts from DOM responses to XmlObjects yields actual element XmlObjects, not Document objects. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


[jira] Updated: (SCOUT-28) XmlBeans conversion compiles but is non-functional

Posted by "David Jencks (JIRA)" <sc...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/SCOUT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks updated SCOUT-28:
------------------------------

    Attachment: SCOUT-28.patch

The attached patch makes a lot of scout work, but there are still some problems I haven't tracked down.

> XmlBeans conversion compiles but is non-functional
> --------------------------------------------------
>
>                 Key: SCOUT-28
>                 URL: https://issues.apache.org/jira/browse/SCOUT-28
>             Project: Scout
>          Issue Type: Bug
>          Components: Scout Implementation
>            Reporter: David Jencks
>         Assigned To: Anil Saldhana
>         Attachments: SCOUT-28.patch
>
>
> The code in RegistryImpl that converts from DOM responses to XmlObjects yields actual element XmlObjects, not Document objects. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org


[jira] Reopened: (SCOUT-28) XmlBeans conversion compiles but is non-functional

Posted by "Kurt Stam (JIRA)" <sc...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/SCOUT-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt Stam reopened SCOUT-28:
----------------------------


Need to add the right Fix Version

> XmlBeans conversion compiles but is non-functional
> --------------------------------------------------
>
>                 Key: SCOUT-28
>                 URL: https://issues.apache.org/jira/browse/SCOUT-28
>             Project: Scout
>          Issue Type: Bug
>          Components: Scout Implementation
>            Reporter: David Jencks
>            Assignee: Anil Saldhana
>             Fix For: 1.0rc1
>
>         Attachments: SCOUT-28.patch
>
>
> The code in RegistryImpl that converts from DOM responses to XmlObjects yields actual element XmlObjects, not Document objects. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org