jsr

Hello everyone. We develop j2me application with still images capture capability. Well the appliction is almost finished and uses both JSR 135 and JSR 234. I have a phone K850 which is JP-8 that supports JSR 234 badly. 1) CameraControl getSupportedStillResolutions() returns single resolution - 640x480 which is rather depressing since K850 has 5megapixel camera.2) When trying SnapshotListener start(1) (trying to shoot ONE image) screen is getting black and there is no way to turn it back on. Pressing hangup button and closing j2me application completely works thought. I have W850 phone which is JP-7 phone and JSR 234 works perfectly there so is it a bug or JP-8 phones implement jsr 234 differently than JP-7 phones regarding camera resolutions and so on? I've found answer to the 2-nd part of my question myself. When shooting photo events that are supplied to PlayerListener interface are invoked from separate thread. On W850 device this thread terminates upon event delivery and on K850 it doesn't. The reason of the bug was MY code. I was expecting that event thread will terminate eventually and used Thread join to wait for it's termination forever. Why this thread lives upon event delivery ? I don't know but this behavior is unspecified in JSR34 anyway so this is not a bug. The fist part of the question still stands. I'm getting only one resolution from JSR 234:int [] resolutions = camCtl getSupportedStillResolutions();after that resolutions length == 2 that means there is only one resolution available resolutions[0] =640 resolutions[1] = 480 so that means only 640X480 is supported. And phone has 5 megapixel camera!!!

Forex Groups - Tips on Trading

Related article:
http://developer.sonyericsson.com/thread.jspa?messageID=110550&tstart=0#110550

comments | Add comment | Report as Spam

It is very often the case that portal users wonder where all the remove / open-source JSR 168 portlets are. After all there is an abundance of portlets for other non-JSR 168 portals (NetVibes and explore come to mind). So what is different in the world of JSR 168 compliant portals?First let's look at portlets bundled with the different JSR 168 portals. After all the number of bundled portlets is (quite astonishingly to me) often used as a selling point for portals. This makes some sense: you want your users to hit the ground running and deploy a portal that does interesting stuff out of the box. The interesting part of it is central to the issue though. Interesting means different things to different users and that's where things start to get complicated... For portals such as NetVibes. Google or Yahoo (which was the first historically) which I call aggregation-oriented portals developing useful portlets is not usually a contend in the sense that users of these portals are not interested in integrating complex services but rather in aggregating information that's usually available as web pages/services. A bit of HTML some javascript a well-crafted API and you're on your way. JSR 168 compliant portals on the other hand usually target business users that have to deal with integration of disparate web applications to provide a unified interface to their users who in all likelihood ordain depend on these services to do their job. Now this is not to say that JSR 168 portals cannot or shouldn't be used as aggregation-oriented portals but the fact is that the user community for such use of JSR 168 portals is quite small compared to business deployments. Interesting in this enterprise context means something quite an order (if not more) of magnitude more complex than aggregating content which won't be missed much if not available... And to me that's the biggest reason why we don't see a more striving marketplace for JSR 168 portlets. The ones that are developed are never seen because they don't make any comprehend outside of the context for which they were developed as they are so tightly bound to the enterprise services they interact with. Sure for some of these portlets some effort could be spent on writing them in a more generic way so that they can be reused by other populate but how often do developers have the latitude/measure to pay on extra-curriculum activities as these while working on mission-critical projects?The argument could also be made that portal developers.

Forex Groups - Tips on Trading

Related article:
http://blog.jboss-portal.org/2007/10/open-source-jsr-168-portlets-or-lack.html

comments | Add comment | Report as Spam

Hello everyone. We develop j2me application with comfort images capture capability. Well the appliction is almost finished and uses both JSR 135 and JSR 234. I undergo a phone K850 which is JP-8 that supports JSR 234 badly. 1) CameraControl getSupportedStillResolutions() returns single resolution - 640x480 which is rather depressing since K850 has 5megapixel camera.2) When trying SnapshotListener start(1) (trying to injure ONE image) screen is getting black and there is no way to turn it approve on. Pressing hangup add and closing j2me application completely works thought. I undergo W850 phone which is JP-7 phone and JSR 234 works perfectly there so is it a bug or JP-8 phones implement jsr 234 differently than JP-7 phones regarding camera resolutions and so on? I've open answer to the 2-nd move of my challenge myself. When shooting photo events that are supplied to PlayerListener interface are invoked from separate thread. On W850 device this thread terminates upon event delivery and on K850 it doesn't. The reason of the bug was MY code. I was expecting that event thread ordain alter eventually and used Thread join to act for it's termination forever. Why this go lives upon event delivery ? I don't know but this behavior is unspecified in JSR34 anyway so this is not a bug. The fist move of the question comfort stands. I'm getting only one resolution from JSR 234:int [] resolutions = camCtl getSupportedStillResolutions();after that resolutions length == 2 that means there is only one resolution available resolutions[0] =640 resolutions[1] = 480 so that means only 640X480 is supported. And phone has 5 megapixel camera!!!

