Best Practice for multivalued parameters in *QL

I have a need to do this:
            <query>
               <query-method>
                    <method-name>ejbSelectAllCasesInFIPS</method-name>
                    <method-params>
                                          <method-param>java.util.Collection</method-param>
                      </method-params>
               </query-method>
                <ejb-ql>     <![CDATA[
                                     select object(c)
                                     from Clients c, in (c.Status) as s
                                     where s.issue='H' or s.issue='P'
                                     and c.ClientCaseInfo.fipsCode in $1
                                     ]]>
                 </ejb-ql>
            </query>But based on the spec, this seems verboten.
Am I restricted to building the query by hand, iterating thru the collection and appending each new string parameter into another String representing a comma delimited list of these parameters?
Many thanks,
Alexandra

Is Sun considering adding Collections (even strongly typed Collections) to this spec? I'm guessing the reason it�s not in the spec is because you can have a Collection of ANYTHING, which could be averted by adding collection types for known types (or specifications for such) . I don't see any reason Java can�t provide StringCollection, IntCollection, LongCollection, etc. It would be incumbent upon DBMS vendors to implement the mapping (which they already do for non-Collection types) but being a programmer I don't see how difficult that could be, since we programmers are repeatedly faced with this relatively low-level problem.

Similar Messages

Best practice for passing parameters to a Timer event handler?

The code hinting is suggesting that I use a Timer object rather than setTimeout or setInterval, however I need to pass a parameter to the timer handler.
What is the best practice for doing this?
+ Subclass Timer?
+ Subclass TimerEvent?
+ Global variable?
+ other?
Thanks

Hmm. I don’t think I would’ve chosen that option. I would probably create a class that listens for the TimerEvent dispatches a custom event. Unless there is information you need in TimerEvent, I don’t see a need to extend it.

JSF - Best Practice For Using Managed Bean

I want to discuss what is the best practice for managed bean usage, especially using session scope or request scope to build database driven pages
---- Session Bean ----
- In the book Core Java Server Faces, the author mentioned that most of the cases session bean should be used, unless the processing is passed on to other handler. Since JSF can store the state on client side, i think storing everything in session is not a big memory concern. (can some expert confirm this is true?) Session objects are easy to manage and states can be shared across the pages. It can make programming easy.
In the case of a page binded to a resultset, the bean usually helds a java.util.List object for the result, which is intialized in the constructor by query the database first. However, this approach has a problem: when user navigates to other page and comes back, the data is not refreshed. You can of course solve the problem by issuing query everytime in your getXXX method. But you need to be very careful that you don't bind this XXX property too many times. In the case of querying in getXXX, setXXX is also tricky as you don't have a member to set. You usually don't want to persist the resultset changes in the setXXX as the changes may not be final, in stead, you want to handle in the actionlistener (like a save(actionevent)).
I would glad to see your thought on this.
--- Request Bean ---
request bean is initialized everytime a reuqest is made. It sometimes drove me nuts because JSF seems not to be every consistent in updating model values. Suppose you have a page showing parent-children a list of records from database, and you also allow user to change directly on the children. if I hbind the parent to a bean called #{Parent} and you bind the children to ADF table (value="#{Parent.children}" var="rowValue". If I set Parent as a request scope, the setChildren method is never called when I submit the form. Not sure if this is just for ADF or it is JSF problem. But if you change the bean to session scope, everything works fine.
I believe JSF doesn't update the bindings for all component attributes. It only update the input component value binding. Some one please verify this is true.
In many cases, i found request bean is very hard to work with if there are lots of updates. (I have lots of trouble with update the binding value for rendered attributes).
However, request bean is working fine for read only pages and simple binded forms. It definitely frees up memory quicker than session bean.
----- any comments or opinions are welcome!!! ------

I think it should be either Option 2 or Option 3.
Option 2 would be necessary if the bean data depends on some request parameters.
(Example: Getting customer bean for a particular customer id)
Otherwise Option 3 seems the reasonable approach.
But, I am also pondering on this issue. The above are just my initial thoughts.

Best practice for declaring and initializing String?

What is the best practice for the way Strings are declared in a class?
Should it be
private String strHello = "";
or should I have the initialization in the constructors?

