bea vendor specific problem
http://forums.java.net/jive/thread.jspa?messageID=117971

available stax jars are described at
http://www.j2ee.me/webservices/docs/1.6/tutorial/doc/SJSXP-jars.html

here is the response from the bea release engineer for not including stax jar 
(sjsxp.jar) 

http://forums.java.net/jive/thread.jspa?messageID=117971

"Any sjsxp.jar would do. The one in the JAX-WS RI would be just fine.
The reason we don't ship sjsxp.jar in the JAXB RI is that we don't want people 
to think that it's a required part of the JAXB" 

HTH
Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




Subject: Provider com.bea.xml.stream.MXParserFactory not found & stax-1.2.0
Date: Wed, 3 Jun 2009 15:21:43 +0200
From: matthias.gai...@t-systems.com
To: axis-user@ws.apache.org
















Hi group,

 

I am encountering some curious problem. I
am developing an application with axis2 v1.4.1. I develop the client and the
server side. I use eclipse for programming. Last week I had to create a new
eclipse workspace, but with the same sources. I also created therefore a new
server in eclipse based on my server executables I used before. (Tomcat 5.5).

Now when I create a ConfigurationContext on
the client side, I get the exception:

javax.xml.stream.FactoryConfigurationError:
Provider com.bea.xml.stream.MXParserFactory not found

 

I found a solution in the internet that I
should add the stax-1.2.0.jar. It is gone with this jar, but I wonder how this
can happen? My colleagues are working without that jar and the same code and
they have no problems at all.

 

Any insights would be appreciated!!

 

Matthias.


_________________________________________________________________
Hotmail® has ever-growing storage! Don’t worry about storage limits. 
http://windowslive.com/Tutorial/Hotmail/Storage?ocid=TXT_TAGLM_WL_HM_Tutorial_Storage_062009

Reply via email to