Kodo 4 final release

Now that JDO2 has successfully passed the final ballot is
there any planned date for full JDO2 support in Kodo 4 ?
Thanks in advance,
Guido

Christiaan wrote:
Hi,
I just came across this link
http://weblog.infoworld.com/techwatch/archives/005738.html
Specifically:
"BEA is delaying the release of Kodo 4.0 until the EJB 3 (Enterprise
JavaBeans) specification is finalized, McBride said. That is expected in the
June timeframe. Version 4.0 features support for EJB 3 and JDO 2."
Would have been nice if this was also on the Solarmetric site or did I miss
it?
kind regards,
Christiaan
Yes, I have read some days ago.
And I didn't like it.
At this point, I don't think that BEA has a great commitment/interest on
its JDO2 implementation and on the JDO technology tout-court.
The facts are that the JPA implementation will be open source while JDO2
implementation, i.e. Kodo 4, will "wait" even if JDO2 spec have been
finally approved.
With BEA vote.
Guido.

Similar Messages

NPE for textField text after migration from ea2 to final release , help....

I migrate an application from JSC2 EA2 to JSC2 final release
In one of my page (first page that i check after migration) I have some text field.
In a button action i used those textfields Text for some processing.
Now after i press submit key (whether text boxes are full or empty) i get null pointer exception when i try to access the textfields text
by using getTextField1().getText().toString()
can any one say where i have mistaken in my migration plane ?
Thanks

Hi,
Suggest to replace all butttons using FCS version.
There was some change from EA to FCS for buttons.
e.g. if you have multiple buttons on a Page that was created using EA
then the wrong action handler will get called
hth
John

Camera Raw 4.5 final release?

Now it's been four weeks since Camera Raw 4.5 Release Candidate (ACR 4.5.0.161) was brought to us via Adobe Labs. Does anyone have any issues with it? I don't. Does anyone have an idea when the final release is supposed to arrive? I feel a four-week testing period is more than adequate for a tentative version that's supposed to be a "Release Candidate" (however the plug-in calls itself "4.5 Beta" ... go figure).
Another Camera Raw version most likely will be due in October, to support all the new digital cameras and backs that (hopefully) will get introduced at Photokina in September. I wonder if that's going to be ACR 4.6 ... or will ACR 4.5 "Grand Master" (which means "final release" in Adobe speak) be deferred until then?
-- Olaf

Jeff Schewe wrote:
> Fortunately, it's not your job
> to worry about it, is it?
Fortunately not, indeed.
Jeff further wrote:
> If you are unhappy [...] you are under
> no obligation to use it if you don't want to.
Huh? The conclusions you're drawing from my thinking aloud are, umm ... strange, to say the least. If you feel my inquiry was inappropriate and/or pointless then your reply also is.
Actually, I am quite happy with ACR 4.5RC, and furthermore I didn't hear anybody else reporting any problems. And that's exactly why I'm wondering why the final release isn't out yet. I guess I'd be less wondering if this tentative version had been announced and communicated as Beta rather than as Release Candidate. Anyway ... I'm just curious. It does not mean I was unhappy in any way.
Jeff further wrote:
> ... so, you'll just have to wait, huh?
Yes, obviously.
Jeff further wrote:
> Hey, it's nice out, go shoot something ...
Glad to hear it's nice on your side of the Big Pond, too.
-- Olaf

Lightroom 3.2 and Camera Raw 6.2 final releases are available

Lightroom 3.2 and Camera Raw 6.2 are now available as final releases on Adobe.com and through the update mechanisms available in Photoshop CS5 and Lightroom 3. These updates include additional lens profiles support among others. Check out http://blogs.adobe.com/lightroomjournal/. Following the example of Adobe's collaboration with SIGMA, leading lens manufacturers such as Pentax, Tamron and Zeiss worked closely with Adobe to create some of the profiles.
-Simon

Excellent! Now if there were only a way to use my S95 in raw... I guess I'll have to wait another few months

Date of Final Release Indicator for PO Release

Is there a table in SAP that provides the date the PO was approved for Final Release? I know that through ME23N you can get this information in the Environment and Header Changes area, but we would like to add this information to a report and are having trouble locating where SAP is storing the data.

