Vahan Harput

Greenhorn
+ Follow
since Dec 11, 2002
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Vahan Harput

Hi Camilo,

I can't find where does the spec say that methods with an unspecified transaction and security context can not acces resource managers.



Thanks for your reply. Here the quote regarding the access to resource managers and transaction/security context from page 81:

"Accessing resource managers and enterprise beans is disallowed in the session bean methods for which the container does not have a meaningful transaction context and/or client security context."

Best regards
Hi all,

I have a question regarding the allowed operations in the lifecycle callback methods of stateful session beans:

On the page 80/81 of the EJB 3.0 core specification, it is specified that the PostConstruct/PreDestroy/PrePassivate/PostActivate lifecycle callback methods run in an unspecified transaction and security context. It is also specified that in such methods it is not allowed to access resource managers and other enterprise beans.

At the same time however, in the table 1 of page 79 accessing resource managers and enterprise beans is allowed for these lifecycle callback methods.

This seems to be a contradiction. Is this an error in the specification or am I missing something?

Best regards
Hi all,

I have a question regarding the allowed operations in the lifecycle callback methods of stateful session beans:

On the page 80/81 of the EJB 3.0 core specification, it is specified that the PostConstruct/PreDestroy/PrePassivate/PostActivate lifecycle callback methods run in an unspecified transaction and security context. It is also specified that in such methods it is not allowed to access resource managers and other enterprise beans.

At the same time however, in the table 1 of page 79 accessing resource managers and enterprise beans is allowed for these lifecycle callback methods.

This seems to be a contradiction. Is this an error in the specification or am I missing something?

Best regards
Hi all,
Currently I am having the following problem with the PetStore Application on the Sun J2EE SDK 1.3.1 under Windows XP Professional:
When I open the URL:
http://localhost:8080/petstore
I get a message that the DB is being populated.
Afterwards I get to see the main screen of the application but at the same time I get the following exceptions from appserver:
java.net.ConnectException: Connection refused: connect
java.security.PrivilegedActionException: javax.servlet.ServletException: An error occurred while evaluating custom actio
n attribute "items" with value "${catalog.categories.list}": An error occurred while getting property "categories" from
an instance of class com.sun.j2ee.blueprints.catalog.client.CatalogHelper
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at com.sun.j2ee.blueprints.waf.view.template.tags.InsertTag.doEndTag(InsertTag.java:99)
at org.apache.jsp.template$jsp._jspService(template$jsp.java:133)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

...
Any help would be much appreciated!
Thanks in advance
Vahan Harput