Core logic of annotation in EJB3.0

Hi,
How does the container implement the core logic of annotation and identify the Stateless or Stateful Beans and dedicate the pool objects to these.
I have studied on annotations, but my doubt is that how annotations are used at runtime, which are substitute of deployment descriptors.

Basically, the container opens up the ejb jar file and looks through all the classes for those with the relevant annotations. it then uses the annotations to determine what needs to be setup for the EJBs.

Similar Messages

Groove 3 Logic 9 explained V'S Logic 9 101: Core Logic 9

Hello all, I am new to Logic; I am a long time cubase & pc user.
I have my hardware set up getting along nicely with my new DAW.
However I would like to get the most out of Logic;
I am going to buy a tutorial DVD, just wondering if anyone can give recommendation on a choice between these two; Groove 3 Logic 9 explained & Logic 9 101: Core Logic 9?
Groove offer 2 releases Logic 9 explained, tips & Logic 9 Tips & Tricks Vol 1, do really need 2? Or is most of this covered in one of a competitor’s company’s tutorial?
Macpro video offer one; Logic 9 101: Core Logic 9
I would prefer to buy just one, which would I get the most out of?
Though if you think 2 would be better I would look into it.
Cheers
Message was edited by: bhc303

Hi
macprovideo have more than one Logic tutorial! I Think they have got easily the most extensive list you will find.
http://www.macprovideo.com/tutorials/logic
Go for the Core Logic 9 first.
Then you will start to know what else you need. Forums like this will help with any questions too. I consider myself an experienced Logic user and I learned a lot from all the macprovideo tutorials.
JG

Help: No more midi core -Logic Studio 8

Hi all,
I run a very simple set up, my imac and an Mbox 2 to do standard home recording via Logic Studio.
2 weeks ago, I upgraded to Snow Leopard and today was the first day that I opened logic.
It came up with some error message saying I needed to get some update from PACE.... Instinctively I cancelled the pop-up and since then when I try to run logic, I have no midi-core process running in the background and as such, cant record using my midi interface....
Is there anything I can do?

Hi all,
I run a very simple set up, my imac and an Mbox 2 to do standard home recording via Logic Studio.
2 weeks ago, I upgraded to Snow Leopard and today was the first day that I opened logic.
It came up with some error message saying I needed to get some update from PACE.... Instinctively I cancelled the pop-up and since then when I try to run logic, I have no midi-core process running in the background and as such, cant record using my midi interface....
Is there anything I can do?

Configure Weblogic-specific settings using annotations in EJB3?

