OK
I'll prepare branch pax-web-6.1.x where pax-web-undertow may be configured
using XML. The trigger is when org.ops4j.pax.web PID has:
org.ops4j.pax.web.config.url = scheme://.../*.xml
or
org.ops4j.pax.web.config.file = /path/to/*.xml
or
org.ops4j.pax.web.config.file = /path/to/directory # when there's
"undertow.xml" in given directory
In other case, normal configuration is used as before (combination of all
PID properties + undertow.properties to configure IdentityManager).
Ah - inside XML we may use property placeholders for properties from:
– org.ops4j.pax.web PID
– bundle context properties
– system properties
Here's sample configuration:
<?xml version="1.0" encoding="UTF-8"?>
<undertow xmlns="urn:org.ops4j.pax.web:undertow:1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:w="urn:jboss:domain:4.2"
xsi:schemaLocation="
urn:jboss:domain:undertow:3.1
http://www.jboss.org/schema/jbossas/wildfly-undertow_3_1.xsd
urn:jboss:domain:4.2
http://www.jboss.org/schema/jbossas/wildfly-config_4_2.xsd">
<subsystem xmlns="urn:jboss:domain:undertow:3.1">
<server name="default-server">
<https-listener name="https" socket-binding="https"
security-realm="default" verify-client="REQUIRED" />
<host name="default-host" alias="localhost">
<location name="/docs" handler="docs-handler" />
<location name="/welcome" handler="welcome-handler" />
<access-log pattern="common" directory="target"
prefix="access--log--simple" suffix=".log" />
<filter-ref name="server" />
<filter-ref name="power" />
</host>
</server>
<servlet-container name="default">
<welcome-files>
<welcome-file name="index.txt" />
</welcome-files>
</servlet-container>
<handlers>
<file name="docs-handler" path="target/sites/docs" />
<file name="welcome-handler" path="target/sites/home" />
</handlers>
<filters>
<response-header name="server" header-name="Server"
header-value="Pax-Web/42" />
<response-header name="power" header-name="X-Powered-By"
header-value="OPS4J" />
</filters>
</subsystem>
<security-realm name="default">
<w:server-identities>
<w:ssl>
<w:engine
enabled-cipher-suites="TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256"
enabled-protocols="TLSv1 TLSv1.1 TLSv1.2" />
<w:keystore
path="src/test/resources-binary/certs/server.keystore" provider="JKS"
alias="server"
keystore-password="secret1" key-password="secret2"
/>
</w:ssl>
</w:server-identities>
<w:authentication>
<w:truststore
path="src/test/resources-binary/certs/server.keystore" provider="JKS"
keystore-password="secret1" />
<w:properties path="target/users.properties" />
</w:authentication>
</security-realm>
<interface name="default">
<w:inet-address value="127.0.0.1" />
</interface>
<socket-binding name="https" interface="default"
port="${org.osgi.service.http.port.secure}" />
</undertow>
best regards
Grzegorz Grzybek
2017-09-04 15:01 GMT+02:00 Jean-Baptiste Onofré <
[email protected]>:
> Hi
>
> It sounds good to me.
>
> Regards
> JB
> On Sep 4, 2017, at 14:03, Grzegorz Grzybek <[email protected]> wrote:
>>
>> Hello
>>
>> I'm almost done with PAXWEB-1103 (XML configuration for Undertow) and it
>> looks like this can no longer be considered a micro change.
>>
>> I wanted to ask you if we can do this:
>> – create new branch pax-web-6.1.x out of current 6.0.x from which
>> version 6.1.0 could be released soon (including PAXWEB-1103)
>> – have pax-web-6.0.x branch as is for 6.0.x maintenance
>> – bump version to 7.0.0-SNAPSHOT in master branch (to reflect work on R7
>> spec)
>>
>> What do you think?
>> regards
>> Grzegorz Grzybek
>>
>> --
> --
> ------------------
> OPS4J - http://www.ops4j.org - [email protected]
>
> ---
> You received this message because you are subscribed to the Google Groups
> "OPS4J" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
--
------------------
OPS4J - http://www.ops4j.org - [email protected]
---
You received this message because you are subscribed to the Google Groups
"OPS4J" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.