RE: Blueprint NamespaceHandler issue with karaf 4.0.5

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

RE: Blueprint NamespaceHandler issue with karaf 4.0.5

Niten Aggarwal

Hi Guillaume,

 

I was trying to fix 1540 on my workspace but kind of stuck and related issue was resolved https://issues.apache.org/jira/browse/ARIES-1540

 

Could you please look into the updated comments on ticket as not sure if resolved ticket being looked again.

 

Else let me know how to apply this fix in Karaf 4.0.5 as we are facing same issue and cannot change aries blueprint version just by changing features.xml. We are on karaf 4.0.5 and feature will be installed through nexus repository directly so we cannot update this feature just for blueprint.core version.

 

<feature name="aries-blueprint" description="Aries Blueprint" version="4.0.5">

<feature prerequisite="false" dependency="false">aries-proxy</feature>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.api/1.0.1</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.cm/1.0.8</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core.compatibility/1.0.0</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core/1.6.1</bundle>

<conditional>

<condition>bundle</condition>

<bundle start-level="30">mvn:org.apache.karaf.bundle/org.apache.karaf.bundle.blueprintstate/4.0.5</bundle>

</conditional>

<capability>

osgi.service;effective:=active;objectClass=org.apache.aries.blueprint.services.ParserService,

osgi.extender; osgi.extender="osgi.blueprint";uses:="org.osgi.service.blueprint.container,org.osgi.service.blueprint.reflect";version:Version="1.0"

</capability>

</feature>

 

Thanks,

Niten Aggarwal

 

-----Original Message-----
From: Sergey Beryozkin [mailto:[hidden email]]
Sent: Friday, July 22, 2016 12:37 PM
To: [hidden email]
Subject: Re: Blueprint NamespaceHandler issue with karaf 4.0.5

 

Sorry. All I know that proxies need to be somehow configured, but I do not work behind the proxy. May be you've discovered a new bug. You might need to debug or ask at Karaf or Aries lists

 

Sergey

On 22/07/16 18:44, Niten Aggarwal wrote:

> Please let me know if there is any fix available?

> ________________________________________

> From: Niten Aggarwal

> Sent: Thursday, July 21, 2016 9:11 PM

> To: [hidden email]

> Subject: RE: Blueprint NamespaceHandler issue with karaf 4.0.5

> 

> Hi Sergey,

> 

> It doesn't have details how to fix the issue I mean how to witch schemes to online mode.. I am behind the proxy so definitely it's a proxy issue while loading schemes but not able to understand how to fix it.

> I thought 1.6.1 has fixed this issue to understand schema resource location.

> 

> Please let me know how to change online mode.

> ________________________________________

> From: Sergey Beryozkin [[hidden email]]

> Sent: Thursday, July 21, 2016 8:30 PM

> To: [hidden email]

> Subject: Re: Blueprint NamespaceHandler issue with karaf 4.0.5

> 

> Hi

> 

> Can this help:

> 

> https://issues.apache.org/jira/browse/CXF-4063 ?

> 

> Sergey

> On 21/07/16 09:54, Niten Aggarwal wrote:

>> Hello,

>> 

>> I am facing an issue while deploying bundles with CXF 3.1.5 on Karaf 4.0.5. They are working fine with Karaf 4.0.4.

>> It looks like there are couple of bugs already opened but don't know what dependency change I have to do to get it worked. Karaf 4.0.5 automatically comes with blueprint-core 1.6.1 so not sure how to update dependency.

>> 

>> Bugs I was following

>> https://issues.apache.org/jira/browse/ARIES-1540

>> https://issues.apache.org/jira/browse/KARAF-4608

>> 

>> 

>> Error I am getting:

>> 

>> 2016-07-19 13:00:29,176 | WARN  | pool-65-thread-1 | NamespaceHandlerRegistryImpl     | 13 - org.apache.aries.blueprint.core - 1.6.1 | Dynamically adding namespace handler http://cxf.apache.org/configuration/parameterized-types to bundle checkout-api-controller/1.1.0.SNAPSHOT

