gmunozfe commented on code in PR #4538:
URL:
https://github.com/apache/incubator-kie-docs/pull/4538#discussion_r1954907277
##########
doc-content/shared-kie-docs/src/main/asciidoc/Commands/runtime-commands-marshalling-ref.adoc:
##########
@@ -0,0 +1,88 @@
+// This section determined obsolete and handled by the Java client services in
KIE Server. Retaining for now, just in case. (Stetson, 13 Nov 2018)
+
+[id='runtime-commands-marshalling-ref_{context}']
+= Runtime commands marshalling
+
+Marshalling and unmarshalling of the {PRODUCT} rule services commands requires
the following classes, depending on the marshaller type:
+
+XStream::
+For the XStream commands marshaller, use the `DroolsHelperProvider` to obtain
an `XStream` instance where the commands converters are registered. Also ensure
that the `drools-compiler` library is present on the class path.
++
+--
+[source,java]
+----
+BatchExecutionHelper.newXStreamMarshaller().toXML(command);
+----
+
+[source,java]
+----
+BatchExecutionHelper.newXStreamMarshaller().fromXML(xml);
+----
+
+The fully-qualified class name of the `BatchExecutionHelper` class is
`org.kie.internal.runtime.helper.BatchExecutionHelper`.
+--
+
+JSON::
+For the JSON commands marshaller, use the `DroolsHelperProvider` to obtain a
`JSON` instance where the commands converters are registered. Also ensure that
the `drools-compiler` library is present on the class path.
++
+--
+[source,java]
+----
+BatchExecutionHelper.newJSonMarshaller().toXML(command);
+----
+
+[source,java]
+----
+BatchExecutionHelper.newJSonMarshaller().fromXML(xml);
+----
+--
+JAXB::
+For the JAXB commands marshaller, you can define your model in an XSD file or
use an object model. In both cases, you declare your model inside `JAXBContext`
using Drools Helper classes. After you have the `JAXBContext`, you can create
the marshellar or unmarsheller as needed.
++
+--
+* *JAXB marshalling in XSD file:* Add the XSD file as an XSD `ResourceType`
into the KIE base and create the `JAXBContext` using the KIE base (created with
the `KnowledgeBuilder`). Ensure that the `drools-compiler` and `jaxb-xjc`
libraries are present on the class path.
++
+[source,java]
+----
+import org.kie.api.conf.Option;
+import org.kie.api.KieBase;
+
+Options xjcOpts = new Options();
+xjcOpts.setSchemaLanguage(Language.XMLSCHEMA);
+JaxbConfiguration jaxbConfiguration =
+ KnowledgeBuilderFactory.newJaxbConfiguration( xjcOpts, "xsd");
+kbuilder.add
+ (ResourceFactory.newClassPathResource
+ ("person.xsd", getClass()), ResourceType.XSD, jaxbConfiguration);
+KieBase kbase = kbuilder.newKnowledgeBase();
+
+List<String> classesName = new ArrayList<String>();
+classesName.add("org.drools.compiler.test.Person");
+
+JAXBContext jaxbContext = KnowledgeBuilderHelper
+ .newJAXBContext(classesName.toArray(new String[classesName.size()]), kbase);
+----
+
+* *JAXB marshalling in object model:* Use `DroolsJaxbHelperProviderImpl` to
create the `JAXBContext`.
`DroolsJaxbHelperProviderImpl.createDroolsJaxbContext()` has two parameters:
+
+** *classNames:* A list with the canonical name of the classes that you want
to use in the marshalling and unmarshalling process
+** *properties:* JAXB custom properties
++
+[source,java]
+----
+List<String> classNames = new ArrayList<String>();
+classNames.add("org.drools.compiler.test.Person");
+
+JAXBContext jaxbContext = DroolsJaxbHelperProviderImpl
+ .createDroolsJaxbContext(classNames, null);
+Marshaller marshaller = jaxbContext.createMarshaller();
+----
++
+The fully-qualified class name of the `DroolsJaxbHelperProviderImpl` class is
`org.drools.compiler.runtime.pipeline.impl.DroolsJaxbHelperProviderImpl`.
+--
+
+The following are example command scripts using XStream, JSON, and JAXB
marshalling:
+
+*
http://fisheye.jboss.org/browse/JBossRules/trunk/drools-camel/src/test/resources/org/drools/camel/component/xstream.mvt?r=HEAD[xstream.mvt]
+*
http://fisheye.jboss.org/browse/JBossRules/trunk/drools-camel/src/test/resources/org/drools/camel/component/json.mvt?r=HEAD[json.mvt]
+*
http://fisheye.jboss.org/browse/JBossRules/trunk/drools-camel/src/test/resources/org/drools/camel/component/jaxb.mvt?r=HEAD[jaxb.mvt]
Review Comment:
Are these links fine? I couldn't access
##########
.github/workflows/pull_request_no_chain.yml:
##########
@@ -0,0 +1,26 @@
+name: Apache KIE Documentation - Build Check
Review Comment:
@domhanak header is not needed here?
##########
doc-content/shared-kie-docs/src/main/asciidoc/KIE/BuildDeployUtilizeAndRun/executable-model-upgrading-proc.adoc:
##########
@@ -0,0 +1,65 @@
+[id='executable-model-upgrading-proc_{context}']
+ifdef::DM,PAM[]
+:PRODUCT_VERSION: 7.8
+endif::[]
+ifdef::DROOLS,JBPM,OP[]
+:PRODUCT_VERSION: 7.39
Review Comment:
Same here 7.67
##########
doc-content/shared-kie-docs/src/main/asciidoc/KIE/BuildDeployUtilizeAndRun/executable-model-upgrading-proc.adoc:
##########
@@ -0,0 +1,65 @@
+[id='executable-model-upgrading-proc_{context}']
+ifdef::DM,PAM[]
+:PRODUCT_VERSION: 7.8
Review Comment:
Is this fine? seems not updated? 7.13.5
##########
doc-content/shared-kie-docs/src/main/asciidoc/Install/Building_from_source-section.adoc:
##########
@@ -0,0 +1,34 @@
+
+= Building from source
+
+== Getting the sources
+
+The source code of each Maven artifact is available in the JBoss Maven
repository as a source JAR.
+The same source JARs are also included in the download zips.
+However, if you want to build from source, it's highly recommended to get our
sources from our source control.
+
+Drools and jBPM use http://git-scm.com/[Git] for source control.
+The blessed git repositories are hosted on https://github.com[GitHub]:
+
+* https://github.com/kiegroup
+
+Git allows you to fork our code, independently make personal changes on it,
yet still merge in our latest changes regularly and optionally share your
changes with us.
+To learn more about git, read the free book http://progit.org/book/[Git Pro].
+
+== Building the sources
+
+In essence, building from source is very easy, for example if you want to
build the [term]_guvnor_
+ project:
Review Comment:
Guvnor still applies? Because it's archived
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