The servlet constructor is usually called once, when the servlet is first accessed. But then again maybe something else happens, google servlet life cycle if you must know.
But let's take a step backwards here. It seems like you are trying to put fields into servlets. Don't do that. When two users fetch the servlet's URL at the same time, the fields are shared between the two hits. If you store something like HTTP parameters in the fields, the two hits' parameters will get mangled. The hits can end up seeing each other's parameter values.
The best way is not to have fields in servlets. (Except maybe "static final" constants, sometimes rarely something else.) Many concurrency worries go away, servlet life cycle worries go away, servlet constructors go away, init() usually goes away.

Best practice for a deplomyent (EAR containing WAR/EJB) in a productive environment

Hi there,
I'm looking for some hints regarding to the best practice deployment in a productive
environment (currently we are not using a WLS-cluster);
We are using ANT for buildung, packaging and (dynamic) deployment (via weblogic.Deployer)
on the development environment and this works fine (in the meantime);
For my point of view, I would like to prefere this kind of Deploment not only
for the development, also for the productive system.
But I found some hints in some books, and this guys prefere the static deployment
for the p-system.
My question now:
Could anybody provide me with some links to some whitepapers regarding best practice
for a deployment into a p-system ??
What is your experiance with the new two-phase-deploment coming up with WLS 7.0
Is it really a good idea to use the static deployment (what is the advantage of
this kind of deployment ???
THX in advanced
-Martin

Hi Siva,
What best practise are you looking for ? If you can be specific on your question we could provide appropriate response.
From my basis experience some of the best practices.
1) Productive landscape should have high availability to business. For this you may setup DR or HA or both.
2) It should have backup configured for which restore has been already tested
3) It should have all the monitoring setup viz application, OS and DB
4) Productive client should not be modifiable
5) Users in Production landscape should have appropriate authorization based on SOD. There should not be any SOD conflicts
6) Transport to Production should be highly controlled. Any transport to Production should be moved only with appropriate Change Board approvals.
7) Relevant Database and OS security parameters should be tested before golive and enabled
8) Pre-Golive , Post Golive should have been performed on Production system
9) EWA should be configured atleast for Production system
10) Production system availability using DR should have been tested
Hope this helps.
Regards,
Deepak Kori

Best Practice for Production environment

Hello everyone,
can someone share the best practice for a production environment? or is there a SAP standard best practice to follow in a Production landscape?
i understand there are Best practices available for Implementation , Migration and upgrade. But, i was unable to find one for productive landscape
thanks.

Hi Siva,
What best practise are you looking for ? If you can be specific on your question we could provide appropriate response.
From my basis experience some of the best practices.
1) Productive landscape should have high availability to business. For this you may setup DR or HA or both.
2) It should have backup configured for which restore has been already tested
3) It should have all the monitoring setup viz application, OS and DB
4) Productive client should not be modifiable
5) Users in Production landscape should have appropriate authorization based on SOD. There should not be any SOD conflicts
6) Transport to Production should be highly controlled. Any transport to Production should be moved only with appropriate Change Board approvals.
7) Relevant Database and OS security parameters should be tested before golive and enabled
8) Pre-Golive , Post Golive should have been performed on Production system
9) EWA should be configured atleast for Production system
10) Production system availability using DR should have been tested
Hope this helps.
Regards,
Deepak Kori

Best practice for backing bean population? (also, ActionListener RANT)

Hello,
I am about 3/4 of the way through development of a small to medium size JSF application. Sometimes I really like JSF, but much of the time I am left puzzled or frustrated for hours trying to find workarounds to JSF's bugs/glitches and design flaws.
For example, early on, I was impressed with how easily it was to invoke a method from a page using an actionlistener. Now that I'm actually building things with JSF, the actionlistener funtionality still seems cool, but incredibly half baked. I find myself using request parameters LIKE CRAZY to work around the fact that JSF doesnt support passing parameters directly to backing bean methods. This feels awkward and wrong considering the fact that JSF is intended to abstract the HTTP underpinnings. To add insult to injury, I often have to iterate through ALL of the request parameters looking for one that has an id with an ending matching my desired property name (since JSF appends it's own crap to the beginning). I don't like doing things in a hacky way. This seems very hacky, and I feel dirty doing it.
So, my first question is, what is the best practice for populating backing beans??? How do others accomplish this. I can think of several other approaches, but none feel less hacky.
Second, are there plans in the next spec (please say there are) to allow parameters to be passed to backing bean methods? If not, WHY THE HECK NOT?
Even though JSF expert group people have been conspicuously absent from this forum of late, I'd really appreciate responses from you as well.
Thank you for your thoughts.

