Re: [Dev] EI 6.0.0 and HL7 transport activation

[Vinod Kavinda]

Hi Thomas,
The issue you are experiencing is happening since we are referring to same
plugins directory (jars location for wso2 products) in all the profiles in
WSO2 EI as you already identified. Even though these profiles are shipped
together, they are not running in the same runtime. So what you can do is
keep separate distributions for each profile. Then install the HL7 features
only for the dist you are using for the ESB.

One more suggestion for you, since you are still in the initial development
phase, please upgrade to WSO2 EI 6.1.1. Since 6.0 is the initial version of
the new structure, we have fixed lot of issues in the later versions.

Regards,
Vinod

On Tue, Nov 14, 2017 at 5:54 PM, Thomas LEGRAND <
thomas.legr...@versusmind.eu> wrote:

> Hello!
>
> I come back concerning this problem to give you some extra informations
> (and to point other problems :))
>
> First, my ESB is configured to be able to process convert automatically
> the content of the files with the content-type application/edi-hl7. To do
> so, I uncommented in the file the axis2.xml:
>
>class="org.wso2.carbon.business.messaging.hl7.
> message.HL7MessageFormatter"/>
>
> Since I deployed manually the previoulsy mentioned libraries by dropping
> them in the dropins directory, I noticed that other problems occur:
>
> - When I start the BPS, an OpenJPA error happens because of the dropped
> openjpa-all_2.2.2.wso2v1 in dropins. Meaning that, if I remove it, the
> following stacktrace does not appear and the BPS starts nicely:
>
> TID: [-1234] [] [2017-11-14 13:17:50,750]  INFO {org.wso2.carbon.humantask.
> core.HumanTaskSchedulerInitializer} -  Starting HumanTasks Scheduler
> {org.wso2.carbon.humantask.core.HumanT
> askSchedulerInitializer}
> TID: [-1234] [] [2017-11-14 13:17:51,523] ERROR {org.wso2.carbon.humantask.
> core.scheduler.SimpleScheduler} -  Error retrieving node list. {
> org.wso2.carbon.humantask.core.scheduler.Si
> mpleScheduler}
> 
> org.apache.openjpa.persistence.ArgumentException: An error occurred while
> parsing the query filter "SELECT DISTINCT t.nodeId
>  FROM org.wso2.carbon.humantask.core.dao.jpa.openjpa.model.HumanTaskJob t
> WHERE t.nodeId IS NOT NULL". Error message: The name
> "org.wso2.carbon.humantask.core.dao.jpa.openjpa.model.H
> umanTaskJob" is not a recognized entity or identifier. Perhaps you meant
> HumanTaskJob, which is a close match. Known entity names: [Task,
> PresentationDescription, Message, ProcessIns
> tanceDAOImpl, CorrelatorDAOImpl, ScopeDAOImpl, MexProperty, Attachment,
> ProcessDAOImpl, PresentationSubject, AttachmentDAOImpl,
> ActivityRecoveryDAOImpl, TaskVersion, MessageExchangeD
> AOImpl, MessageDAOImpl, XmlDataProperty, Comment, HumanTaskJob,
> PresentationParameter, OrganizationalEntity, Deadline, MessageRouteDAOImpl,
> PresentationName, FaultDAOImpl, GenericHum
> anRole, PresentationElement, PartnerLinkDAOImpl, CorrelationSetDAOImpl,
> Event, EventDAOImpl, DeploymentUnit, XmlDataDAOImpl, CorrSetProperty]
>
>
> - When I start the BPS or the Broker, I have a stacktrace concerning the
> hl7 messageing component. This is not blocking but that is not clean
> either. This is caused by the presence of the 
> org.wso2.carbon.business.messaging.hl7.*.jar
> files:
>
> TID: [-1234] [] [2017-11-14 12:08:30,078] ERROR {org.wso2.carbon.utils.
> deployment.Axis2ServiceRegistry} -  Error while adding services from
> bundle : org.wso2.carbon.business.messagin
> g.hl7.store-4.6.6 {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry}
> java.lang.NoClassDefFoundError: org/wso2/carbon/mediation/initializer/
> AbstractServiceBusAdmin
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> blablabla
> Caused by: java.lang.ClassNotFoundException: org.wso2.carbon.mediation.
> initializer.AbstractServiceBusAdmin cannot be found by
> org.wso2.carbon.business.messaging.hl7.store_4.6.6
> at org.eclipse.osgi.internal.loader.BundleLoader.
> findClassInternal(BundleLoader.java:501)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
> BundleLoader.java:421)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(
> BundleLoader.java:412)
> at org.eclipse.osgi.internal.baseadaptor.
> DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 66 more
>
> As workaround as my first blocking problem, I just removed the openjpa
> file from the dropins directory. That seems to work but since I just need
> to process files, I doubt that will work if I need to use the ESB to
> persist some HL7 messages in a database using the ESB-integrated-way.
>
> Regards,
>
> Thomas
>
>
> 2017-11-10 9:38 GMT+01:00 Thomas LEGRAND :
>
>> Hello again!
>>
>> Finally, I made a diff of the directory via the command comp > where there aren't the feature libs> > libs> (I am on 