Forex Groups - Tips on Trading

Related article:
http://developer.sonyericsson.com/thread.jspa?messageID=110381&tstart=0#110381

comments | Add comment | Report as Spam

Hi there. Im searching for a some kind of JSR 82 library which we could just include in our J2ME project based on MIDP 2.0. Basically we just want to include the library into the communicate create it and it should be able to find other devices and send data to them on our request. We are not sure if we have the time to create such a library from scratch so any advice or links would be really appreciated. Anyone experience an already written library? Someone must have already written a framework for it. :)Thanks. I'm more looking for a what to say a framework/package. Basically we are looking for some sort of library/classes that is an implementation of JRS 82. You should just consider the package into your J2ME project and - voila! - you have Bluetooth give in your midlet :)I've tried to search the web for this. Someone somewhere must undergo written an implementation of JSR 82. Either as free or commercial. Just as there are. loads of FTP frameworks for J2SE or SMTP. We don't really want to create by mental act the go around again :)So if anyone at all knows something like this. I would appreciate any comments :)

Forex Groups - Tips on Trading

Related article:
http://forum.java.sun.com/thread.jspa?threadID=5233377

comments | Add comment | Report as Spam

Hi there. Im searching for a some kind of JSR 82 library which we could just include in our J2ME communicate based on MIDP 2.0. Basically we just want to include the library into the project create it and it should be able to sight other devices and displace data to them on our request. We are not sure if we have the measure to create such a library from scratch so any advice or links would be really appreciated. Anyone experience an already written library? Someone must have already written a framework for it. :)Thanks. I'm more looking for a what to say a framework/case. Basically we are looking for some sort of library/classes that is an implementation of JRS 82. You should just consider the package into your J2ME project and - voila! - you undergo Bluetooth support in your midlet :)I've tried to search the web for this. Someone somewhere must have written an implementation of JSR 82. Either as free or commercial. Just as there are. loads of FTP frameworks for J2SE or SMTP. We don't really want to invent the wheel again :)So if anyone at all knows something like this. I would appreciate any comments :)

Forex Groups - Tips on Trading

Related article:
http://forum.java.sun.com/thread.jspa?threadID=5233377

comments | Add comment | Report as Spam

Hi there. Im searching for a some kind of JSR 82 library which we could just include in our J2ME communicate based on MIDP 2.0. Basically we just be to include the library into the communicate create it and it should be able to find other devices and send data to them on our request. We are not sure if we undergo the measure to develop such a library from scratch so any advice or links would be really appreciated. Anyone know an already written library? Someone must undergo already written a framework for it. :)Thanks. I'm more looking for a what to say a framework/case. Basically we are looking for some sort of library/classes that is an implementation of JRS 82. You should just include the case into your J2ME project and - voila! - you have Bluetooth support in your midlet :)I've tried to search the web for this. Someone somewhere must have written an implementation of JSR 82. Either as remove or commercial. Just as there are. loads of FTP frameworks for J2SE or SMTP. We don't really be to invent the wheel again :)So if anyone at all knows something like this. I would appreciate any comments :)

Forex Groups - Tips on Trading

Related article:
http://forum.java.sun.com/thread.jspa?threadID=5233377

comments | Add comment | Report as Spam

JSR-170 the Java Content Repository Standard is being introduced in Sakai scheduled for availability in Sakai 2.6. This presentation will communicate the community of develop that has been made in this area review the available JSR-170 providers and present the roadmap for this crucial area of Sakai. Session leaders are encouraged to post their podcasts on the main Newport Beach Podcasts page (a central repository of podcasts) and may also choose to link to them from their session page. See the main Newport Beach conference wiki page for more details. Participants and Session Leaders are encouraged to post Comments (see Comment form below) or act additional Pages as needed to facilitate collaboration (see Add Page cerebrate come top-right.)

Forex Groups - Tips on Trading

Related article:
http://confluence.sakaiproject.org/confluence/display/CONF08/JSR-170+Content+Hosting

comments | Add comment | Report as Spam