Hi BrownBear,
I've been using JSF for about 6 months now and I'd be glade to help as much as I can.
Concerning parameters, I'm not sure what your issue is but I use the f:param tag to pass them. If you could post an example of what you are trying to do, I could see exactly what your issue is. Maybe the f:param can't help you.
As for best practice for populating backing beans, I personaly try to let JSF do as much as possible. For example, if I have a backing bean with five properties, I make sure that they all are on the JSP page the bean serves. If one of the property is just there as an Id like, lets say, a Person ID (DB row key), then I put it on my JSP page as a hidden input field. I do the same with the properties that only for display, if I want them to be back in my bean when request comesback.
Hope this help some how. Please, feel free to ask specific questions related to your specific problem and I monitor this post and trnasfer to you the ;little JSF experience I have.
I'm pretty happy with JSF as it is but it sure needs improvements. :) What the heck, it's version 1.01 after all, and the next release should be a great one with the integration of JSTL.
Cheers

Best Practice for Servlets

I guess I'm asking for most peoples' input on what I'm planning to do here ....
Here's what I want to do, and know a bit about.
o I want to make a servlet that serves only XML.
o After that, I want to transform the XML into web pages, RSS feeds etc.. using XSLT.
Here's what I'm not so sure about...
o How should I implement the interface to the web-based aspects? Should the servlet be coded to display HTML pages on "GET" requests? Or should I use a pile of HTML files to make forms?
o What do I use to perform the XSLT transformations? Where should the set of solutions be placed relative to my servlet? Would a user then access this solution rather than the servlet itself?
o How do I code the servlet on one machine, and then test it on another without breaking the libraries? How do I set up any libraries I might have to use (like for XSLT transformations) on the server?
Any other advice here? I'm sure this is done often, but I can't find a resource that explains the best practices for it all.
I know this sounds like a lot of stupid questions. I've had lots of programs working with Java before, but I'm at a loss as to how I'm supposed to package libraries I use in my programs - moreso with a servlet. To make matters worse, I plan on using MySQL as the database.
If there's some wizard on the forums here who's willing to say more than just "RTFM" (of which there is none to answer my questions together as one), I'd be very very happy ":^)

Let me re-pose my question so as to be specific
enough to not be picked apart in my answer.
I want to FIRST AND FOREMOST, create a servlet that
serves up XML based on parameters given to it (how?
who cares.).What does "serves up XML" mean?
Let's be precise. Do you intend the servlet to send the XML back to the client? Or is the XML an intermediate step in your processing? (Yes, it matters.)
Then, I want to create interfaces (HTML, RSS,
boogledeedoo) to this XML data by having either JSP,
another servlet or insert something else here,
transform the XML into whatever the desired format
is."interface" is a loaded term in Java. What do you mean by it?
>
My assumption is that I'll make the servlet that is
capable of outputting my desired XML data and then
create another servlet that will poke it for data as
needed to transform the XML into HTML. This servlet
would also likely serve as the web site itself and
would manage user logins etc...(persistance yaddy
yadda)You're not thinking about this properly.
"yadda yadda" == muddled thinking.
My other assumption is that I'll make another servlet
that will poke the XML servlet and transform that
into RSS or anything else I can dream up.How does "poke the XML servlet" fit into the request/response protocol that is HTTP? Please explain.
-=-!REASONING!-=-
Previously, when I was working with PHP, I liked to
make scripts that would display interfaces and post
to themselves. OK, now I see. "interface" == GUI in a browser to you. Very good.
You can create a JSP that is an interface. You can have that JSP submit the HTTP POST or GET request to itself. No problem there, as long as "itself" knows what to do with the request.
It was a nice way of creating a
complete little package. Everything for one function
was encapsulated nicely under one roof. No excessive
HTML files all over the place to nurture.A simple problem, a simple solution. You can do that with a JSP.
Look. Part of my inability to describe this well is
because I DO feel like I'm in a lot of directions at
once. Or you don't understand the technology very well.
But I have to be in order to pull together
some sort of plan for myself. I understand many
concepts and have just finished studying object
oriented design etc..."Just finished"? How long did it take?
I know things about how Tomcat does connection
pooling for SQL connections.Great. Not much to understand there. It's harder to figure out how to do n-tier apps with more than one page well.
I do know how to use Google, probably a lot better
than most. But rest assured, I've yet to find a
little guide as complete as any of the "LAMP" books
there are out there. Which by the way, I have never
purchased.That's because Java Enterprise Edition isn't intended for little problems. LAMP is. Maybe the limitation is that you are used to "little" problems and not bigger ones.
If JEE seems scattered and complex, it's because it is. It encompasses more than LAMP.
I'm confident in good guidance, and not a heartfelt
smackdown. I'm still waiting for some clear suggestions.I gave you one, you just didn't know it: go read about Spring.
http://www.springframework.org
It'll help you structure complex apps from the user interface to the database in the back.
You're welcome.
%