Re: [Dev] EI 6.0.0 and HL7 transport activation

[Thomas LEGRAND]

Hello!

I come back concerning this problem to give you some extra informations
(and to point other problems :))

First, my ESB is configured to be able to process convert automatically the
content of the files with the content-type application/edi-hl7. To do so, I
uncommented in the file the axis2.xml:

 

Since I deployed manually the previoulsy mentioned libraries by dropping
them in the dropins directory, I noticed that other problems occur:

- When I start the BPS, an OpenJPA error happens because of the dropped
openjpa-all_2.2.2.wso2v1 in dropins. Meaning that, if I remove it, the
following stacktrace does not appear and the BPS starts nicely:

TID: [-1234] [] [2017-11-14 13:17:50,750]  INFO
{org.wso2.carbon.humantask.core.HumanTaskSchedulerInitializer} -  Starting
HumanTasks Scheduler {org.wso2.carbon.humantask.core.HumanT
askSchedulerInitializer}
TID: [-1234] [] [2017-11-14 13:17:51,523] ERROR
{org.wso2.carbon.humantask.core.scheduler.SimpleScheduler} -  Error
retrieving node list. {org.wso2.carbon.humantask.core.scheduler.Si
mpleScheduler}

org.apache.openjpa.persistence.ArgumentException: An error occurred while
parsing the query filter "SELECT DISTINCT t.nodeId
 FROM org.wso2.carbon.humantask.core.dao.jpa.openjpa.model.HumanTaskJob t
WHERE t.nodeId IS NOT NULL". Error message: The name
"org.wso2.carbon.humantask.core.dao.jpa.openjpa.model.H
umanTaskJob" is not a recognized entity or identifier. Perhaps you meant
HumanTaskJob, which is a close match. Known entity names: [Task,
PresentationDescription, Message, ProcessIns
tanceDAOImpl, CorrelatorDAOImpl, ScopeDAOImpl, MexProperty, Attachment,
ProcessDAOImpl, PresentationSubject, AttachmentDAOImpl,
ActivityRecoveryDAOImpl, TaskVersion, MessageExchangeD
AOImpl, MessageDAOImpl, XmlDataProperty, Comment, HumanTaskJob,
PresentationParameter, OrganizationalEntity, Deadline, MessageRouteDAOImpl,
PresentationName, FaultDAOImpl, GenericHum
anRole, PresentationElement, PartnerLinkDAOImpl, CorrelationSetDAOImpl,
Event, EventDAOImpl, DeploymentUnit, XmlDataDAOImpl, CorrSetProperty]


