It seems likely that many JDeveloper users would prefer to have redeploys work fast out-of-the-box without having to apply workarounds.
For this, Oracle has bug/ER 12796317, "SPEED UP ADF BC REDEPLOYMENT BY CALLING FORCED SHUTDOWN OF WLS DATASOURCE", filed. Find more details at http://java.net/jira/browse/ADFEMG-49
Workarounds can be applied, but this is about improving the out-of-the-box behaviour. Not sure if it will make a difference, but if you leave a comment in JIRA issue ADFEMG-49 maybe the number of responses can help get this fixed.
On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken wrote:
> hi
> It seems likely that many JDeveloper users would prefer to have redeploys > work fast out-of-the-box without having to apply workarounds.
> For this, Oracle has bug/ER 12796317, "SPEED UP ADF BC REDEPLOYMENT BY > CALLING FORCED SHUTDOWN OF WLS DATASOURCE", filed. > Find more details at http://java.net/jira/browse/ADFEMG-49
> Workarounds can be applied, but this is about improving the out-of-the-box > behaviour. > Not sure if it will make a difference, but if you leave a comment in JIRA > issue ADFEMG-49 maybe the number of responses can help get this fixed.
As a JDeveloper user, if I were to choose between a fast and a slow
redeployment, I would choose a third option: no redeployment.
We were using for some time WLS Fast Swap, but we are currently evaluating
JRebel and after one week of using it, it looks good, so far.
I was able to create new view objects, drop them into pages as ADF
components, compile and refresh the page, without restarting the
application.
I must say that the compilation tends to become slower after some time.
On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <verv...@gmail.com> wrote:
> hi
> Given the lack of response, the idea that many JDeveloper users would
> prefer to have redeploys work fast out-of-the-box, could be wrong.
> It makes me wonder about how easily it is considered normal to have to
> apply workarounds, instead of expecting things to work better
> out-of-the-box.
> regards
> Jan Vervecken
> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken wrote:
>> hi
>> It seems likely that many JDeveloper users would prefer to have redeploys
>> work fast out-of-the-box without having to apply workarounds.
>> Workarounds can be applied, but this is about improving the
>> out-of-the-box behaviour.
>> Not sure if it will make a difference, but if you leave a comment in JIRA
>> issue ADFEMG-49 maybe the number of responses can help get this fixed.
>> many thanks
>> Jan Vervecken
> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
> Hi Jan,
> As a JDeveloper user, if I were to choose between a fast and a slow > redeployment, I would choose a third option: no redeployment. > We were using for some time WLS Fast Swap, but we are currently evaluating > JRebel and after one week of using it, it looks good, so far. > I was able to create new view objects, drop them into pages as ADF > components, compile and refresh the page, without restarting the > application. > I must say that the compilation tends to become slower after some time.
> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com<javascript:> > > wrote:
>> hi
>> Given the lack of response, the idea that many JDeveloper users would >> prefer to have redeploys work fast out-of-the-box, could be wrong.
>> It makes me wonder about how easily it is considered normal to have to >> apply workarounds, instead of expecting things to work better >> out-of-the-box.
>> regards >> Jan Vervecken
>> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken wrote:
>>> hi
>>> It seems likely that many JDeveloper users would prefer to have >>> redeploys work fast out-of-the-box without having to apply workarounds.
>>> Workarounds can be applied, but this is about improving the >>> out-of-the-box behaviour. >>> Not sure if it will make a difference, but if you leave a comment in >>> JIRA issue ADFEMG-49 maybe the number of responses can help get this fixed.
>>> many thanks >>> Jan Vervecken
>> -- >> You received this message because you are subscribed to the ADF >> Enterprise Methodology Group ( >> http://groups.google.com/group/adf-methodology). To unsubscribe send >> email to adf-methodolo...@googlegroups.com <javascript:>
On Sun, Sep 30, 2012 at 9:37 AM, Jan Vervecken <verv...@gmail.com> wrote:
> Thanks for your reply Florin Marcus.
> Thank you for suggesting another potential workaround to try to improve
> some of the out-of-the-box behaviour.
> regards
> Jan Vervecken
> On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
>> Hi Jan,
>> As a JDeveloper user, if I were to choose between a fast and a slow
>> redeployment, I would choose a third option: no redeployment.
>> We were using for some time WLS Fast Swap, but we are currently
>> evaluating JRebel and after one week of using it, it looks good, so far.
>> I was able to create new view objects, drop them into pages as ADF
>> components, compile and refresh the page, without restarting the
>> application.
>> I must say that the compilation tends to become slower after some time.
>> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com> wrote:
>>> hi
>>> Given the lack of response, the idea that many JDeveloper users would
>>> prefer to have redeploys work fast out-of-the-box, could be wrong.
>>> It makes me wonder about how easily it is considered normal to have to
>>> apply workarounds, instead of expecting things to work better
>>> out-of-the-box.
>>> regards
>>> Jan Vervecken
>>> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken wrote:
>>>> hi
>>>> It seems likely that many JDeveloper users would prefer to have
>>>> redeploys work fast out-of-the-box without having to apply workarounds.
>>>> Workarounds can be applied, but this is about improving the
>>>> out-of-the-box behaviour.
>>>> Not sure if it will make a difference, but if you leave a comment in
>>>> JIRA issue ADFEMG-49 maybe the number of responses can help get this fixed.
>> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
> Thank you for suggesting another potential workaround to try to improve
> some of the out-of-the-box behaviour.
> regards
> Jan Vervecken
> On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
>> Hi Jan,
>> As a JDeveloper user, if I were to choose between a fast and a slow
>> redeployment, I would choose a third option: no redeployment.
>> We were using for some time WLS Fast Swap, but we are currently
>> evaluating JRebel and after one week of using it, it looks good, so far.
>> I was able to create new view objects, drop them into pages as ADF
>> components, compile and refresh the page, without restarting the
>> application.
>> I must say that the compilation tends to become slower after some time.
>> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com> wrote:
>>> hi
>>> Given the lack of response, the idea that many JDeveloper users would
>>> prefer to have redeploys work fast out-of-the-box, could be wrong.
>>> It makes me wonder about how easily it is considered normal to have to
>>> apply workarounds, instead of expecting things to work better
>>> out-of-the-box.
>>> regards
>>> Jan Vervecken
>>> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken wrote:
>>>> hi
>>>> It seems likely that many JDeveloper users would prefer to have
>>>> redeploys work fast out-of-the-box without having to apply workarounds.
>>>> Workarounds can be applied, but this is about improving the
>>>> out-of-the-box behaviour.
>>>> Not sure if it will make a difference, but if you leave a comment in
>>>> JIRA issue ADFEMG-49 maybe the number of responses can help get this fixed.
>> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
On Sunday, September 30, 2012 7:42:04 PM UTC+2, Andrejus Baranovskis wrote:
> Hi Jan,
> To use JRebel is not a *workaround* :) I would call it rather another > approach of building ADF applications.
> Andrejus
> On 30 September 2012 19:37, Jan Vervecken <ver...@gmail.com <javascript:>>wrote:
>> Thanks for your reply Florin Marcus.
>> Thank you for suggesting another potential workaround to try to improve >> some of the out-of-the-box behaviour.
>> regards >> Jan Vervecken
>> On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
>>> Hi Jan,
>>> As a JDeveloper user, if I were to choose between a fast and a slow >>> redeployment, I would choose a third option: no redeployment. >>> We were using for some time WLS Fast Swap, but we are currently >>> evaluating JRebel and after one week of using it, it looks good, so far. >>> I was able to create new view objects, drop them into pages as ADF >>> components, compile and refresh the page, without restarting the >>> application. >>> I must say that the compilation tends to become slower after some time.
>>> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com> wrote:
>>>> hi
>>>> Given the lack of response, the idea that many JDeveloper users would >>>> prefer to have redeploys work fast out-of-the-box, could be wrong.
>>>> It makes me wonder about how easily it is considered normal to have to >>>> apply workarounds, instead of expecting things to work better >>>> out-of-the-box.
>>>> regards >>>> Jan Vervecken
>>>> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken wrote:
>>>>> hi
>>>>> It seems likely that many JDeveloper users would prefer to have >>>>> redeploys work fast out-of-the-box without having to apply workarounds.
>>>>> Workarounds can be applied, but this is about improving the >>>>> out-of-the-box behaviour. >>>>> Not sure if it will make a difference, but if you leave a comment in >>>>> JIRA issue ADFEMG-49 maybe the number of responses can help get this fixed.
>>> -- >> You received this message because you are subscribed to the ADF >> Enterprise Methodology Group ( >> http://groups.google.com/group/adf-methodology). To unsubscribe send >> email to adf-methodolo...@googlegroups.com <javascript:>
In the 11.1.2.* versions we now support hot-swap for ADF applications, which means that you can save-compile-reload in browser for most of your changes without the need for a redeployment.
One thing I'm wondering is whether people are using this new capability, and whether they find it useful as a way to reduce re-deployments?
> Indeed "another approach", but not out-of-the-box.
> regards
> Jan Vervecken
> On Sunday, September 30, 2012 7:42:04 PM UTC+2, Andrejus Baranovskis > wrote:
> Hi Jan,
> To use JRebel is not a *workaround* :) I would call it rather
> another approach of building ADF applications.
> Andrejus
> On 30 September 2012 19:37, Jan Vervecken <ver...@gmail.com
> <javascript:>> wrote:
> Thanks for your reply Florin Marcus.
> Thank you for suggesting another potential workaround to try
> to improve some of the out-of-the-box behaviour.
> regards
> Jan Vervecken
> On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus
> wrote:
> Hi Jan,
> As a JDeveloper user, if I were to choose between a fast
> and a slow redeployment, I would choose a third option: no
> redeployment.
> We were using for some time WLS Fast Swap, but we are
> currently evaluating JRebel and after one week of using
> it, it looks good, so far.
> I was able to create new view objects, drop them into
> pages as ADF components, compile and refresh the page,
> without restarting the application.
> I must say that the compilation tends to become slower
> after some time.
> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken
> <ver...@gmail.com> wrote:
> hi
> Given the lack of response, the idea that many
> JDeveloper users would prefer to have redeploys work
> fast out-of-the-box, could be wrong.
> It makes me wonder about how easily it is considered
> normal to have to apply workarounds, instead of
> expecting things to work better out-of-the-box.
> regards
> Jan Vervecken
> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan
> Vervecken wrote:
> hi
> It seems likely that many JDeveloper users would
> prefer to have redeploys work fast out-of-the-box
> without having to apply workarounds.
> Workarounds can be applied, but this is about
> improving the out-of-the-box behaviour.
> Not sure if it will make a difference, but if you
> leave a comment in JIRA issue ADFEMG-49 maybe the
> number of responses can help get this fixed.
> -- > You received this message because you are subscribed to the ADF > Enterprise Methodology Group > (http://groups.google.com/group/adf-methodology). To unsubscribe send > email to adf-methodology+unsubscribe@googlegroups.com
WLS Hot-Swap is definitely a good way of increasing productivity. This is
more obvious in the final phases of a project, when the team focuses more
on bug fixing and small improvements. In these phases, developers tend to
redeploy more often and redeployments are taking longer because the
application is fully featured by now . This is not limited to java files,
but can be used with page definitions as well.
It is worth mentioning though, class reloading is working as long as the
class signature is not changed.
> In the 11.1.2.* versions we now support hot-swap for ADF applications,
> which means that you can save-compile-reload in browser for most of your
> changes without the need for a redeployment.
> One thing I'm wondering is whether people are using this new capability,
> and whether they find it useful as a way to reduce re-deployments?
> Shay
> On 9/30/12 11:46 AM, Jan Vervecken wrote:
> Thanks for your reply Andrejus.
> Indeed "another approach", but not out-of-the-box.
> regards
> Jan Vervecken
> On Sunday, September 30, 2012 7:42:04 PM UTC+2, Andrejus Baranovskis
> wrote:
>> Hi Jan,
>> To use JRebel is not a *workaround* :) I would call it rather another
>> approach of building ADF applications.
>> Andrejus
>> On 30 September 2012 19:37, Jan Vervecken <ver...@gmail.com> wrote:
>>> Thanks for your reply Florin Marcus.
>>> Thank you for suggesting another potential workaround to try to improve
>>> some of the out-of-the-box behaviour.
>>> regards
>>> Jan Vervecken
>>> On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
>>>> Hi Jan,
>>>> As a JDeveloper user, if I were to choose between a fast and a slow
>>>> redeployment, I would choose a third option: no redeployment.
>>>> We were using for some time WLS Fast Swap, but we are currently
>>>> evaluating JRebel and after one week of using it, it looks good, so far.
>>>> I was able to create new view objects, drop them into pages as ADF
>>>> components, compile and refresh the page, without restarting the
>>>> application.
>>>> I must say that the compilation tends to become slower after some time.
>>>> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com>wrote:
>>>>> hi
>>>>> Given the lack of response, the idea that many JDeveloper users would
>>>>> prefer to have redeploys work fast out-of-the-box, could be wrong.
>>>>> It makes me wonder about how easily it is considered normal to have to
>>>>> apply workarounds, instead of expecting things to work better
>>>>> out-of-the-box.
>>>>> regards
>>>>> Jan Vervecken
>>>>> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken wrote:
>>>>>> hi
>>>>>> It seems likely that many JDeveloper users would prefer to have
>>>>>> redeploys work fast out-of-the-box without having to apply workarounds.
>>>>>> Workarounds can be applied, but this is about improving the
>>>>>> out-of-the-box behaviour.
>>>>>> Not sure if it will make a difference, but if you leave a comment in
>>>>>> JIRA issue ADFEMG-49 maybe the number of responses can help get this fixed.
> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
> In the 11.1.2.* versions we now support hot-swap for ADF applications,
> which means that you can save-compile-reload in browser for most of your
> changes without the need for a redeployment.
> One thing I'm wondering is whether people are using this new capability,
> and whether they find it useful as a way to reduce re-deployments?
> Shay
> On 9/30/12 11:46 AM, Jan Vervecken wrote:
> Thanks for your reply Andrejus.
> Indeed "another approach", but not out-of-the-box.
> regards
> Jan Vervecken
> On Sunday, September 30, 2012 7:42:04 PM UTC+2, Andrejus Baranovskis
> wrote:
>> Hi Jan,
>> To use JRebel is not a *workaround* :) I would call it rather another
>> approach of building ADF applications.
>> Andrejus
>> On 30 September 2012 19:37, Jan Vervecken <ver...@gmail.com> wrote:
>>> Thanks for your reply Florin Marcus.
>>> Thank you for suggesting another potential workaround to try to improve
>>> some of the out-of-the-box behaviour.
>>> regards
>>> Jan Vervecken
>>> On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
>>>> Hi Jan,
>>>> As a JDeveloper user, if I were to choose between a fast and a slow
>>>> redeployment, I would choose a third option: no redeployment.
>>>> We were using for some time WLS Fast Swap, but we are currently
>>>> evaluating JRebel and after one week of using it, it looks good, so far.
>>>> I was able to create new view objects, drop them into pages as ADF
>>>> components, compile and refresh the page, without restarting the
>>>> application.
>>>> I must say that the compilation tends to become slower after some time.
>>>> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com>wrote:
>>>>> hi
>>>>> Given the lack of response, the idea that many JDeveloper users would
>>>>> prefer to have redeploys work fast out-of-the-box, could be wrong.
>>>>> It makes me wonder about how easily it is considered normal to have to
>>>>> apply workarounds, instead of expecting things to work better
>>>>> out-of-the-box.
>>>>> regards
>>>>> Jan Vervecken
>>>>> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken wrote:
>>>>>> hi
>>>>>> It seems likely that many JDeveloper users would prefer to have
>>>>>> redeploys work fast out-of-the-box without having to apply workarounds.
>>>>>> Workarounds can be applied, but this is about improving the
>>>>>> out-of-the-box behaviour.
>>>>>> Not sure if it will make a difference, but if you leave a comment in
>>>>>> JIRA issue ADFEMG-49 maybe the number of responses can help get this fixed.
> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
I would appreciate , If Andrejus or Florin can post the instruction on how
to configure Jrebel on Jdeveeloper.
It seems companies has to be buy license.
Thanks, Hasim
On Sun, Sep 30, 2012 at 3:27 PM, Florin Marcus <florin.mar...@gmail.com>wrote:
> WLS Hot-Swap is definitely a good way of increasing productivity. This is
> more obvious in the final phases of a project, when the team focuses more
> on bug fixing and small improvements. In these phases, developers tend to
> redeploy more often and redeployments are taking longer because the
> application is fully featured by now . This is not limited to java files,
> but can be used with page definitions as well.
> It is worth mentioning though, class reloading is working as long as the
> class signature is not changed.
> On Sun, Sep 30, 2012 at 8:43 PM, Shay Shmeltzer <shay.shmelt...@oracle.com
> > wrote:
>> In the 11.1.2.* versions we now support hot-swap for ADF applications,
>> which means that you can save-compile-reload in browser for most of your
>> changes without the need for a redeployment.
>> One thing I'm wondering is whether people are using this new capability,
>> and whether they find it useful as a way to reduce re-deployments?
>> Shay
>> On 9/30/12 11:46 AM, Jan Vervecken wrote:
>> Thanks for your reply Andrejus.
>> Indeed "another approach", but not out-of-the-box.
>> regards
>> Jan Vervecken
>> On Sunday, September 30, 2012 7:42:04 PM UTC+2, Andrejus Baranovskis
>> wrote:
>>> Hi Jan,
>>> To use JRebel is not a *workaround* :) I would call it rather another
>>> approach of building ADF applications.
>>> Andrejus
>>> On 30 September 2012 19:37, Jan Vervecken <ver...@gmail.com> wrote:
>>>> Thanks for your reply Florin Marcus.
>>>> Thank you for suggesting another potential workaround to try to improve
>>>> some of the out-of-the-box behaviour.
>>>> regards
>>>> Jan Vervecken
>>>> On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
>>>>> Hi Jan,
>>>>> As a JDeveloper user, if I were to choose between a fast and a slow
>>>>> redeployment, I would choose a third option: no redeployment.
>>>>> We were using for some time WLS Fast Swap, but we are currently
>>>>> evaluating JRebel and after one week of using it, it looks good, so far.
>>>>> I was able to create new view objects, drop them into pages as ADF
>>>>> components, compile and refresh the page, without restarting the
>>>>> application.
>>>>> I must say that the compilation tends to become slower after some time.
>>>>> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com>wrote:
>>>>>> hi
>>>>>> Given the lack of response, the idea that many JDeveloper users would
>>>>>> prefer to have redeploys work fast out-of-the-box, could be wrong.
>>>>>> It makes me wonder about how easily it is considered normal to have
>>>>>> to apply workarounds, instead of expecting things to work better
>>>>>> out-of-the-box.
>>>>>> regards
>>>>>> Jan Vervecken
>>>>>> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken
>>>>>> wrote:
>>>>>>> hi
>>>>>>> It seems likely that many JDeveloper users would prefer to have
>>>>>>> redeploys work fast out-of-the-box without having to apply workarounds.
>>>>>>> Workarounds can be applied, but this is about improving the
>>>>>>> out-of-the-box behaviour.
>>>>>>> Not sure if it will make a difference, but if you leave a comment in
>>>>>>> JIRA issue ADFEMG-49 maybe the number of responses can help get this fixed.
>> --
>> You received this message because you are subscribed to the ADF
>> Enterprise Methodology Group (
>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>> email to adf-methodology+unsubscribe@googlegroups.com
>> --
>> You received this message because you are subscribed to the ADF
>> Enterprise Methodology Group (
>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>> email to adf-methodology+unsubscribe@googlegroups.com
> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
Additionally, your JVM running Integrated WLS should use the following
configuration:
-noverify -javaagent:C:/jrebel/jrebel.jar -Drebel.adf_core_plugin=true
-Drebel.adf_faces_plugin=true
Also, Hot Swap must be turned off when using JRebel.
On Mon, Oct 1, 2012 at 3:23 PM, hasim <hsai...@gmail.com> wrote:
> I would appreciate , If Andrejus or Florin can post the instruction on how
> to configure Jrebel on Jdeveeloper.
> It seems companies has to be buy license.
> Thanks, Hasim
> On Sun, Sep 30, 2012 at 3:27 PM, Florin Marcus <florin.mar...@gmail.com>wrote:
>> WLS Hot-Swap is definitely a good way of increasing productivity. This
>> is more obvious in the final phases of a project, when the team focuses
>> more on bug fixing and small improvements. In these phases, developers tend
>> to redeploy more often and redeployments are taking longer because the
>> application is fully featured by now . This is not limited to java files,
>> but can be used with page definitions as well.
>> It is worth mentioning though, class reloading is working as long as the
>> class signature is not changed.
>> On Sun, Sep 30, 2012 at 8:43 PM, Shay Shmeltzer <
>> shay.shmelt...@oracle.com> wrote:
>>> In the 11.1.2.* versions we now support hot-swap for ADF applications,
>>> which means that you can save-compile-reload in browser for most of your
>>> changes without the need for a redeployment.
>>> One thing I'm wondering is whether people are using this new capability,
>>> and whether they find it useful as a way to reduce re-deployments?
>>> Shay
>>> On 9/30/12 11:46 AM, Jan Vervecken wrote:
>>> Thanks for your reply Andrejus.
>>> Indeed "another approach", but not out-of-the-box.
>>> regards
>>> Jan Vervecken
>>> On Sunday, September 30, 2012 7:42:04 PM UTC+2, Andrejus Baranovskis
>>> wrote:
>>>> Hi Jan,
>>>> To use JRebel is not a *workaround* :) I would call it rather another
>>>> approach of building ADF applications.
>>>> Andrejus
>>>> On 30 September 2012 19:37, Jan Vervecken <ver...@gmail.com> wrote:
>>>>> Thanks for your reply Florin Marcus.
>>>>> Thank you for suggesting another potential workaround to try to
>>>>> improve some of the out-of-the-box behaviour.
>>>>> regards
>>>>> Jan Vervecken
>>>>> On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
>>>>>> Hi Jan,
>>>>>> As a JDeveloper user, if I were to choose between a fast and a slow
>>>>>> redeployment, I would choose a third option: no redeployment.
>>>>>> We were using for some time WLS Fast Swap, but we are currently
>>>>>> evaluating JRebel and after one week of using it, it looks good, so far.
>>>>>> I was able to create new view objects, drop them into pages as ADF
>>>>>> components, compile and refresh the page, without restarting the
>>>>>> application.
>>>>>> I must say that the compilation tends to become slower after some
>>>>>> time.
>>>>>> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com>wrote:
>>>>>>> hi
>>>>>>> Given the lack of response, the idea that many JDeveloper users
>>>>>>> would prefer to have redeploys work fast out-of-the-box, could be wrong.
>>>>>>> It makes me wonder about how easily it is considered normal to have
>>>>>>> to apply workarounds, instead of expecting things to work better
>>>>>>> out-of-the-box.
>>>>>>> regards
>>>>>>> Jan Vervecken
>>>>>>> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken
>>>>>>> wrote:
>>>>>>>> hi
>>>>>>>> It seems likely that many JDeveloper users would prefer to have
>>>>>>>> redeploys work fast out-of-the-box without having to apply workarounds.
>>>>>>>> Workarounds can be applied, but this is about improving the
>>>>>>>> out-of-the-box behaviour.
>>>>>>>> Not sure if it will make a difference, but if you leave a comment
>>>>>>>> in JIRA issue ADFEMG-49 maybe the number of responses can help get this
>>>>>>>> fixed.
>>>>>> --
>>>>> You received this message because you are subscribed to the ADF
>>>>> Enterprise Methodology Group (http://groups.google.com/** >>>>> group/adf-methodology <http://groups.google.com/group/adf-methodology>).
>>>>> To unsubscribe send email to adf-methodolo...@**googlegroups.com
>>> --
>>> You received this message because you are subscribed to the ADF
>>> Enterprise Methodology Group (
>>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>>> email to adf-methodology+unsubscribe@googlegroups.com
>>> --
>>> You received this message because you are subscribed to the ADF
>>> Enterprise Methodology Group (
>>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>>> email to adf-methodology+unsubscribe@googlegroups.com
>> --
>> You received this message because you are subscribed to the ADF
>> Enterprise Methodology Group (
>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>> email to adf-methodology+unsubscribe@googlegroups.com
> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
On Sunday, September 30, 2012 9:43:48 PM UTC+2, Shay Shmeltzer wrote:
> In the 11.1.2.* versions we now support hot-swap for ADF applications, > which means that you can save-compile-reload in browser for most of your > changes without the need for a redeployment.
> One thing I'm wondering is whether people are using this new capability, > and whether they find it useful as a way to reduce re-deployments?
> Shay
> On 9/30/12 11:46 AM, Jan Vervecken wrote:
> Thanks for your reply Andrejus.
> Indeed "another approach", but not out-of-the-box.
> regards
> Jan Vervecken
> On Sunday, September 30, 2012 7:42:04 PM UTC+2, Andrejus Baranovskis > wrote:
>> Hi Jan,
>> To use JRebel is not a *workaround* :) I would call it rather another >> approach of building ADF applications.
>> Andrejus
>> On 30 September 2012 19:37, Jan Vervecken <ver...@gmail.com> wrote:
>>> Thanks for your reply Florin Marcus.
>>> Thank you for suggesting another potential workaround to try to improve >>> some of the out-of-the-box behaviour.
>>> regards
>>> Jan Vervecken
>>> On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
>>>> Hi Jan,
>>>> As a JDeveloper user, if I were to choose between a fast and a slow >>>> redeployment, I would choose a third option: no redeployment.
>>>> We were using for some time WLS Fast Swap, but we are currently >>>> evaluating JRebel and after one week of using it, it looks good, so far.
>>>> I was able to create new view objects, drop them into pages as ADF >>>> components, compile and refresh the page, without restarting the >>>> application.
>>>> I must say that the compilation tends to become slower after some time.
>>>> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com>wrote:
>>>>> hi
>>>>> Given the lack of response, the idea that many JDeveloper users would >>>>> prefer to have redeploys work fast out-of-the-box, could be wrong.
>>>>> It makes me wonder about how easily it is considered normal to have to >>>>> apply workarounds, instead of expecting things to work better >>>>> out-of-the-box.
>>>>> regards
>>>>> Jan Vervecken
>>>>> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken wrote:
>>>>>> hi
>>>>>> It seems likely that many JDeveloper users would prefer to have >>>>>> redeploys work fast out-of-the-box without having to apply workarounds.
>>>>>> For this, Oracle has bug/ER 12796317, "SPEED UP ADF BC REDEPLOYMENT >>>>>> BY CALLING FORCED SHUTDOWN OF WLS DATASOURCE", filed.
>>>>>> Find more details at http://java.net/jira/browse/ADFEMG-49
>>>>>> Workarounds can be applied, but this is about improving the >>>>>> out-of-the-box behaviour.
>>>>>> Not sure if it will make a difference, but if you leave a comment in >>>>>> JIRA issue ADFEMG-49 maybe the number of responses can help get this fixed.
>>>>>> many thanks
>>>>>> Jan Vervecken
>>>>> -- >>>>> You received this message because you are subscribed to the ADF >>>>> Enterprise Methodology Group (
>>>>> http://groups.google.com/group/adf-methodology). To unsubscribe send >>>>> email to adf-methodolo...@googlegroups.com
>>>> -- >>> You received this message because you are subscribed to the ADF >>> Enterprise Methodology Group (
>>> http://groups.google.com/group/adf-methodology). To unsubscribe send >>> email to adf-methodolo...@googlegroups.com
> -- > You received this message because you are subscribed to the ADF Enterprise > Methodology Group (http://groups.google.com/group/adf-methodology). To > unsubscribe send email to adf-methodolo...@googlegroups.com <javascript:>
On Sep 30, 2012, at 9:44 AM, Jan Vervecken <verv...@gmail.com> wrote:
> Given the lack of response, the idea that many JDeveloper users would prefer to have redeploys work fast out-of-the-box, could be wrong.
> It makes me wonder about how easily it is considered normal to have to apply workarounds, instead of expecting things to work better out-of-the-box.
A couple 'cheats' for speeding up deployment/development:
1) One is actually not a redeployment issue - but a structural one. If you have Java classes / domain objects that can be 'separated' for testing, you can speed your development by using Test Driven Development techniques.
2) WebLogic startup/shutdown can be rather I/O heavy - so… a way to speed up WebLogic startups is to speed up I/O. I installed a dual SSD/HDD in my MacBook Pro recently - my WebLogic startup times are running from between 10-20 seconds, much better than the restart speeds that I had with the original 5200-rpm stock hard drive in the machine.
> Additionally, your JVM running Integrated WLS should use the following
> configuration:
> -noverify -javaagent:C:/jrebel/jrebel.jar -Drebel.adf_core_plugin=true
> -Drebel.adf_faces_plugin=true
> Also, Hot Swap must be turned off when using JRebel.
> On Mon, Oct 1, 2012 at 3:23 PM, hasim <hsai...@gmail.com> wrote:
>> I would appreciate , If Andrejus or Florin can post the instruction on
>> how to configure Jrebel on Jdeveeloper.
>> It seems companies has to be buy license.
>> Thanks, Hasim
>> On Sun, Sep 30, 2012 at 3:27 PM, Florin Marcus <florin.mar...@gmail.com>wrote:
>>> WLS Hot-Swap is definitely a good way of increasing productivity. This
>>> is more obvious in the final phases of a project, when the team focuses
>>> more on bug fixing and small improvements. In these phases, developers tend
>>> to redeploy more often and redeployments are taking longer because the
>>> application is fully featured by now . This is not limited to java files,
>>> but can be used with page definitions as well.
>>> It is worth mentioning though, class reloading is working as long as the
>>> class signature is not changed.
>>> On Sun, Sep 30, 2012 at 8:43 PM, Shay Shmeltzer <
>>> shay.shmelt...@oracle.com> wrote:
>>>> In the 11.1.2.* versions we now support hot-swap for ADF applications,
>>>> which means that you can save-compile-reload in browser for most of your
>>>> changes without the need for a redeployment.
>>>> One thing I'm wondering is whether people are using this new
>>>> capability, and whether they find it useful as a way to reduce
>>>> re-deployments?
>>>> Shay
>>>> On 9/30/12 11:46 AM, Jan Vervecken wrote:
>>>> Thanks for your reply Andrejus.
>>>> Indeed "another approach", but not out-of-the-box.
>>>> regards
>>>> Jan Vervecken
>>>> On Sunday, September 30, 2012 7:42:04 PM UTC+2, Andrejus Baranovskis
>>>> wrote:
>>>>> Hi Jan,
>>>>> To use JRebel is not a *workaround* :) I would call it rather
>>>>> another approach of building ADF applications.
>>>>> Andrejus
>>>>> On 30 September 2012 19:37, Jan Vervecken <ver...@gmail.com> wrote:
>>>>>> Thanks for your reply Florin Marcus.
>>>>>> Thank you for suggesting another potential workaround to try to
>>>>>> improve some of the out-of-the-box behaviour.
>>>>>> regards
>>>>>> Jan Vervecken
>>>>>> On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
>>>>>>> Hi Jan,
>>>>>>> As a JDeveloper user, if I were to choose between a fast and a
>>>>>>> slow redeployment, I would choose a third option: no redeployment.
>>>>>>> We were using for some time WLS Fast Swap, but we are currently
>>>>>>> evaluating JRebel and after one week of using it, it looks good, so far.
>>>>>>> I was able to create new view objects, drop them into pages as ADF
>>>>>>> components, compile and refresh the page, without restarting the
>>>>>>> application.
>>>>>>> I must say that the compilation tends to become slower after some
>>>>>>> time.
>>>>>>> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com>wrote:
>>>>>>>> hi
>>>>>>>> Given the lack of response, the idea that many JDeveloper users
>>>>>>>> would prefer to have redeploys work fast out-of-the-box, could be wrong.
>>>>>>>> It makes me wonder about how easily it is considered normal to have
>>>>>>>> to apply workarounds, instead of expecting things to work better
>>>>>>>> out-of-the-box.
>>>>>>>> regards
>>>>>>>> Jan Vervecken
>>>>>>>> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken
>>>>>>>> wrote:
>>>>>>>>> hi
>>>>>>>>> It seems likely that many JDeveloper users would prefer to have
>>>>>>>>> redeploys work fast out-of-the-box without having to apply workarounds.
>>>>>>>>> Workarounds can be applied, but this is about improving the
>>>>>>>>> out-of-the-box behaviour.
>>>>>>>>> Not sure if it will make a difference, but if you leave a comment
>>>>>>>>> in JIRA issue ADFEMG-49 maybe the number of responses can help get this
>>>>>>>>> fixed.
>>>>>>> --
>>>>>> You received this message because you are subscribed to the ADF
>>>>>> Enterprise Methodology Group (http://groups.google.com/** >>>>>> group/adf-methodology<http://groups.google.com/group/adf-methodology>).
>>>>>> To unsubscribe send email to adf-methodolo...@**googlegroups.com
>>>> --
>>>> You received this message because you are subscribed to the ADF
>>>> Enterprise Methodology Group (
>>>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>>>> email to adf-methodology+unsubscribe@googlegroups.com
>>>> --
>>>> You received this message because you are subscribed to the ADF
>>>> Enterprise Methodology Group (
>>>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>>>> email to adf-methodology+unsubscribe@googlegroups.com
>>> --
>>> You received this message because you are subscribed to the ADF
>>> Enterprise Methodology Group (
>>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>>> email to adf-methodology+unsubscribe@googlegroups.com
>> --
>> You received this message because you are subscribed to the ADF
>> Enterprise Methodology Group (
>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>> email to adf-methodology+unsubscribe@googlegroups.com
> --
> You received this message because you are subscribed to the ADF Enterprise
> Methodology Group (http://groups.google.com/group/adf-methodology). To
> unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
Recently, I was experimenting weblogic startup times with different JDK's
and found out that the best time I was able
to reach was around 30 seconds (Core i7 + 4GB) with JDK 1.6.35.
Do you guys get better times? Just for the server instance...
And a note about hot-swap, it does not work with 64-bit JVM's...
>> Additionally, your JVM running Integrated WLS should use the following
>> configuration:
>> -noverify -javaagent:C:/jrebel/jrebel.jar -Drebel.adf_core_plugin=true
>> -Drebel.adf_faces_plugin=true
>> Also, Hot Swap must be turned off when using JRebel.
>> On Mon, Oct 1, 2012 at 3:23 PM, hasim <hsai...@gmail.com> wrote:
>>> I would appreciate , If Andrejus or Florin can post the instruction on
>>> how to configure Jrebel on Jdeveeloper.
>>> It seems companies has to be buy license.
>>> Thanks, Hasim
>>> On Sun, Sep 30, 2012 at 3:27 PM, Florin Marcus <florin.mar...@gmail.com>wrote:
>>>> WLS Hot-Swap is definitely a good way of increasing productivity. This
>>>> is more obvious in the final phases of a project, when the team focuses
>>>> more on bug fixing and small improvements. In these phases, developers tend
>>>> to redeploy more often and redeployments are taking longer because the
>>>> application is fully featured by now . This is not limited to java files,
>>>> but can be used with page definitions as well.
>>>> It is worth mentioning though, class reloading is working as long as
>>>> the class signature is not changed.
>>>> On Sun, Sep 30, 2012 at 8:43 PM, Shay Shmeltzer <
>>>> shay.shmelt...@oracle.com> wrote:
>>>>> In the 11.1.2.* versions we now support hot-swap for ADF
>>>>> applications, which means that you can save-compile-reload in browser for
>>>>> most of your changes without the need for a redeployment.
>>>>> One thing I'm wondering is whether people are using this new
>>>>> capability, and whether they find it useful as a way to reduce
>>>>> re-deployments?
>>>>> Shay
>>>>> On 9/30/12 11:46 AM, Jan Vervecken wrote:
>>>>> Thanks for your reply Andrejus.
>>>>> Indeed "another approach", but not out-of-the-box.
>>>>> regards
>>>>> Jan Vervecken
>>>>> On Sunday, September 30, 2012 7:42:04 PM UTC+2, Andrejus Baranovskis
>>>>> wrote:
>>>>>> Hi Jan,
>>>>>> To use JRebel is not a *workaround* :) I would call it rather
>>>>>> another approach of building ADF applications.
>>>>>> Andrejus
>>>>>> On 30 September 2012 19:37, Jan Vervecken <ver...@gmail.com> wrote:
>>>>>>> Thanks for your reply Florin Marcus.
>>>>>>> Thank you for suggesting another potential workaround to try to
>>>>>>> improve some of the out-of-the-box behaviour.
>>>>>>> regards
>>>>>>> Jan Vervecken
>>>>>>> On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
>>>>>>>> Hi Jan,
>>>>>>>> As a JDeveloper user, if I were to choose between a fast and a
>>>>>>>> slow redeployment, I would choose a third option: no redeployment.
>>>>>>>> We were using for some time WLS Fast Swap, but we are currently
>>>>>>>> evaluating JRebel and after one week of using it, it looks good, so far.
>>>>>>>> I was able to create new view objects, drop them into pages as ADF
>>>>>>>> components, compile and refresh the page, without restarting the
>>>>>>>> application.
>>>>>>>> I must say that the compilation tends to become slower after some
>>>>>>>> time.
>>>>>>>> On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com>wrote:
>>>>>>>>> hi
>>>>>>>>> Given the lack of response, the idea that many JDeveloper users
>>>>>>>>> would prefer to have redeploys work fast out-of-the-box, could be wrong.
>>>>>>>>> It makes me wonder about how easily it is considered normal to
>>>>>>>>> have to apply workarounds, instead of expecting things to work better
>>>>>>>>> out-of-the-box.
>>>>>>>>> regards
>>>>>>>>> Jan Vervecken
>>>>>>>>> On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken
>>>>>>>>> wrote:
>>>>>>>>>> hi
>>>>>>>>>> It seems likely that many JDeveloper users would prefer to have
>>>>>>>>>> redeploys work fast out-of-the-box without having to apply workarounds.
>>>>>>>>>> Workarounds can be applied, but this is about improving the
>>>>>>>>>> out-of-the-box behaviour.
>>>>>>>>>> Not sure if it will make a difference, but if you leave a comment
>>>>>>>>>> in JIRA issue ADFEMG-49 maybe the number of responses can help get this
>>>>>>>>>> fixed.
>>>>>>>>>> many thanks
>>>>>>>>>> Jan Vervecken
>>>>>>>>> --
>>>>>>>>> You received this message because you are subscribed to the ADF
>>>>>>>>> Enterprise Methodology Group (http://groups.google.com/grou** >>>>>>>>> p/adf-methodology <http://groups.google.com/group/adf-methodology>).
>>>>>>>>> To unsubscribe send email to adf-methodolo...@googlegroups.**com
>>>>>>>> --
>>>>>>> You received this message because you are subscribed to the ADF
>>>>>>> Enterprise Methodology Group (http://groups.google.com/** >>>>>>> group/adf-methodology<http://groups.google.com/group/adf-methodology>).
>>>>>>> To unsubscribe send email to adf-methodolo...@**googlegroups.com
>>>>> --
>>>>> You received this message because you are subscribed to the ADF
>>>>> Enterprise Methodology Group (
>>>>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>>>>> email to adf-methodology+unsubscribe@googlegroups.com
>>>>> --
>>>>> You received this message because you are subscribed to the ADF
>>>>> Enterprise Methodology Group (
>>>>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>>>>> email to adf-methodology+unsubscribe@googlegroups.com
>>>> --
>>>> You received this message because you are subscribed to the ADF
>>>> Enterprise Methodology Group (
>>>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>>>> email to adf-methodology+unsubscribe@googlegroups.com
>>> --
>>> You received this message because you are subscribed to the ADF
>>> Enterprise Methodology Group (
>>> http://groups.google.com/group/adf-methodology). To unsubscribe send
>>> email to adf-methodology+unsubscribe@googlegroups.com
As of Weblogic 10.3, a new startup option has been introduced called
“skipWLSModule” scanning. By default, on startup, WLST scans the
weblogic.jar and all of the classes referenced in its manifest classpath.
With this option, files in the modules directory are not scanned. If you
need them, you can manually add them to the classpath.
Another trick is to define a cache directory for scanned files. When WLST
initializes, it scans all the jar files and writes the information to files
in directory called the cachedir. So to reduce WLST startup time, define a
cache directory for WLST to use.
*Oracle awarded eProseed “ Oracle Middleware Partner of the Year“ 3 times
in a row (2010, 2011, 2012) !*
*From:* adf-methodology@googlegroups.com [mailto:
adf-methodology@googlegroups.com] *On Behalf Of *Renan Monteiro de Castro
*Sent:* 11 October 2012 04:26
*To:* adf-methodology@googlegroups.com
*Subject:* Re: [ADF EMG] Re: help to speed up out-of-the-box redeployment
in JDeveloper
Recently, I was experimenting weblogic startup times with different JDK's
and found out that the best time I was able
to reach was around 30 seconds (Core i7 + 4GB) with JDK 1.6.35.
Do you guys get better times? Just for the server instance...
And a note about hot-swap, it does not work with 64-bit JVM's...
On Mon, Oct 1, 2012 at 12:19 PM, hasim <hsai...@gmail.com> wrote:
Sounds Good !, I have to try with Jdeveloper Studio Edition Version
11.1.1.4.0.
Thanks, Hasim
On Mon, Oct 1, 2012 at 10:08 AM, Florin Marcus <florin.mar...@gmail.com>
wrote:
On Mon, Oct 1, 2012 at 3:23 PM, hasim <hsai...@gmail.com> wrote:
I would appreciate , If Andrejus or Florin can post the instruction on how
to configure Jrebel on Jdeveeloper.
It seems companies has to be buy license.
Thanks, Hasim
On Sun, Sep 30, 2012 at 3:27 PM, Florin Marcus <florin.mar...@gmail.com>
wrote:
WLS Hot-Swap is definitely a good way of increasing productivity. This is
more obvious in the final phases of a project, when the team focuses more
on bug fixing and small improvements. In these phases, developers tend to
redeploy more often and redeployments are taking longer because the
application is fully featured by now . This is not limited to java files,
but can be used with page definitions as well.
It is worth mentioning though, class reloading is working as long as the
class signature is not changed.
On Sun, Sep 30, 2012 at 8:43 PM, Shay Shmeltzer <shay.shmelt...@oracle.com>
wrote:
In the 11.1.2.* versions we now support hot-swap for ADF applications,
which means that you can save-compile-reload in browser for most of your
changes without the need for a redeployment.
One thing I'm wondering is whether people are using this new capability,
and whether they find it useful as a way to reduce re-deployments?
Shay
On 9/30/12 11:46 AM, Jan Vervecken wrote:
Thanks for your reply Andrejus.
Indeed "another approach", but not out-of-the-box.
regards
Jan Vervecken
On Sunday, September 30, 2012 7:42:04 PM UTC+2, Andrejus Baranovskis wrote:
Hi Jan,
To use JRebel is not a *workaround* :) I would call it rather another
approach of building ADF applications.
Andrejus
On 30 September 2012 19:37, Jan Vervecken <ver...@gmail.com> wrote:
Thanks for your reply Florin Marcus.
Thank you for suggesting another potential workaround to try to improve
some of the out-of-the-box behaviour.
regards
Jan Vervecken
On Sunday, September 30, 2012 5:34:09 PM UTC+2, Florin Marcus wrote:
Hi Jan,
As a JDeveloper user, if I were to choose between a fast and a slow
redeployment, I would choose a third option: no redeployment.
We were using for some time WLS Fast Swap, but we are currently evaluating
JRebel and after one week of using it, it looks good, so far.
I was able to create new view objects, drop them into pages as ADF
components, compile and refresh the page, without restarting the
application.
I must say that the compilation tends to become slower after some time.
On Sun, Sep 30, 2012 at 3:44 PM, Jan Vervecken <ver...@gmail.com> wrote:
hi
Given the lack of response, the idea that many JDeveloper users would
prefer to have redeploys work fast out-of-the-box, could be wrong.
It makes me wonder about how easily it is considered normal to have to
apply workarounds, instead of expecting things to work better
out-of-the-box.
regards
Jan Vervecken
On Thursday, September 13, 2012 3:52:56 PM UTC+2, Jan Vervecken wrote:
hi
It seems likely that many JDeveloper users would prefer to have redeploys
work fast out-of-the-box without having to apply workarounds.
For this, Oracle has bug/ER 12796317, "SPEED UP ADF BC REDEPLOYMENT BY
CALLING FORCED SHUTDOWN OF WLS DATASOURCE", filed.
Find more details at http://java.net/jira/browse/ADFEMG-49
Workarounds can be applied, but this is about improving the out-of-the-box
behaviour.
Not sure if it will make a difference, but if you leave a comment in JIRA
issue ADFEMG-49 maybe the number of responses can help get this fixed.
many thanks
Jan Vervecken
--
You received this message because you are subscribed to the ADF Enterprise
Methodology Group (http://groups.google.com/group/adf-methodology). To
unsubscribe send email to adf-methodolo...@googlegroups.com
-- You received this message because you are subscribed to the ADF Enterprise
Methodology Group (http://groups.google.com/group/adf-methodology). To
unsubscribe send email to adf-methodolo...@googlegroups.com
-- You received this message because you are subscribed to the ADF Enterprise
Methodology Group (http://groups.google.com/group/adf-methodology). To
unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
-- You received this message because you are subscribed to the ADF Enterprise
Methodology Group (http://groups.google.com/group/adf-methodology). To
unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
-- You received this message because you are subscribed to the ADF Enterprise
Methodology Group (http://groups.google.com/group/adf-methodology). To
unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
-- You received this message because you are subscribed to the ADF Enterprise
Methodology Group (http://groups.google.com/group/adf-methodology). To
unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
-- You received this message because you are subscribed to the ADF Enterprise
Methodology Group (http://groups.google.com/group/adf-methodology). To
unsubscribe send email to adf-methodology+unsubscribe@googlegroups.com