Best practices for applying sharpening in your workflow

Recently I have been trying to get a better understanding of some of the best practices for sharpening in a workflow. I guess I didn't realize it but there are multiple places to apply sharpening. Which are best? Are they additive?
My typical workflow involves capturing an image with a professional digital SLR in either RAW or JPEG or both, importing into Lightroom and exporting to a JPEG file for screen or printing both lab and local.
There are three places in this workflow to add sharpening. In the SLR, manually in Lightroom and during the export to a JPEG file or printing directly from Lightroom
It is my understanding that sharpening is not added to RAW images even if you have added sharpening in your SLR. However sharpening will be added to JPEG’s by the camera.
Back to my question, is it best to add sharpening in the SLR, manually in Lightroom or wait until you export or output to your final JPEG file or printer. And are the effects additive? If I add sharpening in all three places am I probably over sharpening?

You should treat the two file types differently. RAW data never has any sharpening applied by the camera, only jpegs. Sharpening is often considered in a workflow where there are three steps (See here for a founding article about this idea).
I. A capture sharpening step that corrects for the loss of sharp detail due to the Bayer array and the antialias filter and sometimes the lens or diffraction.
II. A creative sharpening step where certain details in the image are "highlighted" by sharpening (think eyelashes on a model's face), and
III. output sharpening, where you correct for loss of sharpness due to scaling/resampling or for the properties of the output medium (like blurring due to the way a printing process works, or blurring due to the way an LCD screen lays out its pixels).
All three of these are implemented in Lightroom. I. and II. are essential and should basically always be performed. II. is up to your creative spirits. I. is the sharpening you see in the develop panel. You should zoom in at 1:1 and optimize the parameters. The default parameters are OK but fairly conservative. Usually you can increase the mask value a little so that you're not sharpening noise and play with the other three sliders. Jeff Schewe gives an overview of a simple strategy for finding optimal parameters here. This is for ACR, but the principle is the same. Most photos will benefit from a little optimization. Don't overdo it, but just correct for the softness at 1:1.
Step II as I said, is not essential but it can be done using the local adjustment brush, or you can go to Photoshop for this. Step III is however very essential. This is done in the export panel, the print panel, or the web panel. You cannot really preview these things (especially the print-directed sharpening) and it will take a little experimentation to see what you like.
For jpeg, the sharpening is already done in the camera. You might add a little extra capture sharpening in some cases, or simply lower the sharpening in camera and then have more control in post, but usually it is best to leave it alone. Step II and III, however, are still necessary.

Best practices for logging results from Looped steps

Hi all
I would like to start a discussion to document best practices for logging results (to reports and databases) from Looped Steps
As an application example - let's say you are developing a test for one of NI's analog input or output cards and need to measure a voltage across multiple inputs or outputs.
One way to do that would be to create a sequence that switches the appropriate signals and performs a "Voltage Measurement" test in a loop.
What are your techniques for keeping track of the individual measurements so that they can be traced to the individual signal paths that are being measured?
I have used a variety of techniques such as
i )creating a custom step type that generates unique identifiers for each iteration of the loop. This required some customization to the results processing . Also the sequence developer had to include code to ensure that a unique identifier was generated for each iteration
ii) Adding an input parameter to the test function/vi, passing loop iteration to it and adding this to Additional results parameters to log.

