Support for weak entity tags....

Hi All,
Is there is a way to return weak entity tags with objects in the
enterprise server. I would like to use this as weak entity tags which
may lead to a more efficient caching scheme. If it is supported please
help as to how this is configured....
Thanks,
Jack.

Hi Sam,
Thanks! No problem. I understand completely your perspective, especially about the integration stuff.
In case more detail helps:
Each "action" we have has a clear naming structure and actually they all get aggregated up to global in the end using Exists() if the action is on a child entity. They are called action_1 to action_N where N is the total actions in the active delivery. The rule developers update this each time a release is completed.
N is a value set in the rulebase that the calling system can have access to, e.g. N=20. The calling system would then know to look in the response field the value of action_1 through to action_20, and do some further processing based on this. So if action_7 meant at "at least one address needs verifying", it would then look at the address instances returned in the response, and see which one(s) have address_action_7 also set. Both systems are aware of what the actions "are", but OPA contains all of the legal / business rules as to when that action should be raised, and the calling system interprets this and sorts out / transforms the data.
This works well and in terms of performance is optimised, but that said we will be looking at 10.4 and seeing what advantages it could bring over this approach.
Good luck with the implementation!
Cheers,
Ben

Similar Messages

  • [svn] 4875: Adding support for multiple @productversion tags

    Revision: 4875
    Author: [email protected]
    Date: 2009-02-06 08:31:48 -0800 (Fri, 06 Feb 2009)
    Log Message:
    Adding support for multiple @productversion tags
    QE Notes: None.
    Doc Notes: None
    Bugs: SDK-19104
    tests: checkintests
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19104
    Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/DocComment.java

    Revision: 4875
    Author: [email protected]
    Date: 2009-02-06 08:31:48 -0800 (Fri, 06 Feb 2009)
    Log Message:
    Adding support for multiple @productversion tags
    QE Notes: None.
    Doc Notes: None
    Bugs: SDK-19104
    tests: checkintests
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19104
    Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/DocComment.java

  • [svn] 4146: adding support for multiple @playerversion tags.

    Revision: 4146
    Author: [email protected]
    Date: 2008-11-19 21:37:23 -0800 (Wed, 19 Nov 2008)
    Log Message:
    adding support for multiple @playerversion tags.
    Fix for asdoc.exe not outputting information for the @langversion tag.
    Also removing some unused code from DITA generation..
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-18158, SDK-18159
    tests: checkintests, asdoc
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-18158
    http://bugs.adobe.com/jira/browse/SDK-18159
    Modified Paths:
    flex/sdk/trunk/asdoc/templates/asdoc-util.xslt
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/DocComment.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

    Revision: 4146
    Author: [email protected]
    Date: 2008-11-19 21:37:23 -0800 (Wed, 19 Nov 2008)
    Log Message:
    adding support for multiple @playerversion tags.
    Fix for asdoc.exe not outputting information for the @langversion tag.
    Also removing some unused code from DITA generation..
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-18158, SDK-18159
    tests: checkintests, asdoc
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-18158
    http://bugs.adobe.com/jira/browse/SDK-18159
    Modified Paths:
    flex/sdk/trunk/asdoc/templates/asdoc-util.xslt
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/DocComment.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

  • [svn:osmf:] 10440: Add parser support for the Video tag.

    Revision: 10440
    Author:   [email protected]
    Date:     2009-09-20 15:03:56 -0700 (Sun, 20 Sep 2009)
    Log Message:
    Add parser support for the Video tag.  Add unit test for an empty document.
    Modified Paths:
        osmf/trunk/libs/VAST/.flexLibProperties
        osmf/trunk/libs/VAST/org/openvideoplayer/vast/model/VASTInlineAd.as
        osmf/trunk/libs/VAST/org/openvideoplayer/vast/parser/VASTParser.as
        osmf/trunk/libs/VASTTest/org/openvideoplayer/vast/parser/TestVASTParser.as
    Added Paths:
        osmf/trunk/libs/VAST/org/openvideoplayer/vast/model/VASTMediaFile.as
        osmf/trunk/libs/VAST/org/openvideoplayer/vast/model/VASTVideo.as

    The video tag only supports a few formats and MKV (Matroska Multimedia Container) isn't one of them.<br />
    Your only option is to use the object (or embed) tag and use a player that can handle that format.<br />
    If might be better to switch to the WebM format.<br />
    * https://developer.mozilla.org/En/Media_formats_supported_by_the_audio_and_video_elements

  • Support for creating entity instances through rules

    Hi,
    Is there support to generate an instance of an entity purely through rules? For example, if I have an entity called "VerificationItems", can I write a rule in OPA that will one instance of this entity per verification item that the applicant needs to produce (like one instance for address proof, one instance for SSN etc).
    Thanks
    Sam

    Hi Sam,
    Thanks! No problem. I understand completely your perspective, especially about the integration stuff.
    In case more detail helps:
    Each "action" we have has a clear naming structure and actually they all get aggregated up to global in the end using Exists() if the action is on a child entity. They are called action_1 to action_N where N is the total actions in the active delivery. The rule developers update this each time a release is completed.
    N is a value set in the rulebase that the calling system can have access to, e.g. N=20. The calling system would then know to look in the response field the value of action_1 through to action_20, and do some further processing based on this. So if action_7 meant at "at least one address needs verifying", it would then look at the address instances returned in the response, and see which one(s) have address_action_7 also set. Both systems are aware of what the actions "are", but OPA contains all of the legal / business rules as to when that action should be raised, and the calling system interprets this and sorts out / transforms the data.
    This works well and in terms of performance is optimised, but that said we will be looking at 10.4 and seeing what advantages it could bring over this approach.
    Good luck with the implementation!
    Cheers,
    Ben

  • Does Firefox not have support for unparsed-entity-url() (XSLT stylesheet), if not is there a plan to implement it?

    We support a site that generates pages based on XML and XSLT where XSLT uses unparsed-entity-url() but it dont seem to work in Firefox.

    By posting on the forum you are asking the wrong people. We are Apple users, not employees. If you want to provide this feedback directly to Apple you should leave the feedback at:
    http://www.apple.com/feedback/iphone.html

  • Disable weak ciphers and support for all SSL protocols prior to v3.

    I am very new to Weblogic and I need a little help with the SSL configurations. I received a security audit back and discovered that Weblogic's SSL is running weak ciphers and also supporting unacceptable versions of SSL (we require a minimum of SSLv3 and need to deny connections with anything less). That said, can anyone point me in the right direction for disabling weak ciphers as well as forcing support for SSLv3 and up only for client connections. I am running Weblogic 10.3.
    Edited by: David Pulliam on Jan 26, 2011 8:31 AM

    Hi David,
    -Dweblogic.security.SSL.protocolVersion=SSL3 —> Using this JAVA_OPTION will allow Only SSL V3.0 messages are sent and accepted. So add the mentioned JAVA_OPTION in the server start script along with the below OPTION:
    -Dweblogic.security.disableNullCipher=true
    Also you can do the following in your "config.xml" to make sure that the Weblogic will not accept weak and medium weak passwords:
    <ssl>
           <enabled>true</enabled>
          <ciphersuite>TLS_RSA_WITH_RC4_128_SHA</ciphersuite>
          <ciphersuite>TLS_RSA_WITH_RC4_128_MD5</ciphersuite>
          <hostname-verification-ignored>true</hostname-verification-ignored>
          <listen-port>7002</listen-port>
          <server-private-key-alias>aliasHere</server-private-key-alias>
          <server-private-key-pass-phrase-encrypted>encryptedpassphraseHere</server-private-key-pass-phrase-encrypted>
    </ssl>Thanks
    Jay SenSharma
    http://middlewaremagic.com/weblogic (Middleware magic Is Here)

  • Support for jsp:include page tag

    Is there a support for the jsp:include page tag ?
    I get an exception when trying to include jsp's
    Thanks

    Hi
    I use a page with a one column template
    I print a JSP that include another JSP using <jsp:include page="my_shopping_cart.jsp"
    flush="true"/>
    i get this exception :
    java.lang.IllegalStateException: Can not set buffer size after writing data. at
    com.bea.portlet.container.HttpServletResponseImpl.setBufferSize(HttpServletResponseImpl.java:179)
    at weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:66) at
    weblogic.servlet.jsp.PageContextImpl.(PageContextImpl.java:105) at weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:37)
    at jsp_servlet._portlets._oci.__my_shopping_cart._jspService(my_shopping_cart.jsp)
    at com.bea.portlet.jsp.PortletJspBase.service(PortletJspBase.java:110) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:101)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:597)
    at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:409)
    at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:155) at jsp_servlet._portlets._oci.__oci._jspService(oci.jsp:209)
    at com.bea.portlet.jsp.PortletJspBase.service(PortletJspBase.java:110) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:101)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:597)
    at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:409)
    at com.bea.portlet.container.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:98)
    at com.cgi.poc.jsr168.MyAccountsPortlet.doView(MyAccountsPortlet.java:107) at
    javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:208) at javax.portlet.GenericPortlet.render(GenericPortlet.java:137)
    at com.bea.portlet.container.PortletStub.render(PortletStub.java:370) at com.bea.portlet.container.AppContainer.renderStub(AppContainer.java:501)
    at com.bea.portlet.container.AppContainer.invokeRender(AppContainer.java:436)
    at com.bea.portlet.server.PortletHttpServer.invoke(PortletHttpServer.java:218)
    at com.bea.portlet.server.PortletHttpServer.process(PortletHttpServer.java:162)
    at com.bea.portlet.server.PortletHttpServer.doGet(PortletHttpServer.java:119)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:101)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:597)
    at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:409)
    at com.bea.netuix.servlets.controls.content.JavaPortletContent.fireRender(JavaPortletContent.java:246)
    at com.bea.netuix.servlets.controls.content.JavaPortletContent.renderInternal(JavaPortletContent.java:146)
    at com.bea.netuix.servlets.controls.content.JavaPortletContent.beginRender(JavaPortletContent.java:108)
    at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:424) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:427)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
    at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:95)
    at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:380) at com.bea.netuix.nf.UIControl.render(UIControl.java:580)
    at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:341)
    at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:123)
    at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:58)
    at jsp_servlet._framework._skeletons._bellca.__gridlayout._jspService(gridlayout.jsp:29)
    at com.bea.portlet.jsp.PortletJspBase.service(PortletJspBase.java:110) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:101)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:597)
    at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:409)
    at com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:187)
    at com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:90)
    at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:420) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:427)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
    at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
    at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172) at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:220)
    at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:158) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:363)
    at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:207) at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:584)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
    at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at
    weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
    at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Subbu Allamaraju <[email protected]> wrote:
    Could you please post more details of the exceptions?
    Thanks
    Subbu
    Carl Samson said the following on 12/09/2003 01:15 PM:
    Is there a support for the jsp:include page tag ?
    I get an exception when trying to include jsp's
    Thanks

  • Can Apple comment on their lack of support for burning CD-TEXT?

    Can Apple comment on their lack of support for burning CD-TEXT?
    I've been getting the runaround from the support people. They said to resolve my issue check out the following kb articles. The articles were aimed at giving me more information about ID3 tags and formats that I care about. I just want my burnt cd's to work in my CD-TEXT capable cd player.
    I've done this using alternate software packages so I know my hardware supports it. I'm really looking for a complete solution for myself (techie) and my wife (non-Techie) to use and make us both happy. I have to admit, this really bothers me.
    I know I'm not the only person asking about this. Please add the support for CD-TEXT to I-Tunes.
    Thanks
      Windows XP  
      Windows XP  

    Apple people don't comment here, it's a user to user forum.
    But you've got me interested. CD-TEXT, what is it? Should I just look it up in wikipedia or do you have a better explanation of what it is you're after?

  • Future support for using PL/SQL core business logic with ADF BC

    We want to migrate our large Forms client/server (6i) application to ADF, possibly using a migration tool like Ciphersoft Exodus.
    One scenario could be to use ADF BC and ADF-Faces or a different JSF-Implementation for presentation and business layer but keep our heavy PL/SQL-businesslogic inside the Oracle database in packages, triggers, functions and procedures.
    This scenario could be chosen due to the huge amount of interconnected logic inside the database (10 years of development; no technical components; any package may access any table and more of this kind of dependencies). The business logic nowadays held in Forms client will be moved mainly into the database as a prerequisite to this scenario.
    Choosing this "keep-logic-in-DB"-scenario we need a good support by ADF BC to do so. We know and prototyped that it is possible to call some PL/SQL via JDBC from ADF BC and it is possible to use stored procedure calls for standard business entity data access (ins, del, upd, ..). But this does not solve our problems. We want to reuse core business logic coded in PL/SQL. This is much more than change the ADF standard behavior for an update with an own PL/SQL-call.
    Now my question:
    Will there be a kind of sophisticated support to use ADF BC in combination with database-kept logic?
    If so, when will this happen and how will the common problems of transactional state inside the database and inside the ADF BC be solved? Any plans or ideas yet?
    Many other clients do have similar applications built in Forms and PL/SQL and would be glad to hear about a path of direction.
    I've read the technical article 'understanding the ADF BC state management feature' which you have contributed to. One current limitation is pointed out there: Using PL/SQL with ADF BC limits ADF AM pooling to 'restricted level' which reduces scalability.
    Are you aware of additional main problems/tasks to solve when using PL/SQL heavily with ADF BC, which we have to think about?
    Thank you for any response.
    Ingmar

    My main problem is two 'concurrent' areas holding state in an application system based on DB-stored PL/SQL-logic in combination with ADF BC.
    For a new System everything can be made ok:
    Sure, it is possible to build a new system with the business logic included in ADF BC only. All long-living state will be handled in the BC layer ( including support for UnitsOfWork longer than the webside short HTTP-requests and HTTP-sessions and longer than the database transactions.
    For an old system these problems arise:
    1. DB data changes not reflected in BC layer:
    Our PL/SQL-logic changes data in tables without notifying the ADF BC layer (and its cache). To keep the data in ADF BC entity objects identical to the changed database content a synchronization is needed. BC does not know which part of the application data has been changed because it has not initiated the changes through its entity objects. Therefore a full refresh is needed. In a Forms4GL environment the behavior is similar: We do frequently requeries of all relevant (base)tables after calling database stored logic to be sure to get the changed data to display and to operate on it.
    -> Reengineering of the PL/SQL-logic to make the ADF BC layer aware of the changes is a big effort (notifying BC about any change)
    2. longer living database transactions
    Our PL/SQL-logic in some areas makes use of lengthy database transactions. The technical DB-transaction is similar to the UnitOfWork. If we call this existing logic from ADF BC, database state is produced which will not be DB-committed in the same cycle.
    This reduces scalability of ADF BC AM pooling.
    Example:
    a) Call a DB-stored logic to check if some business data is consistent and prepare some data for versioning. This starts a DB-transaction but does not commit it.
    b) Control is handed back to the user interface. Successful result of step a) is displayed
    c) User now executes the versioning operation
    d) Call another DB-stored logic to execute the versioning. DB-transaction is still open
    e) Business layer commits the transaction automatically after successful finishing step d). Otherwise everything from a) to e) is rolled back.
    -> redesign of this behavior (= cutting the 1to1 relation between LogicalUnitOfWork and the technicalDatabaseTransaction is a big effort due to the big amount of code.

  • Support for HTML and CSS properties

    My biggest frustration with Acrobat Pro 9 is that it dropped support for certain HTML and/or CSS properties that were available in Acrobat Pro 8. In particular, the page-break-before attribute no longer works, nor does colspan. When I convert an HTML table with some colspans into a PDF, the table looks okay to the naked eye, but the structure behind the table (PDF tags) is incorrect.
    I can live without the page breaks, but I need colspan. I need to do this for hundreds of tables, so opening the Acrobat Table Editor and fixing the colspan by hand is not an option. A scripting/programming solution is required. Has anyone found a workaround? Does Acrobat X fix this problem?

    hello
    not trying to hijack the thread but needed some clarification
    your very short tutorial
    http://alt-web.blogspot.com/2012/11/primer-for-using-jquery-plug-ins.h tml
    was really informative. Just have a couple quick questions:
    you state:
    "the core code library which you ref in your <head> tags,"
    the below code just has to be declared ONCE at the beging in your head section, correct?
    <!-- jQuery latest core library from CDN-->
    <script type="text/javascript" src="http://code.jquery.com/jquery-latest.min.js">
    </script>
    then any number of jquery plugin scripts can be placed in ANY order in your head section following the above code, correct?
    "the function code inside <script> tags to invoke the plug-in."
    so then in the body, does the functions code have to come RIGHT AFTER the place it is being used?
    example
    <body>
    <div class="slideshow1"
    </div>
    <!--Plug-In Function Code1-->   
    <script type="text/javascript">
    </script>
    <div class="slideshow2"
    </div>
    <!--Plug-In Function Code2-->   
    <script type="text/javascript">
    </script>
    </body>
    or can you take all the function codes and paste them in the end outside of the respective divs that are using the code?
    ie does the position of the code matter?\
    thanks guys
    Nancy O. wrote:
    Try jQuery Fancybox
    http://fancybox.net/
    If you're new to using jQuery plugins, see this primer:
    http://alt-web.blogspot.com/2012/11/primer-for-using-jquery-plug-ins.h tml
    Nancy O.

  • [svn] 3275: Initial check in for support for asdoc comments in mxml files.

    Revision: 3275
    Author: [email protected]
    Date: 2008-09-19 15:01:57 -0700 (Fri, 19 Sep 2008)
    Log Message:
    Initial check in for support for asdoc comments in mxml files.
    For adding comments at the class level or to properties defined inside mxml use the syntax
    Other tags supported in asdoc should also work. for example @see, @includeExamples etc.
    QA: Yes
    Doc:
    Reviewed By: Paul
    Tests: checkintests
    Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/AsDocAPI.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/ImplementationCompiler.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/ImplementationGenerator.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/InterfaceCompiler.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/MxmlCompiler.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/AbstractBuilder.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/DocumentBuilder.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/dom/MxmlScanner.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/dom/Node.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/gen/ClassDef.vm
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/Model.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/MxmlDocument.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/decl/PropertyDeclaration .java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/decl/UninitializedProper tyDeclaration.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/init/ValueInitializer.ja va
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/ASDocConfiguration.java
    Added Paths:
    flex/sdk/trunk/asdoc/templates/images/AirIcon12x12.gif
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/util/MxmlCommentUtil.java

    @John - no luck on the plugin angle. In checking both JDev installs that previously had the problems, they have the default extensions.
    @Dave - at the time I can't say we noticed any migration notices, we certainly didn't see the migration dialog though. However the application in SVN was built on the same version of JDev so I don't expect a migration to find any changes anyhow.
    However on your second point we always check out into an empty directory, as we're checking out the whole application. As such if as you say the migration utilities is always called, shouldn't that mean we always see the projects modified? We certainly don't, we're on a day by day basis checking out whole applications to different directories and we don't see that behaviour.
    In turn reconsidering the modified .jpr file, from what I saw it looks to me that the whole project file is re-set to it's original state. Initially the problem detected was the libraries attached to the project were gone so we couldn't compile, but in close inspection it seems the whole .jpr file has been modified to a rather vanilla setup.
    One thing I can say when we originally experienced the problem (and from memory this was true in the dim dark past when it also occurred another time), is it was a check out from a SVN tags directory, not the trunk. In thinking about it, it may be the first check out from the tags directory that we see the issue. However to get around the issue we just revert the project file in the tags directory, we don't actually change the SVN repository code (ie. commit), so the issue should keep occurring. Yet at the moment if we check out the same tags directory, the issue doesn't occur?
    Hmmm?
    Btw Dave, are you an Oracle employee?
    CM.

  • Does HTMLEditorKit's object support include support for applets?

    Hello,
    I have a Swing application containing a JEditorPane used to display some HTML pages. I would like to embed a Java applet in one of the pages, but have had no success getting it to load.
    Is it possible to load an applet within an HTML document displayed by JEditorPane/HTMLEditorKit? From http://java.sun.com/j2se/1.5.0/docs/api/javax/swing/text/html/HTMLEditorKit.html:
    "The <applet> tag is not supported, but some support is provided for the <object> tag."
    What does "some support" mean exactly? (I'm using JDK 1.5)
    The applet I've written loads successfully in Firefox using the following code:
    <applet code=cprgraph.CPRGraphApplet width="557" height="319"></applet>as well as
    <object codetype="application/java" classid="java:cprgraph/CPRGraphApplet.class" width=557 height=319>
    </object>The applet is in the package cprgraph, and located in a directory cprgraph which is in my CLASSPATH.
    If HTMLEditorKit can't load applets, is there an alternative that can? Or any other way to embed a JComponent in an HTML document displayed by a Java application?
    Thanks,
    Ben

    Use Java SE 6.0 beta or wait untill it is released in Fall 2006

  • [svn] 3319: Adding support for documentation of SkinStates metadata.

    Revision: 3319
    Author: [email protected]
    Date: 2008-09-23 13:29:09 -0700 (Tue, 23 Sep 2008)
    Log Message:
    Adding support for documentation of SkinStates metadata. xslt files still needs to be updated to generate html for this metadata.
    Removing some unused code from ASDocExtension
    Fix for SDK-16759 - @example tag adds 'How to use examples' link to a file that's not present
    Fix for SDK-17001 - ASDoc should add "import flash.events.Event" when it encounters the [Bindable] tag
    QA: Yes
    Doc:
    Reviewed By: Paul
    Tests: checkintests
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-16759
    http://bugs.adobe.com/jira/browse/SDK-17001
    Modified Paths:
    flex/sdk/trunk/asdoc/templates/class-files.xslt
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ASDocExtension.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/AsDocAPI.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/DocComment.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelGenerator.java

    There is actually code in the base class that tests for
    whether the (extended) class implements the interface, so you don't
    need to add any methods - the interface itself is used as a "marker
    interface". Try setting the focusEnabled property to true as well
    (if you haven't already).
    If none of this works, have a look at the source of the
    canvas class - from within flexBuilder, hold down Ctrl and click on
    the reference to Canvas in your class (extends...). This should
    open the source in your editor and you can search for "focus" and
    probably find our where it's going wrong.

  • UCS 1.4 support for PVLAN

    Hi all,
    Cisco advise UCS 1.4 supports PVLAN. But i see the following comment about PVLAN in UCS 1.4
    "UCS extends PVLAN support for non virtualised deployments (without vSwitch ) . "
    "UCS release 1.4(1) provides support for isolated PVLAN support for physical server access ports or for Palo CNA vNIC ports."
    Does this means PVLAN won't work for virtual machine if VMs is connected to UCS by Nexus1000v or vDS although i am using PALO (M81KR) card?
    Could anybody can confirm that?
    Thank you very much!

    Have not got that working so far...how would that traffic flow work?
    1000v -> 6120 -> 5020 -> 6500s
    (2) 10Gbe interfaces, one on each fabric to the blades. All VLANs (including the PVLAN parent and child VLAN IDs) are defined and added to the server templates - so propagated to each ESX host.
    At this point, nothing can do layer 3 except for the 6500s. Let's say my primary VLAN ID for one PVLAN is 160 and the isolated vlan ID is 161...
    On the Nexus 1000v:
    vlan 160
      name TEN1-Maint-PVLAN
      private-vlan primary
      private-vlan association 161
    vlan 161
      name TEN1-Maint-Iso
      private-vlan isolated
    port-profile type vethernet TEN1-Maint-PVLAN-Isolated
      description TEN1-Maint-PVLAN-Isolated
      vmware port-group
      switchport mode private-vlan host
      switchport private-vlan host-association 160 161
      no shutdown
      state enabled
    port-profile type vethernet TEN1-Maint-PVLAN-Promiscuous
      description TEN1-Maint-PVLAN-Promiscuous
      vmware port-group
      switchport mode private-vlan promiscuous
      switchport private-vlan mapping 160 161
      no shutdown
      state enabled
    port-profile type ethernet system-uplink
      description Physical uplink from N1Kv to physical switch
      vmware port-group
      switchport mode trunk
      switchport trunk allowed vlan all
      channel-group auto mode on mac-pinning
      no shutdown
      system vlan 20,116-119,202,1408
      state enabled
    This works fine to and from VMs on the same ESX host (PVLAN port-profiles work as expected)...If I move a VM over to another host, nothing works...pretty sure not even if in same promiscuous port-profile. How does the 6120 handle this traffic? What do they get tagged with when they leave the 1000v?

Maybe you are looking for