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_EI>/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 <[email protected]>: > 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 <[email protected]>: > >> 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 < >> [email protected]> 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 >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Vinod Kavinda >> Senior Software Engineer >> *WSO2 Inc. - lean . enterprise . middleware <http://www.wso2.com>.* >> Mobile : +94 (0) 712 415544 >> Blog : http://soatechflicks.blogspot.com/ >> [image: http://wso2.com/signature] >> <http://wso2.com/signature> >> >> >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
