Facet support for eap6.x?
by Rob Stryker
Hey all:
So about a year ago I bumped facet support for wildfly and eap6.x to
include the jee7 facets. See:
https://github.com/jbosstools/jbosstools-server/commit/871c03d310bb85ea03...
Unfortunately there's no JIRA id attached to the commit.
Does anyone remember specifically asking me to enable some jee7 facets
on eap6.1+ runtime? Or was this purely a mistake on my part? As I
recall, there was a minor discussion where it was determined eap6.x was
"partially compliant" and it was better to leave the facets enabled than
not. But I can't find any written documentation of this at all, which is
a failure on my part to not post summaries to any jiras.
- Rob Stryker
10 years, 3 months
PTO March 19th to April 4
by Rob Stryker
Hi All:
I'm on PTO from March 19th to April 4th. Just keep opening bugs for me
and I'll fix them when I get back :D
- Rob
10 years, 3 months
Any webkit / internal browser masters around?
by Rob Stryker
Hey all:
The internal browser view / browser editor when using WebKit (and
Snjezana indicates other internal browser implementations as well) seems
to be caching requests that they shouldn't. The interesting thing here
is that BrowserViewer (used in both editor and view) are passing in
"Cache-Control: no-cache" into the request, and yet the results are
still being cached. This seems to indicate that the underlying WebKit
is ignoring this flag for some reason.
https://issues.jboss.org/browse/JBIDE-18685
https://bugs.eclipse.org/bugs/show_bug.cgi?id=448933
Is anyone experienced enough in the underlying APIs that can assist here
in debugging or finding what in WebKit (or other browsers) is going
wrong that they're ignoring this flag? w3.org documentation indicates
these flags should *never* be ignored:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html
14.9 Cache-Control
The Cache-Control general-header field is used to specify directives
that MUST be obeyed by all caching mechanisms along the request/response
chain. The directives specify behavior intended to prevent caches from
adversely interfering with the request or response. These directives
typically override the default caching algorithms. Cache directives are
unidirectional in that the presence of a directive in a request does not
imply that the same directive is to be given in the response.
This could be a bug in webkit, or in how the internal browser is
communicating with webkit, but I seem to be out of my area of expertise
trying to drill down into the JNI commands and webkit proper.
Anyone have any ideas or experience in this area?
- Rob Stryker
10 years, 3 months
ACTION REQUIRED: Reminder, code freeze for JBT 4.2.3.CR1 / JBDS 8.1.0.CR1 is tomorrow
by Nick Boldt
Please make sure you're using the latest 4.2.3.CR1-SNAPSHOT parent pom
in your builds, in order to pick up the latest 4.42.0.Final-SNAPSHOT
target platform.
If you've contributed fixes to 4.2.3.CR1 (since 4.2.3.Beta1) and your
job is NOT currently enabled, please remember to do so, or at least to
tell me so I can do so for you.
More nags tomorrow!
Cheers,
Nick
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
10 years, 4 months