- When I start the BPS or the Broker, I have a stacktrace concerning the
hl7 messageing component. This is not blocking but that is not clean
either. This is caused by the presence of the
org.wso2.carbon.business.messaging.hl7.*.jar files:

TID: [-1234] [] [2017-11-14 12:08:30,078] ERROR
{org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -  Error while
adding services from bundle : org.wso2.carbon.business.messagin
g.hl7.store-4.6.6 {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry}
java.lang.NoClassDefFoundError:
org/wso2/carbon/mediation/initializer/AbstractServiceBusAdmin
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
blablabla
Caused by: java.lang.ClassNotFoundException:
org.wso2.carbon.mediation.initializer.AbstractServiceBusAdmin cannot be
found by org.wso2.carbon.business.messaging.hl7.store_4.6.6
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 66 more

As workaround as my first blocking problem, I just removed the openjpa file
from the dropins directory. That seems to work but since I just need to
process files, I doubt that will work if I need to use the ESB to persist
some HL7 messages in a database using the ESB-integrated-way.

Regards,

Thomas


2017-11-10 9:38 GMT+01:00 Thomas LEGRAND :

> Hello again!
>
> Finally, I made a diff of the directory via the command comp  where there aren't the feature libs>  libs> (I am on Windows). So, something like that:
>
> C:\Users\t.legrand>comp D:\ProjetESB\wso2ei-6.0.0-bis\wso2\components\plugins
>> D:\ProjetESB\wso2ei-6.0.0\wso2\components\plugins /A > test.log
>> Comparer d’autres fichiers (O/N) ? n
>>
>
> This generated a file where I could see some messages like
>
> Comparaison de D:\ProjetESB\wso2ei-6.0.0-bis\
>> wso2\components\plugins\axis2-transport-mqtt_2.0.0.wso2v1.jar et
>> D:\ProjetESB\wso2ei-6.0.0\wso2\components\plugins\axis2-
>> transport-mqtt_2.0.0.wso2v1.jar...
>> Comparaison des fichiers OK
>>
> Comparaison de D:\ProjetESB\wso2ei-6.0.0-bis\wso2\components\plugins\org.
>> wso2.carbon.business.messaging.hl7.common_4.6.6.jar et
>> D:\ProjetESB\wso2ei-6.0.0\wso2\components\pluginsorg.
>> wso2.carbon.business.messaging.hl7.common_4.6.6.jar...
>>
> Impossible de trouver/ouvrir le fichier: D:\ProjetESB\wso2ei-6.0.0\
>> wso2\components\plugins\org.wso2.carbon.business.
>> messaging.hl7.common_4.6.6.jar
>>
>
> So, in the end, the installed libraries were:
>
> - openjpa-all_2.2.2.wso2v1
> - 

Re: [Dev] EI 6.0.0 and HL7 transport activation

[Thomas LEGRAND]

Hello again!

Finally, I made a diff of the directory via the command comp   (I am on Windows). So, something like that:

C:\Users\t.legrand>comp
> D:\ProjetESB\wso2ei-6.0.0-bis\wso2\components\plugins
> D:\ProjetESB\wso2ei-6.0.0\wso2\components\plugins /A > test.log
> Comparer d’autres fichiers (O/N) ? n
>

This generated a file where I could see some messages like

Comparaison de
> D:\ProjetESB\wso2ei-6.0.0-bis\wso2\components\plugins\axis2-transport-mqtt_2.0.0.wso2v1.jar
> et
> D:\ProjetESB\wso2ei-6.0.0\wso2\components\plugins\axis2-transport-mqtt_2.0.0.wso2v1.jar...
> Comparaison des fichiers OK
>
Comparaison de
> D:\ProjetESB\wso2ei-6.0.0-bis\wso2\components\plugins\org.wso2.carbon.business.messaging.hl7.common_4.6.6.jar
> et
> D:\ProjetESB\wso2ei-6.0.0\wso2\components\pluginsorg.wso2.carbon.business.messaging.hl7.common_4.6.6.jar...
>
>
Impossible de trouver/ouvrir le fichier:
> D:\ProjetESB\wso2ei-6.0.0\wso2\components\plugins\org.wso2.carbon.business.messaging.hl7.common_4.6.6.jar
>

So, in the end, the installed libraries were:

- openjpa-all_2.2.2.wso2v1
- org.wso2.carbon.business.messaging.hl7.common_4.6.6.jar
- org.wso2.carbon.business.messaging.hl7.message_4.6.6
- org.wso2.carbon.business.messaging.hl7.store.ui_4.6.6.jar
- org.wso2.carbon.business.messaging.hl7.store_4.6.6.jar
- org.wso2.carbon.business.messaging.hl7.transport_4.6.6.jar

So, I dropped those in my dropins directory, in the EI installation without
the feature installed, and that works!

Regards,

Thomas



2017-11-10 5:13 GMT+01:00 Vinod Kavinda :

> [Adding few more people]
>
> On Thu, Nov 9, 2017 at 9:27 PM, Thomas LEGRAND <
> thomas.legr...@versusmind.eu> wrote:
>
>> Hello again!
>>
>> That works nicely after I installed the thingy. But, I am behind a proxy
>> which causes problems so I had to download the whole Wilkes repository and
>> modify the elements metadataRepository & artifactRepository to point to it
>> (something like file:///to/my/local/repo). And I am disappointed because it
>> installs directly in the components directory which make the installation
>> on production a more painful. I think this is overkill to deploy a 2 Gb
>> repository to install jar (And I don't think I am the only person who think
>> that :))).
>>
>> Is there a way to extract the jars that was installed to install them
>> "manually" on another platform? Except by making a diff of the directory
>> /wso2/components? And if I copy/paster them manually, will that
>> work or P2 make some hidden configuration on the EI too?
>>
>> Regards,
>>
>> Thomas
>>
>> 2017-11-09 16:08 GMT+01:00 Thomas LEGRAND :
>>
>>> Hello Vinod,
>>>
>>> This is embarrassing... :$
>>>
>>> I did not "see" this paragraph thinking that it was just a *boring*
>>> introduction (like we have in every tutorial on the net) so I jumped
>>> directly to the "Enabling the transport" part via the summary. :$
>>>
>>> Regards,
>>>
>>> Thomas
>>>
>>> 2017-11-09 16:04 GMT+01:00 Vinod Kavinda :
>>>
 Hi Thomas,
 The HL7 feature is not shipped with EI 6 by default, due to the
 licensing issues. Did you install the HL7 feature as mentioned in the first
 paragraph of the doc [1]?

 [1] https://docs.wso2.com/display/EI600/HL7+Transport

 Regards,
 Vinod

 On Thu, Nov 9, 2017 at 4:07 PM, Thomas LEGRAND <
 thomas.legr...@versusmind.eu> wrote:

> Hello,
>
> I have a use case where I have a directory in which are dropped HL7
> messages in the ER7 format (the pipe one). So I created an inbound 
> endpoint
> which monitors this directory and eat every .hl7 file it founds. But, it
> does not know how to parse them correctly because it displays some error
> about a mistake in the file prolog (expecting a < and found a M). OK, so 
> it
> tries to read my HL7 file like if it was an XML one.
>
> So I check the doc and found that [1]. Nice! Let's try this!
>
> And... BOOM:
>
> Caused by: org.apache.axis2.deployment.DeploymentException:
> org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
> cannot be found by axis2_1.6.1.wso2v20
> at org.apache.axis2.deployment.Ax
> isConfigBuilder.processTransportReceivers(AxisConfigBuilder.java:639)
> at org.apache.axis2.deployment.Ax
> isConfigBuilder.populateConfig(AxisConfigBuilder.java:130)
> at org.wso2.carbon.core.CarbonAxi
> sConfigurator.populateAxisConfiguration(CarbonAxisConfigurat
> or.java:341)
> at org.wso2.carbon.core.CarbonAxi
> sConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:192)
> ... 41 more
> Caused by: java.lang.ClassNotFoundException:
> org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
> cannot be found by axis2_1.6.1.wso2v20
>
> I searched a little and I found a class [2] which seems to be in a
> business-adaptors 