Hello.
Something that really bothers me about using EJB3 in Weblogic is that, in our projects (running in Weblogic 10.0), we need to configure Weblogic-specific settings in weblogic-ejb-jar.xml anyway. Things like work managers, JNDI names and security (the latter doesn't work if we just declare it in a spec annotation, we need to also define it in weblogic-ejb-jar.xml).
It's hard to understand the point of migrating to EJB3 when you can just do half the things using annotations.
Does Weblogic have extensions to help on that? I never found anything related to this for Weblogic 10.0.
Thanks.

The link is interesting, thanks. There are only a few weblogic-specific annotations, but at least it's a start. Unfortunately, it seems to only be available in 10.3.
About EJBGen, from what I investigated in the past, it would only work well with EJB2 (to generate the weblogic-ejb-jar content, you also have to use EJB2 annotations that were deprecated by EJB3 annotations - if you do this, you will end up with spaghetti code, in my humble opinion).
Regards,

Problems with @namedquery annotation with EJB3.0

Hi,
I want to use multiple EJB @namedquery annotation in for an entity bean, but I am getting the following error:
Error(30): duplicate annotation
when I compile this file:
@Entity
@Table(name = "PLAYER")
@NamedQuery(name = "findPlayerById",
queryString = "SELECT OBJECT(player) FROM Player player WHERE player.id = :id")
@NamedQuery(name = "findPlayerByFirstname",
queryString = "SELECT OBJECT(player) FROM Player player WHERE player.firstname = :firstname")
public class Player implements Serializable
In the EJB specification there is nothing said about the impossibillity to use multiple named queries in one entity file. So is this not possible in Oracle implementation? or..
is this still a bug in jdev 10.1.3.0.1 ...?
- Tom

Add the @NamedQuery annotations to the @NamedQueries annotation.
@NamedQueries({@NamedQuery(name = "findPlayerById",
queryString = "SELECT OBJECT(player) FROM Player player WHERE player.id = :id"),
@NamedQuery(name = "findPlayerByFirstname",
queryString = "SELECT OBJECT(player) FROM Player player WHERE player.firstname = :firstname")
})

Logic bounces won't open in Sound Studio

Properly speaking, this is a Sound Studio (2.0.7) problem, but as I've used it for many months (and would like to continue) for minor tweaking of bounced Logic AIFs, I'm hoping someone will have some idea as to what's going on here.
Since I got my G4 iBook back with a new 100GB HD, 7200 rpm, Sound Studio now crashes when trying to open Logic's AIF bounces. The Logic AIFs open fine and play in iTunes, QuickTime, and RealPlayer, no problem, which also rules out problems with my system audio prefs -- doesn't it?
SS will open and play other AIFs that it always has, BUT even while I see its SPL tracking the waveform, I get no audible playback (via iBook internal audio/headphones)!
At a loss for anything else, I've repaired permissions and rebooted, several times. I've chanted, burned incense, fine-tuned my feng shui. No improvement.
Anyone have any suggestions?
iBook G4, iMac Intel Duo Core, Logic Pro 7.2.3 Mac OS X (10.4.9)

First, make sure your audio file matches the sampling
rate and bit depth that Sound Studio requires.
Haven't found any documentation yet of what they require. Thing is, it all worked fine before. I did trash the two SS .plists and reboot — no help.
If that's not the problem then try opening your .aiff
in QT and exporting it as a new file... see if SS
will accept that.
Very helpful. Having tried QT's "Save As" and finding only .mov options, I'd overlooked the EXPORT command, which did offer Sound as AIFF. That worked, partly — it yielded an inexplicably overamplified AIFF — significantly distorted, even to my amateur ears. And I still want to get back to the one-step direct route. But this is progress. I'll keep working with this. Thanks much!

Logic quits after time compression/expansion

Logic Pro 8 quits EVERY TIME after I use a time compression/expansion plug-in in the sample editor. It does not matter if I use Logic's own plug-in or if I use Serato Pitch 'n Time LE. I am currently spending all my time in core audio as opposed to DAE/TDM land. Anyone else have this issue?
Mark Miller

I used to be hard core Logic only, and then I noticed something (this may seem off topic but I'm getting around to the point). For the first time, probably about 2 or 3 years ago, Digidesign got off their laurels and realized that other software platforms were taking legitimate shots at their "industry standard."
That's when you saw instrument tracks implemented - that's when you saw better (but still far from the quality of Logic) MIDI implementation. . . that's when the Digidesign AIR group was created. . . that's when Digi added the dynamic transport, flexible track resizing, screen sets, included software instruments.
As a whole, Pro Tools still does not give you the abilities out of the box that Logic does. However, whatever gap Logic 8 closed between itself and Pro Tools with audio editing, Digi widened even further than before with the introduction of elastic time. That's when I finally realized that Pro Tools, a great editor, tracking, and mixing machine, finally realized that its throne was threatened and went to defend it. My work used to primarily take place in Logic, however, that has switched. I probably do 60-80% of my work now in PT and still use Logic for mixing and such. For whatever reason I just like it better. . . I"m sure that will change over too. All pro tools has to do is implement a Logic-esque MIDI editor and I'm not sure I'd have any reason to stay with Logic. Digi has really stepped up to the plate in a time where it has looked like Logic has stepped up, and then done nothing to stay up.
All that to say if you want good timestretching, right now PT is just about the only way to go.

Logic Time Compression/Expansion vs. WAVES SoundShifter

I'm considering upgrading my WAVES Platinum to the Diamond, largely because of the SoundShifter plug-in. Does anybody have any experience with the WAVES SoundShifter plug-in? Is it significantly better than what is already included in Logic 8?
Thanks!
M

I used to be hard core Logic only, and then I noticed something (this may seem off topic but I'm getting around to the point). For the first time, probably about 2 or 3 years ago, Digidesign got off their laurels and realized that other software platforms were taking legitimate shots at their "industry standard."
That's when you saw instrument tracks implemented - that's when you saw better (but still far from the quality of Logic) MIDI implementation. . . that's when the Digidesign AIR group was created. . . that's when Digi added the dynamic transport, flexible track resizing, screen sets, included software instruments.
As a whole, Pro Tools still does not give you the abilities out of the box that Logic does. However, whatever gap Logic 8 closed between itself and Pro Tools with audio editing, Digi widened even further than before with the introduction of elastic time. That's when I finally realized that Pro Tools, a great editor, tracking, and mixing machine, finally realized that its throne was threatened and went to defend it. My work used to primarily take place in Logic, however, that has switched. I probably do 60-80% of my work now in PT and still use Logic for mixing and such. For whatever reason I just like it better. . . I"m sure that will change over too. All pro tools has to do is implement a Logic-esque MIDI editor and I'm not sure I'd have any reason to stay with Logic. Digi has really stepped up to the plate in a time where it has looked like Logic has stepped up, and then done nothing to stay up.
All that to say if you want good timestretching, right now PT is just about the only way to go.

Quad G5 Logic Pro Users

I've been following this forum for a few weeks, and I've seen several users demanding better optimization for Quad G5.
I wonder what they think needs improvement specifically for the Quad?
I just got my Quad 2.5 G5 a couple days ago. I've installed Logic Pro 7.1.1, and I've been doing some testing. From what I've seen, using Activity Monitor and the CHUD CPU preference panel (for enabling/disabling cores), Logic Pro is distributing the load across the 4 cores quite effectively.
My tests have definitely not been comprehensive. I haven't gotten around to trying audio tracks, but using a bunch of Logic Instruments (EXS24, Sculpture) and Space Designer, I see what we'd call in software engineering 'good load balancing' as I disable/enable CPUs.
I'm not saying (yet) that those who've compained about Logic on the Quad are wrong, but I'm wondering what they're doing, and how they're monitoring it?
Or is it all just about Logic still being a 32-bit app, with limited memory available per process? That's an issue which would apply to all G5's, not just Quads.
Quad G5 2.5Ghz, 2.5GB, PB 15" 1.5Ghz,80G,1.5G Mac OS X (10.4.4)

You don't need to install CHUD, Activity Monitor is enough. CHUD's Processor Palette and CPU switches just let me confirm what I'd been seeing.
Logic not showing 4 meters would be a bug, but doesn't mean it doesn't know how to use 4 processors.
Yes, Activity Monitor is showing all the computer's processes, but if you watch it enough, you'll realize there isn't much else going on. Logic is definitely running on all cores.
I've spent the last 8 years writing server code to run on Sun servers, much of it multi-threaded. I'm pretty good at interpreting CPU load statistics.
Watch an idle multi-proc Mac on Activity Monitor. You'll notice an occasional blip on the CPUs. Now run Logic, and watch activity monitor on a quad, and subtract (in your mind) the little blips that you know are the OS, and you'll see what I mean.
Anyway, I'd say Logic Pro 7.1.1 is definitely using all four processors. Whether there are cases where they could be used better, I don't know. But they're definitely not sitting idle when using Logic's virtual instruments.
Quad G5 2.5Ghz, 2.5GB, PB 15" 1.5Ghz,80G,1.5G Mac OS X (10.4.4)

REQUEST: GFX Card temp control for Core Center

Hi !
I'm using both MSI Mainboard and GFX card, 875P Neo MP (using P4 3.2 GHz Prescott) and GF6800 Ultra AGP GFX card.
I got processor/ northbridge and GFX card watercooled.
I got one problem however, I currently am controlling the fans for the radiator with the fan control for the processor since I sometimes use processor more than GFX card, but I may have to change it to the GFX card fan controller since this also gets hottest some of the time...
I would love if there was possible to add the function to Core Center that would show the GFX card temperature, and then set the fan speed according to the greatest temperature of the GFX/CPU temperatures.
Or if it is easier, if there is a program that can do this allready made, a link to it would be nice
Thanx
Regards
Flaps

There is no thing as system/case temp sensor on theese mobos.Only cpu & nv-chipset .
The temperature you see in corecenter as systemp is actually the nvidia chipset temperature .
Northbridge memory functions is taken over by the athlon 64 , thats why MSI finds it more reasonable to display
the nv-chip temp as systemp (remember that corecenter is an allround app for all msi mobos) .
Rest of the nb/sb functions are implemented as a single chip solution in the nvidia chipset chip.
So the traditional nb/sb solution is no longer existing.
The Athlon 64 and Athlon 64 FX each features its own integrated memory controller—single-channel for the Athlon 64 and dual-channel for the Athlon 64 FX. Instead of connecting to a traditional northbridge, these CPUs connect to a video card through a HyperTransport Graphics Tunnel. Data intended for components like PCI cards, disk drives, and USB peripherals is then routed through a HyperTransport I/O Hub, which is embedded in the core logic chip.
http://www.techworthy.com/PCUpgrade/NovDec2003/Athlon-64.htm?Page=5

JESD204B PHY missing DRP data port in "shared logic in example design" mode

Hi,
I have a JESD204B design with the PHY and core logic split. In addition, the PHY is *also* configured not to include common logic in the generated core. In practice, this means my RTL directly instantiates three blocks:
- the JESD204B core,
- the JESD204B PHY core, and
- the GTE2_COMMON core.
My purpose for splitting the GTE2_COMMON core out of the PHY is to debug a PLL reset issue -- my first question is: Are there known issues with the JESD204B IP failing to reset the QPLL? My system-level reset triggers rx_reset on the JESD204B core, but it does not appear to reset the QPLL.
My second question follows. The JESD204B PHY core includes a number of ports to drive DRP on the GTE2_COMMON core:
common0_drpaddr : OUT STD_LOGIC_VECTOR(7 DOWNTO 0);
common0_drpen : OUT STD_LOGIC;
common0_drpdo : IN STD_LOGIC_VECTOR(15 DOWNTO 0);
common0_drpwe : OUT STD_LOGIC;
common0_drprdy : IN STD_LOGIC;
However, I don't see a common0_drpdi port here to write data from the PHY to the DRP interface. It's odd that the write *enable* is present when the data itself isn't. Is this a flaw in the core, or am I missing something? Has the JESD204B IP been validated in this mode (separate PHY, separate GTE2_COMMON, using the QPLL, and including an AXI management bus)?
thanks,
Graeme

Hi Duncan,
Thanks for the response -- my first cut at this RTL connected *both* tx_reset_gt and rx_reset_gt on the PHY to the JESD204B core's rx_reset_gt output. In other words, a reset from the JESD204B core should have created both TX and RX resets in the PHY. It didn't appear to trigger QPLL resets that way. (This is how the example design is hooked up, too.)
I've traced the reset path through the PHY in Vivado's schematic viewer, and it does look like these resets play a role in QPLL resets -- though not an obvious role, and perhaps only during post-configuration initialization.
After some thought, it seems debateable whether tx_reset_gt or rx_reset_gt should be issuing QPLL resets at all. If the current behaviour is deliberate, I'd be content to toggle the QPLL power-down register for now. (I suspect the failure of the QPLL to lock reliably is due to my test set-up, and won't be present on production hardware anyhow.)
At any rate, I'd love to hear from Xilinx (1) if these reset signals can be used to trigger QPLL resets, and (2) if the JESD204B PHY is missing a DRP signal. (If so, I'd love to get that DRP port fixed in the next Vivado release or two.)
cheers,
Graeme

Snap is flakey in Logic X

Is anyone else having this? I have been a hard core logic user for 15 years, and I understand the various snap functions perfectly. i have used them every day.
But suddenly the snap seems much more rubbery. it wants to snap to absolute value when relative value is clearly checked. This used to be rock solid. And sometimes it wants to snap to a different time when i am just moving vertically, with the one direction option clearly chosen
What gives??

Hi cris2121, assuming you're using a mouse from apple, go to >System Preferences<
it's here where one can configure a mouse device.
Additionally you can also configure Scrubbing in Logic: "When in scrub mode, you can slowly move the playhead in the Tracks Window and the Audio (and optional MIDI) will be played back. The playback speed depends on how fast you move the Playhead in either direction."
Have a nice day!

How to balance core useage for vsti instruments

I have read the Apple bulletin on this but was unable to duplicate it successfully. I would like to create a template for live use where I can load up Omnisphere and Trillian (or Stylus, or....) and each use their own core.
I noticed that Logic would just use a single core for all the loaded instruments (one suggested that Logic would automatically balance which it didn't). I tried rerouting the instances to their own buses (using the Apple support page technique)- but it didn't work either.
Is this possible- as I would like an option to maximize core useage in live situations and avoide the dreaded zipper effect when it maxes a single core.

Logic handles the core distribution, based on a combination of things. You cannot choose which core to run which channel strip on.
Anything in Live mode will be forced to run on one core - if you are playing all those instruments at once, they will all be in live mode and therefore bunged together according to how Logic wants to handle things.
if you aren't playing them all together, it doesn't matter which core they are running on so much as only the instrument you are playing is using a core.
For Live situations, does Mainstage handle this better? I would assume it's pretty much the same as Logic as it uses the same audio engine, but you never know, as it's optimised to playing multiple instruments together...

Core Center wont show NB temp on K8N Neo2 Platinum

Is it just me or does core center not show my north bridge temp? i can control the fan speeds for the cpu and nb and it shows my cpu and system temp, but under my nb temp it doesn't show anything.
Is it because the board doesn't have a sensor for the north bridge? or is core center just screwing up??

There is no thing as system/case temp sensor on theese mobos.Only cpu & nv-chipset .
The temperature you see in corecenter as systemp is actually the nvidia chipset temperature .
Northbridge memory functions is taken over by the athlon 64 , thats why MSI finds it more reasonable to display
the nv-chip temp as systemp (remember that corecenter is an allround app for all msi mobos) .
Rest of the nb/sb functions are implemented as a single chip solution in the nvidia chipset chip.
So the traditional nb/sb solution is no longer existing.
The Athlon 64 and Athlon 64 FX each features its own integrated memory controller—single-channel for the Athlon 64 and dual-channel for the Athlon 64 FX. Instead of connecting to a traditional northbridge, these CPUs connect to a video card through a HyperTransport Graphics Tunnel. Data intended for components like PCI cards, disk drives, and USB peripherals is then routed through a HyperTransport I/O Hub, which is embedded in the core logic chip.
http://www.techworthy.com/PCUpgrade/NovDec2003/Athlon-64.htm?Page=5

Adobe AIR runtime update dialog breaks application

I'm working on a large project that utilizes a C++ application to house the core logic and an AIR application to display a UI. The C++ program launches the AIR UI and passes it several command line parameters, including locale and port number to call back to the C++ application with. Under normal circumstances, this works great.
However, when there's an Adobe AIR runtime update, things go bad. The runtime intercepts the UI invocation, kills it, and displays the generic AIR "do you want to update?" dialog. Whether the user presses update or cancel, the UI application eventually gets relaunched -- but without the command line parameters originally passed to it! I presume this is a bug in the Adobe AIR runtime updater code.
The end result of this is that the UI gets relaunched, but doesn't know how to localize itself or what port to call back to the C++ application with! If the user relaunches, it works fine (because the update dialog won't intercept again), but by then the user experience has already been mangled. We can't even display a localized error message to tell them to relaunch because we don't know what locale they're using any more, and we can't call back to the C++ application to ask.
I'm trying to find solutions/workarounds to this issue. Because AIR won't let us turn off the update check on a per-application basis, it seems like the only viable solution would be to turn off the runtime update check for the whole machine. But altering machines settings for the benefit of one application is definitely bad form, and I'd prefer not to do that if any other viable workaround exist.
Any ideas?

I filed a bug report last night using that same form.
The duplication steps are straightforward. I can duplicate the following with 100% success on a freshly imaged Win 7 32-bit box, admin user account:
1) Install older version of Adobe AIR framework (I tried both 1.1 and 1.5.1). It will ask you to update. Click "Update later".
2) Pull up task manager and watch the process list
3) Run ANY Adobe AIR app with some parameters (I used Adobe's Settings Manager as a sample because it's small)
4) Note that your application appears in the task manager briefly
5) Your app is terminated and "Adobe Air Installer.exe" appears in the task manager. A dialog pops up asking you to update.
6) Click cancel
7) Your app is reinvoked without any parameters
As for my specific case, by "session" I do mean a single launch.
I'm not aware of an evoke event -- perhaps you meant invoke event? The invoke event is not executing before the app terminates (in step 5 above). I think the AIR app is just running long enough to load the runtime and then the runtime takes over from there.
Thanks...

Core logic of annotation in EJB3.0

Similar Messages

Maybe you are looking for