Hello all,
I'm experiencing a weird issue in trying to load documents in XMLBeans.
I'm working with a NetBeans platform application and we use XMLBeans
extensively throughout the application. This issue is a first for me and
I'm not sure how to proceed.
I have an object that stores XML data as
make sure first it does
run correctly from command line.
Cezar
On Tue, 2012-12-11 at 13:39 -0800, Michael Bishop wrote:
Hello all,
I'm experiencing a weird issue in trying to load documents in
XMLBeans. I'm working with a NetBeans platform application and we use
XMLBeans extensively
This is awfully unfortunate. To my knowledge, there's no comparable product
out there. We're still struggling with a few XMLBeans issues that we've had
to go to straight DOM to work around. I was hoping that future releases
would address some of these issues, but it doesn't appear to be the case.
22, 2013 at 2:00 PM, Nick Burch apa...@gagravarr.org wrote:
On Mon, 22 Jul 2013, Michael Bishop wrote:
This is awfully unfortunate. To my knowledge, there's no comparable
product out there. We're still struggling with a few XMLBeans issues that
we've had to go to straight DOM to work around
I think I can answer your first question. From what I recall in
parsing/reading documents, InputStream is a poor choice for XML documents
that include other documents. An InputStream object can't tell you where
its source is. Therefore, there is no way to find relative paths. I would
try the
Hello all,
I'm a bit stuck in trying to achieve this with XmlObjects and XmlCursor.
Imagine the following scenario:
parent
childSome text/child
/parent
I want to insert a new element AFTER the child element.
parent
childSome text/child
!-- New element here! --
/parent
I don't
= testcurs.toEndToken(); //END tag of
parent element
testcurs.**insertElementWithText(child,**second);
On 10/23/2013 11:51 AM, Michael Bishop wrote:
Hello all,
I'm a bit stuck in trying to achieve this with XmlObjects and XmlCursor.
Imagine the following scenario:
parent
childSome
parse properly.
It's not a big deal since the namespace is intact and things work as they
should, but I can't figure out why this is happening. I don't declare xmlns:
*yyy* anywhere in the schema or xsdconfig files.
Michael Bishop
more I can provide, I can do so.
Michael Bishop
On Fri, Aug 1, 2014 at 12:10 PM, Cezar Andrei cezar.and...@oracle.com
wrote:
If you don't provide a prefix, XmlBeans will automatically pick a prefix,
and it tries to pick one that is part of the URI.
Cezar
On 07/28/2014 01:27 PM, Michael
, Michael Bishop wrote:
OK, thanks for the information. Unfortunately, this doesn't seem to fix
the problem. I thought I'd tried the steps outlined in the linked blog
before, but I did it again, just in case.
Here's the full schema definitions:
Old:
xs:schema xmlns:xs=http://www.w3.org/2001
to xmlns:aaa as declared? I'd be hard pressed
to believe that something in XMLBeans is causing this. It's probably
something I'm doing. Does the XSDConfig file have any influence that I'm
missing?
Michael Bishop
On Thu, Aug 7, 2014 at 1:22 PM, Michael Bishop bisho...@gmail.com wrote:
I've got
,
OK - now this is getting to the heart of the question...
On Thu, 2014-08-07 at 16:02 -0400, Michael Bishop wrote:
Hi Peter,
You're right, I came across that table recently since I've been
working at this problem most of the day. Let me share one more thing
I've discovered. It appears
12 matches
Mail list logo