Re: [Dev] EI 6.0.0 and HL7 transport activation

[Vinod Kavinda]

[Adding few more people]

On Thu, Nov 9, 2017 at 9:27 PM, Thomas LEGRAND  wrote:

> Hello again!
>
> That works nicely after I installed the thingy. But, I am behind a proxy
> which causes problems so I had to download the whole Wilkes repository and
> modify the elements metadataRepository & artifactRepository to point to it
> (something like file:///to/my/local/repo). And I am disappointed because it
> installs directly in the components directory which make the installation
> on production a more painful. I think this is overkill to deploy a 2 Gb
> repository to install jar (And I don't think I am the only person who think
> that :))).
>
> Is there a way to extract the jars that was installed to install them
> "manually" on another platform? Except by making a diff of the directory
> /wso2/components? And if I copy/paster them manually, will that
> work or P2 make some hidden configuration on the EI too?
>
> Regards,
>
> Thomas
>
> 2017-11-09 16:08 GMT+01:00 Thomas LEGRAND :
>
>> Hello Vinod,
>>
>> This is embarrassing... :$
>>
>> I did not "see" this paragraph thinking that it was just a *boring*
>> introduction (like we have in every tutorial on the net) so I jumped
>> directly to the "Enabling the transport" part via the summary. :$
>>
>> Regards,
>>
>> Thomas
>>
>> 2017-11-09 16:04 GMT+01:00 Vinod Kavinda :
>>
>>> Hi Thomas,
>>> The HL7 feature is not shipped with EI 6 by default, due to the
>>> licensing issues. Did you install the HL7 feature as mentioned in the first
>>> paragraph of the doc [1]?
>>>
>>> [1] https://docs.wso2.com/display/EI600/HL7+Transport
>>>
>>> Regards,
>>> Vinod
>>>
>>> On Thu, Nov 9, 2017 at 4:07 PM, Thomas LEGRAND <
>>> thomas.legr...@versusmind.eu> wrote:
>>>
 Hello,

 I have a use case where I have a directory in which are dropped HL7
 messages in the ER7 format (the pipe one). So I created an inbound endpoint
 which monitors this directory and eat every .hl7 file it founds. But, it
 does not know how to parse them correctly because it displays some error
 about a mistake in the file prolog (expecting a < and found a M). OK, so it
 tries to read my HL7 file like if it was an XML one.

 So I check the doc and found that [1]. Nice! Let's try this!

 And... BOOM:

 Caused by: org.apache.axis2.deployment.DeploymentException:
 org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
 cannot be found by axis2_1.6.1.wso2v20
 at org.apache.axis2.deployment.AxisConfigBuilder.processTranspo
 rtReceivers(AxisConfigBuilder.java:639)
 at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig
 (AxisConfigBuilder.java:130)
 at org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConf
 iguration(CarbonAxisConfigurator.java:341)
 at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfigura
 tion(CarbonAxisConfigurator.java:192)
 ... 41 more
 Caused by: java.lang.ClassNotFoundException:
 org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
 cannot be found by axis2_1.6.1.wso2v20

 I searched a little and I found a class [2] which seems to be in a
 business-adaptors component which I can't find in my distribution.

 Where can I have it, please?

 Regards,

 Thomas

 [1] https://docs.wso2.com/display/EI600/HL7+Transport
 [2] https://github.com/wso2/carbon-mediation/blob/master/compone
 nts/business-adaptors/hl7/org.wso2.carbon.business.messaging
 .hl7.transport/src/main/java/org/wso2/carbon/business/messag
 ing/hl7/transport/HL7TransportListener.java

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Vinod Kavinda
>>> Senior Software Engineer
>>> *WSO2 Inc. - lean . enterprise . middleware .*
>>> Mobile : +94 (0) 712 415544
>>> Blog : http://soatechflicks.blogspot.com/
>>> [image: http://wso2.com/signature]
>>> 
>>>
>>>
>>
>


-- 
Vinod Kavinda
Senior Software Engineer
*WSO2 Inc. - lean . enterprise . middleware .*
Mobile : +94 (0) 712 415544
Blog : http://soatechflicks.blogspot.com/
[image: http://wso2.com/signature]

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] EI 6.0.0 and HL7 transport activation

[Thomas LEGRAND]

Hello Vinod,

This is embarrassing... :$

I did not "see" this paragraph thinking that it was just a *boring*
introduction (like we have in every tutorial on the net) so I jumped
directly to the "Enabling the transport" part via the summary. :$

Regards,

Thomas

2017-11-09 16:04 GMT+01:00 Vinod Kavinda :

> Hi Thomas,
> The HL7 feature is not shipped with EI 6 by default, due to the licensing
> issues. Did you install the HL7 feature as mentioned in the first paragraph
> of the doc [1]?
>
> [1] https://docs.wso2.com/display/EI600/HL7+Transport
>
> Regards,
> Vinod
>
> On Thu, Nov 9, 2017 at 4:07 PM, Thomas LEGRAND <
> thomas.legr...@versusmind.eu> wrote:
>
>> Hello,
>>
>> I have a use case where I have a directory in which are dropped HL7
>> messages in the ER7 format (the pipe one). So I created an inbound endpoint
>> which monitors this directory and eat every .hl7 file it founds. But, it
>> does not know how to parse them correctly because it displays some error
>> about a mistake in the file prolog (expecting a < and found a M). OK, so it
>> tries to read my HL7 file like if it was an XML one.
>>
>> So I check the doc and found that [1]. Nice! Let's try this!
>>
>> And... BOOM:
>>
>> Caused by: org.apache.axis2.deployment.DeploymentException:
>> org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
>> cannot be found by axis2_1.6.1.wso2v20
>> at org.apache.axis2.deployment.AxisConfigBuilder.processTranspo
>> rtReceivers(AxisConfigBuilder.java:639)
>> at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig
>> (AxisConfigBuilder.java:130)
>> at org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConf
>> iguration(CarbonAxisConfigurator.java:341)
>> at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfigura
>> tion(CarbonAxisConfigurator.java:192)
>> ... 41 more
>> Caused by: java.lang.ClassNotFoundException:
>> org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
>> cannot be found by axis2_1.6.1.wso2v20
>>
>> I searched a little and I found a class [2] which seems to be in a
>> business-adaptors component which I can't find in my distribution.
>>
>> Where can I have it, please?
>>
>> Regards,
>>
>> Thomas
>>
>> [1] https://docs.wso2.com/display/EI600/HL7+Transport
>> [2] https://github.com/wso2/carbon-mediation/blob/master/compone
>> nts/business-adaptors/hl7/org.wso2.carbon.business.messaging
>> .hl7.transport/src/main/java/org/wso2/carbon/business/
>> messaging/hl7/transport/HL7TransportListener.java
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Vinod Kavinda
> Senior Software Engineer
> *WSO2 Inc. - lean . enterprise . middleware .*
> Mobile : +94 (0) 712 415544
> Blog : http://soatechflicks.blogspot.com/
> [image: http://wso2.com/signature]
> 
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] EI 6.0.0 and HL7 transport activation

[Thomas LEGRAND]

Hello again!

That works nicely after I installed the thingy. But, I am behind a proxy
which causes problems so I had to download the whole Wilkes repository and
modify the elements metadataRepository & artifactRepository to point to it
(something like file:///to/my/local/repo). And I am disappointed because it
installs directly in the components directory which make the installation
on production a more painful. I think this is overkill to deploy a 2 Gb
repository to install jar (And I don't think I am the only person who think
that :))).