>> 2016-07-19 13:00:50,188 | ERROR | pool-65-thread-1 | BlueprintContainerImpl           | 13 - org.apache.aries.blueprint.core - 1.6.1 | Unable to start blueprint container for bundle checkout-api-controller/1.1.0.SNAPSHOT

>> org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'ptp:ParameterizedInt' to a(n) 'simpleType definition' component.

>>                   at

>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Un

>> known Source)[:]

>> 

>> Thanks,

>> Niten Aggarwal

>> 

>> 

>> 

>> ::DISCLAIMER::

>> ---------------------------------------------------------------------

>> ---------------------------------------------------------------------

>> ----------

>> 

>> The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.

>> E-mail transmission is not guaranteed to be secure or error-free as

>> information could be intercepted, corrupted, lost, destroyed, arrive

>> late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.

>> Views or opinions, if any, presented in this email are solely those

>> of the author and may not necessarily reflect the views or opinions

>> of HCL or its affiliates. Any form of reproduction, dissemination,

>> copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.

>> Before opening any email and/or attachments, please check them for viruses and other defects.

>> 

>> ---------------------------------------------------------------------

>> ---------------------------------------------------------------------

>> ----------

>> 

> 

> 

> --

> Sergey Beryozkin

> 

> Talend Community Coders

> http://coders.talend.com/

> 

 

 

--

Sergey Beryozkin

 

Talend Community Coders

http://coders.talend.com/

Reply | Threaded
Open this post in threaded view
|

RE: Blueprint NamespaceHandler issue with karaf 4.0.5

Niten Aggarwal

Any update?

 

Thanks,

Niten Aggarwal

 

From: Niten Aggarwal
Sent: Monday, August 08, 2016 8:38 AM
To: '[hidden email]'; '[hidden email]'
Subject: RE: Blueprint NamespaceHandler issue with karaf 4.0.5

 

Hi Guillaume,

 

I was trying to fix 1540 on my workspace but kind of stuck and related issue was resolved https://issues.apache.org/jira/browse/ARIES-1540

 

Could you please look into the updated comments on ticket as not sure if resolved ticket being looked again.

 

Else let me know how to apply this fix in Karaf 4.0.5 as we are facing same issue and cannot change aries blueprint version just by changing features.xml. We are on karaf 4.0.5 and feature will be installed through nexus repository directly so we cannot update this feature just for blueprint.core version.

 

<feature name="aries-blueprint" description="Aries Blueprint" version="4.0.5">

<feature prerequisite="false" dependency="false">aries-proxy</feature>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.api/1.0.1</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.cm/1.0.8</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core.compatibility/1.0.0</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core/1.6.1</bundle>

<conditional>

<condition>bundle</condition>

<bundle start-level="30">mvn:org.apache.karaf.bundle/org.apache.karaf.bundle.blueprintstate/4.0.5</bundle>

</conditional>

<capability>

osgi.service;effective:=active;objectClass=org.apache.aries.blueprint.services.ParserService,

osgi.extender; osgi.extender="osgi.blueprint";uses:="org.osgi.service.blueprint.container,org.osgi.service.blueprint.reflect";version:Version="1.0"

</capability>

</feature>

 

Thanks,

Niten Aggarwal

 

-----Original Message-----
From: Sergey Beryozkin [mailto:[hidden email]]
Sent: Friday, July 22, 2016 12:37 PM
To: [hidden email]
Subject: Re: Blueprint NamespaceHandler issue with karaf 4.0.5

 

Sorry. All I know that proxies need to be somehow configured, but I do not work behind the proxy. May be you've discovered a new bug. You might need to debug or ask at Karaf or Aries lists

 

Sergey

On 22/07/16 18:44, Niten Aggarwal wrote:

