[JBoss JIRA] Created: (JBIDE-6001) NoCachingEnabledException in Console Config with Seam 2.2 DVD Store Example
by Vitali Yemialyanchyk (JIRA)
NoCachingEnabledException in Console Config with Seam 2.2 DVD Store Example
---------------------------------------------------------------------------
Key: JBIDE-6001
URL: https://jira.jboss.org/jira/browse/JBIDE-6001
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.CR2
Reporter: Vitali Yemialyanchyk
Assignee: Vitali Yemialyanchyk
Priority: Minor
Fix For: 3.1.1
Attachments: screenshot-1.jpg
1) download Seam 2.2 DVD Store Example;
2) open dvdstore22-ejb Console Config session Factory - get exception:
org.hibernate.cache.NoCachingEnabledException: Second-level cache is not enabled for usage [hibernate.cache.use_second_level_cache | hibernate.cache.use_query_cache]
at org.hibernate.cache.impl.NoCachingRegionFactory.buildEntityRegion(NoCachingRegionFactory.java:66)
at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:261)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1341)
at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867)
at org.hibernate.console.ConsoleConfiguration$4.execute(ConsoleConfiguration.java:554)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:98)
at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:549)
at org.hibernate.eclipse.console.workbench.LazySessionFactoryAdapter.getChildren(LazySessionFactoryAdapter.java:43)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.getChildren(BasicWorkbenchAdapter.java:100)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:234)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-6172) New Seam Test Generation
by Jim Tyrrell (JIRA)
New Seam Test Generation
------------------------
Key: JBIDE-6172
URL: https://jira.jboss.org/jira/browse/JBIDE-6172
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Environment: All
Reporter: Jim Tyrrell
It would be nice to create a New -> Option in Seam land to stub out a test case. Currently this happens when a New Action is created, however it would be better to be able to add testing to an already created page, or more importantly for TDD, it would be important to be able to create this first, and then create a new Action/Form after the fact w/o any test files. I would like to see this test class generated with all the various JSF phases testers already implemented created w/o any code in them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBDS-1169) PicketLink Integration with SOA-P5 (JBDS ESB XML Tooling plus Action design)
by Gary Lamperillo (JIRA)
PicketLink Integration with SOA-P5 (JBDS ESB XML Tooling plus Action design)
----------------------------------------------------------------------------
Key: JBDS-1169
URL: https://jira.jboss.org/jira/browse/JBDS-1169
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Reporter: Gary Lamperillo
With the PicketLink and SOA-P 5 quickstart sample (security_saml), a client requests a web service and immediately receives an acknowledgement back. A more realistic use case would be to request a token and use it for the request using a chainhandler. SOA-P 5 can still be utilized as the intermediate. There are a few additional pieces that are needed. The SOA-P 5 needs a Service which forwards issue requests to PicketLink and then sends the Token client. SOA-P 5 needs another service that validates the tokens in the requests and either forwards the request or logs the exception and send error to the client. Both of these services should be implemented as new actions, and should be available in the ESB Actions as "Security Services". In addition, the current implementation requires smooks to add the assertion to the out going message. While the internal implementation using smooks is fine, it should not be required by the user to deal with these internals. In the new "Security Services" section a "Add Assertion" should be available.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months