CDI Embedded Mode
by Vaibhav Kulkarni
Hi,
Can anyone please let me know if the Embedded mode is supported in newly
released CDI 1.1?
Could you also be point me to documentation on how to use it please?
Thanks,
Vaibhav
11 years, 5 months
[JBoss JIRA] (CDI-383) Clarify that session context is also destroyed at shutdown/undeploy
by Marko Lukša (JIRA)
Marko Lukša created CDI-383:
-------------------------------
Summary: Clarify that session context is also destroyed at shutdown/undeploy
Key: CDI-383
URL: https://issues.jboss.org/browse/CDI-383
Project: CDI Specification Issues
Issue Type: Bug
Components: Contexts
Affects Versions: 1.1.PFD
Reporter: Marko Lukša
Section 6.7.2. states "The session context is destroyed
when the HTTPSession times out, after all HttpSessionListener s have been called, and at the very end of any request
in which invalidate() was called, after all filters and ServletRequestListener s have been called."
The first part of the above sentence should not only say that the context is destroyed after all listeners have been called specifically in the event of a session timeout. It should specify that this is also true when the session is being destroyed as a result of server shutdown or web-app undeploy.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
TCK GitHub repository transfered to the "cdi-spec" organization
by Martin Kouba
Hello everyone,
today the TCK repo was transfered to the "cdi-spec" organization. We
believe this is the right place - next to the spec.
The new GitHub repository URL: https://github.com/cdi-spec/cdi-tck
GitHub should automatically redirect all requests so that it's not
necessary to do anything. Though it's recommended to change the URL for
your upstream remote repo:
git remote set-url upstream git@github.com:cdi-spec/cdi-tck.git
Martin
--
Martin Kouba
JBoss Quality Assurance Engineer
CDI TCK lead
Red Hat, Czech Republic
11 years, 5 months
Re: [cdi-dev] Lifecycle Callback Interceptor and @Target "METHOD"
by Radim Hanuš
Hi,
I just went through this thread and corresponding issue
WELD-1416<https://issues.jboss.org/browse/WELD-1416>and still not
clear for me
Josef Hartinger referenced a statement from the current version of spec:
"With the exception of AroundConstruct lifecycle callback interceptors, an
interceptor for lifecycle callbacks may only declare interceptor binding
types that are defined as Target(TYPE)."
but does it mean that adding @AroundConstruct callback interceptor into
class PerformanceInterceptor prevents from DefinitionException ?
or in such case there should be only @AroundConstruct defined and none of
both @PostConstruct and @PreDestroy ?
enhanced sample of Jens Schumann:
@Interceptor
@Measure
public class PerformanceInterceptor implements Serializable {
@AroundInvoke
public Object measure(InvocationContext ctx) throws Exception { ... }
@PostConstruct
public void measureCreate(InvocationContext ctx) { ... }
*@AroundConstruct*
Object onAroundConstruct(InvocationContext ctx) throws Exception {...}
}
@InterceptorBinding
@Target({*ElementType.METHOD*, ElementType.TYPE})
@Retention(RetentionPolicy.RUNTIME)
@Inherited
public @interface Measure {
}
thanx for clarification,
Radim
11 years, 5 months
[JBoss JIRA] (CDI-380) Clarify SessionScoped
by Jens Schumann (JIRA)
[ https://issues.jboss.org/browse/CDI-380?page=com.atlassian.jira.plugin.sy... ]
Jens Schumann commented on CDI-380:
-----------------------------------
Copy & paste from CDI-379: As stated in CDI-370 I still believe the CDI spec is way to verbose regarding scopes and related APIs. I think it would be better to move most of the stuff to the related specs (servlet, ejb, ...) or even the Java EE umbrella.
> Clarify SessionScoped
> ---------------------
>
> Key: CDI-380
> URL: https://issues.jboss.org/browse/CDI-380
> Project: CDI Specification Issues
> Issue Type: Clarification
> Reporter: Joseph Snyder
> Priority: Minor
>
> The javadocs say:
> The request context is destroyed:
> - at the end of the servlet request, after the service() method, all
> doFilter() methods, and all requestDestroyed() and onComplete()
> notifications return,
> ...
> The session context is destroyed when the HTTPSession times out, after all
> HttpSessionListeners have been called, and at the very end of any request in
> which invalidate() was called, after all filters and ServletRequestListeners
> have been called.
> Those definitions are different.
> The session context rule seems to be a combination of "or" items that
> include some "and" items. It's difficult to parse. It would be clearer
> if it was written as a list. And, like request scoped, it would be clearer
> if it described when the session scope/context is created.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months