Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

[14:52:41 CST(-0600)] <athena> EricDalquist: do you have an example of configuring something as an inline entity with JPA?
[15:10:38 CST(-0600)] <EricDalquist> athena: um ... not sure
[15:10:45 CST(-0600)] <EricDalquist> I can check my JPA book in a few minutes
[15:11:10 CST(-0600)] <athena> thanks! i couldn't find anything in mine, but maybe i'm just looking for the wrong words
[15:22:41 CST(-0600)] <EricDalquist> athena check out @Embedded
[15:22:57 CST(-0600)] <EricDalquist> and @Embeddable
[15:25:16 CST(-0600)] <athena> ah, thanks
[15:26:38 CST(-0600)] <athena> hm that does in fact look familiar
[15:26:40 CST(-0600)] <athena> perfect (smile)
[15:26:50 CST(-0600)] <EricDalquist> yay (smile)
[15:28:37 CST(-0600)] <athena> oh by the way
[15:28:47 CST(-0600)] <athena> with that theme messages stuff - the xalan helper
[15:29:07 CST(-0600)] <athena> i think i've found that actually we need the input to it to be a DOM node rather than a string
[15:29:14 CST(-0600)] <athena> in addition to having the output be a node
[15:29:17 CST(-0600)] <EricDalquist> ah ok
[15:29:29 CST(-0600)] <EricDalquist> that is doable
[15:29:32 CST(-0600)] <athena> awesome
[15:29:35 CST(-0600)] <EricDalquist> I think the URL helpers are doing that
[15:29:40 CST(-0600)] <athena> i'll take a look
[15:30:07 CST(-0600)] <athena> a bit worried about the output, since i'm not sure we can represent the current messages as single nodes
[15:30:29 CST(-0600)] <EricDalquist> :/
[15:30:36 CST(-0600)] <EricDalquist> you can do NodeLists I think
[15:30:37 CST(-0600)] <athena> something like "Welcome <span>User</span>" sort of seems like maybe it's a text node followed by a span node?
[15:30:42 CST(-0600)] <athena> hmm, that might work then
[15:32:28 CST(-0600)] <EricDalquist> hrm ... maybe not ...
[15:32:36 CST(-0600)] <EricDalquist> so what I was thinking of is how I have portlet urls working
[15:32:52 CST(-0600)] <athena> i'll take a look
[15:33:41 CST(-0600)] <EricDalquist> <xsl:variable name="removePortletUrl">
[15:33:42 CST(-0600)] <EricDalquist> <xsl:call-template name="layoutUrl">
[15:33:42 CST(-0600)] <EricDalquist> <xsl:with-param name="folderId" select="@ID" />
[15:33:42 CST(-0600)] <EricDalquist> <xsl:with-param name="action">true</xsl:with-param>
[15:33:42 CST(-0600)] <EricDalquist> <xsl:with-param name="parameters">
[15:33:42 CST(-0600)] <EricDalquist> <layout-param name="remove_target" value="test"/>
[15:33:42 CST(-0600)] <EricDalquist> </xsl:with-param>
[15:33:43 CST(-0600)] <EricDalquist> </xsl:call-template>
[15:33:43 CST(-0600)] <EricDalquist> </xsl:variable>
[15:33:56 CST(-0600)] <EricDalquist> the handling for that is in /uportal-war/src/main/resources/layout/theme/resourcesTemplates.xsl
[15:34:15 CST(-0600)] <EricDalquist> the <xsl:with-param name="parameters"> does some tricks to pass multiple parameters into a java callback
[15:35:57 CST(-0600)] <athena> gotcha
[15:36:10 CST(-0600)] <athena> multiple params seems to be working ok for this