Is there a way to extract the jars that was installed to install them
"manually" on another platform? Except by making a diff of the directory
/wso2/components? And if I copy/paster them manually, will that
work or P2 make some hidden configuration on the EI too?

Regards,

Thomas

2017-11-09 16:08 GMT+01:00 Thomas LEGRAND :

> Hello Vinod,
>
> This is embarrassing... :$
>
> I did not "see" this paragraph thinking that it was just a *boring*
> introduction (like we have in every tutorial on the net) so I jumped
> directly to the "Enabling the transport" part via the summary. :$
>
> Regards,
>
> Thomas
>
> 2017-11-09 16:04 GMT+01:00 Vinod Kavinda :
>
>> Hi Thomas,
>> The HL7 feature is not shipped with EI 6 by default, due to the licensing
>> issues. Did you install the HL7 feature as mentioned in the first paragraph
>> of the doc [1]?
>>
>> [1] https://docs.wso2.com/display/EI600/HL7+Transport
>>
>> Regards,
>> Vinod
>>
>> On Thu, Nov 9, 2017 at 4:07 PM, Thomas LEGRAND <
>> thomas.legr...@versusmind.eu> wrote:
>>
>>> Hello,
>>>
>>> I have a use case where I have a directory in which are dropped HL7
>>> messages in the ER7 format (the pipe one). So I created an inbound endpoint
>>> which monitors this directory and eat every .hl7 file it founds. But, it
>>> does not know how to parse them correctly because it displays some error
>>> about a mistake in the file prolog (expecting a < and found a M). OK, so it
>>> tries to read my HL7 file like if it was an XML one.
>>>
>>> So I check the doc and found that [1]. Nice! Let's try this!
>>>
>>> And... BOOM:
>>>
>>> Caused by: org.apache.axis2.deployment.DeploymentException:
>>> org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
>>> cannot be found by axis2_1.6.1.wso2v20
>>> at org.apache.axis2.deployment.AxisConfigBuilder.processTranspo
>>> rtReceivers(AxisConfigBuilder.java:639)
>>> at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig
>>> (AxisConfigBuilder.java:130)
>>> at org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConf
>>> iguration(CarbonAxisConfigurator.java:341)
>>> at org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfigura
>>> tion(CarbonAxisConfigurator.java:192)
>>> ... 41 more
>>> Caused by: java.lang.ClassNotFoundException:
>>> org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
>>> cannot be found by axis2_1.6.1.wso2v20
>>>
>>> I searched a little and I found a class [2] which seems to be in a
>>> business-adaptors component which I can't find in my distribution.
>>>
>>> Where can I have it, please?
>>>
>>> Regards,
>>>
>>> Thomas
>>>
>>> [1] https://docs.wso2.com/display/EI600/HL7+Transport
>>> [2] https://github.com/wso2/carbon-mediation/blob/master/compone
>>> nts/business-adaptors/hl7/org.wso2.carbon.business.messaging
>>> .hl7.transport/src/main/java/org/wso2/carbon/business/messag
>>> ing/hl7/transport/HL7TransportListener.java
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Vinod Kavinda
>> Senior Software Engineer
>> *WSO2 Inc. - lean . enterprise . middleware .*
>> Mobile : +94 (0) 712 415544
>> Blog : http://soatechflicks.blogspot.com/
>> [image: http://wso2.com/signature]
>> 
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] EI 6.0.0 and HL7 transport activation

