-
1. Re: Upgrading from 4.0.0.4 to 4.1.0.2 leads to an error on webservice comm
ubhole Jul 31, 2009 9:48 AM (in response to maku_martin.kuhn)This is related to the classloader loading different class than expected. Are you specifying a specific version in your bundle Metadata?
If you have a testcase that you can share we can take further look at it. To me it looks like different versions of SAAJ classes being pulled in from 4.1.0.2 than 4.0.0.4.
Ulhas
-
2. Re: Upgrading from 4.0.0.4 to 4.1.0.2 leads to an error on webservice comm
maku_martin.kuhn Aug 1, 2009 1:09 PM (in response to ubhole)hi,
i do only maven specific things. That means that I define my dependencies only in the maven pom.xml (in my first post I added the definings of the relevant dependencies).
This works pretty well with version 4.0.0.x (And as naive guy I would also expect that it works with 4.1.0.x)
To provide an example (at least with a real call to a webservice) is not easy because it needs a certain infrastructure. What would you need for an example
TIA
Martin
BTW, No offence but this occurs already some times that this kind of stuff (classloading and so on) leads to a really time consuming task to solve this none functional things. With my current knowledge I think I would not select a piece of software like SMX (although I think it is brilliant from it's conceptual design). But the stuff which is handled behind the scenes is a beast...
-
3. Re: Upgrading from 4.0.0.4 to 4.1.0.2 leads to an error on webservice comm
ubhole Aug 4, 2009 5:15 AM (in response to maku_martin.kuhn)Hi Martin,
I agree with you that it is time consuming to solve classloader issues but we surely want to help people to get around the issues quickly. Sometimes even though they look like not related to your application it possibly is related to how third party dependecies and bundles gereated on which many time neither you nor us would have control.
Can you atleast attach full stack trace and pom.xml if possible? This will give some more information. Current stacktrace only shows SUN saaj classes related problem but doesn't show the who called it. We have seen in past sometimes some of the sun dependencies in java.net have been overwritten with incompatible API changes.
Regards,
Ulhas
-
4. Re: Upgrading from 4.0.0.4 to 4.1.0.2 leads to an error on webservice comm
maku_martin.kuhn Aug 4, 2009 7:39 AM (in response to ubhole)Hi Ulhas,
thank you for supporting...
I attached a zip file with: the pom of my service unit (pom_su.xml), the pom of the project with my business logic (pom_comp) which performs the webservice call and the exception (exception.txt).
In the meantime I recognized that in 4.1.0.2 there is a bundle (system/org/apache/servicemix/bundles/org.apache.servicemix.bundles.saaj-impl) which isn't available in 4.0.0.4 -> Maybe is this the source of the error.
TIA
Martin
-
smx_files.zip 2.3 KB
-
-
5. Re: Upgrading from 4.0.0.4 to 4.1.0.2 leads to an error on webservice comm
maku_martin.kuhn Aug 28, 2009 4:17 AM (in response to ubhole)Hi Uhlas,
do you have any further comments to my problem?
TIA
Martin
-
6. Re: Upgrading from 4.0.0.4 to 4.1.0.2 leads to an error on webservice comm
ubhole Aug 28, 2009 4:52 AM (in response to maku_martin.kuhn)Sorry I was bit busy so will take a look at it as soon as possible.
Ulhas
-
7. Re: Upgrading from 4.0.0.4 to 4.1.0.2 leads to an error on webservice comm
maku_martin.kuhn Sep 14, 2009 3:31 AM (in response to ubhole)Anything new for this problem?
TIA