Robert,

thanks for the adivce, however, after further testing, I don't think
I'm picking up another StAXUtils implementation.  I had been using
maven to build/run, but to be sure, I ran from command-line explicitly
declaring my jars: (with the versions taken out):

java -cp axiom.jar;axis2.jar;commons-logging.jar;wstx.jar;stax.jar;test.jar
   -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory
  test.Main

I still get the same instantiation error when I call:

  XMLInputFactory sf = StAXUtils.getXMLInputFactory();

but, don't get an exception when I directly call:

  XMLInputFactory f = XMLInputFactory.newInstance();


any other possibilities? Are there some known errors with running with
JDK6 perhaps?

thanks
Tom



On 5/19/10, robert lazarski <robertlazar...@gmail.com> wrote:
> On Wed, May 19, 2010 at 10:38 AM, Tom Herbert <twh...@gmail.com> wrote:
>> So, I'm not sure why the StAXUtils doesn't seem to be pickign up my
>> implementation file setting.
>>
>
> You most likely are picking up another StAXUtils implementation from
> another jar, often loaded from a AppServer (JBoss etc) classloader
> with a higher precedence. I'd look at the happy axis2 page shows the
> jars and their file paths.
>
> - R
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
> For additional commands, e-mail: java-dev-h...@axis.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Reply via email to