Hi,
Pass into CDPOS table:
OBJECTCLAS = u201CEINKBELEGu201D , OBJECTID = PO Number (EBELN), T. Code = u201CME28 or equal to ME29Nu201D and Get all change document no. (CHANGENR)
TABNAME = u201CEKKOu201D, u201CField Name= FRGKE, Old Value = u201C0u201D and New value = u201C1u201D in to CDPOS and get latest change document number (CHANGENR).
Then pass CHANGENR into Change document No (CDHDR- CHANGENR), OBJECTCLAS = u201CEINKBELEGu201D,
U get who has released and date also.
Regards,
chinna

Changeability of PO after final release

Dear Gurus,
My client requirement is, PO should not be able to be changed once final release has happened. They should be able to change only after revoking the final release and again releasing it.
So, if I put changeability of Release indicator as "1", it will not allow to do any changes after final release including revoking the PO once it is outputted. How to resolve this?
Thanks,
Satish

See the changeability option under Release group
1     Cannot be changed
2     Changeable, no new determination of strategy
3     Changeable, new release in case of new strategy
4     Changeable, new release in case of new strat. or val. change
5     Changeable, new release if new strategy/outputted
6     Changeable, new rel. if new strat. or value change/outputted
     Changeable, new release in case of new strategy
to my understanding option 4 is more relevant to your requirement

Restriction of revoke after final release

Hi experts,
After final release of purchasing document lets say PR or PO user should not be able to revoke it.
Any suggestions highly appreciated apart from getting it done through user exit.
Regards,
Maverick

Dear Ramesh,
Thanks for your response.
I have already set changeability to 1 but my concern is after PR final approval if a PO is created with its reference then in this PR user should not be able to revoke or cancel an approval.
I think we can do this with user exit but is there any other alternative?
regards,
Maverick
Edited by: Maverick 331 on Jun 16, 2009 1:00 PM

What field in EKKO determine the final release dateof PO

hi,
i need to have the final release date to be show in a purchase Order print out. but i cant find the final release date field in EKKO table. can you please advice how am i going to get the final release date?
very thanks for the help.

Hi,
Final release date is not stored in EKKO it store in CDHDR table you can chaeck CDHDR-UDATE field for that.
Regards
Gagan

Could I use jstl tag in the JSP page of Creator 2 final release?

I have a JSP page used to work well in Creator 2EA2. The page
has the following code snippets:
<c:forEach items="${SessionBean1.webQuery1.details}" var="item">
                                                    <tr>
                                                        <td class="detailKey">
                                                            <c:out value="${item.key}"/>
                                                        </td>
                                                        <td class="detailValue">
                                                            <c:out value="${item.value}"/>
                                                        </td>
                                                    </tr>
                                                </c:forEach>
...Basically, it generates a table columns.
After migrating to Creator2 final release, a fatal exception is thrown
when the page is launched :
Description: An unhandled exception occurred during the execution of the web application. Please review the following stack trace for more information regarding the error.
Exception Details: org.apache.jasper.JasperException
/Page1.jsp(148,132) According to TLD or attribute directive in tag file, attribute items does not accept any expressions
Possible Source of Error:
   Class Name: org.apache.jasper.compiler.DefaultErrorHandler
   File Name: DefaultErrorHandler.java
   Method Name: jspError
   Line Number: 43
Source not available. Information regarding the location of the exception can be identified using the exception stack trace below.
Stack Trace:
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:43)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:414)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:155)
org.apache.jasper.compiler.Validator$ValidateVisitor.checkXmlAttributes Any suggestion, or work around?
Thanks

There is something strange in the HTML for you posedt, so I cannot clearly see what you are trying to do in your JSP page. But either of the following kinds of usage would cause this kind of error:
    <h:dropDown ... items="<%= ...some Java expression ...>"/>or
    <h:dropDown ... items="${...some JSP EL expression...}"/>This is because JSF component tags allow neither Java runtime expressions nor JSP EL expressions (at least in JSF 1.1, which is what Creator 2 supports). The answer is to use a JSF EL expression instead, like this:
    <h:dropDown ... items="#{... some EL expression}"/>Craig

