'Re: OpenSAML - Java compatibility (9, 10, 11?)'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       shibboleth-dev
Subject:    Re: OpenSAML - Java compatibility (9, 10, 11?)
From:       Ian Young <ian () iay ! org ! uk>
Date:       2018-10-12 16:20:55
Message-ID: 9A3EE3B2-E363-4ABE-8240-12FB66B9E834 () iay ! org ! uk
[Download RAW message or body]

[Attachment #2 (multipart/signed)]

[Attachment #4 (multipart/alternative)]


Sorry not to CC you on my previous reply, but it's below anyway.

Just to add to this:

I --- personally, this is not a project position --- would like us to be able to \
support the Java module path in the long run. That's not an easy thing to do, though, \
because of the way they have defined things. A lot of products which were invented \
long before the JPMS was will have some trouble fitting into the constraints that \
have been introduced, particularly around the way things need to be strictly \
partitioned between what were JAR artifacts. It remains to be seen, really, whether \
everyone will adopt the module system or whether instead it will just wither because \
too many things can't use it.

One aspect of this is that I'd be very surprised if OpenSAML was the only thing you'd \
hit problems with if you attempt to deploy things on the module path today. It may \
interest you to know that I surveyed all of the dependencies we ship with the IdP \
product, and other than our own components the only JAR which even has a reserved \
module names is Guava. Everything else is completely unaware of the module system and \
it's a toss-up whether they will work in that environment.

We know of a number of cases where the split package issue comes up in our code, \
which is one reason we don't support the module path at this point. You shouldn't \
expect that we will be able to address that soon. It _would_ nevertheless be useful \
for the longer term if you could open a JIRA case for the issue you've found so that \
we can make sure that we consider it for a future release.

https://issues.shibboleth.net/jira/projects/OSJ/

Cheers,

	-- Ian

> On 12 Oct 2018, at 16:49, Ian Young <ian@iay.org.uk> wrote:
> 
> 
> 
> > On 12 Oct 2018, at 15:43, Cristi Chircu <cristian.chircu@gmail.com \
> > <mailto:cristian.chircu@gmail.com>> wrote: 
> > Hello everyone, 
> > 
> > I've been using OpenSAML 3.3.0   \
> > <https://mvnrepository.com/artifact/org.opensaml/opensaml-core/3.3.0>for a java 8 \
> > service provider and it made my life a lot easier (thanks for sharing, by the way \
> > :) ).  Now I'm trying to upgrade to java 10 and it looks like I'm out of luck. \
> > When I try to deploy I get an exception: "java.lang.module.ResolutionException: \
> > Modules opensaml.saml.impl and opensaml.saml.api export package \
> > org.opensaml.saml.config to module jersey.client".
> 
> I'm guessing that you are trying to put OpenSAML on the Java module path rather \
> than on the classpath. We don't support that at present. 
> > I've searched around for a bit and I can't seem to find clear information on your \
> > plans for newer java versions support.
> 
> We have a page describing our approach here:
> 
> https://wiki.shibboleth.net/confluence/display/DEV/Java+Modularity \
> <https://wiki.shibboleth.net/confluence/display/DEV/Java+Modularity> 
> You will be aware that we recently released a new version of the Shibboleth IdP, \
> and in conjunction with that a new version of OpenSAML. These versions include \
> reserved module names for the various components, and it's _possible_ that may help \
> with the issue you're seeing. As before, though, no guarantees at this stage \
> because we don't support use of the module path yet (we're aware of some split \
> packages, although I don't think the one you've come across was one I was aware \
> of). 
> 
> > I would like to know when you are planning to release a version that works with \
> > java 11 (since it's the newest LTS version)
> 
> The IdP (which uses OpenSAML) works just fine under Java 11. Use the classpath, not \
> the module path. 
> 
> > and what will your approach be regarding Oracles change to their release strategy \
> > (will you support all versions? will you support all LTS versions?). 
> 
> For more information:
> 
> https://wiki.shibboleth.net/confluence/display/DEV/Product+Platforms \
> <https://wiki.shibboleth.net/confluence/display/DEV/Product+Platforms> 
> 
> -- Ian
> 


[Attachment #7 (unknown)]

<html><head><meta http-equiv="Content-Type" content="text/html; \
charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: \
space; line-break: after-white-space;" class="">Sorry not to CC you on my previous \
reply, but it's below anyway.<div class=""><br class=""></div><div class="">Just to \
add to this:</div><div class=""><br class=""></div><div class="">I --- personally, \
this is not a project position --- would like us to be able to support the Java \
module path in the long run. That's not an easy thing to do, though, because of the \
way they have defined things. A lot of products which were invented long before the \
JPMS was will have some trouble fitting into the constraints that have been \
introduced, particularly around the way things need to be strictly partitioned \
between what were JAR artifacts. It remains to be seen, really, whether everyone will \
adopt the module system or whether instead it will just wither because too many \
things can't use it.</div><div class=""><br class=""></div><div class="">One aspect \
of this is that I'd be very surprised if OpenSAML was the only thing you'd hit \
problems with if you attempt to deploy things on the module path today. It may \
interest you to know that I surveyed all of the dependencies we ship with the IdP \
product, and other than our own components the only JAR which even has a reserved \
module names is Guava. Everything else is completely unaware of the module system and \
it's a toss-up whether they will work in that environment.</div><div class=""><br \
class=""></div><div class="">We know of a number of cases where the split package \
issue comes up in our code, which is one reason we don't support the module path at \
this point. You shouldn't expect that we will be able to address that soon. It \
_would_ nevertheless be useful for the longer term if you could open a JIRA case for \
the issue you've found so that we can make sure that we consider it for a future \
release.</div><div class=""><br class=""></div><div class=""><a \
href="https://issues.shibboleth.net/jira/projects/OSJ/" \
class="">https://issues.shibboleth.net/jira/projects/OSJ/</a></div><div class=""><br \
class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div \
class=""><span class="Apple-tab-span" style="white-space:pre">	</span>-- Ian<br \
class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 12 Oct \
2018, at 16:49, Ian Young &lt;<a href="mailto:ian@iay.org.uk" \
class="">ian@iay.org.uk</a>&gt; wrote:</div><br \
class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" \
content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; \
-webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div \
class=""><br class=""><blockquote type="cite" class=""><div class="">On 12 Oct 2018, \
at 15:43, Cristi Chircu &lt;<a href="mailto:cristian.chircu@gmail.com" \
class="">cristian.chircu@gmail.com</a>&gt; wrote:</div><br \
class="Apple-interchange-newline"><div class=""><div class="WordSection1" \
style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Helvetica; \
font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; \
letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; \
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; \
text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; \
font-family: Calibri, sans-serif;" class="">Hello everyone,<span \
class="Apple-converted-space">&nbsp;</span><br class=""><br class="">I've been \
using<span class="Apple-converted-space">&nbsp;</span><a \
href="https://mvnrepository.com/artifact/org.opensaml/opensaml-core/3.3.0" \
target="_top" style="color: purple; text-decoration: underline;" class="">OpenSAML \
3.3.0<span class="Apple-converted-space">&nbsp;</span></a>for a java 8 service \
provider and it made my life a lot easier (thanks for sharing, by the way :) ).<span \
class="Apple-converted-space">&nbsp;</span><br class="">Now I'm trying to upgrade to \
java 10 and it looks like I'm out of luck. When I try to deploy I get an exception: \
"java.lang.module.ResolutionException: Modules opensaml.saml.impl and \
opensaml.saml.api export package org.opensaml.saml.config to module \
jersey.client".</div></div></div></blockquote><div class=""><br class=""></div><div \
class="">I'm guessing that you are trying to put OpenSAML on the Java module path \
rather than on the classpath. We don't support that at present.</div><div \
class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div \
class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); \
font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: \
normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: \
0px; text-transform: none; white-space: normal; word-spacing: 0px; \
-webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in \
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I've searched \
around for a bit and I can't seem to find clear information on your plans for newer \
java versions support.</div></div></div></blockquote><div class=""><br \
class=""></div><div class="">We have a page describing our approach here:</div><div \
class=""><br class=""></div><div class=""><a \
href="https://wiki.shibboleth.net/confluence/display/DEV/Java+Modularity" \
class="">https://wiki.shibboleth.net/confluence/display/DEV/Java+Modularity</a></div><div \
class=""><br class=""></div><div class="">You will be aware that we recently released \
a new version of the Shibboleth IdP, and in conjunction with that a new version of \
OpenSAML. These versions include reserved module names for the various components, \
and it's _possible_ that may help with the issue you're seeing. As before, though, no \
guarantees at this stage because we don't support use of the module path yet (we're \
aware of some split packages, although I don't think the one you've come across was \
one I was aware of).</div><div class=""><br class=""></div><div class=""><br \
class=""></div><blockquote type="cite" class=""><div class=""><div \
class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); \
font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: \
normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: \
0px; text-transform: none; white-space: normal; word-spacing: 0px; \
-webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in \
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I would like \
to know when you are planning to release a version that works with java 11 (since \
it's the newest LTS version)</div></div></div></blockquote><div class=""><br \
class=""></div><div class="">The IdP (which uses OpenSAML) works just fine under Java \
11. Use the classpath, not the module path.</div><div class=""><br \
class=""></div><div class=""><br class=""></div><blockquote type="cite" class=""><div \
class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, \
0); font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: \
normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: \
0px; text-transform: none; white-space: normal; word-spacing: 0px; \
-webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in \
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">and what will \
your approach be regarding Oracles change to their release strategy (will you support \
all versions? will you support all LTS versions?).<span \
class="Apple-converted-space">&nbsp;</span><br \
class=""></div></div></div></blockquote><div class=""><br class=""></div><div \
class=""><div class="">For more information:</div><div class=""><br \
class=""></div><div class=""><a \
href="https://wiki.shibboleth.net/confluence/display/DEV/Product+Platforms" \
class="">https://wiki.shibboleth.net/confluence/display/DEV/Product+Platforms</a></div><div \
class=""><br class=""></div><div class=""><br class=""></div></div></div><div \
class=""><span class="Apple-style-span" style="border-collapse: separate; \
font-variant-ligatures: normal; font-variant-east-asian: normal; \
font-variant-position: normal; line-height: normal; border-spacing: 0px; \
-webkit-text-decorations-in-effect: none;"><div style="word-wrap: break-word; \
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span \
class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; \
font-size: 12px; font-style: normal; font-variant-ligatures: normal; \
font-variant-caps: normal; font-variant-east-asian: normal; font-variant-position: \
normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; \
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: \
0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; \
-webkit-text-stroke-width: 0px;"><div class="">&nbsp; &nbsp; -- Ian<br \
class=""></div><div class=""><span class="Apple-style-span" style="font-size: \
13px;"><br class=""></span></div></span></div></span></div></div></div></blockquote></div><br \
class=""></div></body></html>


["smime.p7s" (smime.p7s)]

0�	*�H��
 �0�10
	`�He0�	*�H��
 �0�'0� jMt�0�J��,I��<0
	*�H��
0��10	UGB10UGreater Manchester10USalford10U
COMODO CA Limited1=0;U4COMODO RSA Client Authentication and Secure Email CA0
180806000000Z
190806235959Z010	*�H��
	ian@iay.org.uk0�"0
	*�H��
�0�
���7�h=��C\3�溰b]D\������E����=c��3�:���3�YK��A���|��>nY?7DT���y����+!�1}��5"N��L5OS�����g�=-��	x��"з�#�ޭ#W�'��}ŀZa�w�� \
nL	�4��YqA��/L!��*[�ZB���W�|a\O.Q��8�̙�n�5�����7Y�換�]MRpIb���s�����z~��u�N \
�%4��=`6��t��2s���0��0U#0���l�����a|�=+qH^ċ�0UY4�� \
��F�ۇD �r���0U� 0U�00 \
U%0++�10	`�H��B 0FU \
?0=0;+�10+0)+https://secure.comodo.net/CPS0ZUS0Q0O M \
K�Ihttp://crl.comodoca.com/COMODORSAClientAuthenticationandSecureEmailCA.crl0��+ \
0}0U+0�Ihttp://crt.comodoca.com/COMODORSAClientAuthenticationandSecureEmailCA.crt0$+0�http://ocsp.comodoca.com0U0�ian@iay.org.uk0
 	*�H��
��*�k��L'��\[V�Τ-�@CG�+lrC�e��#�ԃBR⑥�lL�	�%d�ٸxP����:�=������ \
�%g�_�>̵�wB��v�T�x�6A𮼎�rT|z1H)������Fh1�ޙNR!��Gt���֤n��������y��a1�>8�[ϥ&�5u��n�N�-�!5�7�~g8�/���>�HW�e��iыܭm��|���6TN:
 %Ӯ�<ԡ�e��%���"1Z�� f-0��0�� j��8;�+k��ٸ�RV0
	*�H��
0��10	UGB10UGreater Manchester10USalford10U
COMODO CA Limited1+0)U"COMODO RSA Certification Authority0
130110000000Z
280109235959Z0��10	UGB10UGreater Manchester10USalford10U
COMODO CA Limited1=0;U4COMODO RSA Client Authentication and Secure Email \
CA0�"0 	*�H��
�0�
����W�(vu@�8���v!P�%yL� �}:X>��1.��4vلj��=4H���������K \
�hyt4�z|��e`'�"��2��@rF5 �P�3*U�T��+�%4D5��+ ���ZS�u+�� �=7F_��Z��t ���e���
�>)�
��94�F���ro�8��pN��h�FF���#���Ne6���/M{UW���ֱ�m���A \
�Y����T"o�)�CI�	����m8�4$.zW4 ��r�^M9,R��$ \
����<0�80U#0���~=���<����8���22�0U��l�����a|�=+qH^ċ�0U��0U�0�0U \
 00U 0LUE0C0A ? \
=�;http://crl.comodoca.com/COMODORSACertificationAuthority.crl0q+e0c0;+ \
0�/http://crt.comodoca.com/COMODORSAAddTrustCA.crt0$+0�http://ocsp.comodoca.com0
 	*�H��
�x\��(4O<�_VΟ�V쏢k���I��/5��@��q���B!�f�k&k�n���{hJd|�� \
q��[��L���ǿᓬ�?���"@�f�C���O�ݐrX�ur���J�H5;#���6����8�jle��) �)Y���4 \
�N�ezyq{:��������k�x��%���iچ:w#f6�H�LP~jo9KX��n��M������#:�!!6�����9i\��� \
}�^�M�;�TSX�7�	̯�3�]����Tc�6�O$�v�oX�*5!���������4��������.��a���KE8�HI�Ĺ7�?������Ar���}�r#� \
��R�/�h�<�ס��n���uy<1	3�mɔv�#��~&�p��v�g�' s��kMH#��/ƨ����$/uX�q� \
T���u�(�|�^�-vM҆�NKX�7fA\X��5s��h2���q����P�\Yǟ�E��NR�ar��pG��tZ�p��_"���k�7Dd�JVG�z1��0��0��0��10	UGB10UGreater \
Manchester10USalford10U COMODO CA Limited1=0;U4COMODO RSA Client \
Authentication and Secure Email CAjMt�0�J��,I��<0 	`�He ��0	*�H��
	1	*�H��
0	*�H��
	1
181012162055Z0/	*�H��
	1" R���O�W��[����)���ֳ�>�KZ
�^0��	+�71��0��0��10	UGB10UGreater \
Manchester10USalford10U COMODO CA Limited1=0;U4COMODO RSA Client \
Authentication and Secure Email CAjMt�0�J��,I��<0��*�H�� 	1�� \
��0��10	UGB10UGreater Manchester10USalford10U COMODO CA \
Limited1=0;U4COMODO RSA Client Authentication and Secure Email \
CAjMt�0�J��,I��<0 	*�H��
����=ב��j3A�%u��Ĕ	pq���K�k�I �5�
I�%�'�Ff8�9��J���lQ����Va`S������M��N�����ow���n�������6_�-#]�l�?puT��J��� \
fi'�B�i��gqTLD��,_�lў�<$1���6YQ[u�����S|�}��%ud�}q̓K���T���8��qw٘�|��n�}H�����D�R�&>�5�/.�����s�6�a@����M�




-- 
To unsubscribe from this list send an email to dev-unsubscribe@shibboleth.net

[prev in list] [next in list] [prev in thread] [next in thread]
Configure | About | News | Add a list | Sponsored by KoreLogic