Re: [wildfly-dev] HTTP Upgrade for AS8 Management
by David M. Lloyd
On 03/28/2013 05:15 AM, Stuart Douglas wrote:
> - ModelControllerClient.Factory.create() now allows you to specify a
> protocol, which can be either remote, http or https.
>
> - Remote JMX will now require a service:jmx:http(s)-remoting-jmx:// URL
> rather than the current service:jmx:remoting-jmx://
Unfortunately I missed-slash-bungled this way back when, but we need to
sort out our URI schemes.
When we have multi-layer protocol going on, the URI scheme we should use
is like this:
outer+middle+inner://
where "outer" is the outermost protocol (e.g. "remote"), and "inner" is
the innermost (not counting layer 3 and lower *unless* that figures
directly in to the URI scheme; an example of this sub-case is
"stratum+tcp" vs "stratum+udp").
So we *should* have:
remote:// Direct Remoting-protocol connection
remote+http:// Remoting over HTTP upgrade
remote+https:// Remoting over HTTPS upgrade
And (if these are even really needed; I think we dropped this
distinction though maybe I'm wrong):
jmx+remote:// JMX over Remoting
jmx+remote+http:// JMX over Remoting over HTTP
jmx+remote+https:// JMX over Remoting over HTTPS
The most common "de facto" function of hyphenation in a URI scheme is to
be a separator for a two-word protocol, like "view-source" or "ms-help"
etc. The most common "de facto" function of using "+" is as I've
described above, perhaps made most popular by Subversion's use.
You may be wondering: Why not apply this to every single protocol we
have? And/or every single protocol in existence? I think this goes
beyond practicality - the point is to be unambiguous and consistent, and
also align on the correct "remote" scheme name (we have a mix of
"remote" and "remoting" today which is kind of confusing).
Fixing this is not really a top priority obviously, but I would like to
eventually unify our configuration on these scheme names (still
supporting the old scheme names for compatibility of course).
--
- DML
10 years, 6 months
WildFly 8.1.0.Final Released!
by Jason Greene
Hi Everyone,
I’m happy to announce the release of 8.1.0.Final. This release includes a few minor enhancements and a significant number of bug fixes (247 issues resolved!). Also, as requested by my recent poll, the release includes an update package that can be used with the patch command to update an 8.0.0.Final distro in-place.
More details are available here:
https://community.jboss.org/wiki/WildFly810FinalReleaseNotes
The standard download location is here:
http://wildfly.org/downloads
Thank you everyone for all the hard work you put into this release!
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
10 years, 7 months
8.2 Release Plan
by Jason Greene
Hello Everyone,
Since we were forced to pull the CDI 1.1 update out of 8.1 (TCK rules), and the work was already completed, I have added an 8.2 into jira, with a primary focus on delivering this important update. This release is dependent on an EE7 TCK update allowing it in, so I unfortunately can’t yet set a date for the release. While the focus should be on 9, I am leaving the 8.x branch open for high priority bug fixes that can be included with the CDI update.
As in the past, I need two pull requests for every proposed addition to 8.x, one against master, and the other against the 8.x branch. Please prefix the subject of the pull request with [8.x].
Thanks!
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
10 years, 7 months