JSF 1.0 final release problem.

My application was working when I was using the beta release. (with the old tag like input_text)
I downloaded the JSF 1.0 final release from Sun and everything stopped working.
The funny part is the the samples in the fina release are working. However, they are using the old jar files!!! The jsf-impl.jar inside the samples is different from the one inside the jsf-1_0/lib directory. How can we follow those samples???
When I tried to use the jsf-impl.jar inside the sample application, my application gave me the famous NullPointerException when the listener ConfigLister is initialized.
When I tried to use the jsf-1_0/lib/jsf-impl.jar inside the lib directory, my application gave me:
org.apache.jasper.JasperException: Error setting property 'description' in bean of type null
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684)
Looks like my bean is not found. Has anyone seen this before? I got the same error when I tried to move an application from Java Creator to tomcat.
I am using tomcat 4.1.29
Someone from Sun please fix the samples inside th final release.

Thanks.
The second exception is gone. It ends up to be I am using binding instead of value for one attribute inside my jsp.
Still, it's so confusing to have the older version implementtion inside the samples for final release.
In the old verion, it's called ConfigListener and the version called ConfigureListener.

PO Item Deletion ON Final Release

Hi ,
Can u tel me , purchase order is released by three levels of approvers then any one delete the released po line item through me22n transaction a mail should go to the all released approvers . on deletion after final release CHANGE event is triggering in SWEL...plz help me out how to solve this..
i copied standard WS20000075 to custom Z , every thing working fien , but on deletion of line item standard supports or how to approach this i am not getting ?
thanks,
sandeep..

Hi ,
After final release workflow will not be active the actual release workflow will be in completed status if all level release is complete .
So i want to send a mail to all approvers in new workflow ...
created an event deleted Ybus2012 delegation of bus 2012..
in swec transaction try to create a entry , FIELD RESTRICTIONS what to enter for my event..
when i enter AENNR , (Key for change doc. object AENNR and business object type BUS2012 are incompatible) error is coming ....
can anyone suggest me ..
thanks ..
sandeep

[Announcement: Java server-side web controls] - TICL 1.0 Final Released

Hello JSP developers,
We are pleased to announce the immediate availability of TICL (Tag Interface
Component Library) 1.0 Final Release. TICL is library of server-side user
interface components accessible through JSP tags. Like a conventional
desktop toolkit, the components maintain state and manage interaction logic
with the end-user with little or no assistance from the programmer.
Read more about TICL at http://www.kobrix.com/ticl/ticlmain.jsp.
If you are already a TICL user, check out the release notes at
http://www.kobrix.com/ticl/releasenotes.jsp for the latest changes.
More info
One of the major goals of TICL is to bring RAD-like development to the WEB
platform. Programmers can concentrate on logical functionality and build JSP
pages by placing TICL components through tags and responding to user events.
Every component is self-contained and manages interaction with the end-user.
Visual appearance of components is abstracted into a high-level styles
framework. In fact, TICL is probably the only server-side Java toolkit that
rivals Microsoft ASP.NET's web controls.
The library is tailored more towards WEB application development, rather
than content only oriented sites. It is designed to quickly build clean,
robust, well-structured and therefore highly maintainable code. It
integrates seemlessly into existing JSP applications and it will work on any
standard compliant JSP 1.1 container (e.g. Tomcat 3.2.1 and above, Resin
etc.) and with fairly recent versions of the popular browsers.
Core features are:
- A powerful and extensible server-side event model. Component-end user
interaction is encapsulated into a well defined set of server-side events.
You can of course define event listeners, develop custom events, event
filters etc.
- Predefined components like panels, tabbed panels, tree views, DHTML menus,
table views. Most can perform their interaction with the end-user at the
browser through DHTML or by making a trip back to server on every user
action (like expanding a tree node or minimizing a panel) - that is
components are either "client" or "server" managed.
- Smart browser handling. A complete framework for dealing with browser
(user agent) capabilities, including detection of dynamic properties like
connection speed, screen resolution, available plugins etc.; supporting JSP
tags; on the fly selection of component rendering based on the current user
agent.
- A high-level styles framework for complete customization of the look&feel
of components. Styles can be organized into themes. An inheritence mechanism
of style objects provides for a powerful high-level structuring. The
framework allows for a clean separation between look&feel and functional
behaviour of GUI elements. No more copy&paste, no more code cluttering with
tedious, browser-specific HTML details - consistency of look&feel can be
easily achieved by maintaining a single TICL style sheet, a simple XML file,
that is applied to all pages in your WEB application.
- Full encapsulation of HTML forms, including a file upload component,
augmented with things such as server-side command handlers, labels and DHTML
tooltips. Form fields are typed, true server-side components. Not limited to
the standard HTML form fields, they operate on a high level and custom ones
can be developed and plugged into the framework.
- A very powerful and easy to use declarative form validation mechanism
(both client and server-side). You define validation rules and handlers for
invalid forms in a clean, declarative way. The same rules you define can be
applied at the client (through automatic generation of the necessary
JavaScript) or at the server. Special purpose syntax allows you to easily
handle interdependencies between field values.
- A Data Objects framework integrated with TICL forms. Allows you to
manipulate complex aggregate structures and associate them with forms for
automatic mapping to/from form field values and data object fields (e.g.
Java beans). A type mapping framework allows you to map any form field type
to any Java type.
- An integration module for the popular Struts framework is provided also.
For example, it is possible to use the powerful TICL form tags with Struts'
ActionForms.
TICL is FREE for non-commercial and non-govermental use, and for an
unlimited evaluation period. It comes with an extensive, over 200 pages,
Reference Manual. To download it, please goto http://www.kobrix.com and
select Downloads from the TICL pulldown menu. If you are not already a TICL
user, you may need to register first.
We sincerely hope you will enjoy TICL and are looking forward to your
feedback!
Best Regards,
Borislav Iordanov
[email protected]
Kobrix Software Inc.
http://www.kobrix.com

