Little reminder :
bpel file uses the next :
xsl file used to be using the next :
this will fail (the location of the dvm file isn't relative to both the .bpel file and the .xsl file), correct path to the dvm file will be
besides that i had to use 'actie.dvm' instead of the...
On designtime we use the oramds to develop our processflows in our bpel processes.
Basically the composite.xml part for a bpel process would look like this :
When you open the bpel in jdeveloper, jdeveloper will automatically add the next import to your .bpel file :
The value from the ui:wsdlLocation-attribute is copied to the import/@location.
We had some issues with deploying a composite which retrieves his wsdl for the partnerlinks from Nexus.
The supplier of the services adds the archive with the wsdl artifacts in Nexus, we download the dependency and after that we compile/validate the composite against the downloaded set of artifacts.
For one particular partnerlink the composite just wouldn't compile.
Error message :
In our middleware solutions (Oracle SOA Suite) we use a lot of xsl transformations.
Part of these transformations use database backend systems to do lookups for transforming internal values to external values (which can then be communicated to the customers).
In the Oracle SOA Suite you can create custom xsl function and store the jar in the domain/lib folder and then you will be able to use it in the xsl transformations.
We use Altova XMLSpy a lot for creating all these xsl...
In one of my xsl transformations i needed to import a generic xsl from the mds store.
For this i created a new jdeveloper application with a soa sar deployment descriptor and jar descriptor in it.
Contents of the jar :
When i browse the mds repository i see the SharedMDSResources folder in the root of the tree (instead of in the apps folder).
For testing i deployed the jar manually in the EM.