[Vinod Kavinda]

Hi Thomas,
The HL7 feature is not shipped with EI 6 by default, due to the licensing
issues. Did you install the HL7 feature as mentioned in the first paragraph
of the doc [1]?

[1] https://docs.wso2.com/display/EI600/HL7+Transport

Regards,
Vinod

On Thu, Nov 9, 2017 at 4:07 PM, Thomas LEGRAND  wrote:

> Hello,
>
> I have a use case where I have a directory in which are dropped HL7
> messages in the ER7 format (the pipe one). So I created an inbound endpoint
> which monitors this directory and eat every .hl7 file it founds. But, it
> does not know how to parse them correctly because it displays some error
> about a mistake in the file prolog (expecting a < and found a M). OK, so it
> tries to read my HL7 file like if it was an XML one.
>
> So I check the doc and found that [1]. Nice! Let's try this!
>
> And... BOOM:
>
> Caused by: org.apache.axis2.deployment.DeploymentException:
> org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
> cannot be found by axis2_1.6.1.wso2v20
> at org.apache.axis2.deployment.AxisConfigBuilder.
> processTransportReceivers(AxisConfigBuilder.java:639)
> at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(
> AxisConfigBuilder.java:130)
> at org.wso2.carbon.core.CarbonAxisConfigurator.
> populateAxisConfiguration(CarbonAxisConfigurator.java:341)
> at org.wso2.carbon.core.CarbonAxisConfigurator.
> getAxisConfiguration(CarbonAxisConfigurator.java:192)
> ... 41 more
> Caused by: java.lang.ClassNotFoundException: org.wso2.carbon.business.
> messaging.hl7.transport.HL7TransportListener cannot be found by
> axis2_1.6.1.wso2v20
>
> I searched a little and I found a class [2] which seems to be in a
> business-adaptors component which I can't find in my distribution.
>
> Where can I have it, please?
>
> Regards,
>
> Thomas
>
> [1] https://docs.wso2.com/display/EI600/HL7+Transport
> [2] https://github.com/wso2/carbon-mediation/blob/master/
> components/business-adaptors/hl7/org.wso2.carbon.business.
> messaging.hl7.transport/src/main/java/org/wso2/carbon/
> business/messaging/hl7/transport/HL7TransportListener.java
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vinod Kavinda
Senior Software Engineer
*WSO2 Inc. - lean . enterprise . middleware .*
Mobile : +94 (0) 712 415544
Blog : http://soatechflicks.blogspot.com/
[image: http://wso2.com/signature]

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] EI 6.0.0 and HL7 transport activation

