[JBoss JIRA] Created: (SEAMREPORTS-10) Dynamic reporting from customer template
by alberto Gori (JIRA)
Dynamic reporting from customer template
----------------------------------------
Key: SEAMREPORTS-10
URL: https://issues.jboss.org/browse/SEAMREPORTS-10
Project: Seam Reports
Issue Type: Feature Request
Reporter: alberto Gori
Would be nice to see a solution for dynamic reporting using customer templates. Many times customers give us a template (OpenOffice or Word document), and we are supposed to produce reports based on them, maybe adding some other images, signature etc.
So I suggest a Seam Report API able to read a customer template (odt etc), manipulate this document (set fields, adding table rows, adding images, etc) and produce PDF. For example an API that hides all the complexity of UNO (http://udk.openoffice.org/) or some other tool for document manipulation.
The key part is existent document manipulation.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (SEAMJCR-4) OCM Bindings
by John Ament (JIRA)
OCM Bindings
------------
Key: SEAMJCR-4
URL: https://issues.jboss.org/browse/SEAMJCR-4
Project: Seam JCR
Issue Type: Feature Request
Components: OCM
Reporter: John Ament
Fix For: 3.0.0.Alpha2
OCM Bindings should support either Seam JCR created annotations denoting node types as well as field level annotations denoting the properties. The bindings should happen once on startup, not at runtime, so doing this in the JcrExtension makes sense.
The alternative would be to use JAX-B bindings. I think either would work, and if we can we should support JAX-B.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2006) Improve handling of dependencies in examples
by Pete Muir (JIRA)
Improve handling of dependencies in examples
--------------------------------------------
Key: JBSEAM-2006
URL: http://jira.jboss.com/jira/browse/JBSEAM-2006
Project: JBoss Seam
Issue Type: Task
Affects Versions: 2.0.0.CR1
Reporter: Pete Muir
Assigned To: Pete Muir
Priority: Critical
Fix For: 2.0.1.GA
Currently dependencies are just handled as before, with all dependencies copied into lib/
I propose to replace lib/ with a local maven repository (just a simple directory structure). This will only be used if present (not present in CVS, created using dependency:copy-dependencies when running dist target). The fileset's used to declare example libraries and inclusion into deployed archives will be altered to use maven ant tasks to pull in these filesets from repositories (using the local repo if present).
This requires some extensions to existing ant tasks.
A similar scheme can be used for seam-gen
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (SOLDER-93) Add more thorough tests for @Requires
by Dan Allen (JIRA)
Add more thorough tests for @Requires
-------------------------------------
Key: SOLDER-93
URL: https://issues.jboss.org/browse/SOLDER-93
Project: Seam Solder
Issue Type: Enhancement
Components: Core
Affects Versions: 3.0.0.CR4
Reporter: Dan Allen
Add more thorough tests for @Requires for scenarios in which the required class is referenced in the bean that relies on that class. Currently, the only reference to the required class is in the @Requires annotation as a string.
Test scenarios:
- @Requires on package-info.java references class on classpath
- inject required class into bean in package
- use required class as return value of method on bean in package
- use required class a super class of bean in package
- do not include injected class in shrinkwrap archive
- make sure deployment succeeds
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (SEAMCATCH-18) Provide exception type mapping (to deal with vendor-specific exception types)
by Dan Allen (JIRA)
Provide exception type mapping (to deal with vendor-specific exception types)
-----------------------------------------------------------------------------
Key: SEAMCATCH-18
URL: https://jira.jboss.org/browse/SEAMCATCH-18
Project: Seam Catch
Issue Type: Feature Request
Components: Core Implementation
Affects Versions: Alpha2
Reporter: Dan Allen
Assignee: Jason Porter
There are cases when the useful information about an exception is only available in an implementation-specific exception. It would be useful to provide an exception type mapping infrastructure so that implementation-specific exceptions can be mapped to portable exception types.
A classic example is JPA provider exceptions. Hibernate throws a SQLGrammarException in cases where the SQL statement is invalid (has a syntax error or refers to an invalid table/column). However, if you are writing portable JPA code, you cannot catch this exception. Thus, it would be useful to be able to catch an portable exception that represents this vendor-specific exception.
Obviously, the actual mapping in this example would be done in the persistence module. Catch needs to provide some mechanism for an integration to register the mappings, which it will honor when notifying handlers.
It should be noted that this is a very popular feature from Spring. Refer to SessionFactoryUtils for an example of the exception type mapping.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months