I am trying to configure wildfly10 and JDK 1.8.xx.212 for the truststore and following is my configuration in host.xml.
but I see following error.
[Server:wildfly-server-one] 09:00:04,441 INFO [stdout] (MSC service thread 1-3) trustStore type is : jks
[Server:wildfly-server-one] 09:00:04,441 INFO [stdout] (MSC service thread 1-3) trustStore provider is : PKCS12
[Server:wildfly-server-one] 09:00:04,441 INFO [stdout] (MSC service thread 1-3) init truststore
[Server:wildfly-server-one] 09:00:04,443 INFO [stdout] (MSC service thread 1-3) SunX509: skip default keystore: java.security.NoSuchProviderException: no such provider: PKCS12
[Server:wildfly-server-one] 09:00:04,449 INFO [stdout] (MSC service thread 1-3) trigger seeding of SecureRandom
[Server:wildfly-server-one] 09:00:04,450 INFO [stdout] (MSC service thread 1-3) done seeding SecureRandom
I have reinstalled jvm to ensure clean installation. However there is no change.
I have copied the stacktrace for the handshaking error at pastebin webpage.
It does seems our certificate gets added initially as per following:
The somebody choose OSGI for the project. That means there is a smart architect sitting there who knows importance of modularity. I believe there must be other supporting frameworks will be used on need basis, and project manager may not aware of it.
And what made you think that learning something new in software industry will reduce job opportunity for you?
I started going through OSGI at later stage of my career and then I am wondering why did I spent learning Struts vs Spring vs Seam. I could have learnt OSGI and keep it using from last 10 years. The framework is cloud agnostic from day one. Thanks Kirk for promoting OSGI concepts further.
Interesting thought, I am inline with you. Modularity is a modularity, what it has to do with language(.Net or Java). But it has to do with framework, to bring smart and average engineer in same page. And the best way of achieving Modularity is through usage OSGI. Does the book follows same root? Do you expand it to explain the usage of AOP in modularity?
As you mention books goes beyond OO concepts. However I assume the nucleus of modularity must be OOP. Do you share same thoughts.
Seems you are creating new patterns in the context of modularity. In that case, I believe the GOF patterns can be applicable in side a module but not between the modules.
For the sack of POC I have used JBoss 7.x(which has OSGI container) and HBase and integrated them. Though for the web application I have not used OSGI, the concept is very valid. You can deploy OSGI in the container and connect with Big Data(I don't know which DB you planning to choose). I choose JBoss as I plan to use it as more of an ESB then just a container. In normal situation Felix will work too.