[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1841) Need examples/documentation for how to use seamgen generated EntityHome interefaces and related functionality
by steve tynor (JIRA)
Need examples/documentation for how to use seamgen generated EntityHome interefaces and related functionality
-------------------------------------------------------------------------------------------------------------
Key: JBSEAM-1841
URL: http://jira.jboss.com/jira/browse/JBSEAM-1841
Project: JBoss Seam
Issue Type: Feature Request
Components: Documentation
Affects Versions: 2.0.0.BETA1
Reporter: steve tynor
Please add some documentation, perhaps an example project, that uses seamgen-generated EntityHome classes in order to demonstrate the intended use of the wire(), isWired(), createInstance(), getDefinedInstance(), setId(), etc. functions. Some discussion on how these related to <param> and <f:param> in XHTML is also needed.
As it stands, these are completely undocumented without any explanation of their intended use, so those of us that have boostrapped a project with seamgen, have no guidance on how to maintian these classes as our application changes (new properties added to entities, etc.)
--
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
14 years, 3 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2938) org.jboss.seam.util.XML doesn't validate
by Christian Bauer (JIRA)
org.jboss.seam.util.XML doesn't validate
----------------------------------------
Key: JBSEAM-2938
URL: http://jira.jboss.com/jira/browse/JBSEAM-2938
Project: Seam
Issue Type: Bug
Components: Core
Reporter: Christian Bauer
Assigned To: Norman Richards
Priority: Minor
The getRootElement() method is probably supposed to validate the XML file. However, it only sets a DTD EntityResolver:
SAXReader saxReader = new SAXReader();
saxReader.setEntityResolver(new DTDEntityResolver());
saxReader.setMergeAdjacentText(true);
return saxReader.read(stream).getRootElement();
This might trigger some magic flag that says "validate against this DTD", but the dom4j documentation says otherwise: http://www.dom4j.org/faq.html#how-validate
I've implemented my own routine which validates against my schema properly:
try {
SAXReader saxReader = new SAXReader();
if (isSchemaValidating()) {
saxReader.setEntityResolver(new DTDEntityResolver());
saxReader.setValidation(true);
saxReader.setFeature("http://apache.org/xml/features/validation/schema",true);
}
saxReader.setMergeAdjacentText(true);
elements.put(fileInputStream.getKey(), saxReader.read(fileInputStream.getValue()).getRootElement());
} catch (DocumentException dex) {
Throwable nested = dex.getNestedException();
if (nested != null) {
if (nested instanceof FileNotFoundException) {
throw new RuntimeException(
"Can't find schema/DTD reference for file: "
+ fileInputStream.getKey() + "': "
+ nested.getMessage(), dex
);
} else if (nested instanceof UnknownHostException) {
throw new RuntimeException(
"Cannot connect to host from schema/DTD reference: "
+ nested.getMessage()
+ " - check that your schema/DTD reference is current", dex
);
}
}
throw new RuntimeException("Could not parse XML file: " + fileInputStream.getKey() ,dex);
} catch (Exception ex) {
throw new RuntimeException("Could not parse XML file: " + fileInputStream.getKey() ,ex);
}
I can use that with the classpath:// feature of the DTDEntityResolver (which is the same as in Hibernate):
<?xml version="1.0" encoding="UTF-8"?>
<plugin key="hw" label="Hello World"
xmlns="http://jboss.com/products/seam/wiki/plugin"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation=
"http://jboss.com/products/seam/wiki/plugin classpath://org/jboss/seam/wiki/core/plugin/plugin-1.0.xsd">
...
--
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
14 years, 3 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4408) Unable to easily replace asynchronous dispatchers because of package-private methods
by Reid Pinchback (JIRA)
Unable to easily replace asynchronous dispatchers because of package-private methods
------------------------------------------------------------------------------------
Key: JBSEAM-4408
URL: https://jira.jboss.org/jira/browse/JBSEAM-4408
Project: Seam
Issue Type: Feature Request
Components: Async
Affects Versions: 2.2.0.GA, 2.2.0.CR1, 2.1.2.GA, 2.1.2.CR2, 2.1.2.CR1, 2.1.1.GA
Reporter: Reid Pinchback
One of the benefits of Seam is that you can install your open components to replace the built-in ones provided by Seam.
I was attempting to replace the ThreadPoolDispatcher, when I encountered something that maybe should change in the Schedule and TimerSchedule API. Instances of those classes can be created, but the values in them cannot be accessed because their accessors are package-private. For example:
public class Schedule implements Serializable {
private Long duration;
...
Long getDuration()
{
return duration;
}
...
}
Since the member variables are private, you can't create subclasses of Schedule or TimerSchedule to get at them, and because the accessors are package-private, you can't get at them that way. Similarly any subclass of AbstractDispatcher in a different package can't access those values for determining the appropriate values for scheduled futures.
The only work-arounds at present are pretty grungy - either creating a subclass of TimerSchedule that keeps shadow copies of the member variables, or placing the application-specific dispatcher code in a package whose name mimics the Seam package structure. Neither is a show-stopper, but not really a good solution for a framework that is intentionally attempting to make itself extensible.
I'd recommend making the Schedule and TimerSchedule accessors public.
--
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
14 years, 3 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2301) JBoss EL bug handling overloaded methods with varargs mixed in
by Matthew Lieder (JIRA)
JBoss EL bug handling overloaded methods with varargs mixed in
--------------------------------------------------------------
Key: JBSEAM-2301
URL: http://jira.jboss.com/jira/browse/JBSEAM-2301
Project: JBoss Seam
Issue Type: Bug
Components: EL
Affects Versions: 2.0.0.GA
Reporter: Matthew Lieder
Doing facesMessages.add("Message") from an EL expression doesn't work, complaining about the String class not being compatible with the FacesMessage class. The problem is caused by a combination of two things:
1. There are two FacesMessages.add(...) that can accept one parameter: add(FacesMessage facesMessage) and add(String messageTemplate, Object... params)
2. The FacesMessages.add(...) that accepts a String as the first parameter can optionally accept additional parameters through a vararg
If only one of those was the case, it'd work fine. However, having both at the same time triggers the error.
--
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
14 years, 3 months