> Please let me know if there is any fix available?

> ________________________________________

> From: Niten Aggarwal

> Sent: Thursday, July 21, 2016 9:11 PM

> To: [hidden email]

> Subject: RE: Blueprint NamespaceHandler issue with karaf 4.0.5

> 

> Hi Sergey,

> 

> It doesn't have details how to fix the issue I mean how to witch schemes to online mode.. I am behind the proxy so definitely it's a proxy issue while loading schemes but not able to understand how to fix it.

> I thought 1.6.1 has fixed this issue to understand schema resource location.

> 

> Please let me know how to change online mode.

> ________________________________________

> From: Sergey Beryozkin [[hidden email]]

> Sent: Thursday, July 21, 2016 8:30 PM

> To: [hidden email]

> Subject: Re: Blueprint NamespaceHandler issue with karaf 4.0.5

> 

> Hi

> 

> Can this help:

> 

> https://issues.apache.org/jira/browse/CXF-4063 ?

> 

> Sergey

> On 21/07/16 09:54, Niten Aggarwal wrote:

>> Hello,

>> 

>> I am facing an issue while deploying bundles with CXF 3.1.5 on Karaf 4.0.5. They are working fine with Karaf 4.0.4.

>> It looks like there are couple of bugs already opened but don't know what dependency change I have to do to get it worked. Karaf 4.0.5 automatically comes with blueprint-core 1.6.1 so not sure how to update dependency.

>> 

>> Bugs I was following

>> https://issues.apache.org/jira/browse/ARIES-1540

>> https://issues.apache.org/jira/browse/KARAF-4608

>> 

>> 

>> Error I am getting:

>> 

>> 2016-07-19 13:00:29,176 | WARN  | pool-65-thread-1 | NamespaceHandlerRegistryImpl     | 13 - org.apache.aries.blueprint.core - 1.6.1 | Dynamically adding namespace handler http://cxf.apache.org/configuration/parameterized-types to bundle checkout-api-controller/1.1.0.SNAPSHOT

>> 2016-07-19 13:00:50,188 | ERROR | pool-65-thread-1 | BlueprintContainerImpl           | 13 - org.apache.aries.blueprint.core - 1.6.1 | Unable to start blueprint container for bundle checkout-api-controller/1.1.0.SNAPSHOT

>> org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'ptp:ParameterizedInt' to a(n) 'simpleType definition' component.

>>                   at

>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Un

>> known Source)[:]

>> 

>> Thanks,

>> Niten Aggarwal

>> 

>> 

>> 

>> ::DISCLAIMER::

>> ---------------------------------------------------------------------

>> ---------------------------------------------------------------------

>> ----------

>> 

>> The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.

>> E-mail transmission is not guaranteed to be secure or error-free as

>> information could be intercepted, corrupted, lost, destroyed, arrive

>> late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.

>> Views or opinions, if any, presented in this email are solely those

>> of the author and may not necessarily reflect the views or opinions

>> of HCL or its affiliates. Any form of reproduction, dissemination,

>> copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.

>> Before opening any email and/or attachments, please check them for viruses and other defects.

>> 

>> ---------------------------------------------------------------------

>> ---------------------------------------------------------------------

>> ----------

>> 

> 

> 

> --

> Sergey Beryozkin

> 

> Talend Community Coders

> http://coders.talend.com/

> 

 

 

--

Sergey Beryozkin

 

Talend Community Coders

http://coders.talend.com/

Reply | Threaded
Open this post in threaded view
|

RE: Blueprint NamespaceHandler issue with karaf 4.0.5

Niten Aggarwal
In reply to this post by Niten Aggarwal

Just checking if there is any fix? I haven’t seen any update on this issue so please let me know.

 

Thanks,

Niten Aggarwal

 

From: Niten Aggarwal
Sent: Monday, August 08, 2016 8:38 AM
To: '[hidden email]'; '[hidden email]'
Subject: RE: Blueprint NamespaceHandler issue with karaf 4.0.5

 

