Package name
by Tomaž Cerar
Hi,
What should be package name for new stuff being added to WildFly?
org.wildfly.<subsystem-name>
or
org.wildfly.as.<subsystem-name>
or something else?
I would go for org.wildfly.<subsystem-name>
this mostly applies to new subsystems and as we agreed we won't rename
packages for existing code until it break compatibility.
--
tomaz
11 years, 5 months
Return types of i18n logging methods and their "equality" expectations
by Jaikiran Pai
I have a interface annotated with @MessageBundle which has a method:
@Message(id = xxxx, value = "No param message")
SomeException fooBar();
So the method expects no format params for the log message and returns a
"SomeException" type. Assuming some piece of code then uses this logging
method to do:
throw fooBar();
is it fine to expect that if the caller does:
try {
...
doSomething();
} catch (Exception e) {
// is this fine to do?
if (e.equals(fooBar()) {
// do some other thing
}
}
I think the equals and even == would work for the no param logger
method, but is this considered as relying/guessing about the
implementation details or is this fine to do?
-Jaikiran
11 years, 7 months
Re: [wildfly-dev] [jboss-as7-dev] EL 3
by Hardy Ferentschik
On 24 Jan 2013, at 1:36 PM, Rémy Maucherat <rmaucher(a)redhat.com> wrote:
> On 04/24/2013 10:13 AM, Emmanuel Bernard wrote:
>> We have seen bugs in the EL around calls to methods with varargs that made it unusable for Bean Validation. We reported it to oracle but I don't know if that has been fixed since. Hardy and Gunnar can comment more accurately than my 10000 feet view.
>> We have been happy with JUEL AFAIR.
> I don't see anything wrong with using your own, especially if you don't
> need the EL3 functionality ASAP. If you do, it's probably the only
> option available for some time. So it will be used by Jasper through the
> EL3 API and from its own com.sun.el module (probably), while the current
> impl is bundled.
+1 for having our own copy of EL libs in the Hibernate Validator module. This is the easiest way to move the Bean Validation integration forward for now.
We re-evaluate once we see what's happening with the current EL module. Just keep in mind there are potentially other modules (for example Hibernate Validator)
which need UEL so hard wiring things via the org.jboss.as.web does not seem to be the way forward.
--Hardy
11 years, 7 months