I have attached a simple example (LV 2012 and TS 2012) that includes steps inside a loop structure as well as a looped test.
If you enable both database and report generation, you will see the following:
1) The numeric limit test in the for loop always generates the same name in the report and database which makes it difficult to determine the result of a particular iteration
2) The Max voltage test report includes the paramater as an additional result but the database does not include any differentiating information
3) The Looped Limit test generates both uniques reports and database entries - you can easily see what the result for each iteration is.
As mentioned, I am seeking to start a discussion for how others handle results for steps inside loops. The only way I have been able to accomplish a result similar to that of the Looped step (unique results and database entry for each iteration of the loop) is to modify the process model results processing.
Attachments:
test.vi ‏27 KB
Sequence File 2.seq ‏9 KB

Best Practices for FSCM Multiple systems scenario

Hi guys,
We have a scenario to implement FSCM credit, collections and dispute management solution for our landscape comprising the following:
a 4.6c system
a 4.7 system
an ECC 5 system
2 ECC6 systems
I have documented my design, but would like to double check and rob minds with colleagues regarding the following areas/questions.
Business partner replication and synchronization: what is the best practice for the initial replication of customers in each of the different systems to business partners in the FSCM system? (a) for the initial creation, and (b) for on-going synchronization of new customers and changes to existing customers?
Credit Management: what is the best practice for update of exposures from SD and FI-AR from each of the different systems? Should this be real-time for each transaction from SD and AR (synchronous) or periodic, say once a day? (assuming we can control this in the BADI)
Is there any particular point to note in dispute management?
Any other general note regarding this scenario?
Thanks in advance. Comments appreciated.

Hi,
I guess when you've the informations that the SAP can read and take some action, has to be asynchronous (from non-SAP to FSCM);
But when the credit analysis is done by non-SAP and like an 'Experian', SAP send the informations with invoices paid and not paid and this non-SAP group give a rate for this customer. All banks and big companies in the world does the same. And for this, you've the synchronous interface. This interface will updated the FSCM-CR (Credit), blocking or not the vendor, decreasing or increasing them limit amount to buy.
So, for these 1.000 sales orders, you'll have to think with PI in how to create an interface for this volume? What parameters SAP does has to check? There's an time interval to receive and send back? Will be a synchronous or asynchronous?
Contact your PI to help think in this information exchange.
Am I clear in your question?
JPA

Best Practices for JMS Service Documentation

Our software consists of a variety of JMS producers and consumers used to transform and transmit business to business messages on a large scale.
The service nodes do a variety of things, and we've had trouble over the years ensuring every queue-based service clearly identifies the parameters and payload it accepts, so that everyone from programmers to system administrators can easily see what services are available and how they are to be used.
Some have advocated always adding a web service in front of each message-based service to guarantee interface contracts are all well publicized. I think there are reasons to choose web services and reasons to choose message-based services, and am not convinced this is the right answer to address limitations in expressing the design contract for a message-based service. That said, I really like what we've been able to do with self-documenting web services based on annotations, and wonder if there's a conceptual equivalent in message-based software.
What are your best practices for ensuring your message-based services are as self-documenting as your modern web service?
Thanks in advance for your advice!
Edited by: lsamaha on Apr 16, 2012 11:46 AM

*bump

Universe Design Best Practices for Oracle

Hello All,
We recently moved from XIR2 on MS SQL 2005 to XI 3.1 on Oracle. This has been a difficult move for us as my team is new to oracle. I'm currently working on several performance issues between BOBJ and Oracle and am looking for documentation on best practices for universe design with oracle. I've foudn tidbits here and there regrading using parameters joing_by_sql and boundary_weight_table, wondering if there are other options out there that might help. We have queries taking 45+ minutes to run and that is totally unacceptable.
thanks
Andrea

