On 7/20/05, David Jencks <[EMAIL PROTECTED]> wrote:
I fixed my problems by setting the TCCL to include all the xmlbeans
generated classes I expected to use. This cl also included xmlbeans
itself.
thanks
david jencks
On Jul 19, 2005, at 12:36 PM, Radu Preotiuc-Pietro wrote:
> The fact that the same code works fine when invoked from outside
> Eclipse leads me to believe that there is some classloader setup
> issue. So yeah, probably the TCCL needs to be set up so that xbean.jar
> is accessible. Or at the very least to have _some_ CL with the Schema
> resources in it.
>
> Radu
>
> -----Original Message-----
> From: David Jencks [mailto: [EMAIL PROTECTED]]
> Sent: Tuesday, July 19, 2005 11:59 AM
> To: dev@xmlbeans.apache.org
> Subject: Re: Integrating XMLBeans into an Eclipse plugin
>
>
>
> On Jul 19, 2005, at 4:13 AM, Ajith Ranabahu wrote:
>
>> Hi all,
>> I am a developer with the Apache Axis2 project. Some of you might
>> already know that we are using XMLBeans to do our data binding and the
>> integration with XMLBeans has been quite successful despite several
>> problems . I am working mostly on the tooling part these days and
>> would appreciate a pointer/suggestion to some of these issues I've
>> come across when dealing with XMLBeans. After all my expertise is
>> mainly in Web Services :).
>> Ok here goes
>> 1. The core tool that has XMLBeans integrated works fine. However
>> when I put the tool as an Eclipse plugin, it seizes to work. in more
>> accurate terms it throws out an Exception saying 'The 0th supplied
>> input is not a schema document: its type is N='. I've made sure that a
>> DOM element representing the schema is passed onto XMLBeans. The funny
>> thing is the code works fine when invoked outside Eclipse.
>
> I'm struggling with similar problems in geronimo right now. Does this
> have to do with making sure the appropriate SchemaTypeLoader is
> available from the TCCL? What is the best way to do this? Are there
> any other ways?
>
> thanks
> david jencks
>> 2. Since Axis2 is based on StAX, we have a heavy dependency on the
>> XML Stream reader. However the returned XML Stream reader has it's
>> initial pointer to START_ELEMENT not START_DOCUMENT. Our builder code
>> expects a START_DOCUMENT event initially. We've overcome the problem
>> with a wrapper but it's not really elegant in terms of code. Was the
>> placement of the initial pointer done deliberately for a reason ?
>>
>> Guess thats all for now. Any pointer or a helpful hint is appreciated
>>
>> Thanks
>> --
>> Ajith Ranabahu
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Ajith Ranabahu