Hi Guillaume,

 

I was trying to fix 1540 on my workspace but kind of stuck and related issue was resolved https://issues.apache.org/jira/browse/ARIES-1540

 

Could you please look into the updated comments on ticket as not sure if resolved ticket being looked again.

 

Else let me know how to apply this fix in Karaf 4.0.5 as we are facing same issue and cannot change aries blueprint version just by changing features.xml. We are on karaf 4.0.5 and feature will be installed through nexus repository directly so we cannot update this feature just for blueprint.core version.

 

<feature name="aries-blueprint" description="Aries Blueprint" version="4.0.5">

<feature prerequisite="false" dependency="false">aries-proxy</feature>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.api/1.0.1</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.cm/1.0.8</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core.compatibility/1.0.0</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core/1.6.1</bundle>

<conditional>

<condition>bundle</condition>

<bundle start-level="30">mvn:org.apache.karaf.bundle/org.apache.karaf.bundle.blueprintstate/4.0.5</bundle>

</conditional>

<capability>

osgi.service;effective:=active;objectClass=org.apache.aries.blueprint.services.ParserService,

osgi.extender; osgi.extender="osgi.blueprint";uses:="org.osgi.service.blueprint.container,org.osgi.service.blueprint.reflect";version:Version="1.0"

</capability>

</feature>

 

Thanks,

Niten Aggarwal

 

-----Original Message-----
From: Sergey Beryozkin [mailto:[hidden email]]
Sent: Friday, July 22, 2016 12:37 PM
To: [hidden email]
Subject: Re: Blueprint NamespaceHandler issue with karaf 4.0.5

 

Sorry. All I know that proxies need to be somehow configured, but I do not work behind the proxy. May be you've discovered a new bug. You might need to debug or ask at Karaf or Aries lists

 

Sergey

On 22/07/16 18:44, Niten Aggarwal wrote:

> Please let me know if there is any fix available?

> ________________________________________

> From: Niten Aggarwal

> Sent: Thursday, July 21, 2016 9:11 PM

> To: [hidden email]

> Subject: RE: Blueprint NamespaceHandler issue with karaf 4.0.5

> 

> Hi Sergey,

> 

> It doesn't have details how to fix the issue I mean how to witch schemes to online mode.. I am behind the proxy so definitely it's a proxy issue while loading schemes but not able to understand how to fix it.

> I thought 1.6.1 has fixed this issue to understand schema resource location.

> 

> Please let me know how to change online mode.

> ________________________________________

> From: Sergey Beryozkin [[hidden email]]

> Sent: Thursday, July 21, 2016 8:30 PM

> To: [hidden email]

> Subject: Re: Blueprint NamespaceHandler issue with karaf 4.0.5

> 

> Hi

> 

> Can this help:

> 

> https://issues.apache.org/jira/browse/CXF-4063 ?

> 

> Sergey

> On 21/07/16 09:54, Niten Aggarwal wrote:

>> Hello,

>> 

>> I am facing an issue while deploying bundles with CXF 3.1.5 on Karaf 4.0.5. They are working fine with Karaf 4.0.4.

>> It looks like there are couple of bugs already opened but don't know what dependency change I have to do to get it worked. Karaf 4.0.5 automatically comes with blueprint-core 1.6.1 so not sure how to update dependency.

>> 

>> Bugs I was following

>> https://issues.apache.org/jira/browse/ARIES-1540

>> https://issues.apache.org/jira/browse/KARAF-4608

>> 

>> 

>> Error I am getting:

>> 

>> 2016-07-19 13:00:29,176 | WARN  | pool-65-thread-1 | NamespaceHandlerRegistryImpl     | 13 - org.apache.aries.blueprint.core - 1.6.1 | Dynamically adding namespace handler http://cxf.apache.org/configuration/parameterized-types to bundle checkout-api-controller/1.1.0.SNAPSHOT