This looks quite nice. I'm going to evaluate it now, but I wish it was open-source....
Judging from the release notes, it's been around for a while. Has anybody had any experience with this product? Is it reliable? Does it scale well?

Help needed get JSF final release running on tomcat 5

Hi there,
I know my topic seems to be a easy thing which is often discusseb but I tell you it's not. And after searching the forum an the web... it's driving me crazy I want to make some development and tests but I can' get my stuff running on tomcat 5 and jsf final release.
This is my last error message... seems like tomcat don't know anything about jsf...
my directories---------------------------
my webbapp
-- WEB-INF
classes
lib
scr
web.xml
faces-config.xml
WEB-INF
commons-beanutils.jar
commons-collections.jar
commons-digester.jar
commons-logging.jar
jsf-api.jar
jsf-impl.jar
jstl.jar
standard.jar
web.xml ------------------------------------------------------------------------
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<display-name>MyWeb</display-name>
<description>
FElix
</description>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
</context-param>

<servlet>
<servlet-name>JavaServer Faces Servlet</servlet-name>
<servlet-class>
javax.faces.webapp.FacesServlet
</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>

<servlet-mapping>
<servlet-name>JavaServer Faces Servlet</servlet-name>
<url-pattern>/faces/*</url-pattern>
</servlet-mapping>
<listener>
<listener-class>
com.sun.faces.config.ConfigureListener
</listener-class>
</listener>
</web-app>
faces-config.xml---------------------------------
<?xml version="1.0"?>
<!DOCTYPE faces-config PUBLIC
"-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.0//EN"
"http://java.sun.com/dtd/web-facesconfig_1_0.dtd">
<faces-config>
<navigation-rule>
<from-view-id>/eingabe.jsp</from-view-id>
<navigation-case>
<from-outcome>success</from-outcome>
<to-view-id>/ausgabe.jsp</to-view-id>
</navigation-case>
</navigation-rule>
<managed-bean>
<managed-bean-name>Square</managed-bean-name>
<managed-bean-class>src.com.edu.jsf.bean.SquareBean</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
</managed-bean>
</faces-config>
ERROR - MESSAGE
org.apache.jasper.JasperException: /eingabe.jsp(19,3) No tag "input_number" defined in tag library imported with prefix "h"
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:83)
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:402)
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236)
org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1346)
org.apache.jasper.compiler.Parser.parseElements(Parser.java:1598)
org.apache.jasper.compiler.Parser.parseBody(Parser.java:1827)
org.apache.jasper.compiler.Parser.parseOptionalBody(Parser.java:1100)
org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1405)
org.apache.jasper.compiler.Parser.parseElements(Parser.java:1598)
org.apache.jasper.compiler.Parser.parseBody(Parser.java:1827)
org.apache.jasper.compiler.Parser.parseOptionalBody(Parser.java:1100)
org.apache.jasper.compiler.Parser.parseCustomTag(Parser.java:1405)
org.apache.jasper.compiler.Parser.parseElements(Parser.java:1598)
org.apache.jasper.compiler.Parser.parse(Parser.java:171)
org.apache.jasper.compiler.ParserController.doParse(ParserController.java:258)
org.apache.jasper.compiler.ParserController.parse(ParserController.java:139)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:237)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:456)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:439)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:553)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:291)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248)
javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:142)
com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:200)
com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
I really stuck so any help is appriciated...
I also tried to put the jars in the common/lib
but still not working...
I tried to get it running with jwsdp ... but same s*** ...
best regards
Felix

thanks....
this means... everything was working and I better should have read the notes...
I went back.... installed jwsdp1.3 and everything was fine...
so I will give it a try... change the classes and at this time i use the right tags...
but this will also work for the tomcat downloaded from the apache.org site?
I only need the jar files in the jsf-1.0/lib file and the latest jstl-jars ---
thanks again
reagards felix

Jsf-1.0 Final Release and tomcat 5.019

I post again to say that is works well finally.
To make it works:
- download jsf-1.0 FR
- in your application .war put in WEB-INF/lib/: common-digester.jar, jsf-api.jar, jsf-impl.jar, common-beanutils.jar and jstl.jar. (libs of jsf + lib of jsp).
- dont use in web.xml <listener-class>com.sun.config.configListener<listener-class>
- put your appli in jakarata.../webapps
It works without a class extending ServletContextListener (servlet-api.jar).
If you have problems erase jakarta.../work/Catalina/yourappli and reload.

Just for my own information : where did you get jstl.jar and standard.jar ?
I had to dig in the latest nightly snapshot from jstl jakarta web site to find them but I don't even know if the one I use are final releases of not...

Does the final Release 5.1 Support ear type deployment in Weblogic

I down loaded final Release 5.1 and trying to find deploying different
modules using using ear (Enterprise Archieve), I can not find
any documents.
Does the final Release support ear type deploying or not.
Regards
Krishna

No, it supports war and jar deployments only.
-- Rob
Krishna Chaganti wrote:
I down loaded final Release 5.1 and trying to find deploying different
modules using using ear (Enterprise Archieve), I can not find
any documents.
Does the final Release support ear type deploying or not.
Regards
Krishna

Change in Expected Delivery date (EDD) field in the PO after final release

Hello Experts,
There is a business requirement, whereby after PO final release is completed & when the PO is released for further processing, no further changes should be possible, except for the expected delivery date (EDD) field in the Delivery schedule tab of the PO Item details. Other than this, no changes should be possible in the PO, neither qty, nor price, not even the simple PO text should be allowed to get changed. In other words no field should be allowed to change.
Ideally, except the EDD field, other all fields should be in grey mode, or atleast changes in any of the PO fields (except EDD) should not be allowed to get saved after the PO is final released.
Please let me know if SAP provides any such facility, whereby you can selectively choose certain fields (like EDD field) on which Release Strategy should not be applied & changes should be allowed in these fields even after PO final release.
Thanks in advance,
Zafar.

If you go to OMET transciton and here you can assign the field selection key in the field FieldSe
and assing the User parameter EFB in user id of the user using SU3 transction
for more help see below
Create a Functional Authorization in the Following path:
Material Mangement - Purchasing - Authorization Management - Define Functional Authorization for Buyers
Now, in SU3 trxn ,Give the User Parameter EFB in the user master Parameters Tab and give the parameter value.
create the fields selction which you want use here in PO field seleciton config.

Kodo 4 final release

Similar Messages

Maybe you are looking for