You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@xmlbeans.apache.org by chlee <le...@etri.re.kr> on 2010/08/12 09:29:01 UTC

org.apache.xmlbeans.impl.values.XmlAnyTypeImpl problem in Equinox

Hello, 

I'm having a strange problem during developing my osgi bundles in equinox.


When I run the below code within a A bundle, 

    XmlObject docXml = (XmlObject)XmlObject.Factory.parse(new File
("test.xml")); 
    System.out.print("Type of docXml: " + docXml.getClass());

the result is "Type of docXml: class myclass". (normal case)


but when I made another B bundle calling A bundle(exactly A bundle's
registered service)  and then run the same code, 

the result is "Type of docXML: class
org.apache.xmlbeans.impl.values.XmlAnyTypeImpl"  (abnormal case)

I verified that the passed document("test.xml") is correct.

I don't know why the result of same module are different?


-- 
View this message in context: http://old.nabble.com/org.apache.xmlbeans.impl.values.XmlAnyTypeImpl-problem-in-Equinox-tp29415479p29415479.html
Sent from the Xml Beans - User mailing list archive at Nabble.com.

RE: [ANN]VTD-XML 2.9

Posted by Cezar Andrei <ce...@oracle.com>.
Jimmy,

 

This is not the right list for these kind of announcements, we're not enforcing it, but please have respect for all the people subscribing.

 

Thanks,

Cezar

 

  _____  

From: jimmy Zhang [mailto:jzhang@ximpleware.com] 
Sent: Thursday, August 12, 2010 9:33 PM
To: user@xmlbeans.apache.org
Subject: [ANN]VTD-XML 2.9

 

VTD-XML 2.9, the next generation XML Processing API for SOA and Cloud computing, has been released. Please visit  HYPERLINK "wlmailhtml:%7b337D6FBA-0A97-4A74-88E7-1478CBE3B230%7dmid://00000796/!x-usc:https://sourceforge.net/projects/vtd-xml/files/"https://sourceforge.net/projects/vtd-xml/files/ to download the latest version.

Strict Conformance 

VTD-XML now fully conforms to XML namespace 1.0 spec 

Performance Improvement

Significantly improved parsing performance for small XML files 

Expand Core VTD-XML API  

Adds getPrefixString(), and toNormalizedString2() 

Cutting/Splitting 

Adds getSiblingElementFragment()  

A number of bug fixes and code enhancement including: 

Fixes a bug for reading very large XML documents on some platforms 
Fixes a bug in parsing processing instruction 
Fixes a bug in outputAndReparse() 

[ANN]VTD-XML 2.9

Posted by jimmy Zhang <jz...@ximpleware.com>.
VTD-XML 2.9, the next generation XML Processing API for SOA and Cloud computing, has been released. Please visit  https://sourceforge.net/projects/vtd-xml/files/ to download the latest version.
  a.. Strict Conformance 
    a.. VTD-XML now fully conforms to XML namespace 1.0 spec 
  b.. Performance Improvement
    a.. Significantly improved parsing performance for small XML files 
  c.. Expand Core VTD-XML API  
    a.. Adds getPrefixString(), and toNormalizedString2() 
  d.. Cutting/Splitting 
    a.. Adds getSiblingElementFragment()  
  e.. A number of bug fixes and code enhancement including: 
    a.. Fixes a bug for reading very large XML documents on some platforms 
    b.. Fixes a bug in parsing processing instruction 
    c.. Fixes a bug in outputAndReparse() 

Re: org.apache.xmlbeans.impl.values.XmlAnyTypeImpl problem in Equinox

Posted by chlee <le...@etri.re.kr>.
I appreciate your kindness.

I did as you'v recommended. but, the result was same.

When I explained my problem, I had one thing that I missed.
Bundle B is http servlet bundle ( imported packages are javax.servlet,
javax.servlet.http, org.osgi.service.http).
If I add Bundle A's method at BundleActivator/start() of Bundle B, it works
well.
The abnormal case is when called as http get/post service.
That is, if I add Bundle A's method at HttpServlet/doPost() of Bundle, it
doesn't work.

Thanks,
chlee