>> 2016-07-19 13:00:50,188 | ERROR | pool-65-thread-1 | BlueprintContainerImpl           | 13 - org.apache.aries.blueprint.core - 1.6.1 | Unable to start blueprint container for bundle checkout-api-controller/1.1.0.SNAPSHOT

>> org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'ptp:ParameterizedInt' to a(n) 'simpleType definition' component.

>>                   at

>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Un

>> known Source)[:]

>> 

>> Thanks,

>> Niten Aggarwal

>> 

>> 

>> 

>> ::DISCLAIMER::

>> ---------------------------------------------------------------------

>> ---------------------------------------------------------------------

>> ----------

>> 

>> The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.

>> E-mail transmission is not guaranteed to be secure or error-free as

>> information could be intercepted, corrupted, lost, destroyed, arrive

>> late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.

>> Views or opinions, if any, presented in this email are solely those

>> of the author and may not necessarily reflect the views or opinions

>> of HCL or its affiliates. Any form of reproduction, dissemination,

>> copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.

>> Before opening any email and/or attachments, please check them for viruses and other defects.

>> 

>> ---------------------------------------------------------------------

>> ---------------------------------------------------------------------

>> ----------

>> 

> 

> 

> --

> Sergey Beryozkin

> 

> Talend Community Coders

> http://coders.talend.com/

> 

 

 

--

Sergey Beryozkin

 

Talend Community Coders

http://coders.talend.com/

Reply | Threaded
Open this post in threaded view
|

RE: Blueprint NamespaceHandler issue with karaf 4.0.5

Niten Aggarwal
In reply to this post by Niten Aggarwal

I am not seeing update to this ticker for long time. Please let me know.

 

Thanks,

Niten Aggarwal

 

From: Niten Aggarwal
Sent: Tuesday, August 09, 2016 7:18 AM
To: '[hidden email]'; '[hidden email]'
Cc: [hidden email]
Subject: RE: Blueprint NamespaceHandler issue with karaf 4.0.5

 

Just checking if there is any fix? I haven’t seen any update on this issue so please let me know.

 

Thanks,

Niten Aggarwal

 

From: Niten Aggarwal
Sent: Monday, August 08, 2016 8:38 AM
To: '[hidden email]'; '[hidden email]'
Subject: RE: Blueprint NamespaceHandler issue with karaf 4.0.5

 

Hi Guillaume,

 

I was trying to fix 1540 on my workspace but kind of stuck and related issue was resolved https://issues.apache.org/jira/browse/ARIES-1540

 

Could you please look into the updated comments on ticket as not sure if resolved ticket being looked again.

 

Else let me know how to apply this fix in Karaf 4.0.5 as we are facing same issue and cannot change aries blueprint version just by changing features.xml. We are on karaf 4.0.5 and feature will be installed through nexus repository directly so we cannot update this feature just for blueprint.core version.

 

<feature name="aries-blueprint" description="Aries Blueprint" version="4.0.5">

<feature prerequisite="false" dependency="false">aries-proxy</feature>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.api/1.0.1</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.cm/1.0.8</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core.compatibility/1.0.0</bundle>

<bundle start-level="20">mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core/1.6.1</bundle>

<conditional>

<condition>bundle</condition>

<bundle start-level="30">mvn:org.apache.karaf.bundle/org.apache.karaf.bundle.blueprintstate/4.0.5</bundle>

</conditional>

<capability>

osgi.service;effective:=active;objectClass=org.apache.aries.blueprint.services.ParserService,

osgi.extender; osgi.extender="osgi.blueprint";uses:="org.osgi.service.blueprint.container,org.osgi.service.blueprint.reflect";version:Version="1.0"

</capability>

</feature>

 

Thanks,

Niten Aggarwal

 