[Thomas LEGRAND]

Hello,

I have a use case where I have a directory in which are dropped HL7
messages in the ER7 format (the pipe one). So I created an inbound endpoint
which monitors this directory and eat every .hl7 file it founds. But, it
does not know how to parse them correctly because it displays some error
about a mistake in the file prolog (expecting a < and found a M). OK, so it
tries to read my HL7 file like if it was an XML one.

So I check the doc and found that [1]. Nice! Let's try this!

And... BOOM:

Caused by: org.apache.axis2.deployment.DeploymentException:
org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
cannot be found by axis2_1.6.1.wso2v20
at
org.apache.axis2.deployment.AxisConfigBuilder.processTransportReceivers(AxisConfigBuilder.java:639)
at
org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:130)
at
org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(CarbonAxisConfigurator.java:341)
at
org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:192)
... 41 more
Caused by: java.lang.ClassNotFoundException:
org.wso2.carbon.business.messaging.hl7.transport.HL7TransportListener
cannot be found by axis2_1.6.1.wso2v20

I searched a little and I found a class [2] which seems to be in a
business-adaptors component which I can't find in my distribution.

Where can I have it, please?

Regards,

Thomas

[1] https://docs.wso2.com/display/EI600/HL7+Transport
[2]
https://github.com/wso2/carbon-mediation/blob/master/components/business-adaptors/hl7/org.wso2.carbon.business.messaging.hl7.transport/src/main/java/org/wso2/carbon/business/messaging/hl7/transport/HL7TransportListener.java
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev