[EJB 3.0] - Problem when deploy java persistence on jboss-4.0.4.GA
by boomboom
I am trying to deploy the sample code --masteringEJB3.0Code\Micah Examples--from Mastering Enterprise JavaBeans 3.0 by Rima Patel Sriganesh, Gerald Brose, and Micah Silverman on jboss-4.0.4.GA.
I used its build.xml to build a package called EntityExamplesEJB.jar, and when I deployed on jboss-4.0.4.GA. I got the following exceptions:
2006-12-11 14:37:29,178 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/Karen/tools/jboss-4.0.4.GA/server/default/deploy/jmx-console.war/
2006-12-11 14:37:29,178 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/C:/Karen/tools/jboss-4.0.4.GA/server/default/deploy/jmx-console.war/ -> file:/C:/Karen/tools/jboss-4.0.4.GA/server/default/deploy/jmx-console.war/WEB-INF/web.xml
2006-12-11 14:37:29,178 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: persistence.units:jar=EntityExamplesEJB.jar,unitName=pu1
State: NOTYETINSTALLED
I Depend On:
jboss.jca:name=jdbc/__default,service=ManagedConnectionFactory
Depends On Me:
jboss.j2ee:jar=EntityExamplesEJB.jar,name=StudentCourseBidBean,service=EJB3
jboss.j2ee:jar=EntityExamplesEJB.jar,name=CompanyEmployeeOMBidBean,service=EJB3
jboss.j2ee:jar=EntityExamplesEJB.jar,name=OrderShipmentBidBean,service=EJB3
jboss.j2ee:jar=EntityExamplesEJB.jar,name=RoadVehicleStatelessJoinedBean,service=EJB3
jboss.j2ee:jar=EntityExamplesEJB.jar,name=RoadVehicleStatelessBean,service=EJB3
jboss.j2ee:jar=EntityExamplesEJB.jar,name=StudentCourseUniBean,service=EJB3
jboss.j2ee:jar=EntityExamplesEJB.jar,name=EmployeeAddressMOUniBean,service=EJB3
jboss.j2ee:jar=EntityExamplesEJB.jar,name=CompanyEmployeeOMUniBean,service=EJB3
jboss.j2ee:jar=EntityExamplesEJB.jar,name=OrderShipmentUniBean,service=EJB3
ObjectName: jboss.j2ee:jar=EntityExamplesEJB.jar,name=StudentCourseBidBean,service=EJB3
State: NOTYETINSTALLED
I Depend On:
persistence.units:jar=EntityExamplesEJB.jar,unitName=pu1
ObjectName: jboss.j2ee:jar=EntityExamplesEJB.jar,name=CompanyEmployeeOMBidBean,service=EJB3
State: NOTYETINSTALLED
I Depend On:
persistence.units:jar=EntityExamplesEJB.jar,unitName=pu1
ObjectName: jboss.j2ee:jar=EntityExamplesEJB.jar,name=OrderShipmentBidBean,service=EJB3
State: NOTYETINSTALLED
I Depend On:
persistence.units:jar=EntityExamplesEJB.jar,unitName=pu1
ObjectName: jboss.j2ee:jar=EntityExamplesEJB.jar,name=RoadVehicleStatelessJoinedBean,service=EJB3
State: NOTYETINSTALLED
I Depend On:
persistence.units:jar=EntityExamplesEJB.jar,unitName=pu1
ObjectName: jboss.j2ee:jar=EntityExamplesEJB.jar,name=RoadVehicleStatelessBean,service=EJB3
State: NOTYETINSTALLED
I Depend On:
persistence.units:jar=EntityExamplesEJB.jar,unitName=pu1
ObjectName: jboss.j2ee:jar=EntityExamplesEJB.jar,name=StudentCourseUniBean,service=EJB3
State: NOTYETINSTALLED
I Depend On:
persistence.units:jar=EntityExamplesEJB.jar,unitName=pu1
The following is persistence.xml. Actually, I didnot use oracle toplink or derby platform. I am not sure how to write the right persistence.xml. Please help me.
<persistence-unit name="pu1" transaction-type="JTA">
<jta-data-source>jdbc/__default</jta-data-source>
<!--Use the java2db feature -->
<!-- -->
<!-- Generate the sql specific to Derby database -->
</persistence-unit>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992924#3992924
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992924
19 years, 4 months
[Security & JAAS/JBoss] - Re: Login encryption not working
by ewade
Ok. Then perhaps I am not being clear. That is precisely what I am trying to do.
I have (correctly) encrypted and encoded passwords stored in my database.
We are using the database server login module. It works fine for clear text passwords -- that is passwords stored and entered as plain text. However, when we try to turn on the encryption/encoding it does not work any differently than it did when we did not have these options enabled.
You can see my config set up in the first post.
Here is what happens. For purposes of this test, I have stored one user with a plain text password.
Scenario 1:
User has plain text (clear) password stored.
Logon with correct plain text password works.
It should not work with encryption turned on.
(I can provide a excerpt of the server log file if you need it, but it is lengthy.)
Scenario 2:
User has plain text password stored.
Logon with incorrect password.
It fails, which is the expected outcome.
Here is an excerpt from the server log.
2006-12-11 15:58:13,656 DEBUG [org.jboss.security.auth.spi.DatabaseServerLoginModule] Bad password for username=E0andre
2006-12-11 15:58:13,656 DEBUG [org.jboss.seam.contexts.Lifecycle] >>> Begin web request
2006-12-11 15:58:13,656 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.manager
2006-12-11 15:58:13,656 DEBUG [org.jboss.seam.core.Manager] No stored conversation
2006-12-11 15:58:13,656 DEBUG [org.jboss.seam.contexts.Contexts] found in application context: org.jboss.seam.core.init
2006-12-11 15:58:13,656 DEBUG [org.jboss.seam.jsf.AbstractSeamPhaseListener] After restoring conversation context: ConversationContext(5)
2006-12-11 15:58:13,656 DEBUG [org.jboss.seam.Component] instantiating Seam component: facesMessages
2006-12-11 15:58:13,687 DEBUG [org.jboss.seam.core.Manager] Discarding conversation state: 5
2006-12-11 15:58:13,687 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing page context
2006-12-11 15:58:13,687 DEBUG [org.jboss.seam.core.Manager] Discarding conversation state: 5
2006-12-11 15:58:13,687 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing page context
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Lifecycle] After render response, destroying contexts
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying event context
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Contexts] destroying: javax.servlet.forward.request_uri
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Contexts] destroying: javax.servlet.forward.context_path
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Contexts] destroying: javax.servlet.forward.servlet_path
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.jboss.seam.core.manager
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Contexts] destroying: class org.apache.myfaces.renderkit.html.util.JavascriptUtils.OLD_VIEW_ID
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.apache.myfaces.application.jsp.JspStateManagerImpl.SERIALIZED_VIEW
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Contexts] destroying: com.sun.facelets.legacy.ELCONTEXT
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying conversation context
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Contexts] destroying: facesMessages
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing server-side conversation context
2006-12-11 15:58:13,703 DEBUG [org.jboss.seam.contexts.Lifecycle] <<< End web request
Scenario 3.
User has (correctly) encrypted password stored in the database.
Logon using matching plain text password.
It fails as it should not. Here is the excerpt from the server.log
2006-12-11 16:03:06,343 DEBUG [org.jboss.security.auth.spi.DatabaseServerLoginModule] Bad password for username=E0ewade
2006-12-11 16:03:06,343 DEBUG [org.jboss.seam.contexts.Lifecycle] >>> Begin web request
2006-12-11 16:03:06,343 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.manager
2006-12-11 16:03:06,343 DEBUG [org.jboss.seam.core.Manager] No stored conversation
2006-12-11 16:03:06,343 DEBUG [org.jboss.seam.contexts.Contexts] found in application context: org.jboss.seam.core.init
2006-12-11 16:03:06,343 DEBUG [org.jboss.seam.jsf.AbstractSeamPhaseListener] After restoring conversation context: ConversationContext(14)
2006-12-11 16:03:06,343 DEBUG [org.jboss.seam.Component] instantiating Seam component: facesMessages
2006-12-11 16:03:06,343 DEBUG [org.jboss.seam.core.Manager] Discarding conversation state: 14
2006-12-11 16:03:06,343 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing page context
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.core.Manager] Discarding conversation state: 14
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing page context
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Lifecycle] After render response, destroying contexts
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying event context
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Contexts] destroying: javax.servlet.forward.request_uri
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Contexts] destroying: javax.servlet.forward.context_path
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Contexts] destroying: javax.servlet.forward.servlet_path
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.jboss.seam.core.manager
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Contexts] destroying: class org.apache.myfaces.renderkit.html.util.JavascriptUtils.OLD_VIEW_ID
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Contexts] destroying: org.apache.myfaces.application.jsp.JspStateManagerImpl.SERIALIZED_VIEW
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Contexts] destroying: com.sun.facelets.legacy.ELCONTEXT
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Lifecycle] destroying conversation context
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Contexts] destroying: facesMessages
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Lifecycle] flushing server-side conversation context
2006-12-11 16:03:06,359 DEBUG [org.jboss.seam.contexts.Lifecycle] <<< End web request
Scenario 4:
User has encrypted password stored in the database.
Logon is done with the encrypted string.
Result: Logon succeeds when it should fail.
(Again this is a really long log entry. But it is exactly like scenario 1)
In summary, even though I have done my very best to enable ecryption (hashing) and encoding, the login module is behaving as though these things are not turned on. What do I need to do to get it to work?
Elise
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992922#3992922
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992922
19 years, 4 months
[Tomcat, HTTPD, Servlets & JSP] - Re: JSF JBoss question
by stan.silvert＠jboss.com
In JBoss 4.x, the main advantage JSF has over other frameworks is that it is already installed and supported by JBoss support. Also, JSF standard taglibs are cached and available globally.
In JBoss 5.x, the integration is deeper. As part of JEE 5, JSF becomes the standard web framework. JBoss 5 integrates everything in JBoss 4.x plus support for resource injection, JBoss Serialization, and automatic initialization.
See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossFaces for links to details.
Again, the ability to get support from JBoss for both the app server and JSF is often see as a big plus whereas you would need to find support for other frameworks from separate vendors.
As long as you are evaluating frameworks, you should also take a close look at JBoss Seam. There is a lot of advanced stuff in there that complements and builds on JSF. In many ways, Seam is the big answer to how we are making things easier for developers. See http://www.jboss.com/products/seam. I think you'll be duly impressed.
Everything you mention is addressed one way or another in either JSF, third-party JSF components, or Seam. The possible exception is FB2 (I don't know what that is). For the enum support you need JSF 1.2 which is in JBoss 5.
Stan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992920#3992920
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992920
19 years, 4 months