-----Original Message-----
From: Sergey Beryozkin [mailto:[hidden email]]
Sent: Friday, July 22, 2016 12:37 PM
To: [hidden email]
Subject: Re: Blueprint NamespaceHandler issue with karaf 4.0.5

 

Sorry. All I know that proxies need to be somehow configured, but I do not work behind the proxy. May be you've discovered a new bug. You might need to debug or ask at Karaf or Aries lists

 

Sergey

On 22/07/16 18:44, Niten Aggarwal wrote:

> Please let me know if there is any fix available?

> ________________________________________

> From: Niten Aggarwal

> Sent: Thursday, July 21, 2016 9:11 PM

> To: [hidden email]

> Subject: RE: Blueprint NamespaceHandler issue with karaf 4.0.5

> 

> Hi Sergey,

> 

> It doesn't have details how to fix the issue I mean how to witch schemes to online mode.. I am behind the proxy so definitely it's a proxy issue while loading schemes but not able to understand how to fix it.

> I thought 1.6.1 has fixed this issue to understand schema resource location.

> 

> Please let me know how to change online mode.

> ________________________________________

> From: Sergey Beryozkin [[hidden email]]

> Sent: Thursday, July 21, 2016 8:30 PM

> To: [hidden email]

> Subject: Re: Blueprint NamespaceHandler issue with karaf 4.0.5

> 

> Hi

> 

> Can this help:

> 

> https://issues.apache.org/jira/browse/CXF-4063 ?

> 

> Sergey

> On 21/07/16 09:54, Niten Aggarwal wrote:

>> Hello,

>> 

>> I am facing an issue while deploying bundles with CXF 3.1.5 on Karaf 4.0.5. They are working fine with Karaf 4.0.4.

>> It looks like there are couple of bugs already opened but don't know what dependency change I have to do to get it worked. Karaf 4.0.5 automatically comes with blueprint-core 1.6.1 so not sure how to update dependency.

>> 

>> Bugs I was following

>> https://issues.apache.org/jira/browse/ARIES-1540

>> https://issues.apache.org/jira/browse/KARAF-4608

>> 

>> 

>> Error I am getting:

>> 

>> 2016-07-19 13:00:29,176 | WARN  | pool-65-thread-1 | NamespaceHandlerRegistryImpl     | 13 - org.apache.aries.blueprint.core - 1.6.1 | Dynamically adding namespace handler http://cxf.apache.org/configuration/parameterized-types to bundle checkout-api-controller/1.1.0.SNAPSHOT

>> 2016-07-19 13:00:50,188 | ERROR | pool-65-thread-1 | BlueprintContainerImpl           | 13 - org.apache.aries.blueprint.core - 1.6.1 | Unable to start blueprint container for bundle checkout-api-controller/1.1.0.SNAPSHOT

>> org.xml.sax.SAXParseException: src-resolve: Cannot resolve the name 'ptp:ParameterizedInt' to a(n) 'simpleType definition' component.

>>                   at

>> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Un

>> known Source)[:]

>> 

>> Thanks,

>> Niten Aggarwal

>> 

>> 

>> 

>> ::DISCLAIMER::

>> ---------------------------------------------------------------------

>> ---------------------------------------------------------------------

>> ----------

>> 

>> The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.

>> E-mail transmission is not guaranteed to be secure or error-free as

>> information could be intercepted, corrupted, lost, destroyed, arrive

>> late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.

>> Views or opinions, if any, presented in this email are solely those

>> of the author and may not necessarily reflect the views or opinions

>> of HCL or its affiliates. Any form of reproduction, dissemination,

>> copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.

>> Before opening any email and/or attachments, please check them for viruses and other defects.

>> 

>> ---------------------------------------------------------------------

>> ---------------------------------------------------------------------

>> ----------

>> 

> 

> 

> --

> Sergey Beryozkin

> 

> Talend Community Coders

> http://coders.talend.com/

> 

 

 

--

Sergey Beryozkin

 

Talend Community Coders

http://coders.talend.com/