Srijith Kochunni wrote:
> 
> Hi chlee,
>  
>      I recommend you try creating an object of myclass in the Bundle 'B'.
> Verify that you dont hit across a 'ClassNotFound Error'. Also check
> whether Bundle A has myclass in the 'Export-Package' header.
>  
>     To verify that the wiring has happened correctly, run command packages
> 'myclass' (full class name) in the osgi prompt to check the wiring.
>  
>    Hope this helps.
>  
> Thanks,
> Srijith.
> 
>>>> chlee <le...@etri.re.kr> 13/08/2010 07:16 >>>
> 
> Thanks for your reply.
> 
> I did what you said.
> but, unfortunately the result was same.
> do you have other solution?
> 
> 
> Srijith Kochunni wrote:
>> 
>> myclass should be visible to bundle 'B'. Verify, if you have added it in
>> the Import-Package header.
>>  
>> Thanks,
>> Srijith.
>> 
>>>>> chlee <le...@etri.re.kr> 12/08/2010 12:59 >>>
>> Hello, I'm having a strange problem during developing my osgi bundles in
>> equinox. When I run the below code within a A bundle, XmlObject docXml =
>> (XmlObject)XmlObject.Factory.parse(new File ("test.xml"));
>> System.out.print("Type of docXml: " + docXml.getClass()); the result is
>> "Type of docXml: class myclass". (normal case) but when I made another B
>> bundle calling A bundle(exactly A bundle's registered service) and then
>> run the same code, the result is "Type of docXML: class
>> org.apache.xmlbeans.impl.values.XmlAnyTypeImpl" (abnormal case) I
>> verified
>> that the passed document("test.xml") is correct. I don't know why the
>> result of same module are different? 
>> View this message in context:
>> org.apache.xmlbeans.impl.values.XmlAnyTypeImpl problem in Equinox (
>> http://old.nabble.com/org.apache.xmlbeans.impl.values.XmlAnyTypeImpl-problem-in-Equinox-tp29415479p29415479.html
>> )
>> Sent from the Xml Beans - User mailing list archive (
>> http://old.nabble.com/Xml-Beans---User-f349.html ) at Nabble.com.
>> 
>> 
> 
> -- 
> View this message in context:
> http://old.nabble.com/org.apache.xmlbeans.impl.values.XmlAnyTypeImpl-problem-in-Equinox-tp29415479p29424917.html
> Sent from the Xml Beans - User mailing list archive at Nabble.com.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
> For additional commands, e-mail: user-help@xmlbeans.apache.org
> 
> 
> 

-- 
View this message in context: http://old.nabble.com/org.apache.xmlbeans.impl.values.XmlAnyTypeImpl-problem-in-Equinox-tp29415479p29446770.html
Sent from the Xml Beans - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org


Re: org.apache.xmlbeans.impl.values.XmlAnyTypeImpl problem in Equinox

Posted by Srijith Kochunni <ks...@novell.com>.
Hi chlee,
 
     I recommend you try creating an object of myclass in the Bundle 'B'. Verify that you dont hit across a 'ClassNotFound Error'. Also check whether Bundle A has myclass in the 'Export-Package' header.
 
    To verify that the wiring has happened correctly, run command packages 'myclass' (full class name) in the osgi prompt to check the wiring.
 
   Hope this helps.
 
Thanks,
Srijith.

>>> chlee <le...@etri.re.kr> 13/08/2010 07:16 >>>

Thanks for your reply.

I did what you said.
but, unfortunately the result was same.
do you have other solution?


Srijith Kochunni wrote:
> 
> myclass should be visible to bundle 'B'. Verify, if you have added it in
> the Import-Package header.
>  
> Thanks,
> Srijith.
> 
>>>> chlee <le...@etri.re.kr> 12/08/2010 12:59 >>>
> Hello, I'm having a strange problem during developing my osgi bundles in
> equinox. When I run the below code within a A bundle, XmlObject docXml =
> (XmlObject)XmlObject.Factory.parse(new File ("test.xml"));
> System.out.print("Type of docXml: " + docXml.getClass()); the result is
> "Type of docXml: class myclass". (normal case) but when I made another B
> bundle calling A bundle(exactly A bundle's registered service) and then
> run the same code, the result is "Type of docXML: class
> org.apache.xmlbeans.impl.values.XmlAnyTypeImpl" (abnormal case) I verified
> that the passed document("test.xml") is correct. I don't know why the
> result of same module are different? 
> View this message in context:
> org.apache.xmlbeans.impl.values.XmlAnyTypeImpl problem in Equinox (
> http://old.nabble.com/org.apache.xmlbeans.impl.values.XmlAnyTypeImpl-problem-in-Equinox-tp29415479p29415479.html
> )
> Sent from the Xml Beans - User mailing list archive (
> http://old.nabble.com/Xml-Beans---User-f349.html ) at Nabble.com.
> 
> 

-- 
View this message in context: http://old.nabble.com/org.apache.xmlbeans.impl.values.XmlAnyTypeImpl-problem-in-Equinox-tp29415479p29424917.html
Sent from the Xml Beans - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org


Re: org.apache.xmlbeans.impl.values.XmlAnyTypeImpl problem in Equinox

Posted by chlee <le...@etri.re.kr>.
Thanks for your reply.

I did what you said.
but, unfortunately the result was same.
do you have other solution?


Srijith Kochunni wrote:
> 
> myclass should be visible to bundle 'B'. Verify, if you have added it in
> the Import-Package header.
>  
> Thanks,
> Srijith.
> 
>>>> chlee <le...@etri.re.kr> 12/08/2010 12:59 >>>
> Hello, I'm having a strange problem during developing my osgi bundles in
> equinox. When I run the below code within a A bundle, XmlObject docXml =
> (XmlObject)XmlObject.Factory.parse(new File ("test.xml"));
> System.out.print("Type of docXml: " + docXml.getClass()); the result is
> "Type of docXml: class myclass". (normal case) but when I made another B
> bundle calling A bundle(exactly A bundle's registered service) and then
> run the same code, the result is "Type of docXML: class
> org.apache.xmlbeans.impl.values.XmlAnyTypeImpl" (abnormal case) I verified
> that the passed document("test.xml") is correct. I don't know why the
> result of same module are different? 
> View this message in context:
> org.apache.xmlbeans.impl.values.XmlAnyTypeImpl problem in Equinox (
> http://old.nabble.com/org.apache.xmlbeans.impl.values.XmlAnyTypeImpl-problem-in-Equinox-tp29415479p29415479.html
> )
> Sent from the Xml Beans - User mailing list archive (
> http://old.nabble.com/Xml-Beans---User-f349.html ) at Nabble.com.
> 
> 

-- 
View this message in context: http://old.nabble.com/org.apache.xmlbeans.impl.values.XmlAnyTypeImpl-problem-in-Equinox-tp29415479p29424917.html
Sent from the Xml Beans - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org


Re: org.apache.xmlbeans.impl.values.XmlAnyTypeImpl problem in Equinox

Posted by Srijith Kochunni <ks...@novell.com>.
myclass should be visible to bundle 'B'. Verify, if you have added it in the Import-Package header.
 
Thanks,
Srijith.

>>> chlee <le...@etri.re.kr> 12/08/2010 12:59 >>>
Hello, I'm having a strange problem during developing my osgi bundles in equinox. When I run the below code within a A bundle, XmlObject docXml = (XmlObject)XmlObject.Factory.parse(new File ("test.xml")); System.out.print("Type of docXml: " + docXml.getClass()); the result is "Type of docXml: class myclass". (normal case) but when I made another B bundle calling A bundle(exactly A bundle's registered service) and then run the same code, the result is "Type of docXML: class org.apache.xmlbeans.impl.values.XmlAnyTypeImpl" (abnormal case) I verified that the passed document("test.xml") is correct. I don't know why the result of same module are different? 
View this message in context: org.apache.xmlbeans.impl.values.XmlAnyTypeImpl problem in Equinox ( http://old.nabble.com/org.apache.xmlbeans.impl.values.XmlAnyTypeImpl-problem-in-Equinox-tp29415479p29415479.html )
Sent from the Xml Beans - User mailing list archive ( http://old.nabble.com/Xml-Beans---User-f349.html ) at Nabble.com.