I am not sure if you are looking for Optimization or anything else. sorry for that following link might help you considering Oracle as DB.
Link:[Universe Optimization 1|http://www.bidwtoday.com/business-objects/universe-designer/business-objects-universe-optimization/]
Link:[Universe Optimization 2|http://forums.sdn.sap.com/post!reply.jspa?messageID=8721932]
--Kuldeep

Tips and best practices for translating C into LabVIEW? SERIOUS newbie...

I need to translate a C function into LabVIEW. This will be my *first* LabVIEW project. I've been reading some tutorials, and I'm still struggling to get my brain out of "C/C++ mode" and learn the LabVIEW paradigms.
Structurally, the function that I need to translate gets called from a while-loop and performs a bunch of mathematical calculations.
The basic layout is something like this (this obviously isn't the actual code, it just illustrates the general flow control and techniques that it uses).
struct Params
// About 20 int and float parameters
int CalculateMetrics(Params *pParams,
float input1, float input2 [etc])
int errorCode = 0;
float metric1;
float metric2;
float metric3;
// Do some math like:
metric1 = input1 * (pParams->someParam - 5);
metric2 = metric1 + (input2 / pParams->someOtherParam);
// Tons more simple math
// A couple for-loops
if (metric1 < metric2)
// manipulate metric1 somehow
else
// set some kind of error code
errorCode = ...;
if (!errorCode)
metric3 = metric1 + pow(metric2, 3);
// More math...
// etc...
// update some external global metrics variables
return errorCode;
I'm still too green to understand whether or not a function like this can translate cleanly from C to LabVIEW, or whether the LabVIEW version will have significant structural differences.
Are there any general tips or "best practices" for this kind of task?
Here are some more specific questions:
Most of the LabVIEW examples that I've seen (at least at the beginner level) seem to heavily rely on using the front panel controls to provide inputs to functions. How do I build a VI where the input arguments(input1, input2, etc) come as numbers, and aren't tied to dials or buttons on the front panel?
The structure of the C function seems to rely heavily on the use of stack variables like metric1 and metric2 in order to perform calculations. It seems like creating temporary "stack" variables in LabVIEW is possible, but frowned upon. Is it possible to keep this general structure in the LabVIEW VI without making the code a mess?
Thanks guys!

There's already a couple of good answers, but to add to #1:
You're clearly looking for a typical C-function. Any VI that doesn't require front panel opening (user interaction) can be such a function.
If the front panel is never opened the controls are merely used to send data to the VI, much like (identical to) the declaration of a C-function. The indicators can/will be return values.
Which controls and indicators are used to sending data in and out of a VI is almost too easy; Click the icon of the front panel (top right) and show connector, click which control/indicator goes where. Done. That's your functions declaration.
Basically one function is one VI, although you might want to split it even further, dont create 3k*3k pixel diagrams.
Depending on the amount of calculations done in your If-Thens they might be sub vi's of their own.
/Y
LabVIEW 8.2 - 2014
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
G# - Free award winning reference based OOP for LV

Best practices for setting up users on a small office network?

Hello,
I am setting up a small office and am wondering what the best practices/steps are to setup/manage the admin, user logins and sharing privileges for the below setup:
Users: 5 users on new iMacs (x3) and upgraded G4s (x2)
Video Editing Suite: Want to connect a new iMac and a Mac Pro, on an open login (multiple users)
All machines are to be able to connect to the network, peripherals and external hard drive. Also, I would like to setup drop boxes as well to easily share files between the computers (I was thinking of using the external harddrive for this).
Thank you,

Hi,
Thanks for your posting.
When you install AD DS in the hub or staging site, disconnect the installed domain controller, and then ship the computer to the remote site, you are disconnecting a viable domain controller from the replication topology.
For more and detail information, please refer to:
Best Practices for Adding Domain Controllers in Remote Sites
http://technet.microsoft.com/en-us/library/cc794962(v=ws.10).aspx
Regards.
Vivian Wang

Best Practice for multivalued parameters in *QL

Similar Messages

Maybe you are looking for